Hi all,
I’ve been chasing this issue with Grasshopper Player that was way slower running some complex analysis compared to running the same definition from Grasshopper. As far as I can tell, “Get Geometry” forces the definition to compute the solution twice when run from Grasshopper Player compared to running it from Grasshopper.
The Rhino file just contains a box. GHPTest.gh has the issue and computes the solution twice:
Rhino was unresponsive for ~12 seconds while it computed the solution twice.
GHPTest2.gh adds a Get Boolean component after the Get Geometry component. A Pick’n’Choose component prevents the slow PopGeo component from running until you give it the boolean value in Rhino. With this setup, the solution is twice as fast, and the “solution completed in” dialog only shows up once.
This might be helpful for users in the future. Add a Get Boolean to gate data before running slow functions in Grasshopper Player. No clue on what is causing this. Feels a bit like how buttons in Grasshopper can accidently run a solution twice by sending two state changes, one on click down and one on click up (Pancake’s True Only button being the fix for that one).
I found some threads with issues of prompts being displayed twice in Rhino from Grasshopper Player. Or Python issues. But nothing seems to address this specifically. Looks like @kike was involved in some of those threads if that helps the right people see this.
20260105_GHP_Box_Test.3dm (46.8 KB)
20260105_GHPTest2.gh (6.2 KB)
20260105_GHPTest.gh (5.8 KB)