Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2020.2.4f1
2020.3
2021.1
2021.1.11f1
2021.2
2022.1
Issue ID
1349714
Regression
Yes
Particle Shape Clip Threshold does not affect emitted particle count
Reproduction steps:
1. Open the attached "Project.zip" project
2. Open the "SampleScene" Scene
3. In the Hierarchy, select the "Sparkles" GameObject (MagicWallDisolve > Sparkles)
4. In the Inspector, set the "Clip Threshold" to 1 (Particle System > Shape > Clip Threshold)
5. Restart the "Sparkles" Particle Effect
Expected result: Particles below the threshold should be killed/removed, so the particle count should grow slower as the threshold is increased, in this case, particle count should stay at 0 after restarting
Actual result: Clip Threshold does not affect emitted particle count
Reproducible with: 2020.2.4f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b3, 2022.1.0a2
Not reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.2.3f1
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a6
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b16
Resolution Note (fix version 2021.1):
Fixed in 2021.1.24f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.21f1