Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b11
Issue ID
1013396
Regression
Yes
[GearVR | IL2CPP] Strip engine code pulls out VR module even though Virtual reality is enabled
GearVR Strip engine code pulls out VR module even though Virtual reality is enabled.
1. How we can reproduce it using the example you attached
1) Note that the settings are as follows
- Scritping backend = IL2CPP
- Strip Engine Code is checked
- Virtual reality mode is enabled
- Oculus is the preferred SDK
2) Deploy to a GearVR enabled device
3) Observe the app launches in 2D mode (this is the bug)
Notes:
- Unchecking strip engine code fixes the problem
- Adding a script that references a piece of th VRModule fixes that problem I.e. XRDevice.model
- Switching to Mono backend fixes the problem
Final note,
I consider this fairly low on the USER pain scale as most VR developers are going to have at least 1 call to a XRModule scripting API . That being said, it is a bug and we should fix it.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment