Search Issue Tracker
Fixed in 2017.3.0f3
Won't Fix in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.1f1
Issue ID
924743
Regression
No
3 Particles with mesh Render Mode and the same material are rendered with 3 draw calls instead of 1
Steps to reproduce:
1) Download attached project '561f1.zip' and open in Unity
2) Open scene 'ParticleBatchIssue' and press Play
3) Enable Frame Debugger
You will see in the Frame Debugger that particles with mesh Render Mode and same material are rendered with 3 draw calls
Expected result: Particles with mesh Render Mode and same material should be rendered with 1 draw call (check attached image 'expected.png')
Actual result: Particles with mesh Render Mode and same material are rendered with 3 draw calls (check attached image 'actual.png')
Reproduced with:
5.5.4p3, 5.6.3f1, 2017.1.0p3, 2017.2.0b7, 2017.3.0a4
Note: all 3 particles are rendered with 1 draw call(check Frame Debugger) if Render Mode is Billboard
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment