Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.1p1
Issue ID
981681
Regression
No
[Android] SystemInfo.supportsInstancing returns false on low end devices that support OpenGLES 3.0
To reproduce:
1. Download and open attached "repro981681.zip" project.
2. Build and run on Android device.
3. Check the output via ADB logcat.
Expected result: SystemInfo.supportsInstancing returns true on devices that support OpenGLES 3.0.
Actual result: SystemInfo.supportsInstancing returns false.
Reproduced with: 2018.2.0a1, 2018.1.0b7, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1, 5.6.5p1.
Devices under test:
Samsung GT I9505*, OS:5.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 320,
Build:samsung/jfltexx/jflte:4.2.2/JDQ39/I9505XXUAMDM:user/release-keys
Motorola XT1032*, OS:5.1, CPU:armeabi-v7a, GPU:Adreno (TM) 305,
Build:motorola/falcon_retuglb/falcon_umts:5.1/LPBS23.13-58-2/2:user/release-keys
Htc HTC Desire 510*, OS:4.4.3, CPU:armeabi-v7a, GPU:Adreno (TM) 306,
Build:htc/htc_europe/htc_a11ul:4.4.3/KTU84L/407309.7:user/release-keys
Notes : All of these devices support OpenGLES 3.0 and according to documentation they should support GPU Instancing.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
- 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
Add comment