Summarizes the API and documentation changes made between Cinema 4D versions 2025.1.0 and 2025.2.0.
For an an overview of the required development environment for this release on Windows, MacOS, or Linux, see Development Environments.
Added | CMake support for the C++ SDK. Among other things, this brings Clang build system support to Windows and removes the Legacy Build System requirement under XCode. See the new Build Systems manual for more information. |
Deprecated | the Project Tool build system generator. All Cinema 4D 2025.2.X releases will support both the Project Tool and CMake as build system generators. After that, Project Tool support will be removed entirely and SDKs will only support CMake. |
Updated | the C++ standard the Cinema 4D SDK is targeting. Under CMake, the Cinema 4D C++ SDK is now targeting C++20, see C++ Standards for more information. |
Updated | and streamlined "Introduction" section and multiple manuals in it. There is a new API Overview manual to help beginners with getting started with the Cinema 4D API. The getting started section has been moved to Quickstart and both the Windows and macOS got a small video tutorial series which guide users from unpacking the SDK to creating their first simple plugin. API Migration manuals have been made their own top level category. |
Added | example.hello_world, an example for a very simple module that implements a command plugin. |
Added | objectdata_assetcontainer.cpp, an example for storing scene elements in a document by adding custom branches to a node, here at the use case of an object internalizing assets it can use. |
Added | example_image_layers_area.cpp, an example for drawing multi images with transparencies on top of each other in a GeUserArea, simulating an image buffer as hosted for example by a render engine. |
Summarizes the technical changes made to the public APIs of Cinema 4D within the scope of these change notes.
The section below lists the differences between the 2025.2.0 and 2025.1.0 as collapsible sections organized in frameworks, files, and changes. The collapsible sections each denote the number of changes they contain in light gray on the right of the section bar. Note that change means here block of change, so 10 consecutive lines which have all been changed count as one change. Click a section bar to expand or close it it, or click the ↧ or ↥ button to expand or close a framework section and all its nested sections. With the ▸ button found on file sections, you can jump to the complete file dif for that file, a ⇲ button will transport you to the matching documentation page of a file or framework.