Plugins
Plugins are auxiliary modules that extend the function range of a program. In Cinema 4D, plugins are able, for example, to automate particular functions, to make new tools available (perhaps for modeling or animation), to add new import and export filters or to add new shaders.
Plugins can be created in many different ways. SDKs (Software Development Kits) are available in the following languages:
- Python script languages
- C++
Information and support can be found exclusively at http://developers.maxon.net
We give as much support as possible to all vendors and developers of plugins — however, if a problem should arise with one of these products, please contact the manufacturer of the plugin directly. Please understand that can give no information on, or provide technical support for, products from other manufacturers.
As already mentioned, plugins can solve many diverse tasks and therefore, after installation, your new plugin may appear in different places within the Cinema 4D menu structure. Please always consult the vendor’s documentation that was supplied with your plugin. If there is no special information to be found in the help, a plugin will usually be found on the
menu.This command gives you a quick way to call the last plugin used, especially if you assign a shortcut to this command using the Command manager.
With these commands, existing Python plugins, respectively, can be reloaded (from the corresponding directories). Hence, if you have made a modification to the plugin’s source code, the plugin can be reloaded without having to restart Cinema 4D.
This command is important if you want to buy a third-party plug-in.
Calling up this command will create a ExportedLicensingOverview.json file in your documents folder (Cinema 4D will automatically open the Explorer/Finder at this location).
This file contains information about your Cinema 4D licenses in conjunction with your user account (these files are secure and cannot be used by third-parties).
Using this information, plug-in developers can connect their plug-ins with your licenses and ascertain for which and how many products the plug-in can be made available.
This file should be sent to the plug-in developer when purchasing a plug-in.
This is, of course, only necessary if the plug-in developer licenses their products accordingly. This is not the case for independent plug-in developers.
Displays a list of any plugins that have been installed.