Learn to use this Early Access feature, but use caution when shipping with it.
This feature is Early Access.
Features available in Early Access give you the opportunity to learn how they work, plan your pipeline, and create test content. You should use caution when using these features in production, as we are still working to get to shipping-quality performance, stability, and platform support. We support backward compatibility for assets, and the APIs for these features are stable.

Troubleshooting Mixed Reality Capture

This page provides troubleshooting information for Mixed Reality Capture (MRC).

Flickering During Captures

Depending on the resolution of the Mixed Reality capture target (the default is 1080p), your application may be constrained by its render target pool size. By default, render targets are set to reallocate as needed, which can lead to ping-ponging and flickering as the Mixed Reality capture targets fight with the stereo render targets. (shown in the video below)

If you see this kind of behavior, you can change the render target resize rule to ‘Grow’ (set r.SceneRenderTargetResizeMethod=2 in your engine.ini file, ). Making this change should resolve the issue.


Capture Not Displaying on Spectator Screen

The MRC framework uses the Virtual Reality Spectator Screen to display the composited scene. This means the Mixed Reality capture will only be displayed when running in Virtual Reality. If your project also uses the spectator screen, then you need to conditionally guard where you use them. There are MRC methods to help with this:

Get Mixed Reality Capture Texture
Returns the Capture Texture, or a nullptr if there isn't one.


Is Mixed Reality Capture Broadcasting
Returns true, if the system is sending the capture texture to the spectator screen.


Set Mixed Reality Capture Broadcasting
Toggles whether the capture system is sending the capture texture to the spectator screen or not.


An Example of Using the MRC Methods

Controller/Trigger Not Responding During Calibration

If your controller input does not appear to respond during calibration, below are several possible causes.
  • The headset sensor in not covered. If the headset’s sensor is not covered, the controllers may not be active.
  • The application window needs to have focus. If the MRCalibration window is not the current active window, the controller actions may not be captured by the calibration program. 
  • The Oculus system may not be configured to run from Unknown Sources. As a part of Early Access, the calibration program is still in active development and has not been reviewed by Oculus.  MR_OculusUnknownSourcesSetting.png