Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0a1
2017.4.10f1
Issue ID
1099479
Regression
No
NavMeshAgent teleports from one position to another when following the NavMesh trail
How to reproduce:
1. Download and open the Test.zip project from the provided link bellow
2. Enter the Play mode
3. Inspect the Scene view
Expected: NavMeshAgent follows the NavMesh trail
Actual: NavMeshAgent teleports from one position to another
Reproduced on: 2017.4.15f1, 2018.1.9f2, 2018.2.16f1, 2018.3.0b10, 2019.1.0a9
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note:
Will be fixed as part of substantial refactoring work planned for the NavMeshAgent.
More information will be communicated on the Navigation forum. https://forum.unity.com/forums/navigation.79/