Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.0f1
2021.1
2021.2
2022.1
Issue ID
1345964
Regression
No
Physics2D.SetLayerCollisionMask only affects the row in the 2D collision matrix
How to reproduce:
1. Open the attached project "Physics2D SetLayerCollisionMask Edit Mode Bug.zip"
2. Click Bug > Set Mask
3. Check the 2D collision matrix for MyLayer (Edit > Project Settings > Physics 2D)
Additionally:
1. Open the attached project "Physics2D SetLayerCollisionMask Edit Mode Bug.zip"
2. Open the "SampleScene" scene
3. Press Play, cubes collide and rest on each other (this won't happen if you saved the previous steps)
4. Click Bug > Set Mask
5. Cubes should pass through each other.
Expected result: All of the Checkboxes under MyLayer are unchecked
Actual result: Only the Default - MyLayer checkbox is unchecked
Reproducible with: 2018.4.34f1, 2019.4.28f1, 2020.3.13f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
-
MelvMay
Feb 10, 2022 11:19
Please note, for this fix to work you will need to reassert your settings in the Layer Collision Matrix to remove any corruption from its settings. You can do this by turning-off/on all checkboxes and selecting the settings you want.
You can only toggle the ones that might not be working and they will be fixed for that layer however this won't fix any other corrupt layers.
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
- SHADERPASS has incorrect value when using Shader Graph for Built-In target
- [VFX] Gizmo still incorrectly rendered for a hidden property
- Nested object label indentation is incorrect when using the UI Toolkit Inspector
- Crash on tlsf_free when UI Elements are moved to the side by scrolling
- Setting VideoPlayer.time and pausing results in incorrect player.frame values
Resolution Note (fix version 2020.3):
Fix for this issue is available on Unity 2020.3.27f1 and above
Resolution Note (fix version 2019.4):
Fix for this issue available on Unity 2019.4.35f1 and above