Modernizing and Moving Forward

As we shared last year, we’ve been working hard behind the scenes to transition Cinema 4D to a new, modern core architecture.

In order to move forward, it’s sometimes going to be necessary to streamline some aspects of Cinema 4D. We’ll be discontinuing support for some “legacy” features that would be difficult to maintain or simply don’t make sense as we modernize. Rest assured, we don’t take any of these decisions lightly and will do everything we can to both ensure that better alternatives exist and you’ve got time to prepare.

Features that will be trimmed in late 2018 with the launch of Release 20:



C.O.F.F.E.E.

Cinema 4D’s first and native scripting language launched a vibrant developer community, but Cinema 4D’s robust Python API now provides a much better industry-standard alternative. Cinema 4D’s Python API is much more extensive and the common language makes it easy to integrate scripts from other applications. C.O.F.F.E.E. scripts, tags, nodes, and effectors will no longer be available in Release 20, but Python alternatives exist in all cases.

.c4d importer for R4 - R11.5

We’ve always worked hard to ensure Cinema 4D is both forwards and backwards compatible, but Release 12 marked major changes to Cinema 4D’s internal data structures. As we move towards the next major change, we have to remove the option to import files from versions earlier than R12.

Cinema 4D XML Format

This XML-based file format was one of MAXON’s first attempts to make it possible to easily exchange data with other apps. Since then we’ve introduced the Melange library, which allows third-party developers like Adobe, Archicad, Vectorworks, Ventuz, VizRT, AMD, Speedtree, and more to read, write and render Cinema 4D files natively.

Bridge to Okino Polytrans

Okino Polytrans offers fantastic conversion between 3D and CAD formats, and we jointly developed a bridge that made that conversion possible from within Cinema 4D. Since then Okino has added direct support for .c4d files via Melange, and this direct exchange within their app offers higher-quality results.

Cineman

This export to RenderMan / RIB is no longer compatible with current RenderMan versions.

Softimage - BodyPaint 3D exchange plugin

This plugin has become obsolete due to Autodesk’s discontinuation of Softimage in 2014.

c4d_preview Third-Party API

This specific API was used for BodyPaint bitmap filters that are not compatible with the media classes introduced in Release 19.  


Our goal is always to maintain Cinema 4D’s legendary ease of use and stability, while improving your capabilities and workflow so you can achieve your creative visions. Leaving these legacy elements behind enables our development team to focus on future development, deliver innovative new features and enhance Cinema 4D in general.

 


Karsten Jancke

Director of Engineering

 

About the MAXON Blog

Welcome to the official MAXON Blog. This blog provides the most up-to-date official information about MAXON, its products – in particular its flagship product Cinema 4D – and the Cinema 4D community. You can expect to see posts from a wide variety of MAXON employees.

Feel free to send us feedback via email to blog(at)maxon(dot)net.

While we’re here to provide insight and information on all things Cinema 4D, this blog is not a support forum. If you have a customer service or technical support issue, please contact our technical support team or your local MAXON customer service: