Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.32f1
6000.1.0a9
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-91192
Regression
No
The GameObject's layer, which contains the Rigidbody, is used for "RigidBody.SweepTest" when retrieving a collider from a child GameObject with a non-collide-able layer
How to reproduce:
1. Open the “IN-90907-SweepLayerBug.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: “Cube B hit? False“ is logged (“0 - 6 - 0“ log is not displayed)
Actual result: “Cube B hit? True“ and “0 - 6 - 6“ is displayed
Reproducible in: 2021.3.47f1, 2022.3.55f1, 6000.0.32f1, 6000.1.0a9
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- The child GameObject layer is set to (6: NoCollision) where in the collision matrix the logic is set for objects to collide only between layers 0 and 6
- All parent GameObjects have their layers set to (0: Default)
- “0 - 6 - 6“ respectively is the layers of the parent GameObject, the ground GameObject, the child (collider) GameObject
- In the “SweepTest” method, the RigidBody retrieves the Collider from the child GameObject, but its layer is set as one of the parents'
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment