Since Nanite can handle high-detail geometry, the need for complex normal map baking—a process used to "fake" detail on low-poly models—is significantly reduced. Performance and Hardware
This workflow is broken for several reasons: it is labor-intensive, it introduces artifacts (silhouette popping, texture seams, blurry normal maps), and it fundamentally lies about the geometry. A cliff face rendered with normal maps looks correct under static lighting but reveals its flatness under dynamic light or at grazing angles. The industry had reached a point where the fidelity of assets was constrained not by artistic vision, but by the logistical impossibility of manual optimization. nanite
: High-detail models (with millions of triangles) were too heavy for computers to render in real-time. Since Nanite can handle high-detail geometry, the need
Nanite begins by pre-processing all source meshes offline. It generates a multi-resolution, clustered representation of the geometry, organized into a Directed Acyclic Graph (DAG). This is not a simple pyramid of LODs; it is a hierarchical data structure that breaks each mesh into fixed-size "clusters" of approximately 128 triangles. The engine then creates compressed representations of these clusters at varying levels of detail, down to the level of individual pixels. The industry had reached a point where the
Traditional LODs often "pop" as you move closer to an object. Nanite provides a seamless transition because it scales detail on a per-pixel basis in real time.
