Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
11
Found in
2018.4
2020.1.5f1
2020.2
Issue ID
1278829
Regression
No
NavMeshQuery's BeginFindPath returns an ArgumentException when the Agent Type ID value is negative
How to reproduce:
1. Open user-submitted project (UnityPathfindingTesting.zip)
2. Open the PathfindingTesting scene
3. Enter Play Mode
4. Click the 'Calculate&DrawPath-Experimental' button
Expected result: path is calculated successfully
Actual result: an ArgumentException is thrown: "The start location doesn't belong to any active NavMesh surface"
Reproducible with: 2018.4.27f1, 2019.4.12f1, 2020.1.7f1, 2020.2.0b6
Notes:
Agent Type ID can be checked in the Debug Inspector
Issue can also be observed by creating new agents and making sure their randomly generated Agent Type ID value is negative
Issue will not occur when creating new agents after making sure their randomly generated Agent Type ID value is positive
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
- 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
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7
Resolution Note (fix version 2020.2):
Fixed in 2020.2.1f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.19f1