For those who don’t know the tool: Cinema 4D is Maxon 3D for modeling, animation, sims, and lookdev, with tight Redshift Renderer integration and common handoffs like USD. Think MoGraph, then render, then wonder why lunch is over.

The update in one sentence

Cinema 4D 2026.2.0 comes with new modelling (especially for cloth) and lighting features, plus broad fixes across animation, modelling, MoGraph, simulation, viewport, exchange, and rendering. As well as a load of smaller cool features and updates.

Fabric Brush gets hands-on with soft stuff

The big new feature is Fabric Brush, a modeling tool that uses the app’s simulation system to shape soft materials directly in the viewport. The intent is tactile: push and pull forms while the sim helps create folds, draping, and deformations, without setting up rigs for the job.

In practice, this is a new option for artists who want quick cloth-like sculpting while staying in a familiar modelling workflow. It aims for standard tool responsiveness while adding simulation-driven behaviour for the soft look.

Redshift goes nocturnal

Cinema 4D 2026.2 introduces a night-sky option in the Redshift Sun and Sky system for dusk and night lighting setups. If your scene needs a sky that reads after sunset, this is now a first-class mode inside that system, rather than a workaround of lights and environment tricks.

Cinema 4D 2026.2 ships with Redshift 2026.5.0. Older Redshift versions from 2026.0.0 and higher remain compatible, but they will not include the newer Redshift features, plus enhancements to integration and performance.

Redshift 2026.5.0 also raises a practical requirement: the minimum required version for the 2026 plugin becomes Cinema 4D 2026.2. On the Cinema 4D side, a related integration note calls out Redshift Live replacing Redshift RT.

Deformers, clones, and command lines get small superpowers

A few smaller changes target everyday rigging and motion graphics chores. Bend Deformer improvements add new symmetry origin options, so mirrored bends can come from a single deformer. For quick character tweaks, product flex shots, or anything that wants a symmetric bend without duplicate setups, this is a quality-of-life gain.

A new Xpresso Command Line Argument node allows passing string arguments into Xpresso setups during command line rendering. That is a direct nod to pipeline automation, where renders often start from a farm call, a script, or a build system rather than a human clicking the Viewer.

MoGraph users get a new loop option for the Target Effector, allowing the first and last clones to target each other in closed arrangements. That fits neatly into circular patterns, rings, and repeating layouts where “ends” should not exist.

In the Material Manager, an Active Object Material Filter shows only materials applied to the currently selected objects.

Animation, curves, and viewport comfort

Cinema 4D 2026.2 adds an Align Tangents command to quickly align tangents on F-Curves. If you spend time cleaning curves after mocap, procedural animation, or hand-keyed polish, this is the sort of tiny tool that can save a lot of clicks.

Exchange formats and rendering housekeeping

Cinema 4D 2026.2 includes an exchange crash fix when exporting to Alembic. It also fixes an issue where reimporting a previously exported skeletal animation USD scene could result in an incorrect preview area and scene length even though the export itself was correct.

Rendering and output fixes include preventing multipass images from being saved in viewport render, and a Physical renderer change where Remesh no longer recalculates during rendering. The Picture Viewer gets reduced color banding, and a Redshift-related workflow fix allows creating a render setting from a render to work with Redshift renders.

Redshift 2026.5.0 adds and fixes several Cinema 4D specific items, including a new default native Projection Mode intended to resolve material tag UV tiling incompatibilities with UV Contexts, a fix for UDIMs not rendering correctly when using Team Render, and a fix for random black images when rendering heavy meshes with deformation blur enabled. It also notes a faster connection and smoother navigation for the RS Live Viewport IPR, limited to Cinema 4D 2026.2 and higher.

ARM downloads and driver reality checks

Cinema 4D 2026.2 includes a warning for downloads on ARM: update the GPU driver to the latest version – they even have a link for Windows on Snapdragon users to Qualcomm for the latest drivers.

https://support.maxon.net/hc/en-us/articles/8658038724124-Cinema-4D-2026-2-0-April-15-2026

https://support.maxon.net/hc/en-us/articles/8814051767964-Redshift-2026-5-0-2026-04-April-15-2026

The post Maxon ships Cinema 4D 2026.2 update first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Gaussian Splat Studio brings Gaussian splat point data into Cinema 4D as something you can actually work with, not just stare at. The tool is built to import, view, render, and export Gaussian splats directly inside the host app, while keeping viewport controls and render controls in their own lanes. That separation matters because splats tend to swing between two extremes: either they look great and crawl, or they move fast and look like a snow globe during an earthquake.

