1 Overview
For years, the standard workflow for adding surface detail to game assets has relied on baking normal maps. Artists sculpt high-resolution meshes, retopologize low-poly versions, and then transfer the fine details into texture maps that fake the appearance of depth. This process is time-consuming, technically fragile, and often produces artifacts that require hours of cleanup. More importantly, it forces a compromise: the low-poly mesh must carry enough geometry to support the normal map without distortion, yet remain light enough for real-time rendering. That balance has always been a bottleneck.
Virtualized micropolygon rendering, often referred to by its most prominent implementation, Nanite, changes the equation entirely. Instead of faking detail with normal maps, you can import the high-resolution sculpt directly into the engine. The system automatically manages level of detail, streaming, and rendering, allowing millions of polygons to appear on screen without manual optimization. This means you can stop baking normal maps for many assets and start using the actual geometry. The result is cleaner silhouettes, more accurate lighting, and a dramatically simplified pipeline. This article explains why this shift matters, how to adapt your workflow, and what technical constraints still apply.
It is not a magic bullet for every asset. Characters, foliage, and transparent surfaces still require traditional techniques. But for hard-surface environment pieces, architectural elements, and props, the old bake-and-fake approach is becoming obsolete. By understanding the strengths and limitations of virtualized geometry, you can make informed decisions about when to abandon normal maps and when to keep them. The goal is not to eliminate normal maps entirely, but to use them only where they truly add value.
2 What this asset does in the game
In a game, high-density geometry with virtualized rendering serves as the visual backbone of the environment. It provides the physical forms that players see, touch, and navigate around. Unlike a normal-mapped low-poly mesh, which only simulates surface detail, this geometry contains actual polygons for every bevel, crack, and sculpted ridge. That means lighting interacts with the surface exactly as it would in reality, producing accurate shadows, highlights, and ambient occlusion without additional texture maps. The asset becomes a true three-dimensional object rather than a flat approximation.
Because the geometry is rendered directly, it also eliminates many common visual artifacts. Normal maps can produce seams, tangent-space errors, and shading discontinuities, especially on curved or deforming surfaces. With virtualized geometry, those problems disappear because there is no map to misinterpret. The asset also supports dynamic lighting more gracefully, since the engine can compute per-pixel lighting on the actual surface. This is particularly valuable for scenes with moving light sources or time-of-day systems, where baked normal maps would need constant reauthoring.
From a gameplay perspective, the asset behaves like any other static mesh. It can be placed, scaled, rotated, and collided with. The difference is purely in the rendering and memory management. The engine streams only the polygons that are visible at the required detail level, so distant objects consume fewer resources. This allows designers to populate scenes with far more geometric complexity than before, creating richer and more immersive environments without sacrificing performance. The asset is not just a visual upgrade; it is a structural one that enables new levels of environmental storytelling.
3 Style and art direction
The style of an asset built for virtualized geometry can range from photorealistic to highly stylized, but it tends to favor high-frequency detail. Because the system can handle millions of polygons, artists are free to sculpt fine cracks, chipped edges, fabric weaves, and organic imperfections that would be impractical to bake into a normal map. This encourages a more naturalistic approach, where surfaces tell a story through wear and tear. Even stylized assets benefit, as bold shapes can be accented with subtle micro-detail that reads clearly at close range.
Art direction must still consider readability and silhouette. A common mistake is to assume that more polygons automatically mean better art. In reality, the geometry should support the intended look, not overwhelm it. For a realistic style, that means studying reference materials and reproducing surface imperfections accurately. For a stylized style, it means using detail selectively to reinforce the artistic intent, such as exaggerating cracks on a ancient stone or smoothing a futuristic metal panel. The key is intentionality: every polygon should serve a purpose.
Lighting also plays a larger role with virtualized geometry. Because the surface is real, the art direction must account for how light will interact with it. Artists should test their assets under various lighting conditions early in production. This may reveal that some sculpted details are too shallow or too deep, or that the material response needs adjustment. Unlike normal maps, which can be tweaked in a texture editor, geometry changes require returning to the sculpt. Therefore, art direction should be locked down before high-resolution detailing begins, or at least be flexible enough to accommodate revisions. The payoff is a more cohesive and believable world.
4 The production pipeline
The pipeline for virtualized geometry removes several steps from the traditional workflow. Instead of sculpting high-poly, retopologizing to low-poly, unwrapping UVs, baking normal maps, and then texturing, you can often skip directly from high-poly sculpt to engine import. This streamlined process saves time and reduces technical debt. However, it does not eliminate the need for good topology entirely. While the engine can handle dense meshes, the source geometry should still be clean, with no overlapping faces, inverted normals, or non-manifold edges. These issues can cause rendering artifacts or performance problems.
A typical pipeline begins with blockout and sculpting in a digital content creation tool. Artists focus on form and detail, using subdivision or dynamic topology to achieve the desired resolution. Once the sculpt is complete, it can be exported as a dense mesh, often in a format that preserves vertex order and attributes. Some tools offer decimation or optimization passes, but with virtualized geometry, these are often unnecessary. The mesh is then imported into the engine, where the virtualized system automatically generates a cluster hierarchy and level-of-detail chain. This process is largely automatic, but artists should verify that the results look correct.
Texturing still matters. Even with real geometry, assets need materials to define color, roughness, and metallic properties. The difference is that normal maps are no longer needed for surface detail. Artists can focus on albedo and material definition, often using tiling textures or procedural materials. UV mapping is still required for texturing, but the density of the mesh means that UV seams are less visible. Some pipelines use triplanar projection or world-space texturing to avoid UVs entirely, though this can limit texture control. Overall, the pipeline is more direct and less error-prone, allowing artists to spend more time on creative decisions.
5 Technical constraints to respect
Despite its power, virtualized geometry has limitations. Not all assets are suitable. Characters and skinned meshes, for example, often cannot use the system because they require deformation and animation, which the current implementations do not support efficiently. Transparent materials, such as glass or foliage, also pose challenges because they rely on alpha blending and sorting, which the virtualized renderer may not handle. For these cases, traditional normal-mapped low-poly meshes remain the standard. Artists must therefore decide early which assets will use virtualized geometry and which will not.
Memory and storage are other constraints. Although the system streams data, the source meshes can be large. A single high-resolution sculpt may contain millions of vertices, and a scene with many such assets can consume significant disk space and memory bandwidth. Compression and streaming help, but they are not infinite. Artists should be mindful of the polygon budget per asset, not because the renderer cannot handle it, but because the data must be stored and loaded. Overly dense meshes that do not contribute visible detail are wasteful. A good rule is to sculpt only what will be seen.
Performance also depends on the target hardware. Virtualized geometry is designed for modern GPUs with advanced features, and it may not run on older devices or lower-end platforms. Developers must consider their minimum spec and whether the system is available. If not, they need a fallback path, such as a traditional low-poly mesh with normal maps. This dual pipeline adds complexity, so it is often best to choose a target platform early. Additionally, the system may have a maximum polygon count per object or per scene, which artists should verify in the engine documentation. Respecting these constraints ensures smooth integration.
6 Polishing for the engine
Once the asset is imported, polishing focuses on integration and visual quality. The first step is to verify that the virtualized geometry renders correctly. Check for holes, shading errors, or missing details. Because the system automatically generates LODs, you should inspect the asset from various distances to ensure that transitions are smooth and that no popping occurs. If you see artifacts, they may stem from issues in the source mesh, such as non-manifold geometry or flipped normals. Fixing these in the DCC tool and re-importing is usually the solution.
Material setup is next. Even with real geometry, materials define the surface appearance. Assign physically based materials with appropriate roughness and metallic values. Since normal maps are not used for detail, you can rely on the geometry to provide the bumps and grooves. However, you may still use a normal map for very fine details that are impractical to model, such as micro-scratches. This hybrid approach can be effective, but be careful not to reintroduce the artifacts you sought to avoid. Test under different lighting conditions to ensure the material responds naturally.
Finally, consider performance profiling. Use the engine's profiling tools to monitor draw calls, polygon counts, and memory usage. Virtualized geometry can be very efficient, but it is not free. If an asset is not contributing to the scene visually, consider reducing its density or removing it. Also, check that the streaming system is working correctly; you should not see assets popping in and out unexpectedly. With careful polishing, the asset will blend seamlessly into the game world, providing a level of detail that was previously impossible without compromising performance.
7 Frequently asked questions
Q: Can I use virtualized geometry for everything? A: No. It is best suited for static, opaque, hard-surface assets. Characters, foliage, and transparent objects still require traditional workflows. Q: Do I still need to UV map? A: Yes, for texturing. However, the high polygon density means UV seams are less noticeable, and some pipelines use alternative projection methods. Q: What about normal maps? A: You can stop baking normal maps for surface detail, but you may still use them for very fine details or on assets that do not support virtualized geometry. Q: Is it compatible with all platforms? A: No. It requires modern hardware and may not be available on older consoles or low-end PCs. Always check your target platform. Q: How do I optimize? A: Focus on sculpting only visible detail, use compression, and profile regularly. The system handles LODs automatically, but you should still avoid unnecessary complexity. Q: Can I animate these assets? A: Generally no, because the system does not support skinned deformation. Use traditional meshes for animated objects. Q: What about file sizes? A: They can be large, but streaming and compression help. Keep an eye on disk and memory budgets. Q: Will this make my game look better? A: It can, by providing more accurate lighting and detail, but art direction and material setup are still crucial. Q: Do I need special training? A: Not necessarily, but understanding the limitations and best practices is important. Experiment with small assets first. Q: Is this the future? A: It is a significant evolution, but traditional techniques will remain relevant for many asset types. Use the right tool for the job.