Search Issue Tracker
Fixed in 2019.2
Votes
18
Found in
Issue ID
753940
Regression
Yes
[Particles] Particle system glitches when using Simulate from script, after the first loop
1) Open scene 'scene'
2) Press play, the left system will glitch after a few seconds.
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
- Results of Texture ScaleMode is not intuitive when parent has a width or height set to pixel value and the other is set to auto
- Crash regression on ComputeShader inspector "Compile and show code" button
- Silent Crash on Windows when opening a project created in Ubuntu
- Profiler mouse and keyboard navigation is inconsistent and skips entries when analyzing Instantiate calls from a unit test
- Unmaximizing Editor Window results in a new window being created and deleted
DMINATOR
May 08, 2019 17:31
Yes, I've checked it on 2019.2.0a14 and looks like this issue is fixed. Wish it would be released earlier...
SugoiDev
Oct 29, 2018 03:17
This has been hitting me too for some time now.
It doesn't have many votes and is a somewhat advanced usage, so we can't expect it to be fixed any time soon.
FeastSC2
Oct 08, 2018 14:16
This problem is still there, here's a thread about it on Unity forum:
https://forum.unity.com/threads/particle-system-preview-scrubbing-by-script.565648/#post-3762199
xophiix
Jul 25, 2018 03:28
please..please fix it... we wait for almost 1 year
Ludiq
Jul 16, 2018 18:51
I would argue this is definitely not a "minor or cosmetic issue"; it renders the entire particle system useless under simulation. The bug has been reported over 3 years ago!
loopyllama
Feb 03, 2017 13:26
Need this long-standing issue fixed as soon as possible. Thank you.
panta
Feb 02, 2017 05:28
Also seeing this - it really makes using Shuriken difficult for any time manipulation games
Thelo
Jan 30, 2017 22:26
This issue prevents us entirely from using ParticleSystem.Simulate, which is a core feature of the particle system that has never worked correctly to my knowledge.
We have been waiting on a fix to this for over half a year. Please fix this post-haste.