Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.20f1
Issue ID
UUM-64322
Regression
No
[Quest] Entering the Play Mode takes 10-20 seconds when there is a mismatch between Oculus Software and Oculus PC App versions
Reproduction steps:
1. Create a new VR Project
2. Connect Quest with Oculus Link
3. Enter the Play Mode
Expected result: Entering the Play Mode takes about 1-3 seconds
Actual result: Entering the Play Mode takes 10-20 seconds
Reproducible with: 2022.3.20f1
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Quest 3 (User reported)
Quest Pro (User reported)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Workaround:
1. Update your Oculus PC App (62.0.0.235.346)
2. Update your Quest device (62.0.0.247.343.563460087)
Notes:
- Joining the Public Test Channel in the Meta Quest app on your phone, lets you manually update to v62, by using the Software Update option in your Quest device
- Reproducible with OpenXR and Oculus XR
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Fixed on Meta's side