Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2017.3.0a1
2017.3.0f3
Issue ID
1124570
Regression
No
NavMesh.SamplePosition finds the closest point on the different Y position when an agent cannot find a path
How to reproduce:
1. Create a new project
2. Import the attached "NavMesh_Bug.unitypackage" asset's package
3. Open "JoinedNavMeshScene" scene and play it
4. Click on the NavMesh space on the black cube
Expected result: NavMesh.SamplePosition finds the closest point on NavMesh on the same X-Z plane
Actual result: NavMesh.SamplePosition finds the closest point on NavMesh on the different Y position
Reproducible: 2017.3.0a1, 2017.4.20f1
Can't reproduce: 2018.1.9f2, 2018.3.5f1, 2019.1.0b2, 2019.2.0a2, because of a lot of 'The type or namespace name ... could not be found' errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment