Search Issue Tracker
By Design
Votes
0
Found in
5.3.3p2
Issue ID
778669
Regression
No
NavMeshAgent.remainingDistance doesn't work with two NavMeshAgents in the scene
NavMeshAgent.remainingDistance doesn't work with two NavMeshAgents in the scene.
According to the docs, "If the remaining distance is unknown then this will have a value of infinity." In the script I compare it with zero.
To reproduce:
1. Open the scene "TestNavMeshAgent" and run it.
2. See that one of the bears is destroyed on Start (randomly is destroyed Bear or Bear (1)).
If you disable one of the NavMeshAgents, everything works fine.
Reproducible with 5.4.0b10, 5.3.4f1, 5.2.4p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment