Search Issue Tracker
By Design
Votes
0
Found in
2018.2.0b6
2018.2.8f1
Issue ID
1083905
Regression
Yes
OnParticleCollision() isn't called for Colliders which are marked as triggers
Repro steps:
1. Open QA attached project "repro_1083905"
2. Enter Play Mode
3. Observe the Console
Expected: The name of the of the "Blue" GameObject which is marked as a trigger is logged when particles collide with it
Actual: Only the name of the "Red" GameObject is logged when particles collide with it
Reproducible with: 2017.4.12f1, 2018.2.12f1, 2018.3.0b5, 2019.1.0a4
Not reproducible with: 2017.4.6f1, 2018.2.0b5
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
- 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
Resolution Note:
This bug is By Design. It changed in Unity 2018.3 because we fixed this bug: https://issuetracker.unity3d.com/issues/2d-particle-system-is-colliding-with-2d-colliders-even-when-collider-is-set-to-trigger