Search Issue Tracker
Won't Fix
Votes
4
Found in
2017.4.0f1
2018.3.0a1
2018.3.1f1
2019.1.0a1
2019.2.0a1
Issue ID
1120554
Regression
No
Disabling and then enabling VR results in performance loss if None was the VRDevice when first loaded
Steps to reproduce:
1. Download and open the attached project
2. Enter Playmode with an HMD connected
Expected result: after loading oculus, disabling and enabling vr game plays without issue
Actual result: for a few seconds, the performance drops to about 1fps
Reproduced on 2017.4.0f1, 2017.4.18f1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a3
Notes:
- Does not appear reproducible if Oculus is the starting VRDevice
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (2019.3.X):
This issue has been resolved in 2019.3 using XR Management and XR Plug-in System. We will not be fixing this for the built-in XR system as it is now deprecated.