Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.3.0a3
Issue ID
727785
Regression
No
When Destination is far away from the NavMesh, the agent does not go to closest spot on Navmesh
To reproduce the issue follow the steps:
1. Open attached "New Unity Project 9 - AI Test" project
2. Open "Untitled" scene
3. Enter play mode
Expected result: Cube goes to spot directly above Sphere
Actual result: Cube does not walk to the spot
Note: If the sphere is moved directly upwards to be closer to NavMesh, the Cube starts walking
Note#2: If the Destination is too far away from the NavMesh, then SetDestination will return false and the agent will not work. To go around this, set the destination to a closer point to NavMesh itself.
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
- Packages cannot be added from a registry that returns invalid publish dates [Windows-only]
- Physics.SyncColliderTransforms syncs every collider when the local position hasn't changed
- [GPU PLM] Part of baked shadows are broken when hitting a backface
- [DX12] Nothing is being rendered when using Alt+Enter to maximize a resized windowed player
- [DX12] Player freezes and/or crashes when switching between full screen modes
DanjelRicci
Feb 01, 2018 09:34
This issue is still alive in Unity 2017.3.0p3. I'm getting mad trying to get a workaround for this since we really need to push some updates. NavMesh.SamplePosition works almost ok, while NavMeshAgent.SetDestination totally fails most of the times and gets a point on seemingly random parts of the NavMesh.