Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0p1
Issue ID
984886
Regression
No
[Android] Loading already loaded "cardboard" VR device forcibly exits VR mode
How to reproduce:
1. Open user attached project
2. Deploy to device
3. Notice that after switching scene the device returns to 2D mode
Expected behaviour: App loads, switches to "Cardboard" VR mode, toggles between two scenes forever while staying in VR
Actual behaviour: App loads, switch to "Cardboard" VR mode, switches scene then exits VR mode and repeats this cycle forever\
Reproduced on: 2017.1.3f1, 2017.2.1p2, 2017.3.0p1, 2018.1.0b2
Workaround: Surround the code to check if it is already in cardboard mode
example: if (UnityEngine.XR.XRSettings.loadedDeviceName != "cardboard")
Favro card: https://favro.com/card/c564ede4ed3337f7b17986b6/Uni-34332
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment