DCC Renderer Material Translation Guide

1. Inventory the source graph before translation

Duplicate the approved scene and record renderer versions, color-management configuration, texture search paths, displacement bounds, and render overrides. In the source Node Material, capture every connection from texture reader through utility nodes to the terminal Shader. Flag renderer-only nodes such as Redshift triplanar, V-Ray dirt, flakes, thin film, or ray switches. The inventory is a semantic map: it says what a branch does, not merely where its socket sits.

2. Separate portable physics from renderer conveniences

Translate physical intent first: base reflectance, metalness, index of refraction, microsurface roughness, transmission, subsurface response, coat, emission, opacity, normal, and displacement. Treat procedural noise, remapping, coordinate projection, and layered masks as inputs to those properties. A Redshift Material and a V-Ray Material may expose different controls, but a dielectric plastic still requires plausible albedo, IOR, and roughness. Do not copy numeric values between controls with different ranges or inversion conventions.

3. Normalize textures and color roles

Resolve UDIM tokens and missing paths, then classify every bitmap as color or data. Albedo and authored emission color usually enter through the working display transform; roughness, metalness, masks, normals, and displacement remain linear. Confirm whether glossiness must be inverted to roughness. Convert unsupported procedural branches to versioned textures only after choosing resolution, bit depth, UV set, padding, and bake domain. Keep originals beside the baked fallback so the migration remains reversible.

4. Rebuild lobes in a controlled order

Start with an untextured gray Shader and establish diffuse, reflection, and roughness under a neutral studio rig. Add transmission and subsurface only after the opaque response agrees. Add coat, sheen, anisotropy, and emission last, because these can hide a wrong base response. For each lobe, render a small wedge or parameter sweep. This isolates which mapping changed the image instead of debugging a completed graph whose branches interact unpredictably.

5. Handle normals and displacement explicitly

Check tangent-space orientation, object transforms, normal strength, and whether the renderer expects a normal node rather than direct RGB. For displacement, document scalar versus vector mode, midpoint, units, subdivision method, and bounding expansion. A material that looks acceptable in close-up can still clip silhouettes when the new renderer uses a smaller bound. Compare a low-angle light pass and a silhouette pass; beauty images alone often conceal inverted normals and under-scaled displacement.

6. Use a reference scene, not memory

Build one locked turntable containing matte spheres, curved metal, grazing highlights, a thin transmissive object, and a displaced plane. Use identical camera exposure, light geometry, environment, and output transform for source and destination renders. Compare linear EXR values or calibrated crops rather than two differently tone-mapped JPEGs. A match is bounded by agreed tolerances: highlight width, average albedo, transmission tint, silhouette displacement, and render-time budget.

7. Work a renderer migration decision

A coated red automotive surface uses a Redshift Material with a proprietary flakes node, while delivery requires V-Ray. Rebuild base paint and coat as a V-Ray Material, preserve measured IOR and roughness, then bake flakes to a tileable normal and mask at the camera-approved texel density. Keep procedural Redshift files in the archive. This choice sacrifices infinite procedural detail but meets look, memory, and farm-compatibility constraints with a testable fallback.

8. Diagnose visible migration failures

If highlights are too sharp, inspect roughness inversion and remap curves before adjusting lights. If transparent edges turn dark, inspect refraction depth, absorption distance, normals, and alpha mode. If textures shift, compare UV channel, object-space projection, and transform scale. If renders become noisy, isolate coat, transmission, and emission sampling. If the material compiles but renders magenta, inspect unsupported nodes and missing assets rather than rebuilding the entire graph.

9. Package evidence for approval

Deliver source and translated scenes, dependency manifest, graph screenshots, baked fallbacks, conversion notes, renderer presets, and reference renders. Include isolated diffuse, reflection, normal, displacement, and emission passes with pixel comparisons. Record accepted deviations and approver. Another artist must be able to reopen both implementations and explain differences without relying on the original translator’s memory.

Multilingual production vocabulary