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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment