Navigation returned a partial path. Destination may not be reachable by mesh!

[MasterLeon79]

Please see logs.

Is this an issue with kicks profile or with the nav-server?

 

[MasterLeon79]

Please see logs.

Is this an issue with kicks profile or with the nav-server?

Ok nevermind. I am currently working on Profiles (without classquests and classquests only) based on kicks profiles. I was able to "fix" it myself by adding UseTransport to fly the bot to the nearest location. I wonder though if the bot shouldn't have gone there by foot.

 

[MasterLeon79]

Ok nevermind. I am currently working on Profiles (without classquests and classquests only) based on kicks profiles. I was able to "fix" it myself by adding UseTransport to fly the bot to the nearest location. I wonder though if the bot shouldn't have gone there by foot.

hey guys. Sorry but I need to be sure that these errors are not realated to mesh issues. While editing kicks files this is already the 10th time in over an hour ( I watch the bot every 5-10 minutes.. freaky i know) where i needed to unstuck the bot an move the bot partially until it rehooks. In this particular example I had to relocate to in to a building after a long way from the stuck point and even in the instanced building I had to move him almost as close to the target.

I know I can fix this by adding moveto paths but If this is related to mesh errors I'd rather leave the profile as it is and wait for the fixes.

Generating path to Hotspot <-31.61895, -22.92897, -36.87946>
Nav Service path generated.
Generated path to <-31.61895, -22.92897, -36.87946> (Hotspot) with 2 hops.
Moving to next hop: <-31.61895, -13.4, -36.8>, T: None (Hotspot) D: 0,01092339
Navigation reached current destination. Within 9,51838
Generating path to Hotspot <-31.61895, -22.92897, -36.87946>
Waiting for path request to finish...
Nav callback called.
Navigation returned a partial path. Destination may not be reachable by mesh!
Start/Stop Button Clicked!

 

[Cryogenesis]

This problem occurs when there is a sleight hight difference between 2 objects.
Lets say stairs or entering buildings are most culprits.
What you need to do is figure out where this problem occurs.
So its sadly walking a bit manually and start bot again.
then its adding a moveto just in front of this culprit and one behind it with a condition ignoremesh="true".
Only then you will overcome this mesh problem.

Those things cannot be remeshed as its a 'gameproblem'.

You can also get these errors on planets like nar shaddaa when there is travel involved between these spots or missing elevators.
If elevators are the problem you need to give aevitas, 4 spots (mylocation dumps).
in front of the elevator before getting on, one on the elevator top and bottom and lastly again in front of the elevator.

If none of the above work, then it MIGHT be a subzone thats not meshed.