Due to significant changes in the Redshift core DLLs (Dynamic Link Libraries), an in-app update may leave cruft. Follow this protocol:
This update refines the modeling kernel. Users can expect:
The tile-based bucket rendering reduces out-of-core memory swapping. The hybrid backend shows minimal improvement on single-GPU systems but benefits multi-GPU Mac Studio configurations. The native Redshift camera eliminates the need for a separate Redshift Camera Tag, simplifying animation of depth of field. maxon cinema 4d studio 20242 redshift 3524 upd
However, we observed occasional node-editor freezes with complex Redshift material graphs containing more than 80 nodes — a regression not present in 2024.1.
Redshift has long supported CPU+GPU rendering, but version 3.5.24 finally makes it practical: Due to significant changes in the Redshift core
Before dissecting the features, it is important to understand why this specific pairing is significant. Cinema 4D Studio 2024.2 focuses on core architecture improvements—specifically the “Scene Nodes” framework and viewport performance. Redshift 3.5.24, meanwhile, is a stability-focused renderer update that bridges the gap between CPU and GPU rendering.
Key Insight: Previous versions (2024.0–2024.1) struggled with memory fragmentation when using complex Redshift materials. The 2024.2 / 3.5.24 combo directly addresses heap allocation errors, making large-scale scenes viable on mid-tier GPUs. Key Insight: Previous versions (2024
The 3.5.24 update patches a critical issue where Cryptomatte IDs would "bleed" across motion-blurred frames. If you are integrating into Nuke or Fusion, this update ensures mattes stay crisp even with extreme shutter angles (360-degree shutter).
A major pain point in 3.5.23 was broken light linking when using instances. 3.5.24 resolves: