Hi,
I am working on a Rhino plugin that uses grasshopper scripts as commands. I have published the RHP/RUI/YAK file using the script editor but the results seem to vary based on the machine I use. On 3 PCs I’ve tested it works fine, but 1 usually fails and gives the error when it comes to bake the geometry and create the blocks that it will bake an invalid geometry, this also coincides with the preview geometry showing elements oriented incorrectly.
If you choose to bake an invalid object then Rhino creates an empty block with no geometry inside. Is there anything I can do fix this instability?
I would check to see if the document unit tolerance is the same between the machines, depending on the processes in your GH code this can influence if the script produces bad objects.
In my own GH based plugin I use a launch Python script to set the document tolerance (and other items) before running my GH based code.
Thanks for the quick reply. The document tolerances were all set the same so it didn’t affect the results in this case, it’s good to keep that in mind however.
We’ve found that if you open Grasshopper, close it, then drop the YAK file on the Rhino window then it installs correctly and works.
I am simply dropping the YAK file and RUI on the Rhino viewport to install it, this is for the purposes of testing so that the RHP and RUI can be uploaded to Food4Rhino. So yes, users would use PackageManager to install the tool in Rhino.
Hi James, you can include the RUI in the YAK file for a single drag and drop install.
The YAK file is actually a ZIP file. If you rename it to a ZIP, you can open it and drop the RUI file in, then rename back to YAK.
To save time doing the renames I’ve associated .YAK files to a 3rd party ZIP utility that allows a double click auto open so I can just drag in the RUI file.
