Search Issue Tracker
Duplicate
Votes
1
Found in
2017.3
2018.2.14f1
2018.3.0a1
2019.1.0a1
Issue ID
1098589
Regression
No
RaycastHit2D provides slightly incorrect centroid and distance values when casting Physics2D capsule, box or circle shapes
Steps to reproduce:
1. Open attached project "Physics Test.zip"
2. Play the Scene1
3. Press "a"
4. Look at the Console, also select "Hit Capsule" object in Scene to see that it's slightly inside the wall
Expected result: centroid is (2, 0), distance is 2, capsule is touching the wall
Actual result: centroid is (2.005, 0), distance is 2.005, capsule is slightly inside a wall
Reproducible: 2017.4.17f1, 2018.3.0f2, 2019.1.0a12
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
This is a duplicate of issue #1098169