Known issues and limitations

This page lists some known issues and limitations that you might experience with the Recorder. It also gives basic instructions to help you work around them.

Recording slowdown with concurrent Movie Recorders

Limitation: The Unity Editor playback process might substantially slow down if you perform concurrent recordings with multiple Movie Recorders, particularly with large image resolutions (full HD or higher).

Workaround: The recommended use case is to limit yourself to one Movie recording at a time. Ensure that you have only one active Movie Recorder in the Recorder window and no Movie Recorder Clips in Timeline, or vice-versa. If you need to keep concurrent recordings for some reason, you can still set up lower resolutions or try different encoders (for instance, the MP4 encoding step is much faster than the ProRes one).

Targeted Camera recording is not available with URP 2D Renderer

Limitation: Recorder cannot capture images from a Targeted Camera in URP 2D projects. A capture pass that Recorder requires is missing in the renderer.

Workaround: As an alternative, you can capture from the Game View or from a Render Texture Asset.

ActiveCamera recording not available with SRPs

Limitation: The use of a Scriptable Render Pipeline (SRP) in your project prevents you from setting ActiveCamera as the source of the recording in the Movie Recorder and the Image Sequence Recorder. This render pipeline limitation applies to all SRPs including Unity's High Definition Render Pipeline (HDRP) and Universal Render Pipeline (URP). For the same reason, the AOV Recorder, which requires HDRP, doesn't include the ActiveCamera option by design.

Workaround: You can use a Tagged Camera for the recording. In your project, add a Tag to the camera you want to record through, and then in the Recorder Settings, select TaggedCamera and specify your camera's Tag.

Audio recording limited support

Limitation: The Recorder currently supports only the recording of samples from the Unity built-in audio engine. As such, it cannot record audio from third-party audio engines such as FMOD Studio or Wwise.

Workaround: For a movie, you can record the third-party audio output in WAV format through another application, reimport this recorded file into the Unity Timeline, and then use the Recorder to create the final movie with audio. Alternatively, you can use any video editing software to recompose audio and video.

GIF Animation Recorder no longer available

Limitation: This version of the Recorder no longer includes the GIF Animation Recorder, although it is still available in Recorder versions 2.5 and lower.

Workaround: To produce a GIF animation, record your content with the Image Sequence Recorder and then process the result through any external GIF animation software.

Limited support of AA/TAA in AOVs

Limitation: The Beauty AOV is the only AOV that you can currently record with Anti-Aliasing (AA) / Temporal Anti-Aliasing (TAA) enabled on your recording camera.

Color artifacts in AOV recordings when TAA is enabled

Known issue: If you record multiple AOVs while the recording camera has Temporal Anti-Aliasing (TAA) enabled, the recorded outputs might contain unexpected color artifacts. For example, some areas of a Beauty pass might include artificial colors coming from the data recorded for a Normal pass.

Workaround: If you need to record a Beauty pass with TAA enabled on your recording camera, you should record it through its own recording session, separately from any other AOVs.

Recorder does not capture any custom cursors

Known issue: When you record a video where you use a custom cursor set with Cursor.SetCursor, the cursor doesn't appear in the recordings.

Workaround: To make sure that the Recorder captures your custom cursor, you have to:

360 View recording issues and limitations

The Recorder doesn't fully support 360 View recording. Here is a list of known issues you might encounter:

  • If you record a 360 View in projects that use the High Definition Render Pipeline (HDRP), the rendered cube map might have artefacts that make its boundaries visible. One way to work around this issue would be to disable post-process effects such as Shadows, Bloom, or Volumetric Fogs.

  • If you record a 360 View through a Physical Camera, the rendered image is not equirectangular, which makes the output media unusable. To work around the issue, use a regular Camera for the recording.

  • The Recorder doesn't support stereoscopic recording in projects that use any Scriptable Render Pipelines (SRPs). The Stereo Separation property has no effect on the recorded views, which makes the rendering identical for both eyes.

Different Cameras with different Display targets lead to black output

Known issue: Certain camera outputs are black when cameras have different TargetDisplays. This occurs when you set up recorders with Targeted Camera as the Input Source. The Game view triggers the render loop of all cameras that target the same Display number. If no Game view is configured for a specific Display number that is set on a Camera, it does not render.

Workaround: Open another Game view and set it to the Display number that you need to capture.

Impossible to capture multiple Game views at the same time

Known issue: Recorder does not handle a configuration with mutiple Game views as Input Source. Recorder assumes that there is only one Game view and gets the one that has the focus at the moment the Editor enters the Play Mode.

Workaround: Set the Input Source to Targeted Camera or Render Texture Asset.