Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
14
Found in
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1197062
Regression
No
PathQueryStatus.Success is returned in a Script but the Path can't be resolved when using a highly detailed NavMesh
How to reproduce:
1. Open the attached project's "case_1197062-Project.zip" Scene labeled "SampleScene"
2. Enter the Play Mode
3. Click the topmost Button to see a resolved Path shown
4. Click the Button below and Inspect the Console Window
Expected result: The Path is resolved and there are no errors in the Console Window
Actual result: The Path is not resolved and an error is thrown in the Console Window
Reproducible in: 2019.2.13f1, 2019.3.0b11, 2020.1.0a14
Couldn't test with Unity 2018.4.13f1 and lower versions (Errors are thrown in the Console)
Note: Changing the NavMesh Surface Component's Tile Size to a lower value fixes the issue in some Transform Positions on the Mesh
-
hertz-rat
Apr 20, 2020 10:37
My navmesh agents are also failing to find paths when the path is too long, but I do not get a console error and when I log the status I see 'invalid' instead of 'partial.'
My map is maybe 200x300 in size (but u shaped), has no moveable navmesh obstacles, and no offmesh links. By attempting to travel via two separate move actions, there is no problem getting from A to C.
2019.3.9
-
Whipexx_DigitalSun
Jan 10, 2020 10:53
To be expected, but also reproducible in 2019.3.0f1.
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
- [Xcode] "InfoPlist (English)" is required when "InfoPlist (English (United States))" already exists
- [tvOS] Crash when closing the On Screen Keyboard with tvOS version <15.0
- Temporal Anti-aliasing (TAA) produces severe artifacting when quality set to Very High
- [iOS] Player crashes when using “WebCamTexture” on specific iOS devices
- [Linux][IL2CPP] Player crash call stack is not displayed when the build is run with "-batchmode -nographics" arguments
Resolution Note (fix version 2021.2):
The maximum number of nodes the NavMeshNodePool supports is 65,535. A check and exception has been added to prevent the instantiation of a node pool with improper size. The documentation will now reflect the valid range of values, 0 to 65,535. Fixed in Unity 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.14f1