Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
3.0.0-pre.4
Issue ID
OXPB-5
Regression
No
[Quest] Performance.TryGetAvailableDisplayRefreshRates doesn't work when OVRPlugin with OpenXR backend is enabled
Reproduction steps:
1. Open the "90Hz OpenXR" Scene in the attached project "VR Sandbox.zip"
2. In File > Build Settings make sure that the "90Hz OpenXR" Scene is added in Scenes in Build
3. Select Android Platform
4. Build and Run
5. Observe the framerate in the Scene
Expected result: Framerate is set to 90Hz
Actual result: Unable to get available framerate, it stays 72Hz
Reproducible with: 1.11.2, 3.0.0-pre.1, 3.0.0-pre.4 (2019.4.36f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b6, 2022.2.0a3)
Could not test with: 3.0.0-pre.2 (2020.3.27f1, 2021.2.9f1, 2022.1.0b6, 2022.2.0a3) - Build fails
Reproducible with device:
NA Oculus Quest 2 (Quest 2), OS: 10, CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- Does not reproduce if set to Oculus > Tools > OpenXR > Switch to Legacy OVRPlugin (with LibOVR and VRAPI backends)
- Reproducible if set to Oculus > Tools > Open XR > Switch to OVRPlugin with OpenXR backend
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
This will be fixed in a future Oculus firmware update