Search Issue Tracker
Fixed in 5.3.0
Votes
1
Found in
5.0.1f1
Issue ID
689159
Regression
Yes
SphereCast returns incorrect collision point for a scaled non-convex mesh
To reproduce:
1. Open attached 5.0 project (don't change layout, it makes it easier to notice the problem)
2. Run scene Testscene
3. Move mouse around in game view (If mouse is over the mesh a raycast is calculated to find the collision point. If there is an intersection, it will do a SphereCast to do a sphere collision test.)
4. Notice that the sphere cast will not return the closest collision, but instead it seems to return the first collision that it finds (on screenshots attached it is marked as yellow sphere, green line is an angle between them, which should be around 0 on that surface)
http://screencast.com/t/03dNam0wwMcG
Works fine if mesh is uniform or convex
http://screencast.com/t/GOGf9rYQ5
Regression from 4.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment