Search Issue Tracker
Fixed
Fixed in 1.4.X - Physics
Votes
0
Found in [Package]
1.4.2 - Physics
Issue ID
ECSB-1789
Regression
No
CollisionFilter.IsEmpty ignores GroupIndex when used with collision groups
Reproduction steps:
1. Open the attached “IN-120247.zip” project
2. Open the “SampleScene”
3. Enter Play mode
4. Observe the Console
Expected result: The Raycast collides with the Cube, as both utilize GroupIndex 42
Actual result: The Raycast doesn't collide with the Cube, “No collision” logs are visible
Reproducible with: 1.3.14, 1.4.2 (6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2)
Reproducible on: Windows 11
Not reproducible on: no other environments tested
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
- Unclear warning message in Rendering Debugger about the Play mode Debugger Overlay
- [Android][iOS] Particles are not affected by External Forces when loaded from AssetBundles with Strip Engine Code enabled
- Rendering Debugger "STP" and "Reflection Probe Atlas" overlays don't change size when changing the "Map Size"
- "ArgumentException" error when using CameraCaptureBridge with post-processing off and when rendering to a RenderTexture
- Shaders read from the buffer unconditionally
Resolution Note (fix version 1.4.X - Physics):
Fixed through correction of CollisionFilter.IsEmpty property. Fix will be deployed in the next 1.4.x release.