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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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