Search Issue Tracker
Fixed in 4.3.X
Votes
0
Found in
4.3.0b3
Issue ID
564774
Regression
Yes
2D collision filtering is broken
2D collision filtering is broken.
Regression - not present in 4.3.0b2 and 4.3.0b1
Reproduced only on 4.3.0b3
2) How can we reproduce it using the example you attached.
For Win 7:
1. Open the scene.
2. Press play. Notice the cubes do not collide.
3. Open Physics2DSettings(in menu Edit->Project settings) and look at the Layer Collision Matrix. You can see that Player/Ground collision is checked, so they're supposed to be colliding.
4. Check the box for Player/Player collision.
5. Press play. Now they will collide. This makes no sense.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
Add comment