Search Issue Tracker
By Design
Votes
0
Found in
5.6.3p2
Issue ID
953143
Regression
No
Physics2d Boxcast distance is less than it should be
How to reproduce:
1. Download attached project files and open "testPrecision" scene
2. Enter Play Mode and press "Test" button
3. In Console Window Observe that the distance is 0.995, but should be 1
4. Notice the distance 2 3 4 in Console Window when the boxes are touching only the edges
Actual result: Physics2d Boxcast distance is less than it should be. Box coordinates are (2,0), RaycastHit2D hit2d = Physics2D.BoxCast(new Vector2(0f, 0f), new Vector2(1f, 1f), 0, new Vector2(1f, 0)); The distance is 0.995, but it should be 1.
Reproduced with: 5.5.4p3, 5.6.3p4, 2017.1.1p3, 2017.2.0f1, 2017.3.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Text is unreadable when DLSS is applied to the Canvas with Render Mode set to World Space
- NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
Add comment