Corona Materials in Cinema 4D — Complete Conversion Guide

Corona in 3ds Max vs Corona in Cinema 4D

Corona for Cinema 4D is a native port of the same renderer you know from 3ds Max. Chaos Group develops both versions in parallel, and the material types are nearly identical: CoronaPhysicalMtl, CoronaBitmap, CoronaColorCorrect, CoronaMixMtl, CoronaLayeredMtl — they all exist in both versions with the same properties and the same rendering behavior.

The challenge isn't the renderer — it's getting the materials from one host application to the other. There is no built-in way to transfer Corona materials between 3ds Max and Cinema 4D. The .max file format is proprietary to Autodesk and can only be read by 3ds Max itself. FBX export doesn't help either — FBX has no concept of Corona material types, so every CoronaPhysicalMtl, every CoronaBitmap, every node connection is stripped during export.

This means that moving a Corona scene from 3ds Max to Cinema 4D has traditionally required rebuilding every material from scratch — referencing screenshots of the original Max scene, manually recreating node graphs, relinking bitmaps, and guessing parameter values. For a production archviz scene with 200+ materials, this can take days. MAX2C4D eliminates that process entirely by reading the Corona material data directly from the .max scene and rebuilding it as native Corona for C4D materials.

Which Corona Material Types Transfer

MAX2C4D supports the full range of Corona material types. Every material is mapped to its exact Corona for C4D counterpart — not an approximation, not a fallback, but the same material type with the same properties.

All material types are converted with their complete property sets. CoronaPhysicalMtl alone carries base color, roughness, metalness, IOR, anisotropy, SSS, clearcoat, thin film, volumetrics, and emission — every one of these properties transfers to Cinema 4D.

Node Graph Preservation

This is the key differentiator. MAX2C4D doesn't approximate materials — it rebuilds the complete node graph. If a CoronaBitmap feeds into CoronaColorCorrect, which feeds into the roughness slot of a CoronaPhysicalMtl, that exact chain is recreated in Cinema 4D. Every connection, every parameter value, every bitmap with its tiling, offset, rotation, and gamma settings.

The importer walks each material's shader tree recursively. When it encounters a node, it creates the corresponding Corona for C4D shader, copies every property value, and wires it into the same slot on the parent node. The result is an identical node graph — same topology, same values, same visual result.

This matters because real-world Corona materials are rarely simple. A typical archviz material might chain a CoronaBitmap through CoronaColorCorrect for brightness adjustment, then through CoronaTriplanar for projection, then into a CoronaMixMtl that blends it with another material based on a CoronaAO mask. That entire chain — sometimes 5 to 10 nodes deep — transfers intact.

Supported Shader Nodes (80+)

Corona materials panel in Cinema 4D after conversion

Node graph preserved — every connection intact

Common Archviz Material Setups

These are real-world material configurations that appear in nearly every archviz project. Each one converts 1:1 from 3ds Max to Cinema 4D — same node structure, same parameter values, same render result.

What About Non-Corona Shaders?

Real-world 3ds Max scenes often mix Corona-specific shaders with built-in Max texture maps. Some of these have direct equivalents in Corona for C4D — others require creative mapping or fall outside conversion scope entirely.

Before & After: Corona Interior Scene

3ds Max (Original)

Cinema 4D (via MAX2C4D)

Same scene, same materials, same lighting. The Cinema 4D render uses exclusively the converted Corona materials — no manual adjustments were made after import.

Related Guides

Frequently Asked Questions