I’m running into an issue where my Panels in Grasshopper don’t seem to output any data when I open my .gh file.
Even though the panels visibly contain text, the wires coming out of them turn orange, and any components connected to them receive no data (as if the panels are empty).
Once I manually edit or retype something inside the panel, the data starts flowing again and the wires turn grey as expected.
This happens when I try to automatically run my Grasshopper definition right after opening it. It seems like the panels don’t initialize their content properly until they’re “touched”.
Has anyone experienced this before or found a reliable way to make panel data persist and output automatically when the file is opened?
I unfortunately can’t add a .gh file as an example since the problem only seems to occur in larger files (my file) and disappears when the file gets smaller. Also, I have used a lot of Tekla Custom Components, which I can’t share due to privacy reasons. Unfortunately, that means I can’t reliably reproduce the issue in a simplified example. I do hope the image attached shows the problem clearly.
Thanks for the suggestion!
Unfortunately, the solver was already enabled, and pressing F5 doesn’t seem to have any effect in this case. The panels still don’t output any data until I manually edit them.
I’ve prepared a version of the script that I can share here — I removed all sensitive parts and only kept the background geometry.
However, the issue no longer occurs in this simplified version. In my full file (which unfortunately I can’t share due to privacy reasons), the panels still lose their data output when opening the file, but in this cleaned-up version everything works fine.
The parts I deleted are the same as the components and panels in this script.
if the problem does not appear in this attached gh file, at least you have almost certainly circumscribed the problem to -at least- one of the components that were deleted
is there any custom component that uses a higher level of Rhinocommon syntax? meaning, not just handling geometries, but expiring solutions and similars? most probably the problem comes from that
you have script components / custom built components, then I would try saving a copy of the gh file after deleting them one by one, until you find the culprit/s
Thanks a lot for the tip — that really helped me narrow it down!
I went through the definition and started deleting parts step by step, testing after each change. Eventually, I found that the issue was caused by several Stream Filter components that weren’t connected to anything (see image).
I’m not entirely sure why those disconnected Stream Filters caused the panels to lose their data output, but after removing them, everything works as expected now.
Thanks again for pointing me in the right direction!
