Writing

Materials Are Becoming Learned Programs

A material is texture maps, parameters and shader code. It is starting to become a small learned program that answers a rendering question.

Notes

For most 3D production, a material is built from familiar pieces: texture maps, parameters and shader code.

Base colour lives in one texture. Roughness and metallic values live in others. A shader graph defines how those values interact with light. More complex materials add layers, procedural masks, clearcoat, fibres or subsurface models until the renderer can reproduce the desired appearance.

SIGGRAPH 2026 research is pointing toward another representation.

VideoNeuMat extracts compact neural materials from video diffusion models. NVIDIA's richer-material work represents layered appearance with latent textures decoded by a shared MLP. 8DNA goes further by learning light transport through complex assets so effects such as subsurface scattering and glossy interreflection can be evaluated from a neural representation instead of recomputed from scratch.

I think materials are beginning to change from collections of authored parameters into small learned programs that answer a rendering question: given this point, view direction and lighting condition, what appearance should this surface produce?

A texture set stores values. A neural material stores behaviour.

Traditional PBR is powerful because the representation is explicit. Roughness, normals and metallic values have clear meanings, and the renderer combines them through a known model. That gives artists control, but it imposes a fixed vocabulary. Real materials can contain layered scattering, dust, coatings, fibres and other effects that are expensive to express with a small set of maps.

Neural appearance models take a different route. NVIDIA's 2024 Real-Time Neural Appearance Models work trained small networks to reproduce complex multilayered materials and compiled the learned representation into shader code for real-time rendering. The material could preserve effects that would otherwise require much heavier evaluation while still behaving like a shader inside the renderer.

The material is no longer only a bundle of maps. Part of its response to light is encoded in learned weights and latent data.

2026 makes the representation generative

The new work this year adds an important step: neural materials are becoming something generative systems can create directly.

VideoNeuMat starts from a video diffusion model that already contains broad visual knowledge learned from internet-scale data. The researchers finetune it to generate controlled material-observation videos under known camera and lighting trajectories. A second model then reconstructs a reusable neural material from 17 generated frames. That material can be rendered from new viewpoints and under new lighting.

This is different from generating a pretty image of marble. The output is an asset: it can be placed on geometry, relit and viewed from directions that were not part of the generated video. The appearance knowledge has been pulled out of the video model and converted into a representation a renderer can use.

The model becomes a material authoring source

Video generation models contain broad knowledge about how surfaces look across changing viewpoints and illumination, but that knowledge is entangled with geometry, camera motion and lighting.

VideoNeuMat treats the generative model almost like a virtual measurement device. By forcing it to produce controlled observations, the pipeline turns implicit visual knowledge into something closer to material measurements. The reconstruction model then converts those observations into a compact neural asset.

That suggests a new authoring pattern: instead of asking AI to generate the final render, use it to generate a reusable representation that remains inside the 3D pipeline.

I find that much more interesting.

PBR is not disappearing

PBR maps remain useful because they are interpretable and portable. A neural material is harder to inspect: if a highlight is wrong, there may not be one roughness slider responsible for it because behaviour can be distributed across latents and weights. I do not expect learned materials to replace standard PBR everywhere.

In fact, another line of research this year is trying to keep the two worlds connected. NVIDIA's procedural-data work begins with conventional PBR-style materials, expands them into richer layered appearance such as dust and clearcoat, then encodes the non-diffuse behaviour into a compact neural representation using latent textures and a shared decoder.

That hybrid direction makes sense. Keep the properties artists need to understand explicit. Learn the parts that are expensive or awkward to express directly.

A material can contain precomputed light transport

8DNA pushes the idea beyond local surface response.

Complex assets can contain appearance caused by light traveling through or around geometry: subsurface scattering, internal glossy reflections and fibre scattering. A conventional renderer has to simulate these paths, often with many samples.

8DNA learns an eight-dimensional light-transport representation from path-traced training samples. Once trained, the neural asset can reproduce expensive transport effects under changing near-field lighting with faster inference.

The boundary between "material" and "lighting solution" starts to blur. A learned asset can carry knowledge about how light moves through it, not only the static parameters used by a BRDF. For product visualisation, part of the response of translucent plastics, layered coatings or woven materials could live inside the asset itself.

This changes what optimisation means

With neural materials, optimisation can happen by distillation. Start with an expensive material, sample its behaviour, train a smaller network to reproduce the relevant response, then deploy that approximation instead of the original shader. This is already the logic behind neural appearance models and NVIDIA's neural-material direction.

That resembles software compilation more than texture baking: the source material describes high-fidelity intent, while training produces a target-specific runtime representation.

What this means for Blender workflows

For Blender, I would treat neural materials as another representation layer rather than a replacement for the shader editor.

During authoring, explicit nodes are still valuable because they are understandable. I can expose parameters to an artist, procedurally drive them and debug why the material behaves a certain way.

