Search Issue Tracker
Fixed in 4.6.4
Votes
0
Found in
5.0.0b22
Issue ID
669805
Regression
No
[Physics2D] Physics2D.BoxCast less precise than Physics2D.Raycast
To reproduce:
- Open the attached project and the scene
- The test scene in the attached project features a cube that's performing both a boxcast and a raycast towards the ground. Both casts are performed in the same direction with the same distance.
- Observe that the values returned in their respective RaycastHit2D objects, however, are noticeably different.
The RaycastHit2D object returned from the raycast is 100% precise. The hit returned from the boxcast, however, is not. Notice that the hit point from the boxcast has a Y value of -1.9975 when it should be exactly 2.0. The distance and fraction values returned from the boxcast aren't useful at all because boxcast doesn't expose the origin point of the ray that returned the hit. In contrast, the distance and fraction values from the raycast hit are 100% accurate.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment