Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.1.0a1
2018.1.0a7
2019.1.0a6
Issue ID
1094348
Regression
Yes
[Android] [Vulkan] Meshes with Standard shader and GPU instancing enabled are not rendered correctly on Adreno GPUs
Steps to reproduce:
1) Download attached project and open in Unity
2) Build and run project on a device
3) Once the project is launched, check the screen and you will see that half of the meshes are not rendered/ slightly visible
Expected result: All meshes should be rendered with GPU instancing enabled (check attached image)
Reproduced with:
2018.1.0a7, 2018.1.0b1, 2018.1.0f1, 2018.1.5f1, 2018.3.0b8, 2019.1.0a6
Not reproduced with:
2017.4.13f1
Regression since:
2018.1.0a1 - 2018.1.0a7
Devices under testing:
Reproduced with:
VLNQA00123 Google Pixel 2 XL*, OS:9, CPU:arm64-v8a, GPU:Adreno (TM) 540
Not reproduced with:
Samsung Galaxy Note8*, OS:8.0.0, CPU:arm64-v8a, GPU:Mali-G71
Black screen using 2018.1.0a1 - 2018.1.0a6, so I wasn't able to find the exact regressed version
----------------------------------
Fixed in 2019.1.0a9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
Add comment