Unreal Engine Path Tracer Guide: Rendering Architectural Scenes

This guide walks through enabling Path Tracer in an architectural scene in Unreal Engine and rendering a still image or animation. As described in Epic Games’ documentation, Path Tracer calculates lighting, reflections, and refractions based on the scene’s geometry and materials. The goal is to produce physically based, high-quality renders without the limitations of real-time rendering features.

What you’ll learn in this guide

First, you’ll check the operating system, graphics card, and project settings specified for Path Tracer. Then you’ll switch to Path Tracing mode in the viewport and see how samples accumulate. Finally, you’ll learn how to evaluate sample counts, resolution, and output settings when rendering a still frame or animation with Movie Render Queue (MRQ).

When the camera is stationary, Path Tracer accumulates samples for the image over time. The image may therefore look noisy at first; the result gradually improves as the sample count increases. Scene complexity and the materials being sampled affect render time. In interiors, light paths can become longer—and render times can increase—especially when materials have an albedo close to 1.0.

Requirements and project settings

Epic Games’ guide specifies Windows 10 1809 or later as the operating system, and NVIDIA RTX or GTX-series graphics cards with DXR drivers enabled. The target RHI setting for Windows must be DirectX 12. Hardware ray tracing and Path Tracing support must be enabled in the project settings. No specific Unreal Engine version is specified for the Path Tracer guide; the documentation also notes that Unreal Engine 5 has settings for checking Path Tracer-specific material shader options.

If Compute Skin Cache is disabled when hardware ray tracing is enabled, the engine displays a prompt asking you to enable it. According to Epic Games, Compute Skin Cache is required to support hardware ray tracing and Path Tracer. Restart the engine after changing the settings.

Projects that will never use Path Tracer can reduce shader compilation time by disabling the relevant shader option specified in the documentation. This may not be appropriate for projects planning to use Path Tracer, so evaluate the setting against your workflow requirements. Since the sources provide no information about calculation or licensing fees, this guide focuses solely on technical requirements.

Enabling Path Tracer and preparing the scene

1. Check the hardware and project requirements. For Windows, select DirectX 12. Enable hardware ray tracing and Path Tracing in the project settings. If Compute Skin Cache is disabled, enable it and restart the engine.

2. Select Path Tracing in the viewport. Open the View Modes menu in the Level Viewport and switch to Path Tracing. With the camera stationary, the image progressively accumulates samples; noise in the early stages may indicate that the calculation is not yet complete.

3. Keep the scene still while samples accumulate. Camera movement or changes to the view, as well as actions such as adding or moving objects and updating materials, can invalidate samples. It is expected that the calculation will restart after such changes.

4. Review the Post Process Volume settings. The Samples Per Pixel value in the PathTracing category sets the number of samples used for image convergence; a higher value can reduce noise. Max. Bounces sets the maximum number of light bounces before light paths are terminated.

5. Check light contributions. The Emissive Materials option determines whether materials with emissive color contribute to scene lighting. If a light source is represented by both emissive geometry and a local light, its illumination may be counted twice. Disabling emissive contributions can help test for this.

If unwanted bright marks known as “fireflies” appear around small, bright light sources, Max Path Intensity is one setting that can help reduce them. The Denoiser setting uses the loaded denoiser plugin to reduce noise in the final sample; according to the documentation, this option has no effect on the output if the plugin is not enabled. Check the image’s lighting balance as you adjust these settings.

Rendering with Movie Render Queue

Movie Render Queue provides several modules for using Path Tracer in production renders. The Path Tracer module provides settings specific to the render path. Options such as the maximum number of light bounces and the contribution of emissive materials can also be managed through the Post Process Volume. In the output settings, you can specify the file location, naming, resolution, and the start and end frames to render.

The Anti-aliasing module lets you set spatial and temporal sample counts separately. The spatial sample count determines the samples used per pixel for each temporal sample. Increasing this value can reduce noise in each render pass, but it also increases render time per frame. When using MRQ, the Samples Per Pixel setting in the Post Process Volume is ignored.

For still images, Epic Games recommends setting the temporal sample count to 1 and accumulating samples through spatial samples. For animations, the recommendation is to use 1 spatial sample and more temporal samples with Reference Motion Blur enabled. Temporal samples can improve motion blur quality by combining renders taken at different points in time. The appropriate distribution depends on the desired motion blur.

For high-resolution frames, the High Resolution module can render the image in separate tiles and combine them. The resolution available to each tile depends on the limit supported by the graphics card. Warm-up settings, which may be needed to prepare animations and visual effects correctly, are found in the Anti-aliasing settings. Before production, run a short test render and evaluate sample count, render time, and image quality together.

Impact on architecture and visualization workflows

Path Tracer can be considered for architectural and interior scenes where reflections, refractions, and indirect lighting affect visual decisions. In this workflow, offices can combine the need to explore the same scene interactively with the need to produce high-quality output later. However, account for potentially longer render times in interiors, especially when light paths extend through scenes with light-colored materials.

Include hardware compatibility, scene complexity, and target resolution in your production plan. Increasing the sample count can help reduce noise, but requires longer render times. Path Tracer’s suitability should therefore be assessed not only by image quality, but also alongside delivery schedules and available hardware.

Common mistakes and next steps

• If Path Tracing isn’t available: Check DirectX 12, hardware ray tracing, and Path Tracing settings. Restart the engine after making changes.

• If the image isn’t clearing up: Remember that camera or scene changes can invalidate samples. Keep the camera still and allow samples to accumulate; account for the longer render times that may result from increasing the sample count in MRQ.

• If interior renders are slow: Evaluate scene complexity and check whether materials have an albedo close to 1.0. These can lengthen light paths and increase calculation time.

• If animation blur isn’t as expected: Check the spatial-temporal sample distribution in MRQ and the Reference Motion Blur option.

• If light contributions appear too strong: Check whether emissive geometry and a local light are both representing the same source.

As a next step, render a test from a fixed camera angle. Decide on the framing and materials first, then compare sample count, resolution, and render time. You don’t have to use the same sample distribution for still images and animations; choose according to the intended motion blur.

Source and licensing

This guide was prepared in Turkish based on technical information in Epic Games’ Unreal Engine Path Tracer documentation. The source explains Path Tracer’s hardware and project requirements, viewport usage, and Movie Render Queue settings.