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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 2019.3):
need to reactivate once the PhysX4 upgrade is in trunk, as the case looks fixed there.