Redshift 2026.9 Tightens the Bolts

For those who don’t know the tool: Maxon Redshift is Maxon’s production renderer for Cinema 4D, Maya, 3ds Max, Houdini, Katana, Blender and ZBrush. It turns lighting, shading, simulation and scene data into final pixels across NVIDIA, AMD and Apple GPU hardware, with CPU rendering also available. Redshift 2026.9 is chiefly a pipeline and maintenance release: better host support, broader USD handling and fewer opportunities for a renderer to develop personality at 3 a.m.

We saw a small Redshift demonstration at Maxon’s IBC booth over the weekend, which suited this release rather well. Redshift 2026.9 is not a parade of shiny new render tricks. It is a toolbox release aimed at the less glamorous parts of production: host compatibility, scene preparation, USD, memory use, Hydra, colour management and a sizeable collection of fixes. That may be considerably more useful than another checkbox.

Houdini 22 gets through the door

Redshift now supports Houdini 22.0.368 and Solaris 22.0.368, with a USD 26.05 build for Houdini 22’s USD Procedural workflow. For studios moving Solaris pipelines forward, that is the main deployment change. Redshift also adds hair controls to its Hydra viewport settings and fixes several Hydra problems involving instance extraction, shader translation, displacement and error logging. This is pipeline plumbing, but USD pipelines contain quite a lot of plumbing. When Hydra, scene description and the production renderer disagree, artists rapidly become part-time plumbers themselves.

Maya proxies become more useful

Maya gains support for instances of USD and Alembic proxies, plus the ability to use USD proxies with nParticles. That gives heavier scenes another way to keep repeated assets external rather than expanding every copy into native Maya geometry. Alembic remains useful for baked geometry and animation, while USD can carry richer scene structure through a pipeline. Redshift now accommodates more of both without asking the Maya scene to swallow everything whole. The Maya integration also receives fixes around fluids, camera parsing, shaders, RenderView AOVs and custom OpenColorIO configurations on Linux.

Less preparation before the rendering

Maxon says 2026.9 improves render-preparation time while reducing memory consumption during that stage, and the release fixes several memory leaks. Render preparation happens before the renderer starts chewing through samples, so improvements here can affect interactive work as well as batch rendering. Scenes repeatedly opened in IPR, switched between shots or dispatched across many frames all pay some form of preparation cost.

There is no useful universal speed figure because the result depends on scene structure, assets, host and hardware. The production consequence is simpler: less setup overhead and lower memory pressure are welcome wherever scenes are already large enough to make both noticeable.

Several pixels receive corrective action

The renderer itself gets a useful collection of repairs. A problem introduced in 2026.7 could produce artifacts with extensive hex tiling when all textures fitted into GPU memory. Numeric instability at maximum anisotropy values in the Scratches shader has also been corrected, as have problems involving shadow cut-off optimisation with dome and area lights.

RenderView receives its own fixes, including image-position changes when switching scale modes during IPR. None of these warrants a cinematic launch trailer. The artist whose final frame contained the artifact may disagree.

OCIO 2.5.2 joins the pipeline

Redshift now incorporates OpenColorIO 2.5.2. The release corrects a display-profile monitor naming problem, and the 3ds Max integration gains an option to force Redshift OCIO file output while 3ds Max colour management is active. Colour-management updates deserve conservative deployment. Facilities using custom configurations should run known reference scenes through the new build before rolling it across grading-adjacent or finishing-sensitive workflows. Few things create cross-departmental camaraderie faster than discovering that two applications have interpreted the same pixels differently.

Redshift Live closes the gap

Redshift Live adds HDR compression and anisotropy support, while clouds have been adjusted to match production rendering more closely. That last part is perhaps the important direction. Interactive rendering earns its place when artists can trust it as a preview of the final result rather than as a fast but approximate relative.

3ds Max gets better proxy manners

The 3ds Max integration adds control over whether Transform Pivot to Origin occurs before or after a world-space modifier during proxy export. It is an extremely specific option, which is often a sign that somebody, somewhere, had an extremely specific bad afternoon. Pivot handling determines where exported assets expect to live in a scene, so modifier order can matter when proxies travel through a production pipeline. Further fixes cover proxy export during IPR, Hair and Fur settings, unnecessary IPR refreshes, EXR output and viewport behaviour.

A maintenance release with production teeth

The release does add functionality, but its value is distributed across dozens of less photogenic places: current Houdini support, better proxy workflows, leaner preparation, improved Hydra behaviour, refreshed colour management and fewer renderer bugs waiting behind unusual scene combinations.

Our brief look at Redshift at IBC reinforced that impression. The renderer already has plenty of features to put on large screens. This update spends more effort on making the machinery behind those screens behave. Renderers rarely become beloved because somebody fixed a memory leak. Render departments, however, have been known to send flowers.

Studios should test Redshift 2026.9 on representative production scenes, custom OCIO configurations, proxy assets and target hardware before deploying it across an active pipeline.