Search Issue Tracker
Duplicate
Votes
0
Found in
1.16.1
Issue ID
UUM-133839
Regression
No
Switching to Meta Quest Build Profile fails to load interaction profiles
Synopsis
Switching to the Meta Quest platform under Build Profiles generates the following OpenXR warnings and fails to enable relevant OpenXR Interaction Profiles. A workaround is to create a custom Build Profile based on Meta Quest, then switch to this Build Profile. But switching to the Meta Quest platform should work robustly; otherwise the Switch Platform button should be grayed out, or its limitations should be spelled out clearly in the Users' Manual.
{{Oculus Touch interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}
{{Meta Quest Pro interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}
{{Meta Quest Plus interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}
Steps to reproduce:
- Use Unity 6000.3 to crate a new project using URP Template (or open repro project attached).
- File > Build Profiles > Meta Quest > Switch Profile
- Check Console window for warnings.
- Check Edit > Project Settings > XR Plug-in Management > OpenXR Enabled Interaction Profiles.
Actual results:
Console warnings listed above in Synopsis appear in Console window.
There are no enabled interaction profiles in OpenXR Project Settings.
Expected results:
No warnings in Console; three relevant interaction profiles enabled.
Reproducible with versions:
Unity 6000.3.6f1 + OpenXR 1.16.1.
Also occurred in Unity 6.2, so not flagging as regression.
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Warnings occurred on MacBook Pro when setting Build Profile to Meta Quest.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!