Dear McNeel Development Team,
In Rhino 7, the _GrasshopperPlayer command executes a Grasshopper file’s logic without loading it into the Grasshopper editor (i.e., without creating a new GH_Document). This behavior is ideal for automated workflows, as it avoids unnecessary file loading.
However, in Rhino 8, _GrasshopperPlayer automatically loads the Grasshopper file into the editor. This differs from Rhino 7’s behavior and, for users like me who rely on Rhino 7 workflows, requires additional scripting or manual steps to unload the file, adding complexity.
I propose adding a command-line parameter or setting, such as -NoLoad, to achieve the following:
- Execute the Grasshopper file’s logic when running _GrasshopperPlayer.
- Prevent the file from being loaded into the Grasshopper editor (i.e., no new GH_Document).
This feature would restore Rhino 7’s behavior or provide an option for users to choose whether to load the file into the editor. It would significantly enhance Rhino 8’s flexibility and consistency for automated and scripted workflows.
Use Cases:
- Avoid loading multiple files into the editor during batch processing, reducing resource usage.
- Optimize performance in server or non-UI environments when running Grasshopper scripts.
- Maintain workflow consistency between Rhino 7 and Rhino 8.
Thank you for your hard work! I look forward to this feature’s implementation or related suggestions. I’m happy to provide specific workflow examples or test files if needed.
Signed,
Modeling Enthusiast
