Writing

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.

Notes

For most of computer graphics, the renderer has been the final authority. Geometry, materials, lights and cameras go in. Pixels come out. Better rendering has usually meant tracing more rays, sampling more accurately, or finding faster approximations to the same physical process.

I think that boundary is starting to move.

My bet is that geometry and scene structure will remain the reliable ground truth, while the final photorealistic appearance will increasingly be reconstructed by neural systems. The renderer will still matter, but it may stop being the component that determines every visible pixel directly.

Current tools do not do this end to end. The evidence is split across denoising, upscaling, neural materials and scene reconstruction, but the direction is becoming easier to see.

The renderer is already giving up pixels

DLSS is the clearest production example.

Real-time rendering works inside a fixed compute budget. When native-resolution path tracing is too expensive, developers reduce samples or resolution and reconstruct the missing information.

With DLSS 3.5 Ray Reconstruction, NVIDIA replaces several hand-tuned denoisers with a neural network trained to reconstruct higher-quality ray-traced images from sparse samples and temporal data. NVIDIA describes the network as learning lighting patterns from offline-rendered reference images and using them to infer better pixels during real-time rendering.

That changes the role of the renderer. It produces physically meaningful evidence: geometry, motion, sampled rays, depth and lighting information. The neural stage decides how that incomplete evidence should become a clean final image.

Super Resolution pushes the same idea further. Frame Generation goes further again: some displayed frames are synthesised rather than rendered conventionally.

The important point is not faster rendering. The final image is becoming a reconstruction problem.

Rendering has always contained reconstruction

Renderers have always reconstructed to some degree. Path tracing estimates an integral from finite samples; denoisers estimate a converged result; temporal methods reuse prior frames; upscalers infer detail. Neural methods expand how much of that reconstruction can be learned rather than hand-designed.

DLSS 3.5 is interesting because NVIDIA is not placing the neural model after a finished render as a cosmetic effect. Ray Reconstruction replaces part of the ray-tracing pipeline itself. The network sits between sparse physical samples and the image we see.

Once that works reliably, it is reasonable to ask how much more of the appearance pipeline can move into learned representations.

Materials are starting to become learned representations

Material systems are another useful signal.

NVIDIA's Real-Time Neural Appearance Models work shows that complex layered materials can be baked into compact learned representations and evaluated with neural decoders inside a real-time path tracer. The researchers report that these neural material shaders can be more than an order of magnitude faster to evaluate than the original non-neural layered materials while retaining complex appearance.

This is not diffusion-style generative rendering. The material remains constrained by scene, view and light transport, but part of its appearance no longer needs a conventional shader graph evaluated node by node.

The same pattern appears in neural texture compression. NVIDIA's 2023 work stores material textures in a learned representation and decodes them on demand, reporting four times the linear resolution in its examples while using less memory than conventional block-compressed textures.

From a production perspective, this matters because textures and shaders have always been part of the source description of appearance. If those representations become learned, the boundary between asset and renderer becomes less rigid.

Scene representation is moving too

3D Gaussian Splatting is a different branch of the same story.

The 2023 work by Kerbl and colleagues represents a captured scene using optimised 3D Gaussians and renders new viewpoints in real time. It does not use a conventional polygon-and-material pipeline to reproduce appearance. The representation itself stores spatially organised appearance information learned from images.

For product visualisation, games and VFX, I do not expect geometry to disappear. A mesh gives us topology, scale, contact, occlusion and editable structure. Cameras, animation and lights provide more controllable constraints. I expect that explicit scene structure to become more valuable as a control signal, even if the photorealistic surface of the final frame becomes less rigidly represented.

That distinction is the core of my prediction.

Geometry as truth, appearance as reconstruction

When I work in Blender or a real-time engine, I care about two different kinds of correctness.

The first is structural correctness: the product is the right shape, proportions hold, the camera matches, the animation contacts the floor, and the object casts its shadow from the right location.

The second is perceptual fidelity: leather that reads as leather, brushed metal that breaks up light correctly, and scratches, dust, fingerprints and subsurface effects that hold up at the final viewing distance.

Traditional rendering solves both through the same pipeline. We build detailed geometry, texture maps, procedural materials, lights and simulation until the renderer can calculate the final appearance.

I suspect these two responsibilities will separate.

Geometry, animation and coarse physical simulation can remain explicit because they are useful for control. The neural layer can increasingly handle the expensive tail of visual realism: fine material response, high-frequency detail, reconstruction from sparse rays and perhaps eventually parts of lighting appearance that are expensive to sample directly.

The renderer then becomes less like a camera producing the finished photograph and more like a measurement system producing trusted signals for another stage.

Why I would not replace the renderer with a generator

There is an obvious bad version of this idea: render a rough frame, send it through an image generator and accept whatever looks photorealistic.

I would not trust that pipeline. A logo can move, a seam can disappear, or a reflection can imply geometry that is not present. Across animation frames, those mistakes become temporal instability.

A useful neural renderer needs tighter conditioning than a prompt and a low-resolution image.

Depth, normals, motion vectors, object IDs, material properties, lighting samples and camera state are far more useful constraints. They give the neural stage freedom where appearance is expensive to compute while preserving the parts of the scene that production needs to control.

This is why I see hybrid rendering as the likely path. Deterministic graphics establish the scene. Learned systems reconstruct increasingly large parts of its appearance.

What this could change in production

If this direction holds, artists may spend less time manufacturing detail purely so a renderer can reproduce it pixel by pixel.

For product work, I would still build accurate geometry, cameras, animation and controlled lighting. But some microscopic appearance detail could move into learned reconstruction.

Game engines could make the same trade: decide what must be physically sampled and what can be reconstructed reliably. Polygon budgets, texture memory and shader complexity would remain, but signal quality and temporal stability would become larger parts of optimisation.

My prediction

Over the next few years, I expect the phrase "rendered frame" to become less literal.

A frame may contain geometry processed conventionally, a limited set of ray-traced samples, temporally reused information, neural material evaluation, reconstructed lighting, synthesised detail and pixels that were never directly shaded at native resolution.

The mix will depend on the application. Games need temporal stability and predictable latency; product visualisation needs shape and material fidelity; film can spend more compute but tolerates fewer artifacts.

I do not expect physics-based rendering to become obsolete. I expect it to move upstream.

It can provide reference data, training targets and hard constraints. Neural systems can then spend their capacity on the parts of image formation where brute-force sampling is expensive or where learned priors give a better trade between quality and compute.

That is the direction I would design for now: keep geometry explicit, keep production state deterministic, and assume that the layer producing the final photorealistic appearance will become increasingly learned.

The renderer will still tell us what the scene is.

It may no longer be the thing that paints every final pixel.

Sources

  1. NVIDIA, NVIDIA DLSS 3.5: Enhancing Ray Tracing With AI, 22 August 2023.
  2. Zeltner et al. / NVIDIA Research, Real-Time Neural Appearance Models, presented at SIGGRAPH 2024.
  3. Vaidyanathan et al. / NVIDIA Research, Random-Access Neural Compression of Material Textures, SIGGRAPH 2023.
  4. Kerbl et al., 3D Gaussian Splatting for Real-Time Radiance Field Rendering, SIGGRAPH 2023.
  5. NVIDIA Research, AI and Simulation Advancements at SIGGRAPH 2024, 12 July 2024.

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 22 July 2026 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. 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 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