Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.5f1
Issue ID
801105
Regression
No
[Physics2D.BoxCast] Using a float and Infinity in BoxCast distance returns different distances
1. Open the attached project
2. Open the available scene
3. Play scene
4. Check the console
Having the BoxCast distance set to 0.009407002 returns 0.0047035220
Having the BoxCast distance set to infinity returns 0.0030002590, which is the true value
This difference can potentially cause problems.
Workaround: May be avoided if using Mathf.Infinity as BoxCast distance
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