Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.6f1
2023.3.0b3
6000.0.0b11
Issue ID
UUM-60691
Regression
No
Wrong GameObject is reported in “OnParticleCollision” when using the Particle System Collision module and using the “Collides With” layers setting
How to reproduce:
1. Open the attached “collisions.zip” project
2. Open “Particle collision test” Scene
3. Open Project Settings > Tags and Layer and set “User Layer 6” to “test”
4. In the Hierarchy window, select “GameObject” GameObject
5. In the Inspector window, open the “Collision” tab of the “Particle System” Component
6. Set “test” in “Collides With” field
7. Select “GameObject” GameObject that’s inside “Cube” GameObject
8. In the Inspector window, change “Layer” to “test”
9. Select “Cube” GameObject and remove the “Rigidbody” Component
10. Enter Play Mode and observe the Console window
Expected result: “Other object: Collision object, other layer: test” is logged
Actual result: “Other object: Cube, other layer: Default” is logged
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible on: No other environment tested
Note: not reproducible without a “Rigidbody” Component
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.