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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.