Search Issue Tracker
By Design
Votes
1
Found in
2017.4.1f1
Issue ID
1040418
Regression
No
NavMesh.SamplePosition calculates position between nearest points incorrectly
How to reproduce:
1. Open given Unity project
2. Enter "BugScene" scene
3. Notice 3 green lines in the scene menu
4. Try to move "WRONG!!!_NavMeshSamplePosition_Checker"
5. Notice that line is connecting randomly
Expected result: According to the documentation, NavMesh.SamplePosition() finds the closest point
Actual result: Lines are connected randomly
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.2f1, 2017.4.4f1, 2017.3.2f1, 2017.2.2p2, 2017.1.4f1
Comments (1)
-
michaelday008
Oct 04, 2019 10:50
I've added my feedback and photo about this bug here:
My post: https://forum.unity.com/posts/5030135/edit
As you can see from the photo and forum post, it's returning a point 2 meters away downward rather than a point 0.1 meters away sideways like it should.
2019.1.10f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2021.1.X):
SamplePosition() is by design looking for a position on the NavMesh by first projecting the point up or down, and only when that does not return any result will the method search for other positions nearby. This behaviour is useful for some queries that need to inspect the NavMesh in a 2D plane.
The documentation will be updated to reflect this behaviour.