Search Issue Tracker
Fixed in 2020.2.9f1
Fixed in 2020.1.X
Fix In Review for 2019.4.X
Duplicate in 2020.3.X
Votes
2
Found in
2019.3
2020.1
2020.1.0b4
2020.2
Issue ID
1235425
Regression
No
SRP Batcher sets the correct buffer for the first Draw call in the sequence but does not change it for the next calls
How to reproduce:
1. Open the attached project named "Case_1235425"
2. Open the SampleScene
3. Enter Play mode
4. Move the camera around and observe the meshes
Expected result: All three meshes are rendered normally with their vertices drawn in expected positions
Actual result: Only one mesh is rendered normally at the time while others use the wrong vertices position buffer
Reproducible with: 2019.3.15f1(7.3.1), 2020.1.0b10(8.1.0), 2020.2.0a13(9.0.0-preview.13, 10.0.0-preview.1)
Could not test with: 2018.4.23f1(Unable to downgrade the project, and the package was still in a preview state for this stream)
Notes:
1. The meshes are rendered as expected when SRP batcher is disabled
2. Graphics APIs tested: D3D11, D3D12, Vulkan
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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Resolution Note (fix version 2020.2.9f1):
Fixed in: 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b15