[RandleParticipant]

Hello,

I found a fix for your problems! To avoid the lock ups on the timed node scenarios, just add the grid presets for the regular nodes like this.

grid(Timed Nodes)
gatherPreset(Timed Nodes)
goodWeather(Umbral Duststorm)
goodWeather(Umbral Tempest)
skipBadWeather
gather(1)

grid(5DP3BTN)
gatherPreset(5DP3BTN)

Previously it was like

grid(Timed Nodes)
gatherPreset(Timed Nodes)
goodWeather(Umbral Duststorm)
goodWeather(Umbral Tempest)
skipBadWeather
gather(1)

This way, if there are no desirable nodes for Miqobot, it would wait 60 seconds and then continue with the regular botany process. Make sure to do this with every scenario chapter that involves time nodes. Also, I set the branch radius to 30 from 4. 4 felt too low and it has caused similar issues to past grids.

• This reply was modified 3 years, 7 months ago by  Randle.

[RandleParticipant]

Operating on the knowledge that all grids have been thus rendered useless. I will make an educated attempt at extrapolating what I have learnt from your grid. This will fail horribly for sure but I will be glad to test and collaborate.

[RandleParticipant]

Is there an updated grid with fixes? Krude’s method of fixing the tornado issue seemed to have worked, but I am getting kill switch triggers on some nodes still.

• This reply was modified 3 years, 9 months ago by  Randle.

[RandleParticipant]

Flawless thus far! I have not run it for more than 3 hours unattended, which supposedly is a recommended practice by the developer anyway.

[RandleParticipant]

I’ve definitely run into a lot of hiccups, more the reason to never leave your bot unattended!

[RandleParticipant]

Strife025 wrote:

The log doesn’t tell much, but it looks like a missed node:
(12:13:38 AM) Going from 362 to 358 in 5 trips.
(12:13:41 AM) 4 trips more..
(12:13:45 AM) 3 trips more..
(12:13:46 AM) 2 trips more..
(12:13:47 AM) 1 trip more..
(12:13:47 AM) Destination reached!
(12:13:49 AM) Gathering started.
(12:13:49 AM) Max node count: 2
(12:13:49 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*
(12:18:49 AM) Scanning for shiny gathering nodes like ‘<anything>’ *.*

I turned on the nav grid and the radar to show gathering nodes, and it looks like one of the nodes isn’t connected to the grid on the tree trunk.

I connected it but haven’t run the scenario again since last night to see if it fixed it. I’ll check today.

Could I please receive the fixed version you are using?

Regards.

• This reply was modified 3 years, 9 months ago by  Randle.

[RandleParticipant]

If my schedule allows it, I will run it again today in the afternoon to check for more issues 🙂

[RandleParticipant]

Hello, I decided to do some testing with the current scenario you have plotted. I found this issue and I hope I’ve helped!

(5:08:11 PM) I see a shiny node at (523.282715, -521.874390, 194.120407).
(5:08:11 PM) Sorry, can’t find path sequence from 391 to 173 🙁 Maybe grid is not connected?
(5:08:11 PM) Sorry, but I can’t find the way to the next trip 🙁

[RandleParticipant]

Friend, you are doing work of the gods. Thank you so much for your contribution and help! I did not know I have to edit the file directly in the executable! =)

• This reply was modified 3 years, 9 months ago by  Randle.

[RandleParticipant]

SirVG wrote:

Lots of just little adjustments. I tried fixing the tree (waypoint 260) again by moving it back and changing to foot. That should give it a much bigger space to land on and potentially avoid snags.

I also added a lot of extra waypoints around potential enemies it could pick up around the diademBoom spots, just to avoid getting stuck there. Some points were slightly adjusted to try to make sure only Botany enemies are picked up.

A couple of very minor changes to the scenario to account for these changes.

Only the navigation grid and scenario are changed.

Let me know if you have issues with anything and where they occur.

Is it possible I get a copy of these for Slot 3 on both your mining and botany versions? I’ve tried changing things around to harvest slot 3’s and it won’t work, it reverts back to 4 or goes to slot 1.

• This reply was modified 3 years, 9 months ago by  Randle.

[Author]

Posts