Foveated Rendering API switched to Legacy on Build

My reports

Submit feedback

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers

External issue

Issue

1 report

Created 3 days ago

Add your report

Suggest an edit

Copy link

Category

Graphics > Foveated Rendering

Platform

Unity

Investigation summary

When using the Meta XR SDK in Unity, the Foveated Rendering API is being set to Legacy on build, despite being set to SRP Foveation in the OpenXR Plugin settings. This occurs when the Meta XR Foveation feature is disabled and the Foveated Rendering feature is enabled in OpenXR features. However, the XRDisplaySubsystem API can still be used to set the foveated rendering level with this configuration.

Latest official response

Meta's Response:

Both Unity's "OpenXR Plugin" and "Unity OpenXR Meta" packages specify the foveated rendering API, and the setting in the "Unity OpenXR Meta" package will overwrite the other. There is a hidden setting in the MetaQuestFeature (appears as "Meta Quest Support" in the XR Plugin Management UI). However, there is no UI or API to set it, so it always has its default value of "Legacy", which overwrites the OpenXR setting (this happens in the ApplySettingsOverride method in Runtime/MetaQuest/MetaQuestFeature.cs). As a workaround, you can manually edit your project's "OpenXR Package Settings.asset" (a yaml file). Search for "com.unity.openxr.feature.metaquest", then change the value of m_foveatedRenderingApi from 0 to 1.3/3/26 at 11:32 AM

Still need help?

Tell us what you need support with and we'll find the best solution for you.

Get support

Get answers from the community

If you're having trouble, find answers to your questions from Meta Quest users around the world.

Go to community forum