Search Issue Tracker
Active
Votes
11
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
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
- Object references are not loaded after you git checkout to another branch
- Only one of multiple copies of the same StateMachineBehaviour script is visible when added to the Animation state
- [XR][Vulkan][Oculus] Crash in hybrid renderer BeginRenderPass
- [Mobile]Dynamic batching is not working when working with sub mesh on a mobile device
- [Hub] Warning pop-up contains <strong></strong> when attempting to add a project to the list of projects while it's already open
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_WildFrame
Jan 10, 2020 10:53
To be expected, but also reproducible in 2019.3.0f1.