Redshift 2027: More VRAM, Less Waiting

Redshift 2027 revamps GPU memory handling, speeds interactive feedback, adds procedural fur and expands DCC support, with launch-day fixes.
A row of wine glasses on a glossy outdoor table, including clear, amber, and pink-filled stems arranged across the foreground and midground. Soft daylight reflects off the glass and smooth surface, with a blurred dark background that gives the scene a calm, elegant look.

For those who don’t know the tool: Redshift is Maxon’s production renderer, integrated with Cinema 4D and other DCC applications for look development, lighting and final-frame rendering. Version 2027.0 changes how the renderer handles memory, preview feedback and geometry-heavy surface detail.

Redshift 2027.0 cares less about dramatic shader balls than about the machinery that renders them. (That sentence felt like it needed an adjective. I know Shader balls aren’t dramatic.) Maxon has revised GPU memory management, accelerated interactive feedback in Cinema 4D and added a render-time fur system.

The rest of the release stretches from Maya cameras and Solaris viewports to USD command-line rendering and architectural tools. It is a sizeable change list, and the accompanying 2027.0.1 update is rather important. The other Maxon releases are covered in our Maxon 2027.0 overview.

VRAM learns to share

The revised GPU memory architecture changes allocation, resource sharing with other GPU-accelerated software and support for unified-memory systems. Instead of loading the same scene onto one GPU after another, Redshift can load scenes across several GPUs in parallel. The practical target is workstations where complex texture sets, geometry, caches and other GPU users compete for available memory. Maxon identifies multi-GPU and high-memory configurations as likely beneficiaries, but gives no universal speedup or percentage reduction in memory use. The upgrade does not create more physical VRAM, regrettably.

The 2027.0.1 fixes are relevant to this headline feature: 2027.0.0 could retain VRAM allocations after a render finished, or impose an artificially low available-memory limit even after a competing GPU process had closed. The latter had required restarting the DCC. Both bugs are listed as fixed in 2027.0.1, alongside a render-stall issue. Studios assessing memory improvements should therefore test 2027.0.1 rather than the initial build. Quick work, folks!

https://maxonassets.imgix.net/images/Products/Redshift/Redshift_Live.jpeg?fm=webp&auto=format%2Ccompress&w=1920&h=1080&ar=16%3A9&fit=clip&crop=faces&q=80

Cinema 4D: less waiting, more control

Maxon reports faster time to first pixel, shorter turnaround after scene edits and more responsive viewport interactive progressive rendering (IPR). Redshift Live also compiles shaders faster and now supports refraction, transparent shadows, area-light spread and ray-traced depth of field. These additions improve what you can judge during lighting and material development before switching to Production rendering. They don’t mean every Production feature is available in Live.

https://maxonassets.imgix.net/images/Products/Redshift/Streamlined_cinema4D_workflows.jpg?fm=webp&auto=format%2Ccompress&w=1920&h=1080&ar=16%3A9&fit=clip&crop=faces&q=80

Material Tags gain Redshift-specific options for Triplanar Mapping, Hex Tiling and advanced material settings. Dome Lights provide a Browse tab for finding HDRIs. Vertex Map and Vertex Color tags can be dragged into material setups to create the appropriate nodes, and Maxon has refined OpenColorIO handling. A Redshift Camera can focus automatically at the viewport centre. It is the kind of workflow work that may save only a few clicks at a time, which is why artists who repeat those clicks all day will notice.

Cinema 4D 2027 also receives updated material preview scenes, improved preview scaling and a Monitor Profile checkbox enabled by default. Redshift Live displays rendering status in the status bar, while RenderView remembers the locked camera per document. Fixes cover Live/viewport IPR snapshots in Cinema 4D 2026.3 and later, copying Picture Viewer snapshots in the correct colour space, material stacking with mixed UVW/procedural projections, UV Context nodes in stacked materials and resuming viewport IPR after bucket rendering with IPC. One detail for technical directors: Redshift’s Smart Bake documentation specifies Square Tiling only; Hex Tiling is ignored by Smart Bake. A new control is not a waiver of an older constraint, and some stuff is still Hexed, or as least as long until Disney drops that IP. And yes, that was a very random joke.

Fur: from surface to strand at render time

The new Redshift Fur procedural generates fur, fine fuzz, fibers and textile-like structures over a source mesh at render time. It avoids the need to store each strand as a separately modelled asset, and supports motion blur, instancing, UV-driven controls and materials. It is suited to upholstery, carpets, footwear, animal coats and woven or knitted surface effects. A suspiciously well-groomed creature is optional. If you want to have your selfmade avatar perfectly beared, it is an excellent tool for that. I’m not going to show my work.

The Fur controls include source-object selection, surface offset along the mesh normals, strand density per unit surface area, length, thickness measured as radius, tip taper, bend, curl and gravity. Automatic curve segmentation adjusts strand subdivisions for bend and curl; artists can disable it and set the curve-segment count manually. More subdivisions improve smooth curvature but increase render cost, particularly on dense surfaces. Density varies with actual mesh area, rather than simply placing an identical strand count on objects of different sizes.

A blue plush teddy bear with a yellow bow sits in a 3D modeling viewport, its fuzzy texture and round limbs rendered against a gray studio-style background. Interface panels and material controls frame the scene, with soft lighting casting a long shadow across the floor.

Variation controls cover density and its patch scale, individual strand length and thickness, growth direction, bend and curl. Texture maps can multiply surface offset, density, length, thickness, bend, curl and gravity. Separate colour maps steer comb direction and bend direction relative to the source mesh’s U tangent, V bitangent and normal; a neutral comb-direction colour is (0.5, 0.5, 1). Texture-driven controls require UV coordinates. Material shading can combine ordinary textures, Principled Hair and Hair Random Colour, allowing a patterned textile or coat to have more than one colour without painting thousands of strands by hand.

The documented Houdini Fur implementation can instance a source Fur object to save memory when repeating it. Its distance-based level of detail (LOD) mode reduces strand count farther from the camera while increasing thickness to maintain apparent coverage, with Start Distance and Distant Quality controls. In that implementation, LOD requires instancing to be disabled. Camera movement and aggressive distant quality settings deserve testing: bald patches are a poor substitute for optimisation. Maya documentation also notes that Fur is not previewed directly in the Maya viewport, so the Redshift render remains the relevant feedback path.

More hosts, more pipeline plumbing

In Maya, a dedicated Redshift Camera exposes Optical settings, Color Correction, Lens Effects and Background handling. Redshift lights integrate with Maya’s native Light Editor. Fixes in 2027.0.0 address face-level material assignments that did not refresh an active render and deformation-motion-blur tangents. For 3ds Max, the technical notes list tyFlow Inferno integration and a new Redshift tyFlow modifier for shading tyFlow volumes.

Houdini 22 support begins with build 22.0.429 in Redshift 2027.0.0. Version 2027.0.1 adds Houdini 22.0.459 and discontinues the 21.0.700 build. The new Redshift Lister tool helps manage scene objects, and Fur procedural support is available in Houdini. The Vulkan viewport IPR no longer offers WireOver because it is incompatible with that viewport path. Redshift also fixes the RenderView colour-inspection tool invoked using Ctrl and, in 2027.0.1, a Shader-tab submenu issue in Houdini 22.0. Matching the exact Houdini and Redshift plugin builds still matters; Maxon’s compatibility matrix records the supported combinations.

The Hydra/Solaris integration also adds Houdini/Solaris 22 builds 22.0.429 and then 22.0.459, multiple simultaneous rendered viewports and the Redshift Fur procedural. Fixes cover camera post-effects flare parameters, instance light linking and rendering nested instancer prototypes. USD command-line rendering now interprets Start and End frame settings as absolute frame numbers rather than offsets from the sequence start.

It can also use the stage’s default render settings identified by root-layer metadata and time-sampled camera shutter-open/shutter-close attributes. Those changes are particularly pertinent to render-farm and USD interchange workflows, where an incorrect frame range or shutter value is rarely funny. For the artist. Art directors find that shit hilarious.

A 3D architectural rendering shows a modern white two-story house with large glass panels, wood siding on one side, and a slanted roof, set on a vivid green lawn under a partly cloudy blue sky. The scene is displayed inside a design interface with soft daylight and adjustable environment controls.

Architectural rendering and hardware

Redshift for Architects adds a native Graphisoft Archicad integration, allowing preview and production rendering within the host rather than relying on a separate export loop. The architecture tools gain a light palette, a light manager, descriptions in the Attribute Manager, light indicators in the viewport and a gizmo overlay for selecting or toggling lights. Viewport settings now expose refraction depth and a depth-of-field method. Scatter exclusion performance improves, while corrections address scatter editing with multiple selections and instance placement in metre-based scenes. HDRI preset assignment, environment-panel state, window interactions and various UI faults also receive fixes.

Hardware support includes NVIDIA RTX Spark and a Windows on Arm64 installer. Maxon’s system requirements give Windows/NVIDIA a minimum CUDA compute capability of 5.0 and 8 GB VRAM with driver 570 or newer; Windows/AMD requires RDNA 2 or later, 8 GB VRAM and driver 24.Q3 or later. The Mac minimum is an Apple M-series processor or suitable AMD Navi/Vega GPU, with at least 8 GB of GPU memory. For Redshift Live on Windows, an NVIDIA RTX GPU with 8 GB or more is specified; Apple’s Live requirements are narrower than those for ordinary Redshift rendering. Recommended memory and GPU configurations are higher, particularly for complex scenes. These are compatibility thresholds, not render-performance promises.

A 3D-rendered modern living room features a light beige sectional sofa with a matching chaise in the foreground, facing a low wood media console and a wall-mounted TV. A black glass display cabinet, dining chairs, a rug, and a camera settings panel overlay the right side, while soft daylight and warm wood tones create a clean, realistic viewport scene.

Why 2027.0.1 belongs in the story

The first maintenance build corrects more than minor UI irritation. Alongside the VRAM problems, Maxon lists fixes for USD procedural crashes and severe instability, camera-space-rendering crashes, texture displacement with Smart Bake, OSL shader recompilation, hangs, and procedural Fur proxies triggering repeated VRAM resets. It also repairs skies or clouds rendering black or with artefacts when sky parameters changed, and Redshift Live striping and altered wind behaviour when clouds were seen through reflective or refractive objects.

Host-specific 2027.0.1 repairs include legacy Cinema 4D scenes receiving mismatched GeomID and NameID values, Xrefs duplicating materials and incorrect Fur LOD; Maya Fur remaining visible in renders after deletion, missing transform motion blur and reference/rest-position support; and an architectural Viewer freeze when closing with a modal dialogue open. Vectorworks and Archicad fixes are described above. This is useful reading before a studio-wide upgrade, rather than an optional bedtime story for the IT department.

One known issue remains in the 2027.0.1 release notes: Archicad Production renders can show material displacement at ten times its intended strength. Maxon’s workaround is to avoid displacement on affected materials or reduce Displacement Scale to one tenth of its previous value. A subtle paving texture becoming the Alps is not a desirable architectural feature, unless you are working on a History Channel style documentary about “Pompeji 2: The rise of Blarg the Lava monster. “

Availability and the deployment check

Redshift 2027.0.0 and 2027.0.1 were released on 14 October 2026. Maxon provides 2027.0.1 through the Maxon App and direct installers for Windows full/lite, Windows on Arm64, macOS full/lite and Linux. Licensing is subscription-based, with Redshift included in Cinema 4D subscriptions; the available plan and price depend on the purchased entitlement. The Maxon App handles licensing and installation, and Maxon warns that the 2027.0.x App is incompatible with non-unified RLM licences.

DP previously covered Redshift 2026.9; Maxon’s feature overview rounds up the 2027.0 additions. The broader point is straightforward: the renderer now has more tools for memory, interaction and procedural detail, but version numbers and actual render tests still matter more than adjectives. So load the new version, or the free trail, and get shifting.

ProductRedshift
DeveloperMaxon
Versions2027.0.0 and 2027.0.1 (2026.10)
Release14 October 2026
Official notesTechnical changelog
AvailabilityRedshift 2027.0.1 via Maxon App or platform-specific installer
PlatformsWindows, macOS, Linux; Windows on Arm64 installer available
LicensingSubscription; Redshift is included with Cinema 4D subscriptions