Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.2.14f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1111328
Regression
No
Position of the RaycastHit.point is inconsistent when using Physics.BoxCast and Box Collider
How to reproduce:
1. Open attached project "Case_1111328_repro.zip"
2. Open "123" scene
3. Enter Play Mode
4. Open Scene Window
5. Observe the red sphere that indicates the position of the RaycastHit.point position
Expected result: The red sphere is in the middle of the X and Y axes
Actual result: The red sphere is in the bottom left corner of the "Cube" Box Collider
Reproducible with - 2017.4.20f2, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Notes: Change X or Y position of the "Cube" GameObject and notice how the position of the red sphere is correct once Physics.BoxCast and "Cube" Box Collider does not align perfectly.
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 when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note:
I wouldn't count on the hit point returned in this case because we have a face to face touch and any point returned that belongs to the intersection of faces would be correct formally speaking. As far as I could see, all the return results do belong to that intersection so it's not a bug per se I'm afraid.