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
7
Found in
2017.1.1f1
Issue ID
956902
Regression
No
The remaining distance of the Nav Mesh Agent is equal to Infinity even though the agent is moving along the path
To reproduce:
1. Open the project, attached by the user (NAVMESHAGENT REMAINING DISTANCE.zip)
2. Open the "scene 1 Source( 27, 0, -15 )" scene
3. Enter Play mode
4. Observe the console
Expected: NavMeshAgent.remainingDistance is not Infinity
Reproduced in 5.6.4f1, 2017.1.1f1, 2017.1.2f1, 2017.2.0f3, 2017.3.0b4
Could not reproduce in 5.5, quite a few errors in the console
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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/