Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.16f1
2017.4.20f1
Issue ID
1129921
Regression
Yes
[2017.4][GLES3][Android] Textures of a specific width are rendered incorrectly on some devices with Adreno 305 GPUs
Repro steps:
1. Open attached project
2. Make sure the Graphics API is set to GLES3
3. Build and Run on Android
4. Observe the two textures on the screen
Actual: The right one is rendered as a black square
Reproducible with: 2017.4.16f1, 2017.4.23f1
Not reproducible with: 2017.4.15f1, 2018.3.0a1, 2018.3.8f1, 2019.1.0b7, 2019.2.0a8
Tested and reproduced on this device:
VLNQA00035, Motorola Moto E, Android 4.4.4, CPU: Snapdragon 200 MSM2210, GPU: Adreno (TM) 305
Didn't reproduce on these devices:
VLNQA00038, Htc Desire 510 (HTC Desire 510), Android 4.4.3, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00036, Motorola Moto G (1st Gen) (XT1032), Android 5.1, CPU: Snapdragon 400 MSM8226, GPU: Adreno (TM) 305
VLNQA00140, Samsung Galaxy S4 (GT-I9505), Android 5.0.1, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320
Notes:
- Also reported that reproduces on LG Volt
- No repro on GLES2 and Vulkan
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
This is a duplicate of issue #1100390