algorithmic modeling for Rhino
Hello everyone,
I've found that giving different radius to a group of points for "cloud display" component produces odd results in the display of this cloud, and makes the computer slower (a lot more). I've found this problems in several computers, so I'm guessing it is not because graphic cards o config. Not only boundaries don't look blurry, but radius size does not apply, looks like it just gets the higher one...
In example attached, I use random component to create different sizes.
Thoughts?
Tags:
Hi Diego,
this is an unfortunately side effect of an optimization which is not possible when using different radii. I can pump a whole list of sprites to the video card (where they will get correctly depth-sorted and then drawn ultra-quick) as long as they have the same radius. However for different radii I have to send these sprites one by one, resulting in no depth-sorting (and thus ugly edges) and a horrible drop in speed.
This is something we can tune up in the Rhino display, but until we do there's no way to get rid of the display artifacts and the poor performance.
--
David Rutten
david@mcneel.com
Welcome to
Grasshopper
© 2025 Created by Scott Davidson.
Powered by