Please post issues using the new navmesh system in one of the following formats Preferred: Take the info straight from the log and paste it. Code: [08:29:51.419 D] Requesting path on 140 from <-408.4854, 33.54076, -719.6155> to <-464.4073, 49.9257, -721.7181> or Code: ZoneName: ZoneId: Start Location: End Location: Client: Global or Chinese
Outer La Noscea ZoneId: 180 [19:13:31.052 D] Moving to next hop: <46.5, 48.51444, -394.2> (Moving to fate) D: 1.427653 [19:13:31.135 D] Moving to next hop: <46.6, 48.91444, -394.7> (Moving to fate) D: 1.310918 [19:13:31.187 D] Moving to next hop: <46.7, 48.75328, -395.9> (Moving to fate) D: 1.937841 That's all I gathered, it's a stuck point.
Code: ZoneName: Eastern La Noscea ZoneId: 137 Start Location: 270.8905, 44.58365, 539.669 End Location: 487.0531, 17.39324, 463.3648 Fate bot couldn't run back to its "safe" point from this position. Not sure if its a nav mesh error or not though. Below is a copy/paste of the event in from the log. It ran to a fate. Fate finished as it arrived. Remounted and wanted to run "home". Never actually moved - it just sat at the fate location waiting for another fate to pop. Code: [14:31:08.958 N] No fates we can tackle currently. [14:31:08.958 D] [POI Set] Type: Wait [14:31:08.980 D] Poi: Type: Wait () | Idle [14:31:09.027 D] DoAction Mount 1 0xE0000000 [14:31:10.621 D] Requesting path to point on 137 from <270.8905, 44.58365, 539.669> to <487.0531, 17.39324, 463.3648> within 15 [14:31:10.694 D] Poi: Type: Wait () | Moving to rest location [14:31:11.972 N] No fates we can tackle currently. [14:31:33.163 N] No fates we can tackle currently.
ZoneName: North Shroud ZoneId: 154 Start Location: [05:44:25.013 D] Requesting path on 154 from <-244.2387, -29.9207, 215.7966> to <239.4004, -7.82685, 19.69021> End Location: [05:45:18.006 D] Moving to next hop: <142.1617, -11.55023, 91.6629> (Moving to fate) D: 24.12209 Closed gate nearest Fallgourd <133.8974, -12.494, 101.7358> Other end of the gated area between Fallgourd and Peacegarden is <172.6973, -1.547484, 46.75541> When Fatebot is pathing between Fallgourd and Peacegarden, it (logically, to my mind) tries to take the route that happens to be blocked.
Can you get me coordinates for this gate as the mesh looks fine to me Code: Log(Core.Player.Location);
They will open in a future patch if it hasn't opened in 2.3, those gates are for the Ixali beast tribe. That is why there is no gate their in the mesh.
Nope, the gate is actually there, just a bug on our side as the gate doors its self don't have any collision attached to them. I've added a fix and am restarting the server now.
i got a nav error with the 1-50 mining profile I got teleported to Quarrymill as it should, i mounted in chocobo and then i get this nav error. [15:25:37.489 D] Requesting path on 153 from <176.0712, 8.577163, -61.72055> to <3537134, -3617686, 5873518> [15:25:37.653 D] No viable path from <176.0712, 8.577163, -61.72055> to <3537134, -3617686, 5873518> in 00:00:00.1640132 ms
ZoneName: Upper La Noscea ZoneId: 139 Start Location: <645.0983, -1.725523, 112.3924> End Location: <664.9885, -2.017929, 180.5007> Was stuck there on some rocks for 30 some seconds until I noticed it (was watching it thankfully). Others who use the profile have noted getting stuck there as well. It appears to get stuck @ around: Upper La Noscea (34, 24) X: 665.4717 Y: -3.406507 Z: 169.666 Let me know if you need any more info.
Zone Name: South Shroud Zone ID: 121 Gets stuck between a rock and a fence. Character Location: <-208.9643, 6.06125, 25.94692> Log:
Failed to supply the most important parts, start and end location. I need this line. [04:02:09.721 D] Requesting path on 139 from <645.0983, -1.725523, 112.3924> to <664.9885, -2.017929, 180.5007>
Not sure where the best place to put this is, but the bot is unable to navigate to the Unspoiled Mineral Nodes in Coerthas because they are too far in the cliffside. Even if I put the hotspot for the gather tag as a place the bot could interact with the object, it still gives the following error: Code: [07:25:16.879 D] Requesting path on 155 from <293.8702, 305.3441, -91.31522> to <297.1792, 308.5222, -95.92535> [07:25:18.166 D] No viable path from <293.8702, 305.3441, -91.31522> to <297.1792, 308.5222, -95.92535> in 00:00:01.2871013 ms [07:25:18.166 V] Blacklisting 400003B0 for 00:00:30 [Type: All] - Reason : Unable to navigate to target [07:25:18.166 V] [Poi.Clear] Reason: Unable to navigate. Here is data for each Unspoiled Node, including a position from which each node can be accessed. Could the navmesh maybe be tweaked slightly so that the bot can navigate to these nodes specifically?
