Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
Issue ID
727734
Regression
No
BoxCast and CircleCast return imprecise data
This issue has no description.
Comments (1)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
fixwind
Feb 14, 2016 06:19
Hopefully v5.4 will be out soon. I'm having issues with the raycast hit points not being the same for raycasts versus boxcasts. If I cast a ray from the side of a boxcast area, the raycast hit point and the boxcast hit point will be slightly different from each other on both the X and Y axes. The same is true for circlecasts versus raycasts.
This causes problems for me when trying to mix the different types of casts for collision detection.