The core exchange format here is obviously PLY, the same file type commonly produced by mobile capture and processing services. The workflow shown starts with a real-world capture from a phone or camera, then a reconstruction step in a service such as Polycam, which outputs PLY splat data for the plugin to ingest. The result inside Cinema 4D is a splat object you can navigate around, tweak, and eventually render or export back out again.

Viewport control that admits splats can be ridiculous

Splat scenes vary wildly in scale and density. Different captures can come in at very different sizes (D’uh), so the plugin exposes world scale controls to get a scene into a sane range.

It also acknowledges the other common splat reality: point counts can be enormous. A referenced example uses 12 million points, and the plugin includes options meant to keep navigation responsive. One of the visible tactics is interactive splat reduction in the viewport, where quality deliberately drops while you navigate, then returns when you stop moving. The reduction can be turned off, but it exists specifically to keep the editor usable.

There is also a fast preview mode intended for heavy scenes, letting you switch to lighter display settings for camera setup, animation work, and general layout without changing the underlying splat source. The idea is simple: keep interaction smooth while you work, then restore full settings for final output.

Three looks, one splat

The plugin exposes multiple viewing and rendering looks for splat data. True Gaussian splat mode aims for a scan-faithful result. Point cloud mode is presented as both a stylized look and a faster way to iterate, with circular dot rendering as a deliberate aesthetic option. There is also a proxy geometry view described as a way to see what is happening under the hood, rather than a default look.

Alongside those modes, the plugin provides controls for splat size and for the minimum and maximum pixel radius of splats. The workflow frames these as practical dials for balancing detail versus fill. Smaller splats carry more detail, larger splats help fill larger areas. Push the balance too far and thin features can disappear or areas can open up into holes, so the controls exist to tune a capture into something that holds together under motion and framing changes.

A notey: not every PLY is oriented the same way. When a non-Gaussian splat PLY comes in on the wrong axis, the plugin includes a YZ flip option to correct orientation. That kind of messy reality is exactly what a production tool should deal with. If a format is technically correct but visually wrong, artists still have to ship.

Rendering paths and why the viewport can be the honest one

Gaussian Splat Studio supports rendering through the viewport as well as through Cinema 4D render modes, including Redshift and the Standard and Physical renderers.

The workflow shown treats the viewport render as a useful path for accuracy, while also outlining limitations. Native viewport rendering does not provide an alpha channel, so the tool includes an alpha mode that changes what the viewport output looks like. The result is not a perfectly white matte, and the explanation is that this is expected because semi-transparent values are part of how the splat output should composite more accurately. If a comp pipeline needs a harder matte, the suggestion is to adjust levels in the compositing step.

For Standard and Redshift rendering, the plugin builds what it needs in the background when you enable rendering, including generating a shader setup for the geometry it creates. Enabling rendering is off by default and is making the system a little slower while you work, so it is something you switch on when you actually need those render paths.

Relighting as a dial, not a fight

Splat captures often come with baked lighting characteristics. The workflow shown adds a relight blending control in the Redshift render appearance settings, letting the render transition between a fully luminescent look that preserves the captured lighting and a state that responds more to Redshift lights.

MoGraph-friendly splats are the real headline

Once a splat lives in Cinema 4D as something editable, it becomes available to the same ecosystem of tools artists already use to art direct motion graphics and look development. The plugin supports MoGraph-style controls through Effectors, Forces, and Fields, with a workflow that matches common object setups: select the splat object, add an effector or force, and it registers into the plugin’s control tabs. If you add tools out of order, the workflow shown notes you can drag them in manually.

This is the point where splats stop being a novelty and start being a production asset. If you can isolate, animate, and stylize parts of a capture with the same tools you use everywhere else, splats become another piece of the pipeline rather than a special-case import.

Export, cleanup, and downstream handoff

Gaussian Splat Studio supports exporting results back out as PLY, including exporting cleaned results and exporting as splat PLY.

If your pipeline depends on strict interchange, it is also worth remembering that PLY is a general container format used across different kinds of point data. The workflow explicitly differentiates between Gaussian splat files and regular splat files that can both be PLY, which is why orientation fixes and viewing modes exist in the first place. If you need a reference for the file format itself, the PLY format specification is hosted by Stanford.

Price and platform support

The price for Gaussian Splat Studio is $59.99. The product page lists compatibility for Cinema 4D versions 2024, 2025, and 2026, on Windows and Mac. As always, new tools and innovations should be tested before use in production, especially when they touch rendering, caching, and export handoffs that can ripple through an entire shot.

https://alphapixel.net/products/c4d-gaussian-splat-plugin/

The post Alpha Pixel adds Gaussian Splats to Cinema 4D first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Redshift is a GPU renderer built for fast lookdev and final frames. Vectorworks is a BIM (Building Information Modeling) and CAD hub where buildings get drafted and organised.

