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
- Editor UI Text is displayed incorrectly or blank, and "Unable to load font face for [System Normal]." and other warnings are spammed when Editor Font is set to System Font and TMP Package is imported
- TabView with icons is smaller in height then other tabs with text
- [iOS] Error shows and "Microphone.GetPosition" logged as zero when "Microphone.Start()" is called the first time while a microphone is busy in another app and the second time when the microphone is released
- "Check for Updates" Fails to Connect to Update Server
- "Validation: Write range..." errors when creating and destroying GraphicsBuffer rapidly in WebGPU
Add comment