generative modeling for Rhino
I have a more general question that I see happening quite often in larger more complex definitions and kept me thinking for quite some time now. In my mind grasshopper works in a downstream manner (except for plugins like hoopsnake or the Galapagos engine).
When we consider the following model:
Slider 1-> Component A -> Component B
Slider 2 connects to B ---------------^
Component A takes a long time to calculate, displays via preview.
Component B is faster, no waiting here. Also displays via preview.
When I change slider 1 I expect waiting for a while before everything is calculated since A changes. When I change slider 2 I also have to wait very long... This is not what I expected since it does not affect component A.
This is an extremely simplified version, the situation I run into are a lot more complex but basically deal with the same principle.
Anyone got an idea why this is happening.
your expectation is correct, when you change Slider 2 it should only affect Component B. Are you using the Profiler to test for time? Could it be that a lot of time is spend meshing preview geometry?
No. When you modify Slider 2, it will expire the input parameter of Component B where the slider connects, the component itself and all output parameters of the component. If anything is connected to those output parameter that will be expired too.
You can test this by disabling the solver (the padlock icon on the toolbar) and switching on Fancy Wires. If you drag the slider all the wires that connect expired elements will turn orange, the other will remain grey.
Most of the time I'm previewing just points... I expected that to be the simplest type of "geometry" to display.
I usually have the profiler on but switching it off doesn't have that much effect on speed.
"I usually have the profiler on but switching it off doesn't have that much effect on speed."
It wouldn't. In fact, the Profiler won't make any difference at all on the performance, it will only slow down the frames-per-second performance of the display. I was just interested to see how long the Profiler though each component ought to take and how long an actual solution took.
Points and curves (and boxes, breps, surfaces as well if Shading is switched off) will not delay a solution. They will only slow down the viewport display speed.
You would know best