Search Issue Tracker
Active
Votes
0
Found in [Package]
1.4.0-exp.2 - Physics
Issue ID
ECSB-1722
Regression
No
PhysicsWorldSingleton.OverlapSphere and similar methods return hits for each face of MeshCollider instead of the collider itself
How to reproduce:
1. Open the “Test.zip“ project
2. Open the “SampleScene“
3. Enter Play mode
4. Observe the Console
Expected result: Number 6 is logged (for each collider)
Actual result: Number 1532 is logged
Reproducible in: 1.3.8, 1.4.0-exp.2 (2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5)
Could not test in: 0.51.1-preview.2, 1.0.8 (2022.3.63f1, 6000.1.7f1) (Unsolvable PlayMode errors)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: BoxCollider and other primitive type colliders return only one hit each; only MeshColliders are affected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment