Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2019.4
2020.1
2020.1.0b3
2020.2
Issue ID
1276431
Regression
No
[DX12] DrawMeshInstancedIndirect fails to render opaque pass when DX12 is used for standalone builds
How to reproduce:
1. Open the attached project
2. Check if DX12 API is used
3. Build the TestScene
4. Launch the Build and observe the screen
Expected result: All meshes are rendered the same way as in Editor
Actual result: Meshes are either not rendered at all or they become mangled(Depending on HW used)
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Could not test with: 2018.4.27f1(Project scripts would break upon downgrade)
Notes:
1. Graphics APIs tested: D3D11, D3D12, Vulkan, OpenGLCore. The issue would only reproduce on DX12
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
- [iOS] Crash on ScriptingGCHandle::Acquire when calling RequestUserAuthorization without using yield for pending authorization
- Particle is not visible in RenderTexture when Renderer's material is set to Default-Particle and Camera's BG Alpha is set 0
- [Physics] Character Joint jumps around when following Kinetic Rigidbody
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
Resolution Note (fix version 2020.2):
Fixed in - 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in - 2020.2.3f1
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.21f1