Architectural visualisation pipelines love a clean handoff, but they hate the part where you wait for it. Redshift for Archviz positions itself as a single-environment loop: preview inside your BIM tool, iterate while the model still feels editable, then render without rebuilding the whole look in a second app.

The core pitch is direct integration with Vectorworks, aimed at letting artists and designers stay in the same workspace while moving from real-time previews to final renders. The platform targets the usual ArchViz pressure points: quick iterations, look development that stays consistent from draft to final, and visuals that survive client meetings without the dreaded “we will render it later” disclaimer. Maxon describes this as an expansion of the same rendering technology used in its existing ecosystem, tuned for real-world, real-time architecture design workflows

Real-time lighting that behaves like a grown-up

In the feature set, the real-time preview leans hard into lighting, materials, and environment response. The toolset includes controls to change the time of day, sun position, and cloud cover, to show how natural light interacts with the design as you adjust conditions.

Cloud cover control is quite precise, spanning conditions from clear to fully overcast, specifically to visualize how clouds affect natural light, shadows, and the overall mood of an architectural render. That kind of environment knob matters because it ties directly to decision-making. When lighting direction and softness update instantly, material choices stop being theoretical and start becoming compositional tools.

Assets, materials, and the eternal fight against empty rooms

The content side is framed around libraries that help you get to “inhabited space” faster. A growing asset library includes materials, lights, and ready-to-use assets intended to speed up scene building while keeping physical accuracy and visual consistency.

On top of that, the feature descriptions call out drag-and-drop population of interiors and exteriors with a selection that includes furniture, vehicles, realistic plants, and people, and these assets interact naturally with surfaces.

Material coverage is physically correct, spanning concrete and metal through glass, wood, and textiles, with the promise that materials react naturally to light and environment. The workflow emphasis stays on applying, adjusting, and previewing changes in real time, so look development can happen while you are still shaping the design.

Mac and Windows parity, right from the start

Platform coverage is plain: Redshift for Archviz is available for Windows and macOS, andfeature parity across both platforms from the outset. That matters whether you bounce between machines in a studio or your clients do. It also matters if your pipeline includes artists who bring their own gear and do not want a surprise feature gap halfway through a project.

The Cinema 4D escape hatch for the fancy stuff

When a still image turns into a walkthrough, you need more than a preview window. The workflow includes the ability to send a project to Cinema 4D with a simple click, with the intent of enabling more advanced architectural visualisation work, including procedural animations and simulations.

The FAQ describes export from the Redshift for Archviz plugin to Cinema 4D, and states that geometry, materials, cameras, and basic lighting generally transfer well. Once in Cinema 4D, refining scenes, materials, and lighting with a higher level of control is as usual, and then extending the project with animation and simulation.

This is a practical bridge for teams who want the speed of in-app previs but still need a DCC stage for shot craft, camera choreography, or heavier scene management. It also keeps the promise of visual continuity: the same scene, lighting, and materials across preview and final output.

Installation and the beta-shaped reality

The tooling around installation is explicit enough to be useful. The install notes state that the current availability is for Vectorworks, with Revit and Archicad coming soon.

For the Vectorworks side, the guide references installing Vectorworks 2026 using default settings, downloading and signing into the Maxon App, installing an AEC Viewer, then activating the plugin inside the host application by customising the workspace and adding the Redshift entry from the Rendering category. Launch is a Auto Synch button inside the host environment. Use requires creating a MyMaxon account and accepting an EULA. The subscription bundle (Plans and Pricing) supports multiple instances with up to eight GPUs on a single computer.

Because this is new workflow territory, treat early adoption like you treat any new renderer, plugin, or bridge. Run a proper test scene, push the corner cases, and validate the round-trip before you bet a deadline on it. Do that before you put it into production.

What this means for working artists

The practical story is simple: real-time previews inside a BIM host, asset and material libraries geared at architectural scenes, cross-platform support on Windows and macOS, and a pipeline bridge into Cinema 4D for animation and simulation.

If you live in the overlap between design and storytelling, this kind of integration can reduce handoffs and shorten iteration loops. If you live in the overlap between client expectations and physics-based lighting, real-time environment controls can turn “maybe” into “yes” quickly.

Just remember the unglamorous part: new tools and innovations should be tested before use in production, even when the marketing copy sounds like it was written by a very confident sunbeam.

https://www.maxon.net/en/article/maxon-introduces-new-real-time-rendering-and-cinematic-previews-solution-for-architects

The post Maxon ships Redshift for Archviz first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Redshift from Maxon is a GPU renderer for Cinema 4D, Maya, 3ds Max, Houdini and Katana. It targets final-frame GPU rendering and USD Solaris pipelines, sitting at lookdev and lighting in production.

