Unreal Engine Movie Render Queue Guide: Architectural Rendering Settings

Unreal Engine’s Movie Render Queue lets you manage the output format and image-generation method for a render job in a single queue. Output, anti-aliasing, color, camera, and high-resolution options can be added as separate settings. This guide is based on information in Epic’s official Movie Render Queue documentation. Since the relevant page doesn’t specify an Unreal Engine version, the guidance here isn’t tied to a particular version number. [1]

1. Configure output and filenames

1. In the Movie Render Queue window, open the + Setting menu and add the options you need from the Settings section. Each setting you add can be enabled or disabled; select a setting to edit its properties.

2. Configure the Output setting at the start of the job. This required part of the queue cannot be removed; it’s where you define delivery parameters such as the folder where renders are saved, filename format, resolution, and frame rate. If you need a different frame rate than the one set in the sequence, first enable Use Custom Frame Rate, then set Output Frame Rate.

3. Use variables in the filename format field to organize filenames by scene, sequence, camera, or version. For example, you can use {sequence_name}, {camera_name}, {output_resolution}, and {version}. {date} adds the date in year.month.day format. When rendering multiple passes, {render_pass} helps distinguish each pass in the filename.

4. For sequences whose frame numbers start with a negative value, Frame Number Offset can keep filenames compatible with other software. In the documentation’s example, a value of 100 shifts frame numbers written to disk from -2, -1, 0, 1 to 98, 99, 100, 101. Zero Pad Frame Numbers sets the length of the frame numbers in the filename.

Output Frame Step isn’t a substitute for rendering the full sequence: a value of 2 skips every other frame. Since the world state still advances for skipped frames, the result may not be exactly the same as rendering every frame; the documentation warns that differences may be visible due to temporal history.

2. Choose Temporal and Spatial sampling

1. The Anti-Aliasing setting determines the number and method of samples used for the final frame. Movie Render Queue can use Temporal and Spatial sampling separately or combine them.

2. Temporal Sample Count determines how many time intervals are evaluated for a frame. Samples distributed over time account for motion and motion blur; increasing this value can produce smoother, radial motion blur. However, too many temporal samples can make the time interval the engine must process very small and may trigger a warning after rendering.

3. Spatial Sample Count determines the number of renders accumulated for each temporal sample. With this method, the camera position shifts slightly for each render sample, and the different samples are then combined. Epic notes that Spatial sampling may be worth considering when you need more anti-aliasing samples or less noise despite a short motion blur duration.

4. Consider motion in the scene when increasing the sample count. According to the documentation, it may often be more efficient to allocate most samples to Temporal: static objects get anti-aliasing samples, while blur on moving objects can make aliasing less noticeable. There’s no single setting that works for every scene.

When TAA is enabled, the variety of anti-aliasing sample positions is limited by the r.TemporalAASamples variable; the documentation gives a default value of 8. If the product of Spatial Count and Temporal Count exceeds this value, Epic recommends enabling Override Anti-Aliasing and setting the method to None, or increasing r.TemporalAASamples to match the total sample count. Simply increasing the sample counts may not deliver the expected benefit unless you account for this limitation.

If Temporal Sample Count is greater than 1, the sequence is also evaluated over a time range before the frame. It’s therefore important that Sequencer tracks cover the required range before the start. Some track types, such as animation or audio, can’t be extended automatically; these sections may need to be corrected manually after rendering.

3. Color, camera, and large-output options

1. Color Output can override Unreal’s default color-space settings using a custom OpenColorIO (OCIO) configuration. You can also disable the Tone Curve section in post-processing, even if you aren’t using an OCIO-based workflow. Before delivery, check that the selected color configuration matches the target image.

2. The Camera setting includes shutter timing and an overscan percentage for rendering additional pixels around the edges of the image. If you’re preparing output that requires extra image area, consider these controls alongside the camera and framing requirements.

3. For larger images, the High Resolution option uses tiled rendering. According to Epic, this method makes it possible to produce larger images without hitting the GPU’s maximum texture-size or memory limits. This doesn’t mean hardware requirements disappear; determine the output size and rendering conditions in advance.

4. Console commands that need to be applied at the start of rendering and reverted when the process finishes can be defined in the Console Variables setting. The documentation describes this option as a way to apply render-time quality settings that are too computationally expensive for real-time previews in the editor. Debug Options are generally useful when investigating rendering issues.

What changes in architectural and interior visualization workflows?

These options are useful to visualization teams preparing high-resolution stills, animation artists rendering sequences, and offices that need to deliver organized output from multiple cameras or render passes. Filename variables help separate outputs by sequence, camera, resolution, and version. Sampling settings can be selected according to needs such as motion blur, anti-aliasing, and ray tracing noise.

From a hardware perspective, High Resolution’s tiled rendering approach provides an option for working around GPU memory and texture-size limits; the documentation doesn’t say that hardware requirements are eliminated entirely. The source also doesn’t explain licensing terms. Offices should separately verify compatibility with the Unreal Engine version they use and check licensing requirements; after changing sampling or output settings, they should review the results using representative frames.

Common mistakes

• Increasing Temporal Sample Count without checking whether Sequencer tracks cover the time range before the sequence starts.

• Not comparing the combined Spatial and Temporal sample count with the r.TemporalAASamples limit when TAA is enabled.

• Treating frame skipping with Output Frame Step as equivalent to rendering the full sequence.

• Using {version} in the filename without deciding whether Auto Version or Version Number should take precedence.