Takes too long to detect character is stuck

[liquidsnake1989 2]

When the bot tries to move to a herb/ore node and it flies against a tree or hill or something, it takes too long to detect he is stuck. It takes about 10 seconds before the log sais: 
[N] 18:58:02 - [MovementManager] Think we are stuck
[N] 18:58:02 - [MovementManager] Trying something funny, hang on

Most of the times, it will also 'give up' the node and just move on.

 

Is it possible to adjust the time it takes before the bot tries an un-stuck movement?

[Droidz 2708]

Hello, try to active option "Use lua to move"

[liquidsnake1989 2]

I have already enabled the option 'Use lua to move' 

[Droidz 2708]

Hello, Can you share your log file please ( https://wrobot.eu/forums/topic/1779-how-to-post-your-log-file-with-your-topic/ ).

[liquidsnake1989 2]

Here is a log:

 

1 aug 2017 12H52.log.html

[liquidsnake1989 2]

ANother one, it just happens so it should be on the last couple of lines of the log

3 aug 2017 08H58.log.html

[Droidz 2708]

Try to increment your min latency (in advanced general settings) at 400

[liquidsnake1989 2]

My min latency is now 400 but still it hangs for a very long time in a tree and the gives up on the node and moves on.

9 aug 2017 11H04.log.html

[ScripterQQ 88]

Confirmed, sometimes it says "Too far away" then mount and flies away ignoring the node.

[Droidz 2708]

I'll check that, I comeback here when it is fixed