What’s the best method to transfer those across? Eventually I’ll be using PDQ to deploy that to other users, but for now I am just testing on one machine by copying and pasting.
The Grid settings are document properties, not global options, so they won’t transfer over via the settings folder. You would need to modify the default templates with the desired grid settings and copy those over to the new installs.
Not sure about the File explorer settings, what did not transfer over?
So if I’m understanding you correctly, anything that falls within the ‘Document properties’ will need to be adjusted in the main template file?
To answer your question regarding the file explorer, I have it pointing to a specific file path, but that seems to come up blank when deployed on another machine.
Document Properties are just that - properties of the document, they belong to the document and can be different for every file. The supplied templates are just a set of standard Rhino files with default properties - units, tolerances, layers, etc. They can be freely modified and re-saved, or, better, you can create and save your own custom templates with whatever settings you like.
It turns out that the settings on that page are written to the settings-Scheme__Default.xml file of the RDK plug-in.
You can find that file in the following folder:
%AppData%\McNeel\Rhinoceros\8.0\Plug-ins\Renderer Development Kit (16592d58-4a2f-401d-bf5e-3b87741c1b1b)\settings
I am encountering an issue where I want to be able to allow users to create customisation if they want to to their interface, however I still want to be able to deploy updates to the template files and settings files. Is there a way where I can deploy only additional changes rather than wipe what they had created?
a. If you have custom template files, those should be saved by a different name than the original they are based on. Those can be stored in a location that the users in your organization have access to.
The settings file will then point to that path and file. Updating that template file then doesn’t require pushing any changes to the settings on the machines of the users.
b. Allowing your users to only customize certain settings is not possible. To be able to control only certain settings while allowing customization of other settings would require a system that replaces only specific parts of the .xml file. That sounds scriptable…
-wim
Thanks Wim. I am wondering if there’s a way to map the template folder location to a network drive? It doesn’t seem to be allowing me. For context, it shows that the Network drive can be expanded to show the subfolders, but the moment I click on the ‘Network’ drive, the expandable disappears and doesn’t show any subfolders.