The learned representation becomes interesting at the boundaries: generation, deployment and capture. A material could be extracted from a prompt or generative model into a relightable asset, distilled from an expensive offline shader into a real-time neural shader, or reconstructed from observations without forcing every appearance effect into a fixed PBR parameter set.

The hard problem becomes editability

The production problem is control. Artists need local edits, versions and predictable outputs. A learned material that looks excellent but cannot answer "make only this coating slightly rougher" is difficult to use in production.

I expect future systems to separate interpretable controls from learned residual appearance. Some properties will stay as explicit parameters, while the network handles detail that would otherwise require large shader graphs or expensive scattering models.

We may end up authoring a material contract rather than every part of the material implementation.

The contract says what the artist controls. The learned representation solves more of how those controls become appearance.

My prediction

I think neural materials will become a normal asset type alongside texture-based and procedural materials.

Not every surface needs one. Simple painted metal is better served by simple parameters. Standard PBR remains useful because it is cheap, editable and portable.

The value appears when material behaviour is too rich for a small parameter set, too expensive for real-time evaluation, or difficult to recover manually from reference data.

What changed for me in 2026 is that the research is no longer only about compressing one expensive shader. VideoNeuMat shows that material knowledge can be extracted from generative models into reusable 3D assets. Richer-material work shows that generative systems can operate in neural material latent spaces. 8DNA shows that even complex light transport can become part of the learned asset representation.

The old material stack was maps plus code.

The next one may include weights, latents and learned light transport.

A material is starting to look less like a fixed set of textures and more like a small program trained to reproduce appearance.

Sources

  1. NVIDIA Research, VideoNeuMat: Neural Material Extraction from Generative Video Models, SIGGRAPH 2026.
  2. NVIDIA Research, Toward Richer Material Generation via Procedural Data Enhancement, SIGGRAPH 2026.
  3. NVIDIA Research, 8DNA: 8D Neural Asset Light Transport by Distribution Learning, SIGGRAPH 2026.
  4. NVIDIA Research, Real-Time Neural Appearance Models, SIGGRAPH 2024.
  5. NVIDIA Research, An Introduction to Neural Shading, SIGGRAPH 2025.

More

Other write-ups

