Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.22f1, 2023.2.14f1, 6000.0.0b11
Votes
0
Found in
2021.3.35f1
2022.3.17f1
2023.2.10f1
2023.3.0b7
6000.0.0b11
Issue ID
UUM-64297
Regression
Yes
Legacy particle systems with mesh GPU instancing can show visual corruption in certain conditions
Steps to reproduce:
The repro case is problematic due to complexity as it requires a complicated enough scene to run into particle instance buffer synchronization issues. This requires multiple particle systems being observed at once, multiple render passes for each including depth, projector, and BIRP forward pass, graphics jobs enabled, and unknowns related to scene complexity.
This has been seen on a large customer project with fixes verified there.
This bug has seen several dsicussion threads but the closure is here: https://unity.slack.com/archives/C06TQ6134/p1700045776981079
Actual results:
When viewing more than one particle system visual corruption can occur where meshes appear to swap over between two seperate particle systems (or entirely overlap) rapidly and create a flickering effect.
Expected results:
Particle systems should only be rendering the configured data.
Reproducible with versions:
2022.3.17f1
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Windows, Android
Notes:
Regression-point is unknown since we can't easily use anything here to test it backward, however we do know that this didn't occur for us in 2019.4 at least.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment