Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a11
Issue ID
1080298
Regression
No
[XR][Android] Oculus is intialized even though Cardboard is first on SDK list
How to reproduce:
1. Open attached "OculusFirst" project
2. Build & Run on device
Expected result - Cardboard is initalized OR before deploying warning is thrown that there might some initialization issues (example - Daydream and Oculus)
Actual result - Oculus is initialized first and no warnings are thrown
Reproducible with - 2019.1.0a1, 2018.3.0b1, 2018.2.0a1
Note - To reproduce, GearVR developer mode must be turned off
DUT:
VLNQA00143, Samsung Galaxy S9+ (SM-G965U1), 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00164, Samsung Galaxy S8 (SM-G950F), 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00005, Samsung Galaxy S7 (SM-G930V), 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2018.3.X):
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.