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
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
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