Why does Movie Render Queue output black frames in Unreal Engine?

The most common cause is a Warm Up Frame Count of 0. Shaders and textures must stream in before the camera begins capturing, so setting Warm Up Frame Count to at least 32 frames (and Engine Warm Up Count to match) prevents the first frames from rendering before assets are ready.

Why does Temporal Super Resolution produce black frames in MRQ?

TSR requires historical frame data to produce a high-quality result. On the very first frame of a shot, that history does not exist, so TSR outputs black or a smeared result. Adding a warm-up period of at least 16–32 frames before capture begins gives TSR enough frames to build its history buffer.

Does the output format affect whether Movie Render Queue outputs black?

Yes. EXR files support an alpha channel natively, but PNG requires the correct bit depth and alpha settings. JPG has no alpha channel at all. If a render pass expects an alpha channel and the output format does not support one, some passes will appear black. Switch to EXR 16-bit or EXR 32-bit for multi-pass renders.

Fix: Unreal Movie Render Queue Producing Black Frames

Quick answer: Set Warm Up Frame Count to at least 32 in your Anti-Aliasing settings so shaders and textures can stream in before capture begins, and make sure all required plugins (Cryptomatte, etc.) are enabled for your render passes.

Movie Render Queue is Unreal Engine’s professional-grade cinematic renderer, and when it works it is spectacular. When it outputs solid black frames, though, debugging it is maddening because black output could mean a dozen different things: the shader never compiled, the texture never streamed in, TSR has no history buffer, a required plugin is disabled, or the output format simply doesn’t support what you asked it to write. This post walks through every common cause, in the order you should check them.

The First Suspect: Warm Up Frame Count Is Zero

The single most common cause of black MRQ output is a Warm Up Frame Count of 0. Movie Render Queue captures frames as fast as the GPU can render them, which means it can begin capturing before shaders have finished compiling and before streaming textures have finished loading into VRAM. The result is a frame rendered with placeholder black textures or uncompiled materials, which looks identical to a fully black frame.

Open your Job Config, click into the Anti-Aliasing settings, and set both values:

// In Job Config → Anti-Aliasing settings
Spatial Sample Count:      8   // minimum for temporal accumulation
Temporal Sample Count:     8
Warm Up Frame Count:       32  // frames rendered but NOT written to disk
Engine Warm Up Count:      32  // engine ticks before first sample

The warm-up frames are rendered at full quality but discarded — they do not appear in your output sequence. Think of them as a pre-roll that lets the engine flush its shader compilation queue and finish streaming assets. For scenes with heavy Nanite geometry or large Virtual Textures, 64 warm-up frames may be needed.

Temporal Super Resolution and the History Buffer Problem

If you are using Temporal Super Resolution (TSR) as your upscale method, black or extremely blurry first frames are almost guaranteed without warm-up. TSR is a temporally-accumulated upscaler: it builds a high-quality output by blending the current frame with a history of previous frames. On frame zero of a new shot, that history is empty, so TSR outputs either black or a noisy, smeared result.

The fix is identical to the general warm-up solution — set Warm Up Frame Count to at least 16–32 frames before your capture starts. You can also switch to DLSS (if you have the plugin) or TAAU which are more tolerant of cold history buffers, but TSR with adequate warm-up produces the best quality for offline renders.

You can verify TSR is the culprit by temporarily switching to No Anti-Aliasing or FXAA in your render settings and re-running. If the black frames disappear, TSR’s history initialization is the cause.

Anti-Aliasing Sample Count Too Low

Even with warm-up frames set correctly, a Spatial Sample Count of 1 can produce near-black results in scenes with heavy sub-pixel detail (thin geometry, dense foliage, hair). The renderer accumulates multiple samples per pixel to reconstruct the full image. With only one sample and temporal accumulation disabled, extremely fine details may not be sampled at all, producing dark or unexpectedly dim output.

For cinematics, a starting point of 8 spatial samples and 8 temporal samples per frame is reasonable. For hero shots, 32×32 is not unusual. Keep in mind that render time scales with sample count, so use the Level Sequence preview in PIE first to tune your settings before committing a full-resolution render.

Missing or Disabled Plugins for Render Passes

Movie Render Queue supports additional output passes via plugins — notably Cryptomatte for mattes, Object ID passes, and path-tracing integrations. If you add one of these passes to your job config but the corresponding plugin is not enabled in your project, the pass will render black without producing an error message in the MRQ log panel.

To check, open Edit → Plugins and search for the pass name. For Cryptomatte, enable the "Cryptomatte" plugin. For path tracing passes, enable "Path Tracer". After enabling plugins, restart the editor and re-queue your job.

// Console command to list active render passes during PIE
MoviePipeline.ListRenderPasses

// Force shader recompile if passes compile but render black
r.ShaderDevelopmentMode 1
recompileshaders all

Camera Cut Track “When Finished” Settings

Inside Sequencer, your Level Sequence should have a Camera Cuts track that controls which camera MRQ uses for rendering. The When Finished property on the Camera Cut section controls what happens to the camera after the section ends. If this is set to "Restore State" and the cut track ends before the full render range, the camera reverts to its original transform — which may be buried inside geometry, producing a fully occluded (black) view.

Set When Finished to "Keep State" on all Camera Cut sections, and ensure your Camera Cut track spans at least the full render range including warm-up frames. You can see the effective render range MRQ will use by opening the job’s Sequence settings and checking the Frame Range fields.

Output Format and Alpha Channel Handling

If only specific passes render black (not all frames), the output format is a likely culprit. JPG does not support an alpha channel. PNG supports alpha only in 16-bit or 32-bit mode. EXR is the correct format for any pass that writes alpha data, depth, or HDR values outside the 0–1 range.

// Recommended output settings for multi-pass renders
Format:         EXR
Bit Depth:      16-bit   // use 32-bit for HDR > 10 stops
Compression:    ZIP      // lossless; PIZ for maximum compression
Multilayer:     false    // true combines all passes into one EXR

If you need a quick debugging fallback without reconfiguring your job, use the High Resolution Screenshot tool (Ctrl+F9 in the viewport) to render a single frame. If that screenshot looks correct but MRQ output is black, the issue is isolated to MRQ’s pipeline configuration — not your scene or materials.

“Black frames from Movie Render Queue are almost never a GPU or hardware problem — they are a configuration problem, and every cause has a specific setting that fixes it once you know where to look.”

Set your warm-up count first, check your plugin list second, and only then reach for the output format settings — in that order you’ll fix 90% of black-frame renders.