Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3
2019.4
2020.1
2020.1.0b10
2020.2
Issue ID
1251305
Regression
No
DrawMeshInstancedIndirect fails to render opaque pass when using OpenGL ES with Android
Steps to reproduce:
1. Open user's attached project "InstancingRenderingBugs.zip"
2. Build it to Android
3. Notice that nothing is being Rendered on the Screen
Expected results: Objects are rendered
Actual results: No objects are being rendered
Reproducible with: 2019.4.0f1, 2020.1.0b13, 2020.2.0a15
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Note: The project crashed with DX12, does not reproduce with Vulkan or DX11. Expected results and results on Android screenshots below. Unable test with 2018.4, the project was braking
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1