Search Issue Tracker
Feature Request
Votes
0
Found in [Package]
4.5.3
Issue ID
XRMB-146
Regression
No
[XR Management][Usability] Project validation does not output a warning that Meta Quest Support feature is not enabled, thus resulting in non-XR builds
Steps to reproduce:
1. Create a new 3D URP Template project
2. Switch the project to the Android Build Profile
3. Add the Unity XR Hands, Unity OpenXR Android XR, and Unity OpenXR Meta packages to the project
4. Turn on OpenXR for Standalone and Android platforms
5. Switch the project to the Meta Quest Build Profile
6. Observe that there's no warning in Project Validation regarding Meta Quest Support feature not being enabled thus resulting in non-XR Builds
7. If you build to a Quest 2/3/3S device, the resulting application will be in non-XR mode (2D application)
Expected Result: Project validation outputs a warning that Meta Quest Support feature is not enabled
Actual Result: Project validation does not output a warning that Meta Quest Support feature is not enabled
Reproducible with: XR Management 4.5.3 (6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4, 6000.5.0a1)
Environment tested: Windows 11 24H2
Notes:
-This does not occur when creating a VR Template, since settings are preconfigured
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
This is an enhancement we will have to look into and design, as adding a project validation warning does not work with all user workflows. We will take it into consideration. Thank you for the feedback.