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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment