Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0f3
Issue ID
899741
Regression
No
[Android] Changing VRSettings.renderScale during runtime results in OPENGL NATIVE PLUG-IN ERROR with Mali GPU
To reproduce:
1. Download and open "VR Construction Yard_5.6.zip" project.
2. Go to Build Settings and add "Main_compact_2_fixed" scenes in build.
3. Build and run project on device with Mali GPU.
Expected result: Both Virtual reality eyes display view correctly. No errors are thrown in the console.
Actual result: One Virtual reality eye goes black and logcat throws OPENGL NATIVE PLUG-IN ERROR error.
Reproduced with 5.6.0f3, 2017.1.0b1.
DUT:
Reproduced with :
Samsung SM G925F (Galaxy S6 Edge), OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Samsung SM G930F (Galaxy S7), OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:samsung/heroltexx/herolte:7.0/NRD90M/G930FXXU1DQB3:user/release-keys
Not reproduced with :
Sony D6603 (Xperia Z3), OS:6.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 330, Build:Sony/D6603/D6603:5.1.1/23.4.A.1.264/2418263178:user/release-keys
Notes: Could not test on earlier versions because Cardboard was added in 5.6. Reproduces only on Mali GPUs. In Scripts folder there is VRcontroller.cs script where render scale is controlled. If both lines with VRSettings.renderScale are commented or deleted project works without any issues.
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
- Crash on SkinnedMeshRendererManager when interacting with a prefab generated with uncombined meshes using Synty Sidekick Character Creator
- Crash on folly::detail::safe_assert_terminate_v when updating the Meta XR SDK Packages
- The text font falls back on a different font depending on the fallback font used
- Template is opened in Isolation when opening it in Context and users Save the UI Document when prompted to do so in UI Builder
- Mono Windows Builds don't produce full log callstacks when generating logs
This is a duplicate of issue #896321