Arnold 7.5.4 learns to composite right during the render

Autodesk has released Arnold 7.5.4.0. The main change concerns a stage usually separated from rendering: the engine now has a Shader Imager, which lets you build simple compositing and frame stylization right inside the renderer and see the result interactively. Alongside it, the developers made the accelerated viewport more responsive, added a render pause that doesn't lose what has already been computed, and moved rim light out of the Toon shader into a separate node.

The release came out on October 22, 2026. Besides the new features, it contains plenty of optimizations for interactive work: mesh deformation, updating scenes with instances on the GPU, and motion blur with differing key counts are now processed noticeably faster.

A comp can be built without leaving the render

Imagers in Arnold have always processed the finished frame: denoising, lens effects. The new Imager Shader connects a shader network to this stage. Within it, OSL shaders or the image node read AOVs by names of the form "aov:diffuse" and "aov:albedo", so passes can be reassembled, tweaked, and layered over one another before the frame goes off to a compositing package. Autodesk calls this slap compositing — a quick preliminary assembly of the frame in interactive mode.

For lookdev this shortens the "rendered — exported — assembled in the comp — went back to fix the lighting" cycle. For stylized projects another scenario opens up as well: in Autodesk's examples, different styles built in OSL and a painterly brush effect are applied to one and the same render via the Shader Imager.

Intermediate imager results during a CPU render now appear earlier and more regularly — in particular for the shader imager, lens effects, and the OIDN denoiser, while imager runtime stays closer to the imager_overhead_target_percent target value. Changing an imager after the render has finished now shows progress until processing completes.

The viewport holds its frame rate during navigation

The accelerated viewport mode (direct_outputs) appeared in Arnold 7.5.3.0 in July. In the new version it returns to an interactive frame rate faster when the camera moves and holds it longer. To do so, the engine can lower several quality settings at once and reduce resolution: the direct_outputs_max_linear_factor parameter (1 by default, 6 maximum) allows it to be lowered during navigation. If even that isn't enough, the viewport switches to an unlit fast preview where surfaces are shaded by their angle to the camera — the direct_outputs_ndoteye parameter is responsible for that. When the camera stops, the image returns to full quality. These settings work only when rendering on the GPU.

The accelerated mode itself is now available for CPU rendering as well, although the viewport processing stage still requires a graphics card; without one, Arnold will issue a warning and fall back to a regular render. The mode supports more AOV types and works in kick, albeit without color management. The Z, ID, object, and shader buffers returned by AiGetRenderOutput() are filled at every pixel from the first pass after camera movement, so plugins will be able to draw wireframes and overlays on top of the render using the depth buffer.

Pause, a time limit, and rim light as a separate node

• Pause and resume. A render can be paused and resumed within a session without losing what has already been computed. In the interactive kick window this is done with the P key.
• A time limit per frame. The max_render_seconds parameter stops a batch render after approximately the specified number of seconds and writes out the frame obtained by that moment. To make sure the frame is always complete, the progressive sampler is enabled. In interactive sessions the setting is ignored for now.
• Rim Light. Rim light, which used to be a built-in part of the Toon shader, has become a standalone node. It can be mixed into any shader network and used as a separate RGB component. This continues the line of 7.5.3.0, where separate diffuse, fuzz, and specular BSDF nodes appeared for NPR rendering.

Heavy scenes update faster

A significant part of the release speeds up interactive work with large scenes. According to Autodesk:

• deforming a subdivided character with displacement (17 million polygons after subdivision) is processed 43% faster on CPU and GPU, while in the Caldera USD scene of 27,000 meshes, deforming all objects got up to 78% faster on CPU and up to 75% faster on GPU;
• preparing a GPU scene with 100,000 instances before rendering became three times faster, from 660 to 214 ms, and with a million instances — from 9.8 to 4.1 s; the acceleration structure for 500,000 instances became 34% more compact;
• scenes where objects have differing numbers of motion blur keys render several times faster: in a test with 39,000 moving objects the time dropped from 3.76 to 0.28 s.

On Windows, Arnold now warns when a GPU render approaches the video memory limit beyond which rendering slows down sharply and may crash. The Noice denoiser got consistent behavior of the filter_strength parameter across all filters, and its default value rose from 0.45 to 0.6. The Flow Render cloud service, which remains in technical preview status with 2,400 render minutes per month per user, has learned to work with custom OCIO configurations, UDIM tokens in texture names, and the per-frame time limit.

The full list of changes and fixes is published in the Arnold 7.5.4.0 release notes.

What this means for the pipeline

Judging by recent releases, Autodesk is consistently shifting Arnold toward interactive work: the accelerated viewport appeared in 7.5.3, now it has been brought up to CPU and kick, and most of this version's optimizations concern response time during edits rather than the final render. This is probably connected to the expectations of artists accustomed to real-time previews in game engines and GPU renderers.

The Shader Imager and a separate rim light node fit the same logic as the previous release's NPR nodes: stylization and preliminary compositing are moving inside the renderer. This won't replace a full-fledged compositing package, but for lookdev, previsualization, and stylized animation, some iterations will be possible to close without leaving the DCC. If the trend continues, it is logical to expect that new core capabilities will gradually appear in the interface of the plugins for Maya, 3ds Max, Houdini, and Cinema 4D, and that studios and the community will start assembling libraries of ready-made OSL styles for imagers.

What from the release will you put to work first?

• Compositing in the render
• Render pause