• Visit Rebornbuddy
  • Navigation Issues

    Discussion in 'Rebornbuddy Support' started by mastahg, Mar 17, 2014.

    1. ZaneMcFate

      ZaneMcFate Member

      Joined:
      Nov 17, 2014
      Messages:
      137
      Likes Received:
      2
      Trophy Points:
      18
      Could not navigate to a mining node in the Oakwood area of Upper La Noscea. This is an area which can't be teleported to, but I can gather from the other set of outcrops on this island without trouble. Attached the full log, notable error below:

      Code:
      [22:36:32.504 D] [POI Set] Type: Gather
      [22:36:32.561 D] Requesting path on 139 from <-451.0982, -5.816898, 251.5778> to <-437.9622, -11.62337, 212.2627>
      [22:36:33.179 D] No viable path from <-451.0982, -5.816898, 251.5778> to <-437.9622, -11.62337, 212.2627> in 00:00:00.6177789 ms
      [22:36:33.179 V] Blacklisting 4000010D for 00:00:30 [Type: All] - Reason : Unable to navigate to target
      [22:36:33.179 V] [Poi.Clear] Reason: Unable to navigate.
       

      Attached Files:

    2. mphil355

      mphil355 New Member

      Joined:
      Aug 9, 2014
      Messages:
      22
      Likes Received:
      0
      Trophy Points:
      0
    3. phdchristmas

      phdchristmas New Member

      Joined:
      Dec 20, 2014
      Messages:
      56
      Likes Received:
      0
      Trophy Points:
      0
      Getting stuck on the hinge of the gate when trying to leave Forgotten Springs in southern thanalan.

      [07:43:57.054 N] Current fate set to 1FD0C4A0 Name:Children of the Sands Id:429 Icon:Battle ObjectId:E0000000 Location:<-339.6415, 7.286024, 539.2083> TimeLeft:00:15:10.9459661 Radius:50.1188 Progress:0 Level:31 MaxLevel:36 Status:ACTIVE
      [07:43:57.054 D] [POI Set] Type: Fate
      [07:43:57.069 D] Requesting path on 146 from <-331.6258, 7.984517, 420.8535> to <-339.6415, 7.286024, 539.2083>
      [07:43:57.526 D] Generated path to <-339.6415, 7.286024, 539.2083> in 00:00:00.4565806 ms
      [07:43:57.539 D] Moving to next hop: <-335.3349, 8.027107, 437.0262> (Moving to fate) D: 16.59262
      [07:43:59.478 D] Moving to next hop: <-341.7349, 7.82711, 456.2263> (Moving to fate) D: 20.97287
      [07:44:01.726 D] Moving to next hop: <-341.7349, 7.82711, 456.2262> (Moving to fate) D: 0.7365067
      [07:44:01.746 D] Moving to next hop: <-344.2349, 7.627113, 461.3262> (Moving to fate) D: 6.236058
      [07:44:02.352 D] Moving to next hop: <-344.4849, 7.627113, 461.7762> (Moving to fate) D: 1.296446
      [07:44:02.411 D] Moving to next hop: <-346.8349, 7.927109, 463.4762> (Moving to fate) D: 3.617752
      [07:44:02.763 D] Moving to next hop: <-347.0349, 8.027107, 463.8262> (Moving to fate) D: 1.226499
      [07:44:02.822 D] Moving to next hop: <-347.0349, 8.027107, 464.5262> (Moving to fate) D: 1.300848
      [07:44:02.919 D] Moving to next hop: <-341.7349, 6.627113, 526.6262> (Moving to fate) D: 63.03282
       
    4. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,232
      Likes Received:
      364
      Trophy Points:
      83
      Have you changed the path post-processing setting? The default value should be moving it away from the fence.
       
    5. kagamihiiragi17

      kagamihiiragi17 Community Developer

      Joined:
      Jun 24, 2014
      Messages:
      873
      Likes Received:
      25
      Trophy Points:
      0
      A few issues I've saved up:

      The door at <-27.89701, 71.79624, -28.3591> on map 137 isn't meshed - it won't enter the building.

      The door at <-415.596, 211.4575, -283.0018> on map 155 isn't meshed - it won't enter the building.

      The door at <-453.4409, 211.4575, -282.4545> on map 155 isn't meshed - it won't enter the building.

      Occasionally the bot will need to go to the upper floors of the big tower in Whitebrim in Coerthas or the upper towers of the Observatorium in Coerthas, but will say it reaches its destination (on the third floor) when the bot is on the first floor. Example:

      This is in the tower in Whitebrim and the bot needs to go one floor higher - it is currently getting the "target is too far above you" red error in-game.

      Another example of this:

      This time the bot is on the floor above the target and gets the "target is too far below you" red error.
       
      Last edited: Feb 14, 2015
    6. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,232
      Likes Received:
      364
      Trophy Points:
      83
      You'll need to use offmesh navigation for the towers since we don't check 3d height.
       
    7. Djdave

      Djdave New Member

      Joined:
      Feb 22, 2015
      Messages:
      166
      Likes Received:
      1
      Trophy Points:
      0
      Hopefully posted this in the right place! When gathering in Central Thanalan the bot gets stuck on one of the trees after a few mins in the 23,30 area.

      Ive attached the log where I stopped it after it got stuck. I think my exact co-ordinates of where it got stuck are X 192.6871 Y 12.17543 Z431.6082.

      If it helps it always gets stuck after harvesting the tree.

      Sorry if I'm missing anything I'm new to this bot this weekend!
       

      Attached Files:

    8. kagamihiiragi17

      kagamihiiragi17 Community Developer

      Joined:
      Jun 24, 2014
      Messages:
      873
      Likes Received:
      25
      Trophy Points:
      0
      The bot gets stuck on some sacks and a stick at <-71.18267, 64.42052, -280.7716> on 180 (Outer La Noscea).

      Can be seen on the following path: 180 from <-124.0823, 64.7836, -211.5341> to <-338.8877, 61.72266, -120.2564>
       
    9. phdchristmas

      phdchristmas New Member

      Joined:
      Dec 20, 2014
      Messages:
      56
      Likes Received:
      0
      Trophy Points:
      0
      Outter La Noscea its the turn when heading to the western side of the map, a cluster of trees and a broken down tent in the way.

      [19:39:39.564 D] Moving to next hop: <-71.69999, 64.57091, -283.8> (Moving to fate) D: 1.102849
      [19:39:39.598 D] Moving to next hop: <-74.44999, 64.57091, -284.9> (Moving to fate) D: 3.7521
       
    10. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,232
      Likes Received:
      364
      Trophy Points:
      83
      Not helpful. Please read the first post and follow the given format.
       
    11. phdchristmas

      phdchristmas New Member

      Joined:
      Dec 20, 2014
      Messages:
      56
      Likes Received:
      0
      Trophy Points:
      0
      where do i find zone ID, start location, end lcoation
       
    12. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,232
      Likes Received:
      364
      Trophy Points:
      83
      Just copy the line from the log as that is the prefered way to report issues.
       
    13. MagistratMay

      MagistratMay New Member

      Joined:
      Dec 7, 2014
      Messages:
      33
      Likes Received:
      0
      Trophy Points:
      0
      In West La Noscea

      The bot starts to turn left and right really fast and than goes to node

      starting node <528, 16.84645, 361.9003>

      [06:15:08.764 D] Requesting path on 138 from <527.7074, 16.85794, 361.336> to <493.2706, 9.487082, 391.7693>
      [06:15:08.876 D] Generated path to <493.2706, 9.487082, 391.7693> in 00:00:00.1119755 ms
      [06:15:09.407 D] Moving to next hop: <522.1489, 12.01806, 384.0852> (Moving to gather) D: 21,86608
      [06:15:11.719 D] Moving to next hop: <520.1217, 11.30859, 385.0078> (Moving to gather) D: 2,788657
      [06:15:11.974 D] Moving to next hop: <508.6867, 9.711441, 385.4591> (Moving to gather) D: 12,01766
      [06:15:13.216 D] Moving to next hop: <511.5326, 9.5299, 387.2004> (Moving to gather) D: 2,848254
      [06:15:13.474 D] Moving to next hop: <511.9304, 9.254153, 388.8408> (Moving to gather) D: 2,061563
      [06:15:13.624 D] Moving to next hop: <508.7434, 9.709324, 385.563> (Moving to gather) D: 3,887756
      [06:15:13.965 D] Moving to next hop: <511.4077, 9.53508, 387.2004> (Moving to gather) D: 2,586831
      [06:15:14.167 D] Moving to next hop: <511.6729, 9.271201, 388.712> (Moving to gather) D: 2,142687
      [06:15:14.311 D] Moving to next hop: <509.0815, 9.684741, 386.1828> (Moving to gather) D: 2,913493
      [06:15:14.614 D] Moving to next hop: <509.2501, 9.546448, 387.2004> (Moving to gather) D: 0,7334291
      [06:15:14.665 D] Moving to next hop: <509.2501, 9.546448, 387.5004> (Moving to gather) D: 0,527315
      [06:15:14.715 D] Moving to next hop: <509.0881, 9.328687, 388.1963> (Moving to gather) D: 0,8393252
      [06:15:14.780 D] Moving to next hop: <507.5779, 8.635802, 390.0579> (Moving to gather) D: 2,918451
      [06:15:15.085 D] Moving to next hop: <509.2456, 8.65765, 390.6741> (Moving to gather) D: 1,724799
      [06:15:15.171 D] Moving to next hop: <492.8668, 9.174112, 388.6172> (Moving to gather) D: 15,93245
      [06:15:16.841 D] Moving to next hop: <493.0829, 8.746445, 391.1594> (Moving to gather) D: 2,521995
      [06:15:16.879 D] Targeting Rocky Outcrop 0x40000207 0xECD20E0
       
    14. BigBudda87

      BigBudda87 Member

      Joined:
      May 5, 2012
      Messages:
      243
      Likes Received:
      0
      Trophy Points:
      16
      Morning

      Code:
      ZoneName: Outer La Noscea
      ZoneId: 180
      Start Location: <-111.0202, 64.41472, -212.3806>
      End Location: <-423.6712, -3.707844, 155.5542>
      Client: Global
      Code:
      [07:05:57.660 D] Requesting path on 180 from <-111.0202, 64.41472, -212.3806> to <-423.6712, -3.707844, 155.5542>
      [07:06:13.168 D] Moving to next hop: <-68.92104, 64.41473, -284.0088> (Hotspot) D: 4,863

      the bot don´t get away from this point
       
      Last edited: Mar 9, 2015
    15. kagamihiiragi17

      kagamihiiragi17 Community Developer

      Joined:
      Jun 24, 2014
      Messages:
      873
      Likes Received:
      25
      Trophy Points:
      0
      Probably not a good idea to post a picture of your character's name...
       
    16. BigBudda87

      BigBudda87 Member

      Joined:
      May 5, 2012
      Messages:
      243
      Likes Received:
      0
      Trophy Points:
      16
      yeah that was not a good idea :)
       
    17. BigBudda87

      BigBudda87 Member

      Joined:
      May 5, 2012
      Messages:
      243
      Likes Received:
      0
      Trophy Points:
      16
      i don´t know if it´s an issue but i can´t get a path form western la noscea aetheryte to a possition in upper la noscea. that´s what the log say´s.

      Code:
      [09:31:20.883 D] Requesting path on 138 from <261.7882, -22.75, 225.7934> to <-472.0431, 1.210782, 275.1873>
      [09:31:20.998 D] No viable path from <261.7882, -22.75, 225.7934> to <-472.0431, 1.210782, 275.1873>
       
    18. kagamihiiragi17

      kagamihiiragi17 Community Developer

      Joined:
      Jun 24, 2014
      Messages:
      873
      Likes Received:
      25
      Trophy Points:
      0
      You can't get cross-map navigation. You need to first request a path of Upper La Noscea (the MoveTo tag will exit on map transition) and then request a path on Upper La Noscea to where you want to go.
       
      BigBudda87 likes this.
    19. flamepyro

      flamepyro New Member

      Joined:
      Oct 23, 2012
      Messages:
      48
      Likes Received:
      0
      Trophy Points:
      0
      Hey Guys, Been going at the atma awhile and also getting the same issue in Outer La Noscea
      Here is one of the path requests i get.

      Pathing:
      [21:47:19.273 D] Requesting path on 180 from <190.1403, 63.97726, -198.0066> to <-336.9796, 63.07803, -139.8397>

      Specificly i am getting caught on a Barrel at
      X: -71.54379
      Y: 64.49969
      Z: -284.1869
      Player Heading: 4.309999942

      Thanks for all the great work.
       
    20. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,232
      Likes Received:
      364
      Trophy Points:
      83
      thanks for the report. This should be fixed now.
       

    Share This Page