Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0p1
Issue ID
984895
Regression
Yes
"None"->"Cardboard" VR device transition fails if orientation == portrait in player settings
How to reproduce:
1. Open user provided project
2. Deploy app to device
3. Notice that after 2 seconds when app switches from 2D to VR, camera tracking is lost and logcat is spammed with:
OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is not complete or incompatible with command
Expected behaviour: Orientation only applied to the 2D app, and switch to VR working in Landscape Left
Actual behaviour:
Not reproduced on: 2017.3.0b1, 2018.1.0a4, 2018.1.0b2
Reproduced on: 2017.3.0f1, 2018.1.0a3
Note: Issue does not reproduce if orientation is set to 'Auto' or 'Left/Right Landscape'
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
Add comment