peship

I think i know very well what you mean.
I noticed that long time ago when messing with the pre-release H8.
I am pretty sure i reported it to one of the developers.
In fact the problem is not only with the wire solver, but in sop too - there are cases where the normals flip unpredictably.
Never checked again if it was fixed.

Usually i create a rampCOP, then assign attribute values read from it according to point's UV coordinates. Then pipe this information in VEX/VOPS.
Or maybe you have something else in mind.

But yeah, ramp function/VOP will be nice.

Thanks.

I left the static solver in the scene, because it is from a more complex setup where it's needed.
I am wondering, is that some sort of bug, or the order of the nodes in this case matters ( opposite to what the help claims ) ?
I clearly see now why some of my previous tests didn't work. They were little chaotic and i didn't notice the pattern that if i have a static solver somewhere at the end of the networks the things get funky.

Once again - thanks for the feedback.