Consolidation, not features

Maxon has released Redshift 2026.3.0. The build includes plugins for Cinema 4D, Maya, 3ds Max, Houdini and Katana. It is a maintenance release focused on stability, host compatibility and incremental displacement updates. No new headline rendering features are introduced.

On Apple hardware, Redshift now requires macOS Sonoma 14 or higher. Maxon recommends macOS Tahoe 26.2 as the latest officially supported version, while noting known rendering artefacts on Intel CPU plus AMD GPU systems on Tahoe. On Windows and Linux, updated NVidia driver minimums apply, including specific requirements for Blackwell 50xx GPUs. Linux requires glibc 2.28 or higher.

Texture displacement cleaned up

Texture displacement receives performance improvements and several correctness fixes. The update resolves holes in meshes, vertical artefacts in the software ray tracer and cases where displacement disappeared on tessellated meshes without UVs.

Support for smooth normals has been added to texture displacement. The UV Context Projection node gains a new camera selection mode for camera projection mapping.

Additional fixes address deformation motion blur with displacement, incorrect auto-bump behaviour, and noisy details on scaled meshes. Material blending issues involving stacking and the Material Blender shader have also been corrected.

Hydra and Solaris updates

Redshift adds support for Houdini 21.0.559 and 21.0.596 and drops support for 20.5.654 and 21.0.440. The Hydra delegate now supports the Solaris 21.0 statistics panel in the latest Houdini 21.0 production build.

Hydra 2.0 fixes include motion blur limitations, primvars sampling issues, light linking problems, nested instancing errors and live updating of custom light and camera parameters. Support has been added for USD implicit surface primitives, USD mesh lights via the Geometry Light LOP, and updated USD and Alembic procedurals. AOV-related bugs affecting ObjectID, Depth, cryptomatte, deep and Refractions Light Groups have been fixed.

Redshift 2026.3 is a stabilisation release aimed at removing pipeline friction introduced in earlier 2026 builds. As always, new tools and innovations should be tested before use in production.

// Redshift 2026.3.0 Release Notes
// https://support.maxon.net/hc/en-us/articles/Redshift-2026-3-0-2026-02-February-10-2026

The post Redshift 2026.3 fixes displacement headaches first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Cinema 4D Scene Nodes are Maxon’s procedural, data driven graph system inside Maxon Cinema 4D. They operate below the Object Manager, enabling direct control of geometry, hierarchies and attributes. Midlet Dufts is a packaged Scene Nodes asset distributed via Gumroad for artists who prefer not to start with an empty graph.

Scene Nodes, Without the Blank Graph

Midlet Dufts is an asset for Cinema 4D built on the Scene Nodes system. Dufts provides a collection of Scene Nodes-based setups intended to simplify procedural scene construction inside Cinema 4D.

Scene Nodes in Cinema 4D represent Maxon’s lower-level procedural architecture. Unlike the legacy Object Manager-based workflow, Scene Nodes operate on a data-centric graph that directly manipulates geometry, attributes, hierarchies and instancing through node operations. The system is powerful but requires a different mental model from traditional C4D workflows.

Midlet positions Dufts as a ready-made solution built on top of this node system, offering artists access to procedural techniques without constructing node graphs from scratch.

What Dufts Actually Provides

Midlets is built entirely using Cinema 4D Scene Nodes. It is not a plugin compiled in C++, nor a compiled extension. Instead, it is a node based asset constructed within Cinema 4D’s own system. This distinction matters. Because Dufts is created inside Scene Nodes, it relies on native functionality provided by Cinema 4D rather than external SDK hooks. In practice, this means the tool integrates as a Scene Nodes asset within the host application.

Context: Cinema 4D Scene Nodes

Cinema 4D Scene Nodes were introduced as part of a broader architectural evolution. They allow artists and TDs to construct procedural hierarchies and geometry using a graph based system. Nodes operate on data streams rather than static objects, enabling more granular control over attributes, instancing and structure.

In contrast to Xpresso, which focuses on parameter linking and expression driven relationships, Scene Nodes operate at a deeper structural level. They can generate and modify entire object hierarchies and geometry procedurally. Scene Nodes also underpin Capsules, which are packaged node graphs exposed through a more conventional object style interface. Capsules can hide graph complexity while providing user facing controls. As with any third party Scene Nodes asset, studios should validate compatibility, inspect the internal graphs, and run stress tests under real project conditions before committing to production use.

// Midlet Dufts official Gumroad page
// https://midlet.gumroad.com/l/dufts

The post Free Scene Nodes for C4D by Midlet Dufts first appeared on DIGITAL PRODUCTION and was written by Bela Beier.