Over the last years we were working on new core technology for Cinema 4D. This new technology will also be available to third party developers in the form of new and extended API.
To make the transition as smooth as possible, we have introduced the first elements of this new API in the latest releases. With Cinema 4D R20 much more of the new API will be published. This will allow us and third party developers the development of faster, more stable and future-proof software.
To introduce this new API, compatability with older plug-ins needs to be capped. Existing C++ plugins that were build with previous versions of the SDK (R19 or earlier) will not work in Cinema 4D R20. Such plugins will simply not be binary compatible.
To adapt an existing plugin for R20 it is at least necessary to recompile it using the R20 SDK. Additionally there may be code changes necessary. The number of such changes required depends among other things on the code base being already adapted to the API changes of the previous years.
We will provide an extensive documentation and examples on the new API elements as well as information on how to adapt existing plugins. These resources will be available for all developers for free with the release of Cinema 4D R20.
The Python API will not be affected by these changes. Existing Python plugins and scripts will also work in R20.
In contrast, the C.O.F.F.E.E. programming language will be removed starting with Cinema 4D R20. So all C.O.F.F.E.E. plugins and scripts will no longer work in R20.
To stay informed on changes in the SDK you can subscribe to the MAXON Registered Developer program.