Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b11
2022.1
Issue ID
1364520
Regression
Yes
Particles are not detecting 2D Colliders when "Is Trigger" is on
How to reproduce:
1. Open the project "UIToolkit Bug.zip"
2. Select "2D Trigger" in the Hierarchy
3. Enter the Play Mode
4. Switch "Is Trigger" to on and off in the Inspector window
Expected result: Particles are detecting the Collider when "Is Trigger" is on or off
Actual result: Particles are detecting the Collider when "Is Trigger" is off
Reproducible with: 2019.4.30f1, 2020.3.18f1, 2021.1.20f1, 2021.2.0b10, 2022.1.0a7
Notes:
- With different 2D Colliders: Capsule Collider 2D, Circle Collider 2D results are the same
- 3D Collider are detecting the particles when "Is Trigger" is on or off
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 (fix version 2022.1):
Fixed in 2022.1.0a16
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.17f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.39f1