This topic contains 932 replies, has 245 voices, and was last updated by 
-
Posts
-
Seem to still be getting stuck in the same spots previously reported :\
hmmmm X, Y, Z, coordinates please?
also when you import the scenario make sure its being imported and not counted as a duplicate miqobot skips duplicateās and wont update them, if it thinks of it as a duplicate then you will have to delete the grid in miqobot then re-import the grid it will tell you in the text box in the bottom for miqobot weather it was imported or skiped as a duplicate
Another spot at x23.3 y33.0.. Iām trying to jump across a ravine area to get to a node lol.
Iām continuously getting stuck on a big rock ( 10.3 , 17.3 ) or being told āTarget is too far below you.ā ( 11.6 , 17.7 )
Itās very early in the mining section of the scenario (the second and third node it heads to, iirc)
Hmm.. still getting stuck on that giant tree at x25.3 y33.2
Same, hereās the log, starting from the previous node:
(10:05:01 PM) My precious shiny sparkles! (10/40)
(10:05:02 PM) Scanning for shiny gathering nodes like ā<anything>ā *.*
(10:05:02 PM) I see a shiny node at (128.707199, 598.354797, 87.169601).
(10:05:03 PM) Going from 42 to 218 in 5 trips.
(10:05:08 PM) 5 trips more..
(10:05:11 PM) 4 trips more..
(10:05:12 PM) 3 trips more..
(10:05:13 PM) 2 trips more..
(10:05:15 PM) 1 trip more..
(10:05:17 PM) Destination reached!
(10:05:19 PM) Not enough GP for this rotation: 190 of 400 required.
(10:05:19 PM) Hitting that poor node. :3
(10:05:28 PM) Hitting that poor node. :3
(10:05:34 PM) My precious shiny sparkles! (11/40)
(10:05:34 PM) Scanning for shiny gathering nodes like ā<anything>ā *.*
(10:05:34 PM) I see a shiny node at (178.963394, 579.868530, 87.425346).
(10:05:35 PM) Going from 218 to 217 in 5 trips.
(10:05:38 PM) 5 trips more..
(10:05:40 PM) 4 trips more..
(10:05:45 PM) 3 trips more..
(10:05:47 PM) 2 trips more..
(10:05:49 PM) 1 trip more..For some reason itās dropping us off at (195.33, 587.42, 86.59) and getting us stuck on a tree opposite of the node.
hey thanks for the hard work you put in. appreciate it!
I missed the coordinates, but there seems to be a few points where Miqo will stand right next to the node and canāt detect it. Iāll jot down the notes when I see it again! Thanks again for the grid š
no problem š thank you guys for reporting the bugs and error’s every report of said error’s and bugs helps to make the grid better and better so thank yous for the assistance š
(2:56:37 AM) Going from 103 to 301 in 3 trips.
(2:56:40 AM) 3 trips more..
(2:56:42 AM) 2 trips more..
(2:56:50 AM) 1 trip more..
(3:00:15 AM) Oh noes, I couldn’t reach the destination in time. I guess I’m stuck here. š
(3:00:15 AM) Time/Estimate: 205.4638/205.4583
(3:00:15 AM) Destination reached!
(3:00:15 AM) Sorry, can’t move. I got lost in the woods, and I can’t find way back home.
(3:00:15 AM) Poking creatures in the woods… Good night! <3
(3:00:15 AM) (NOTE) Kill switch is triggered.
(3:00:15 AM) (NOTE) Please save the message log for analysis and restart Miqobot.
(3:00:15 AM) Poking creatures in the woods… Good night! <3
(3:00:15 AM) (NOTE) Kill switch is triggered.
(3:00:15 AM) (NOTE) Please save the message log for analysis and restart Miqobot.Received this on the lighting island
(33.7, 12.9)thank you i will get to work on those right now š
(2:56:37 AM) Going from 103 to 301 in 3 trips.
(2:56:40 AM) 3 trips more..
(2:56:42 AM) 2 trips more..
(2:56:50 AM) 1 trip more..
(3:00:15 AM) Oh noes, I couldnāt reach the destination in time. I guess Iām stuck here. š
(3:00:15 AM) Time/Estimate: 205.4638/205.4583
(3:00:15 AM) Destination reached!
(3:00:15 AM) Sorry, canāt move. I got lost in the woods, and I canāt find way back home.
(3:00:15 AM) Poking creatures in the woodsā¦ Good night! <3
(3:00:15 AM) (NOTE) Kill switch is triggered.
(3:00:15 AM) (NOTE) Please save the message log for analysis and restart Miqobot.
(3:00:15 AM) Poking creatures in the woodsā¦ Good night! <3
(3:00:15 AM) (NOTE) Kill switch is triggered.
(3:00:15 AM) (NOTE) Please save the message log for analysis and restart Miqobot.Received this on the lighting island
(33.7, 12.9)was a vortex issue the waypoint was to close to it i had moved it further from it
-
This reply was modified 3 years, 3 months ago by
r51093.
I believe miqobot is not updateing the grids becuse it is thinking they are duplicate’s miqobot will not update duplicate’s but insted skip them to fix this i recommend that you DELETE the old diadem scenario and grid before you import the updated version here you only need to delete the scenario and navigation grid the gathering presets can be left alone
Miqobot identifies a preset as duplicate only if it’s an absolute match.
There are no heuristics involved, the algorithm compares two presets on a binary level. Even if you move a single waypoint slightly, it will be considered a new grid and can not be identified as duplicate.Please note, however, that importing a new navigation grid with the same name does not replace any old grids. They remain in the list as different versions with the same name, unless the user manually deletes them.
Therefore your recommendation to delete old Diadem presets before import is correct.
Albeit for a different reason.Miqobot identifies a preset as duplicate only if itās an absolute match.
There are no heuristics involved, the algorithm compares two presets on a binary level. Even if you move a single waypoint slightly, it will be considered a new grid and can not be identified as duplicate.Please note, however, that importing a new navigation grid with the same name does not replace any old grids. They remain in the list as different versions with the same name, unless the user manually deletes them.
Therefore your recommendation to delete old Diadem presets before import is correct.
Albeit for a different reason.OH! good to know thank you š
-
This reply was modified 3 years, 3 months ago by
You must be logged in to reply to this topic.