Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.4f1
2019.2.0f1
Issue ID
1176195
Regression
Yes
Objects that use spine are broken in application when built to Android device with OpenGles3 API
To reproduce:
1. Open attached project
2. Make sure that Graphics API is set to OpenGles3
4. Build and run to android device
Actual result: the objects that use spine are not visible or glitches
Expected result: everything should be visible and not glitching
Reproduced in: 2019.1.4f1; 2019.1.14f1; 2019.2.1f1;2019.3.0a12
Not reproduced in: 2017.4.32f1; 2018.4.7f1; 2019.1.3f1
Tested with:
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 5.1.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Note: does not reproduce with Vulcan, DX11, and Metal
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
This is a duplicate of issue #1166303