Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.4.2
Issue ID
OXRB-69
Regression
No
Lower performance when VR headset is active
Reproduction steps:
- Open the user's attached project
- Enter Play mode
- Open Stats
- Observe FPS
- Put on a headset and observe FPS
Expected result: The same FPS as before the headset is worn ~4000 FPS
Actual result: ~80 FPS when the headset is worn
Reproduced with: 1.4.1 (2021.3.6f1), 1.4.2 (2020.3.37f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0b1, 2023.1.0a3)
Reproducible on: Windows 11 with Oculus Rift S headset
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
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Resolution Note:
The performance you are observing is expected: when VR is active, vsync is forced on. There is no way to submit frames faster than the headset can display them