Search Issue Tracker
Fixed in 2017.3.0f3
Won't Fix in 2017.1.X, 2017.2.X
Votes
0
Found in
5.6.1f1
Issue ID
926635
Regression
No
Particle collisions are registered more than one time
To reproduce:
1. Download attached project "Mini-Momentum.zip" and open in Unity
2. Open "Particle Collision Debugger" scene
3. Enter Play mode
4. In Hierarchy select "Weapon" game object
5. In Inspector window, on "Weapon" script press Fire button with left mouse button
Expected Result: In Console observe that it prints this log message:
Collision Events 1/1
UnityEngine.Debug:LogFormat(String, Object[])
Weapon:OnParticleCollision(GameObject) (at Assets/Scripts/Weapon/Weapon.cs:26)
as many times as the Fire button was pressed.
Actual Result: In Console observe that it prints log message many times - from 1 to 14 and more
Reproduced on Unity 5.5.4p1 and 5.6.2p2
Could not check for regression on Unity 2017.1 and 2017.2 because particle system becomes broken
Note: This issue appears on both Windows and OSX
Forum post: https://forum.unity3d.com/threads/particle-system-sub-emitters-colliding.481404
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
Add comment