Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.2.0f3
Issue ID
974827
Regression
Yes
SphereCast returned hit point snaps to closest edge of mesh collider when moved
1. Open the attached project "SphereCast Hit Point Edge Snap.zip"
2. Load "Test" scene
3. Go to scene view window and select Wireframe shading mode
4. Slowly move the "SphereCast Test" game object along X or Z axis (Best to use Move Transform tool + zoom as shown in the attached videos)
5. See how the hit point (cyan marker) snaps to mesh edges ("sticky.mp4")
Expected result: the hit point should transition smoothly as shown in "smooth.mp4"
Reproduced with: 5.5.0b1, 5.6.4p4, 2017.1.2p3, 2017.2.0f3, 2017.3.0f1, 2018.1.0a7
Not reproducible with 5.4.6f3
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version 2019.3):
need to reactivate once the PhysX4 upgrade is in trunk, as the case looks fixed there.