Search Issue Tracker
Fixed in 5.3.2
Votes
72
Found in
5.3.1f1
Issue ID
756194
Regression
Yes
Particle system plays only once
To reproduce:
1. Open attached project
2. Open "_Test" scene
3. Play the scene
4. Click "Restart" button
5. Observe appeared particles
6. Click "Restart" button after particles become invisible (2 seconds)
Expected behavior: particle system should play once more (see gif, older versions behavior is shown)
Actual behavior: particle system is not playing again (see gif)
Regression introduced from 5.3.0f4 to 5.3.0p1
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
TimmermanV
Feb 04, 2016 20:32
I can confirm mikklo´s message. Version 5.3.2f1 still has the issue. In my project, the affected particle systems are using simulation space 'Local' as well. If I set the simulation space to 'World', the issue disappears.
mikklo
Jan 30, 2016 19:58
Not fixed! If Simulation space is Local, the same problem appears on 5.3.2f1.
RudyV
Jan 30, 2016 19:56
This is crazy. Children particle systems play and stop as expected but the parent particle systems play only once. Also, it plays only once as long as "Play()" is the last line of the method. Otherwise, it does not play at all while the children systems work fine. The past two upgrades have been destructive to my game in various ways. I'm going to play it safe and stop upgrading once this bug is fixed.
TheValar
Jan 30, 2016 01:23
Yay!!! It's fixed :D
CreativeChris
Jan 28, 2016 11:31
This fix is coming in the first patch of 5.3.2, should be released today.
bazidle_gi
Jan 28, 2016 11:05
I am not entirely sure now, if "playing only once" was the case after all in my project.
Alleged temporary fixes listed in the comments didn't work for me (SetActive(false) -> SetActive(true)).
What I determined some time ago was the bug in the ParticleSystem.Emit() method: I fixed my issues by switching from ParticleSystem.Emit(count) to ParticleSystem.Emit(emitParams, count). After that, particle systems started to behave properly.
E.g. http://pastebin.com/zwxBUN4U
Still, I guess my issue is somewhat related to this one
renaudcor
Jan 28, 2016 10:31
A bit disconcerted . Such an error should have been set in the update that you bring . Scheduled to be resolved in 5.3.2 , still not . This is problematic and painful.
ArvydasS
Jan 28, 2016 10:25
Still Present in 5.3.2!
bluC8
Jan 20, 2016 17:02
So it says fixed in 5.3.2. Does that mean we wont get a patch for this until the next update?! In other words, it's NOT fixed?
PieterAlbers
Jan 18, 2016 09:00
I can't believe this isn't addressed already.