Possible bug? Stream filter becoming inactive

Hi - I am seeing a repeating bug (?) with a relatively long-running script (~10 seconds). The output can be run via one of two routes and is then brought together using a series of Stream Filters. But often after I re-compute, the stream filters become inactive which prevents the output from flowing through the script. A further recompute brings them back to life.

Could it be related to the amount of geometry that is being generated (meshes on a building scale), the length of time that the script runs, or … something else?

Unfortunately I can’s share the script, or recreate the problem in a simpler one but any ideas appreciated.

All five stream filters are inactive? Have you tried to delete the three lower ones? And delete everything downstream…

Thanks for the reply. Yes, all 5 are inactive. I tried deleting the bottom 3 but it made no difference.

However - I have found another clue. The “True” branch of the filters is connected to a Hops component (essentially the “False” branch runs one local iteration, the “True” branch can run many versions of this in parallel). So whilst I am not using the Hops route at the moment, there is still a Hops component on the canvas. And it seems that the stream filters become inactive when this component talks to the server (even if its inputs aren’t changing).

1 Like