This:
I LOVE the new feature about having curvature graph directly on SubDs , with graphs projected to normal direction! (and whoever did it):
That’s a killer feature that could lead me to buy an upgrade alone.
Sadly it was very bad implemented.
As already said:
but also, the new type of curvature graph on SubD have the “hairs” always normal to surface! That is what we need!
The workaround of extracting edges with history is faster but give a different result. (not projected to normals)
You guys have a pearl there, a gold nugget, a fantastic tool… utterly and completely bad implemented.
On my machine, on Rh7, I can work with a SubD of about 5k faces and curvature graph on some edge extracted with history on. 60fps.
On Rh8, same SubD, curvature graph on the whole SubD kill the performance, to like less than a frame each 3/4 seconds… and the visual is completely clogged by hairs.
Indeed! I need 5-30 edges most of the time! … not 10’000!! The cpu/gpu are working for nothing!
Curvature graph scale is the same value for everything, on some part of the subd (with quads) the U direction would need 105 scale, the V direction would need 130 scale.
Doing every edge together is a bad idea. Absolutely.
Like: “We know how to do it! You can see it! … but we won’t properly implement it…”
..?? WHY?
It’s a killer feature right there!
I paid for 8. Where do I have to pay more to have this working properly?
(Can I access to the method for normal hairs via rhinocommon? c++?)
Please!
…
PS
Having a negative scale, so putting the hairs in the opposite direction, would be extremely useful too. Letting one works from the inside of a SubD.
… and this could/should be a not-too-complex edit in the code … maybe? … hopefully…