Components that trigger recompute after layer visibility change?

I’m hunting down components that might trigger a recompute of my script after I change a layer’s visibility. The layer I’m toggling on or off is not in use and shouldn’t affect my script either way. I have already checked all Model Object and Model Layer components, which have a visibility output and hid those. I don’t use any visibility outputs here.


Normally Grasshopper shouldn’t be recomputing the script on a visibility change, so I’m not quite sure which other components I may need to check. As I said, I don’t use any components that check for layer visibility only some Custom Preview and related components from Human. After disabling all of those, the problem still persists, however.

The Query Model Objects component is the problem. The component needs an option what kind of changes should cause a recompute.

There are a few topics about this already.

Query Model Objects lag - Grasshopper - McNeel Forum

@Japhy any news on this?

1 Like

Ah, makes sense. I only have one of those in this script all the way at the start. In another I have multiple and it blinks way more when toggling layers or doing something that triggers a recompute (a bake).

Since it is all the way at the start, it causes recomputation on everything downstream.

Hi Martin,

No news, this will be a Rhino 9 feature first, then backported if possible.

1 Like

I moved to Rhino 9 WIP a while ago and have not used Rhino 8 for weeks…

Same, but be wary that offsets in GH may add extra segments for now in R9 WIP.

What’s the problem with extra segments?

1 Like