Rendering Architecture with Unreal Engine Path Tracer: A Step-by-Step Guide

What you’ll learn in this guide

In Unreal Engine, Path Tracer is a progressive rendering mode that uses scene geometry and materials to calculate physically based lighting, reflections, and refractions. When targeting offline rendering instead of real-time viewing, Movie Render Queue (MRQ) can be used to produce high-quality stills or animation output. Epic Games’ documentation says Path Tracer integrates with Sequencer and MRQ, and that MRQ can queue render jobs and make settings reusable.

In this practical guide, you’ll check the required project and hardware conditions, enable Path Tracer in the viewport, and prepare a Level Sequence for rendering through MRQ. Actual render times depend on scene complexity, materials, and the selected sampling settings. The goal, therefore, isn’t to prescribe one “best” setting, but to help you manage the trade-off between quality and render time.

Requirements

Hardware ray tracing must be enabled in the project settings to use Path Tracer. Epic lists Windows 10 1809 or later and an NVIDIA RTX graphics card or a GTX-series card with DXR drivers enabled as system requirements. DirectX 12 should be selected as the default RHI for Windows, and the Hardware Ray Tracing and Path Tracing options must be enabled. You may also be prompted to enable Support Compute Skin Cache when turning on hardware ray tracing; this feature is required for ray tracing and Path Tracer support. Restart the editor after making changes.

You’ll need a project and a Level Sequence to render. To enable the Movie Render Queue plugin, go to Edit > Plugins, find Movie Render Queue in the Rendering section, enable it, and restart the editor. For projects that don’t yet contain a suitable sequence, Epic’s documentation gives the Main_Seq sequence in the Meerkat Demo as an example.

MRQ’s output settings let you specify the folder, file name, image resolution, and start and end frames to render. Graphics card capacity, scene size, and target image dimensions can all affect the workflow you choose; the documentation doesn’t provide a single general render time or fixed settings that suit every project.

Step-by-step Path Tracer and MRQ workflow

1. Verify the project requirements. Check the Windows target, DirectX 12, and hardware ray tracing settings. Confirm the status of Hardware Ray Tracing, Path Tracing, and Support Compute Skin Cache, then restart the editor if you made any changes.

2. Prepare the scene and sequence. Choose a Level to render and a Level Sequence. Since MRQ lets you select which Level to use in the job details, the same Level doesn’t need to be open when you start the render; the tool can open the specified Level itself.

3. Preview Path Tracer in the viewport. Select Path Tracing from the View Modes menu in the Level Viewport. The image becomes clearer as samples accumulate while the camera remains still. Camera movement, material changes, or adding objects to the scene can invalidate the accumulated samples, so give the image time to converge again before evaluating it.

4. Open Movie Render Queue. From the main menu, choose Window > Cinematics > Movie Render Queue. Alternatively, open Movie Render Queue from the options beside the Render Movie button in Sequencer. If the plugin isn’t enabled, complete the setup step above before opening the window.

5. Add the sequence to the queue. In MRQ, use the + Render button to select a Level Sequence. You can also add one by dragging it from the Content Browser into the job list area. When a job is selected, use the Settings area to review render options and output format, and the Output area to check the destination folder.

6. Choose Path Tracer and sampling settings. The Path Tracer module provides options for this rendering method. In the anti-aliasing module, Spatial Sample Count sets the number of samples per pixel, while Temporal Sample Count controls samples taken at different points in time. A higher spatial sample count can reduce noise in each pass, but it increases render time per frame. Epic’s guide recommends using spatial sampling with 1 temporal sample for still images; for animations, it recommends 1 spatial sample and more temporal samples with Reference Motion Blur enabled. Evaluate this recommendation based on scene motion and test renders.

7. Set the output range and destination. In the Output module, set the folder, file name, resolution, and start and end frames. After checking the settings, start the render locally. If the queue contains multiple jobs, review the sequence, Level, and output location for each one.

In MRQ, Render (Local) runs the process in the same process as Unreal Engine. Render (Remote) starts a separate process and requires you to save project changes first. The second option can be used with remote render farms, but it isn’t a ready-made cloud service. Teams need to set up their own workflows.

Common issues and quality checks

Not waiting for samples to finish accumulating while the scene changes: Camera or material changes can invalidate accumulated samples. Before evaluating the final image, wait for the scene to remain stable and for the samples to progress.

Increasing the sample count for every job: A higher Spatial Sample Count can help reduce noise, but it also increases render time. Start with a short test and find the lowest setting that meets the required quality.

Overlooking the contribution of emissive materials to lighting: If geometry that emits light is also represented by a point or spot light, its contribution to illumination may be counted twice. Check the Emissive Materials option in the Post Process Volume alongside the actual light sources in the scene.

Confusing Path Tracer settings with MRQ settings: The Post Process Volume can adjust Path Tracer features such as maximum light bounces and sampling, while MRQ manages production steps such as output and the job queue. Troubleshooting is easier when you investigate noise, lighting behavior, and output format separately.

Not checking the output location: Each job’s Output connection points to the folder where render files will be written. Before starting the queue, verify the folder and frame range for each job. The High Resolution module can render frames as separate tiles; in this workflow, the preview may show only the bottom-right tile.

Impact on architecture, interior design, and archviz workflows

Path Tracer can be useful for visualization teams that want to evaluate elements such as material reflections, refractions, and global illumination in a more physically based way. In particular, longer light paths in interior scenes can increase render time; open scenes may render faster because rays can leave the scene after fewer bounces. This makes it important to plan sampling and render time for interior presentations.

For architecture firms and students, MRQ’s queue and reusable settings can help organize the production of multiple sequences or outputs. However, the workflow depends on a graphics card with ray tracing support, correct project settings, and scene complexity. Before adopting it, check hardware compatibility and project requirements; for high-resolution or animated deliverables, estimate render time with small test renders.

Next steps

Start with a single-frame test render and check the materials, lighting, noise, and output location. If the result is suitable, carry the same approach over to the rest of the sequence. For animations, assess temporal sampling based on motion blur; for still images, test the balance between render time and noise. When changing settings, adjusting only one variable at a time makes it easier to understand why the result changed.

Sources and licensing

This guide was prepared in Turkish using Epic Games’ Unreal Engine Movie Render Pipeline and Path Tracer documentation, and adapted for architectural visualization workflows. The source pages were provided as license=free; no open-license type not stated in the sources has been assumed here.