Search Issue Tracker
Fixed
Fixed in 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
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'
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.4.0b9):
Fixed in 6000.4.0b9
Resolution Note (fix version 6000.3.9f1):
Fixed in 6000.3.9f1