If hasPluginPath(content, _PLUGINPATH) or hasPluginPath(content, _PLUGINPATHUNC): If data = "(-C,bool)":įor idx, content in enumerate(data): With codecs.open(pluginsJsonPath, "r+", "utf-8-sig") as f:įor data in j: # the plugins.json file is stored as "UTF-8 with BOM", so regular open() will not open it correctly and json.load will fail PluginsJsonPath = os.path.join(maxon, userDir, "plugins.json") Maxon = os.path.join(userAppData, "MAXON") "dataType": "(-C,bool)",ĭef hasPluginPath(content, pathToCheckFor): # not exist until a path is manually added in the application) # The contents of a brand new definition file with out path already in it (by default the plugins.json file does # A JSON block that contains a path definition _PLUGINPATHUNC = "//SERVER/FOLDER/R20/plugins" # instead, so for each UNC path there are two possible ways they may be stored as # C4D can use UNC paths, but the next time they are changed within the app, they are stored as path + authoritypath If you’re interested, I’ve put the script on Github. Instead I decided to write a small Python script, since this is plain JSON and easy to parse. But this will remove any custom setting that user may have made.
You can of course pre-create a plugins.json file and just copy it over the existing (or non-existing-yet) one per user-login. Which also means it’s tricky to centrally manage the setting for all users in a domain. This means it stores the setting per-User. Multi-User EnvironmentsĬinema store the plugin paths in a file called plugins.json, located in the AppData folders.
But since you can combine multiple plugin folder paths, this is not a big issue.
#Cinema 4d r20 install
Unfortunately those you will still have to install in your local plugin folder (e.g.
#Cinema 4d r20 license
These licenses are stored in your workstation’s registry and are thus independent from the plugin folder location.Ī problem occurs when you are dealing with plugins that require license files.
#Cinema 4d r20 serial
Using a shared folder works great for plugins that do not require a license to begin with or those that use the licensing system provided by Cinema itself (via its serial number). However, the big thing here (at least for me) is: the Search Paths also support UNC paths! Which means you can set up a shared network folder and have all your Cinema 4D R20 installations point to this folder and magically manage all your plugins through a single folder. Luckily you can still create your own Cinema 4D R20/plugins if you are so inclined. This works fine if you are the only person working on your Workstation. Instead you are told to use your AppData plugin folder instead. The latter does not exist any more by default. Previously you had you AppData plugin path and the system-wide plugin path in the Cinema 4D Rxx/plugins folder. One of the lesser talked about features is the ability to set up multiple Plugin Search Paths. Maxon has released Release 20 of Cinema 4D and it comes with a bunch of new features (amongst them plugin breaking API changes, which is a bit of a bummer, but it needed to be done…).
0 kommentar(er)