15 September 2026 Approval Is Not Publication Thirty seven items in the queue, one approved, nothing published. The last arrow in the diagram is the only one that pays. 2 min read 14 September 2026 Neural Rendering Is Crossing From Reconstruction Into Synthesis Reconstruction filled in what sparse sampling missed. DLSS 5 generates appearance the renderer never computed. 6 min read 14 September 2026 The Renderer Is Becoming a Training Data Engine The renderer used to sit at the end of the pipeline. Physical AI gives the same scene a second job: teaching a model. 6 min read 13 September 2026 Local AI Is Becoming a Compute Fabric Local AI meant one model on one machine. Routing inference across the devices already on a network changes the unit. 6 min read 12 September 2026 Agent Infrastructure Is Becoming a Product Category Every team used to build the loop, the store, the sandbox. That layer is being sold rather than written. 6 min read 12 September 2026 Choosing a local model with a stopwatch, not a benchmark Three models, five hard tasks, code actually executed. The official build was 2.4 times faster and more accurate than a community repack of the same model. 3 min read 12 September 2026 We measured real time lighting against baked light, and baked won A 3D product simulation that had to look like an offline render. The real time version ran at 60 frames per second and looked like clay. Here is the measurement and the architecture that replaced it. 4 min read 12 September 2026 What actually broke in an agency run by agents Three failures from a delivery stack that runs on AI. None of them were the model's fault, and all three reported success while producing nothing. 4 min read 11 September 2026 A Task Without A Check Command Is Not Automated If a task has no command that can fail, the pipeline advances on the appearance of work. 2 min read 10 September 2026 A Gate The Model Writes Is A Gate The Model Loosens Three quality gates returned green while the work behind them was wrong, each for a different reason. 2 min read 8 September 2026 The Scoring Model Was Wrong And It Put The Worst Lead First A weighted sum let one axis substitute for the other, so a company with money and no problem ranked in the top twenty. 2 min read 5 September 2026 Building Software Got Easy. Getting Value Out Of It Did Not Aristo took weeks to build. Everything after the build is still in progress, and that gap is the whole story. 3 min read 4 September 2026 Capability Is Becoming an Operational Risk Surface Safety questions used to be about the text. Once a model can act, the capability itself becomes something to operate. 6 min read 24 July 2026 The Scene Graph Is Becoming an API for AI A scene graph exists for artists and software. Agents are becoming another consumer, and they need structure rather than pixels. 6 min read 23 July 2026 Animation Is Moving From Clips to Motion Priors Authored keyframes and blended clips are giving way to asking which constraints define acceptable motion. 6 min read 16 July 2026 Procedural Systems Are Expanding Beyond Geometry Geometry Nodes started with a narrow name. Blender 5.2 puts physics, sound and object data through the same graph. 6 min read 29 June 2026 The Unit of AI Work Is Becoming the Task, Not the Turn Chat taught us to think one turn at a time. Long-running agents make the task the thing that is scheduled, resumed and reviewed. 6 min read 24 June 2026 Game Engines Are Becoming Operating Systems for Worlds Engines have been judged on what they render and simulate. The Unreal 6 roadmap points at operating a world rather than drawing one. 6 min read 11 June 2026 The Model Is Becoming a Replaceable Backend Choosing a provider used to mean choosing an architecture. A stable interface makes replacement possible and evaluation makes it safe. 6 min read 17 April 2026 The Harness Is Part of the Capability The same model behaves differently depending on context policy, tool design and execution feedback. That surrounding software is not neutral. 6 min read 19 March 2026 Physics Engines Are Becoming Trainable Components A simulator predicts what happens next. A differentiable one can answer which parameter should change to stop the failure. 6 min read 13 March 2026 The Agent Needs an Environment, Not Just Tools A search function and a database query were enough for short loops. Longer work needs a place to stand. 6 min read 9 February 2026 Coding Agents Are Becoming General-Purpose Computer Workers Repositories were a friendly environment: text in, terminal actions, checkable results. That was a starting point, not a boundary. 6 min read 11 December 2025 Open Standards Outlive Model Generations A year after the MCP bet, the argument can be checked against what happened rather than what was hoped. 7 min read 20 November 2025 Colour Management Is a Pipeline Contract Blender 5.0 reads as better display options. Giving a file an explicit working colour space is an architectural change. 6 min read 11 August 2025 The Best Model May Be a Router, Not a Model GPT-5 moves model selection inside the system. The interesting unit stops being which model and becomes which compute policy. 6 min read 8 August 2025 World Models Are Not Game Engines Yet Genie 3 generates a navigable 720p world at 24 fps. Production work needs state you can inspect when something goes wrong. 6 min read 26 May 2025 Memory Is Becoming a System Capability A follow-up to the long-context argument. Storing, selecting and expiring facts is turning into a named part of the product. 6 min read 19 May 2025 Coding Agents Change the Unit of Software Work AI coding tools have been judged where code appears on screen. The boundary moves when the agent owns a task instead of a snippet. 6 min read 11 April 2025 Agents Need Protocols Between Each Other, Not Just Tools Tool calling solves the inside of the loop. It says nothing about one agent reaching another built by a different team on another platform. 7 min read 13 March 2025 Agents Need a Runtime, Not a Prompt Loop An agent is no longer well described as a prompt inside a while loop. The useful abstraction owns execution around the model. 6 min read 28 February 2025 Reasoning Is Not the Only Path to Better Models Longer thinking improves maths and code. A model that solves a logic puzzle and misreads ordinary intent is not the better production model. 6 min read 9 January 2025 Rendering Is Becoming a Reconstruction Stack Sparse samples, motion data and lower-resolution frames become a larger final result. Debugging becomes layered when reconstruction sits in the middle. 6 min read 16 December 2024 Agent Reliability Is an Evaluation Problem, Not a Prompting Problem When an agent misses a step, the usual fix is a stricter prompt. The failure is more often in how completion is detected. 6 min read 29 November 2024 MCP Might Matter More Than Another Model Release A model can reason well and still be useless inside a company if it cannot reach the files, repositories and tools where work lives. 6 min read 28 October 2024 Computer Use Is the Missing Layer Between Models and Software Most integrations assume useful software exposes the right API. Much of real software never did. 6 min read 19 September 2024 Inference-Time Compute Is a New Scaling Axis o1 improves when it is allowed to spend longer on a problem. A benchmark score without a compute budget is an incomplete number. 6 min read 15 August 2024 The Final Pixel Won't Come From the Renderer Geometry, camera and scene structure stay reliable ground truth. More of final appearance is moving into learned systems. 6 min read 29 July 2024 Open Models Are Becoming Research Infrastructure Llama 3.1 gets discussed as a benchmark result. The licence terms change which experiments are possible at all. 6 min read 24 June 2024 The Model Is Becoming a Runtime Function calling, code execution and structured output turn inference into a loop. The model stops being a text generator and starts being a control layer. 6 min read 16 May 2024 Multimodality Changes the Architecture, Not Just the Interface GPT-4o is easy to read as a faster interface. Training one model end to end across text, vision and audio is an architectural change. 7 min read 11 March 2024 Benchmark Scores Are Not Model Capability Claude 3 posts 86.8% on MMLU and 50.4% on GPQA Diamond. The chart is useful and it is not the same thing as capability. 6 min read 20 February 2024 Long Context Is Not Memory Gemini 1.5 makes a million tokens usable. A larger working set is not a system that decides what should survive the session. 6 min read