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
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
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