Search Issue Tracker
Fixed in 5.2.3
Votes
1
Found in
5.1.0f3
Issue ID
718508
Regression
No
[OverlapArea] Collider isn't detected in some positions
Steps to reproduce:
1. Open attached project
2. Open scene "scene"
3. Select "GameObject" in hierarchy and notice that its Y position is 19
4. Run scene and notice that console is spammed with Null. It means that OverlapArea haven't found any colliders in the area.
5. Change Y position to 19.0001 or 18.999, run scene and notice that this time collider is detected
Note: For OverlapArea coordinates, collider bounds are used.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment