Search Issue Tracker
Fixed in 4.6.1
Votes
0
Found in
4.6.0b20
Issue ID
636761
Regression
No
Physics2D.RaycastAll don't calculate hit for CircleCollider2D if distance parameter is set to float.MaxValue
To reproduce this bug:
1. Open the attached project
2. Open 'test' scene
3. Press play
4. Notice in the console that only RaycCasterBox indicates a hit
5. Select 'RayCasterCircle' in the hierarchy
6. Uncheck 'Max Value Distance' and now distance will be set to 1000.0f instead of float.MaxValue
7. Now everything works fine
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment