Search Issue Tracker
Fixed
Fixed in 6000.0.52f1, 6000.1.10f1, 6000.2.0b8, 6000.3.0a2
Votes
0
Found in
6000.0.50f1
6000.1.2f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-104824
Regression
Yes
XRDevice.refreshRate returns "0.0 Hz" when running Standalone Build in VR mode
Reproduction steps:
1. Open the attached project “ReproProject“
2. Make sure VR headset is connected
3. Make sure to put on the headset or activate headset's screen any other way (for example by blocking the sensor between the lenses)
3. Build & Run Standalone Player for Windows
4. Observe the result in Standalone Player on the monitor (not in the headset)
Expected result: In the top left corner “XR Refresh Rate” should read 72.0 Hz or 90.0 Hz
Actual result: “XR Refresh Rate” returns 0.0 Hz
Reproducible in: 6000.1.0b6, 6000.1.2f1, 6000.2.0a10
Not reproducible in: 2022.3.62f1, 6000.0.48f1, 6000.1.0b5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible with:
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, v72, OS: 14
- Oculus Quest 3, CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, (user reported)
Note: The issue is also reproducible in Play Mode but is unstable. Will reproduce one time but after re-entering Play Mode, the issue will not reproduce. After reopening the project, the issue can be reproduced in Play Mode again
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
Add comment