Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a9
Issue ID
1099278
Regression
No
[Android] [LWRP] Some Sprites are not rendered in the scene
1) Download attached project and open in Unity
2) Make sure Graphics API is set to Gles3
3) Build and run on a device
4) Press Play
Observe: Some of the sprites will not be rendered (check attached image)
Expected result: All sprites should be rendered in the scene
Reproduced with:
2019.1.0a7, 2019.1.0a8, 2019.1.0a9
Devices under testing:
Reproduced with:
VLNQA00030 Lge LG D802 (G2)*, OS:4.4.2, CPU:armeabi-v7a, GPU:Adreno (TM) 330
Not reproduced with:
VLNQA00147 Razer Phone, Adreno 540, CPU:arm64-v8a, 8.1.0
VLNQA00123, Google Pixel 2 XL, Adreno 540, CPU:arm64-v8a, 9
VLNQA00202 Samsung Galaxy Note 9, Adreno 630, CPU:arm64-v8a, 8.1.0
VLNQA00144 Samsung Galaxy S9, Adreno 630, CPU:arm64-v8a, 8.0.0
VLNQA00129 Nvidia Shield, NVIDIA Tegra, CPU:armeabi-v7a, 6.0.1
Note: Can't test with Unity 2019.1.0a6 and lower because of the package manager errors
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Texture size in project exceeds the limit supported by the device.
We will add some kind of warning to runtime and/or editor in the future.