Search Issue Tracker
Not Reproducible
Votes
23
Found in
5.4.0b17
Issue ID
797694
Regression
No
CPU spikes when moving Particle Systems in game; Material.SetPassUncached taking a lot of time?
Reproduction Steps:
1. Open User's project
2. Make sure Profiler is visible
3. Play scene
Note: One or two spikes usually appear at the beginning of run, after that it is random.
Expected behaviour: no CPU spikes, constant CPU workflow.
Reproduced in versions: Unity 5.2.4f1, 5.3.4f1, 5.4.0b12, 5.4.0b17, 5.4.0b18
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
HahnSC
Mar 28, 2017 10:41
And I was found this problem in 5.4.2f2.
Only 7 particles in my scene. The profiler shown ParticleSystem.Update() take nearly 80ms.