Search Issue Tracker

Fixed in 2020.1

Planned for 2018.4

Fixed in 2019.3

Votes

1

Found in

2017.4

2018.4

2019.1

2019.2

2019.2.0f1

2019.3

2020.1.0a1

Issue ID

1175291

Regression

No

[Android][ETC2][OpenGLES2] When ETC2 fallback is set to 32-bit, half resolution, sprites in sprite atlas don't use the fallback

Mobile

-

Reproduction steps:
1. Open "ETC.zip" project
2. Build and Run for Android
3. Connect the Profiler
4. "Memory Profiler" -> "Detailed" -> "Take a Sample"
5. Expand "Assets" -> "Texture2D" and notice 2 objects "sactx" and "sprite_not_in_atlas"
6. Notice that the file "sactx" takes up 1MB
7. Notice that the file "sprite_not_in_atlas" takes up 256.3KB

Expected Result: Sprite Atlases are affected by ETC2 Fallback

Reproduced with: 2020.1.0a1, 2019.3.0b1, 2019.2.3f1, 2019.1.14f1, 2018.4.7f1, 2017.4.32f1

Reproduces on: OpenGLES2, Mono and IL2CPP

Repro Devices:
VLNQA00020, Samsung Galaxy S3 (SGH-T999), Android 4.3, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 225
VLNQA00043, Samsung Galaxy S3 Mini Value Edition (GT-I8200N), Android 4.2.2, CPU: Marvell PXA988, GPU: GC1000 Graphics Engine
VLNQA00067, Motorola RAZR D1 (XT914), Android 4.1.2, CPU: MediaTek MT6575, GPU: PowerVR SGX 531
VLNQA00105, Htc One X (HTC One X), Android 4.2.2, CPU: nVIDIA Tegra 3 AP33, GPU: NVIDIA AP

No Repro Devices:
VLNQA00104, Lge Nexus 5 (Nexus 5), Android 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00035, Motorola DROID MAXX 2 (XT1021), Android 4.4.4, CPU: NOT FOUND, GPU: Adreno (TM) 305
VLNQA00115, Sony Xperia Z3 (D6603), Android 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00002, Samsung Galaxy S5 Neo (SM-G903F), Android 6.0.1, CPU: Exynos 7 Octa 7580, GPU: Mali-T720
VLNQA00112, Htc M9 (HTC One M9), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00106, Samsung Galaxy S2 Plus (GT-I9105P), Android 4.2.2, CPU: Broadcom BCM28155, GPU: VideoCore IV HW
VLNQA00054, Xiaomi MI 4LTE (MI 4LTE), Android 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00224, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 5.1.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00028, Samsung Galaxy Note4 (SM-N910F), Android 6.0.1, CPU: Snapdragon 805 APQ8084, GPU: Adreno (TM) 420
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 5.0.2, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
VLNQA00072, Google Pixel C (Pixel C), Android 8.1.0, CPU: nVIDIA Tegra X1 T210, GPU: NVIDIA Tegra
VLNQA00053, Asus Nexus 7 (2012) (Nexus 7), Android 5.1.1, CPU: nVIDIA Tegra 3 T30L, GPU: NVIDIA Tegra 3

Comments (1)

  1. E6cab90300d5e9236b2c7f24f5c2db1b?d=mm

    Palbuzzo

    Dec 13, 2019 14:48

    I see that this has been fixed in Unity 2019.3 and up, but starting with 2019.3, Unity is dropping support for Android versions lower than 4.4.

    Would it be possible to apply this fix to Unity 2019.2 as well so that we can still benefit from this fix for all currently-supported Android versions?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.