Architectural Visualization in Unreal Engine 5.0: Lumen, Nanite and Shadows

What will you learn in this guide?

This guide covers how to evaluate Lumen, Nanite and Virtual Shadow Maps for real-time inspection of an architectural scene in Unreal Engine 5.0. The steps include observing the effects of changes to lighting and openings, checking detailed models, and examining dynamic shadows at different distances. The goal is not to provide a one-size-fits-all settings recipe, but to show where these features may be useful in a workflow for evaluating design decisions.

According to Epic Games’ Unreal Engine 5.0 release notes, Lumen provides global illumination and reflections that respond to changes in a scene and its lighting. Nanite is a virtualized geometry system designed to work with highly detailed models. Virtual Shadow Maps are designed for dynamic shadows, but are labeled as beta in version 5.0. That beta status and the platform requirements should therefore be taken into account from the outset, especially on projects with critical production deadlines.

Requirements and release notes

The primary source is the Unreal Engine 5.0 release notes. The menu path and feature descriptions below are based on the documentation for this version; don’t assume the interface or behavior will be the same in another Unreal Engine version. Since the source provides no information about account requirements or pricing, this guide does not specify any such requirements.

On Windows, Nanite and Virtual Shadow Maps require DX12; the release notes state that DX11 is not supported for these features. Lumen’s software ray tracing approach is designed to work across a wider range of graphics cards, with hardware ray tracing support also available for higher visual quality. These descriptions do not guarantee the same performance on every project computer. Also bear in mind that Virtual Shadow Maps is in beta: test it in your target scene and on the hardware you plan to use before incorporating it into your workflow.

Evaluate an architectural scene step by step

1. Identify the design decisions you want to assess. First, choose which changes in the scene you want to compare: for example, how an opening affects the interior, changes in sun direction, or reflections on glass surfaces. These are architectural examples for exploring different scene conditions; they do not mean Unreal Engine guarantees a particular result. As you compare them, keep track of which condition you change within the same scene.

2. Observe how Lumen responds to lighting and reflections. Change the lighting direction or scene conditions, then look at how indirect lighting and reflections update. The Unreal Engine 5.0 release notes give examples of Lumen reflecting changes such as a shift in the sun’s angle and the opening of an exterior door. This approach may be useful for architects and visualization teams looking to assess the relationship between interior and exterior lighting, or compare different lighting scenarios in real time. Check the results under other scene conditions as well before final presentation.

3. Inspect detailed models for Nanite. According to the source, Nanite is designed to let users work directly with source models that may contain millions of polygons. The system aims to greatly reduce triangle-count and draw-call constraints by rendering only perceptible detail. The feature can be evaluated when working with detailed façade elements or other models with high geometric density in architectural scenes. Still, don’t assume that every mesh and material will be compatible; the release notes cite issues such as alpha testing, world position offset and pixel depth as examples of compatibility limitations.

4. Run a Nanite audit. The Unreal Engine 5.0 documentation describes the Nanite Auditing Tool as a way to inspect static meshes for issues and optimization opportunities. Access it from the main menu via Tools > Nanite Tools. According to the source, the tool’s error section shows problems with meshes that have Nanite enabled, while its optimization section identifies opportunities to enable Nanite on meshes with no significant incompatibilities. This audit can help you identify which assets to check before making widespread changes across the scene.

5. Test Virtual Shadow Maps as a beta feature. This system aims to produce consistent dynamic shadows on objects of different sizes. The release notes mention improvements for high-quality shadows and large scenes, but explicitly mark the feature as beta. Before using it in a project, verify shadow quality and behavior in your target scene; don’t treat it as a finalized production standard while ignoring its beta status. Also check the DX12 requirement for use on Windows.

6. Inspect shadows at different scales. If your scene includes small and large objects, vegetation or distant areas, don’t evaluate shadows in just one close-up shot. The Unreal Engine 5.0 release notes describe Virtual Shadow Maps as providing consistent quality for differently sized objects and improvements for distant areas in scenes with vegetation. These statements describe the system’s aims; they don’t promise a specific result or performance level in a given project. When comparing results, look at both nearby details and distant parts of the scene.

Impact on architectural and visualization workflows

Lumen can help you inspect in real time how lighting and reflections respond to changes in a scene. This may be useful, especially in projects where lighting conditions and the relationship between interior and exterior spaces are important to design evaluation. Nanite aims to make it easier to work with detailed geometry. Virtual Shadow Maps offer an option for dynamic shadows, but their results should be validated for each project because the feature is in beta.

For visualization artists, practical steps include checking whether the models in use are compatible and confirming that project computers meet the DX12 requirement. The source provides no specific hardware models, pricing or licensing terms, so no assumptions should be made about them. For office and student projects, a more cautious approach is to test the features in a representative scene first, then incorporate them into the workflow if needed.

Common pitfalls

• Overlooking that Virtual Shadow Maps is in beta: The Unreal Engine 5.0 release notes label the feature as beta. Test it for your specific project before using it in production.

• Assuming it will work with DX11: According to the source, Nanite and Virtual Shadow Maps require DX12 on Windows; DX11 is not supported.

• Assuming every model will work flawlessly with Nanite: Keep the stated material compatibility examples in mind and inspect static meshes with the Nanite Auditing Tool.

• Relying on just one lighting or camera condition: When evaluating Lumen and shadow behavior, compare different scene conditions that matter to the design.

• Treating feature descriptions as performance guarantees: The release notes describe the features’ goals and some improvements; they do not specify a frame rate for every scene.

Next steps

Start by choosing the lighting, geometry and shadow scenarios that matter most for your architectural decisions. Use Lumen to compare lighting and reflections, and audit the static meshes you’re considering for Nanite. Test Virtual Shadow Maps on your target system, taking its beta status into account, and confirm the DX12 requirement on Windows. This lets you use a real-time scene not only for visual presentation, but also to assess design alternatives in a controlled way.

Source and license

This guide was adapted into Turkish using Epic Games’ official Unreal Engine 5.0 release notes. The source input lists the license status as “free.”