Search Issue Tracker
Fixed in 5.3.2
Votes
24
Found in
5.3.1f1
Issue ID
755677
Regression
Yes
ParticleSystem.IsAlive() always returns True for particle systems with longer duration
Steps to reproduce:
1. Open attached project
2. Open and play 'TestScene'
3. Notice the labels in top left of the game view, the red particle system IsAlive always returns true
The only thing different in two particle systems in the scene is their duration: Red one is 3. green - 2.
Reproduced with: 5.3.1f1
Not reproduced with: 5.3.0f4, 5.4.0b1
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
kevindaluz
Mar 11, 2017 06:16
Still not fixed in 5.4.1f1
srowland
Mar 21, 2016 14:53
Still an issue in version 5.3.3p1(64-bit)
Clavus
Mar 10, 2016 15:29
Still have issues with the isAlive method returning true when it shouldn't in Unity 5.3.3f1.
glennpow
Mar 03, 2016 21:27
This is still an issue for us in 5.3.2p1
josessito
Feb 23, 2016 02:32
This is not fixed
hai4925
Feb 17, 2016 12:15
When I swicth the renderer's Render Mode, a PartileSystem obj's isAlive() in Stretched Billboard Mode will return false,other Render Mode allways return true.
ottolb
Feb 11, 2016 18:45
The workaround I made here was a timer script to disable particles.
callen
Feb 04, 2016 15:05
Can unity devs actually test things before calling them "fixed"? Different people reported it was buggy in *4* different patch releases before 5.3.2, this should have been fixed.
sworderzhang
Feb 02, 2016 10:04
It's not fixed in 5.3.2.f1(64-bit)
Gerrard
Feb 01, 2016 15:51
Still returns true on 5.3.2f1 (64-bit)