Thecamel
Community Developer
- Joined
- Aug 8, 2012
- Messages
- 2,036
[02:18:05.439 D] Moving to next hop: <194.9151, 3.22711, 944.8262> (Moving to gather) D: 2.028234
[02:18:05.621 D] Moving to next hop: <194.1151, 3.22711, 945.7762> (Moving to gather) D: 1.981046
[02:18:05.788 D] Moving to next hop: <193.3651, 3.22711, 946.6762> (Moving to gather) D: 1.856028
[02:18:05.938 D] Moving to next hop: <192.6651, 3.22711, 948.2762> (Moving to gather) D: 2.409333
[02:18:06.171 D] Moving to next hop: <192.5652, 3.22711, 949.0262> (Moving to gather) D: 1.3464
[02:18:06.269 D] Moving to next hop: <190.2998, 3.82711, 987.0831> (Moving to gather) D: 38.68935
[02:18:11.137 D] Navigation reached current destination. Within 3.563459
[02:18:11.170 D] Requesting path on 146 from <190.3454, 3.486769, 986.3572> to <189.8025, 6.117051, 988.6992>
[02:18:11.580 D] Generated path to <189.8025, 6.117051, 988.6992> in 00:00:00.4105171 ms
[02:18:11.720 D] Navigation reached current destination. Within 3.382831
[02:18:11.737 D] Requesting path on 146 from <190.0777, 3.561574, 986.4998> to <189.8025, 6.117051, 988.6992>
[02:18:12.105 D] Generated path to <189.8025, 6.117051, 988.6992> in 00:00:00.3675420 ms
[02:18:12.120 D] Navigation reached current destination. Within 3.382831
[02:22:22.571 N] Stopping the bot. Reason
ushed the stop button.
The bold text, The bot will arrive at node, But just out of reach to start mining the node, 1 step via the keyboard and the bot starts farming again.
My understanding this is NOT a profile issue but a navigation issue.
I have attached a full log
View attachment 13568 2014-10-30 08.16 - stop.txt
I can confirm other uses have had the EXCACT issue with this node looking at their logs they have posted too.
[02:18:05.621 D] Moving to next hop: <194.1151, 3.22711, 945.7762> (Moving to gather) D: 1.981046
[02:18:05.788 D] Moving to next hop: <193.3651, 3.22711, 946.6762> (Moving to gather) D: 1.856028
[02:18:05.938 D] Moving to next hop: <192.6651, 3.22711, 948.2762> (Moving to gather) D: 2.409333
[02:18:06.171 D] Moving to next hop: <192.5652, 3.22711, 949.0262> (Moving to gather) D: 1.3464
[02:18:06.269 D] Moving to next hop: <190.2998, 3.82711, 987.0831> (Moving to gather) D: 38.68935
[02:18:11.137 D] Navigation reached current destination. Within 3.563459
[02:18:11.170 D] Requesting path on 146 from <190.3454, 3.486769, 986.3572> to <189.8025, 6.117051, 988.6992>
[02:18:11.580 D] Generated path to <189.8025, 6.117051, 988.6992> in 00:00:00.4105171 ms
[02:18:11.720 D] Navigation reached current destination. Within 3.382831
[02:18:11.737 D] Requesting path on 146 from <190.0777, 3.561574, 986.4998> to <189.8025, 6.117051, 988.6992>
[02:18:12.105 D] Generated path to <189.8025, 6.117051, 988.6992> in 00:00:00.3675420 ms
[02:18:12.120 D] Navigation reached current destination. Within 3.382831
[02:22:22.571 N] Stopping the bot. Reason

The bold text, The bot will arrive at node, But just out of reach to start mining the node, 1 step via the keyboard and the bot starts farming again.
My understanding this is NOT a profile issue but a navigation issue.
I have attached a full log
View attachment 13568 2014-10-30 08.16 - stop.txt
I can confirm other uses have had the EXCACT issue with this node looking at their logs they have posted too.