GB2 - attempting to move to some unknown location regardless of which profile I load

Doesn't matter which GB2 profile I load, it's trying to move to the following location.

[17:40:07.748 D] [Flightor] We can neither fly nor run to the destination.
[17:40:07.931 N] Latency to Buddy service: 61 ms
[17:40:08.847 D] [Flightor] Failed ground nav from <2841.79, 6482.29, 206.326> to <755.8647, 6507.188, 112.2476> with status PathGenerationFailed

[17:51:18.160 D] [Flightor] We can neither fly nor run to the destination.
[17:51:19.258 D] [Flightor] Failed ground nav from <2841.79, 6482.29, 206.326> to <755.8647, 6507.188, 112.2476> with status PathGenerationFailed



Something is stuck in cache, maybe?

Log files are small because I didn't let it sit there for 15 minutes before I hit stop. Was just testing to make sure it did the same location for every profile.

 

You've replied with that quote to me multiple times when you obviously haven't bothered to look at the attachments. There are two log files attached to that post already. They're renamed because I was testing, but those are both complete log files from the time I hit "Start" to the time I hit "Stop". They both demonstrate the error, and contain all information your log file contains with nothing extraneous. i.e. I didn't leave the bot running for 2 hours and then attach a ridiculously long log file when I could easily replicate the problem in 30 seconds. If your log file doesn't contain enough information for you to debug with, consider adding a "debugging" option that will turn the logging up to verbose. In any event, I know you see a billion posts in here that don't attach log files, but it's really annoying when I do exactly what's requested and yet still get this same canned response.

 

I guess they have no clue how to fix this problem I have exatced the same problem as you and gut sometime 5minutes farm and than stop with the same error or after i hit start the it does nothing and the log looks like yours.

I hope i am wrong with the no clue thing and that in a few days a new patch comes and fix this