Search Issue Tracker
Fixed in 1.9.0
Votes
3
Found in [Package]
1.7.0
Issue ID
1305447
Regression
No
[XR] Player.log is spammed with "[XR] Error determining if we should quit: Not Initialized" when Oculus Service is disabled
Reproduction steps:
1. Make sure Oculus Service is disabled
2. Open the user's attached "Test_VR_XRig.zip" project
3. Build and Run the project
4. Open the Build's Player.log
Expected result: Player.log is not spammed with the "[XR] Error determining if we should quit: Not Initialized"
Actual result: Player.log is spammed with the "[XR] Error determining if we should quit: Not Initialized"
Reproducible with: Oculus XR 1.5.0, 1.7.0 (2019.4.18f1, 2020.2.1f1, 2021.1.0b4, 2021.2.0a3)
Could not test with 2018.4 (no Oculus XR Plugin available)
To disable Oculus Service:
1. Open Oculus Debug Tool (https://developer.oculus.com/documentation/native/pc/dg-debug-tool/)
2. Select "Service" > "Stop Oculus Service"
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 1.9.0):
Fix Player.log spamming with "[XR] Error determining if we should quit: Not Initialized" when Oculus Service stopped
Fixed in Oculus XR Plugin 1.9.0