Is it possible to have finer grain control over primitives in a wrangler with a dot product; considering a add node is responsible for controlling the dot product ?

If you supplied a small example, this would be a lot easier to understand.

-b

I'm wondering if I'm using this right by using the function RayHitTest to hit a primitive if it's strictly parallel to a point ?

As bonsak suggested…maybe you could upload a hip so we can see what your doing?

This was the help I was given on a particular issue.
Embedded in the code are questions. Instead of posting the HIP file I want to understand the theory

Christopher R
Why does one target attribute have “@” and the other doesn't ?
…
Shouldn't @facing be declaired as a vector or float

1. @target is referencing an attribute called “target” that lives on your geo, whereas the other “target” is a variable from line 1 that only lives inside this VEX code. Attributes require “@” notation, variables do not.

2. @facing is an integer because you're using ceil() to raise the result of the dot product to the next whole number. A dot product returns a float from -1 to 1, so ceil(dot()) will return either 0 or 1, depending on whether the aim vector is aiming more or less than 90 degrees away from the Normal vector.

EDIT: Although, since you're not declaring a type when creating @facing, it is defaulting to float, so actually it's a float value of either 0.0 or 1.0

VFXLife
@target is referencing an attribute called “target” that lives on your geo, whereas the other “target” is a variable from line 1 that only lives inside this VEX code. Attributes require “@” notation, variables do not.

“target” lives on my geo ? As in it's always available ?

if

vector target = {0,0,0};

is in a vex code “window” it's always available within that window, but only there.

v@target = {0,0,0};

is available both within the vex “window” and outside it, alhtough it now must be prefaced with the @ symbol and possibly additional code depending on where your using it.

For all intents and purposes you can consider target a variable which ever way you create it.

That helps
Is there a float alternative to the function findAttributeCount ?

That wouldn't make sense. The number of elements with a certain value should never be a float. “2.7286 number elements has the value N”. Get it?

-b

I understand, but I'm getting the results I want to a degree when adjusting the ramp that previously I wasn't all because I removed the ceiling function. I can't figure out how to fix this without re-inserting the ceiling function ?