What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

PathGenerationFailed with HB

Palette

New Member
Joined
Jul 9, 2013
Messages
9
Hi team,

I've just made some test on the last release of HB.
I've made this test with a fresh install (to be sure about cfg files).

Test with :
- D3D9 / D3D11 (same results)
- Fresh install
- Char in dalaran


For Gatherbuddy2 (3 different profiles), same logs :
Code:
[10:29:19.180 D] [Flightor] We cannot fly and end location is not reachable by ground from our location.
[10:29:19.266 D] [Flightor] Failed ground nav from <-808.0563, 4417.653, 738.1839> to <1881.165, 4972.872, 117.8339> with status PathGenerationFailed

For Questing bot with official profile 1-110 :
Code:
[10:32:06.982 D] [Flightor] Failed ground nav from <-808.0563, 4417.653, 738.1839> to <2659.46, 1517.764, 30.31409> with status PathGenerationFailed
[10:32:06.982 D] Clearing POI: Can not navigate to current POI.
[10:32:07.011 D] Cleared POI

This part of logs looping.

Best regards

View attachment 2736 2016-10-28 12.29.txt
 
Last edited:
Same problem.
On 1 PC with windows 7 no problem
On second pc windows 10 exact same profile and settings - PathGenerationFailed
 
Hi team,

I've just made some test on the last release of HB.
I've made this test with a fresh install (to be sure about cfg files).

Test with :
- D3D9 / D3D11 (same results)
- Fresh install
- Char in dalaran


For Gatherbuddy2 (3 different profiles), same logs :
Code:
[10:29:19.180 D] [Flightor] We cannot fly and end location is not reachable by ground from our location.
[10:29:19.266 D] [Flightor] Failed ground nav from <-808.0563, 4417.653, 738.1839> to <1881.165, 4972.872, 117.8339> with status PathGenerationFailed

For Questing bot with official profile 1-110 :
Code:
[10:32:06.982 D] [Flightor] Failed ground nav from <-808.0563, 4417.653, 738.1839> to <2659.46, 1517.764, 30.31409> with status PathGenerationFailed
[10:32:06.982 D] Clearing POI: Can not navigate to current POI.
[10:32:07.011 D] Cleared POI

This part of logs looping.

Best regards

View attachment 215155


update Hb and also upload the profile you are using
 
Thanks for the answer,

update done for honorbuddy (build 854). Same problem occurred for :

- Gatherbuddy2 : View attachment [MINE+HERB] Suramar+Azsuna+ValSharah [DocTalbuk] v2.0.xml
& Grindbot (same logs) : View attachment EZTest.xml

Code:
[21:14:06.554 N] (Singular) (Singular) info: Pull Distance set to 100 yds by Gatherbuddy2, Plug-in, Profile, or User
[21:14:06.407 V] Blacklisting npc with entry 48959 for 100.00:00:00 [Type: All] - Reason: Globally blacklisted entry.
[21:14:06.427 D] Changed maps to Troll Raid
[21:14:06.622 D] [Flightor] Set up for movement from <-818.431, 4413.722, 737.7638> to <684.2993, 5603.249, 84.80529>
[21:14:06.654 D] Activity: Moving to next hotspot
[21:14:06.745 D] [Flightor] Failed ground nav from <-818.431, 4413.722, 737.7638> to <684.2993, 5603.249, 84.80529> with status PathGenerationFailed
[21:14:06.745 D] [Flightor] We cannot fly and end location is not reachable by ground from our location.
[21:14:06.804 D] [Flightor] Failed ground nav from <-818.431, 4413.722, 737.7638> to <684.2993, 5603.249, 84.80529> with status PathGenerationFailed
[21:14:10.798 Q] Bot stopping! Reason: Main window is closing
[21:14:10.837 N] [Gatherbuddy2]: Stopped gatherbuddy after gathering 0 nodes in 0h 0m 4s.




- Questing : Auto-Loader v2 (from official Questing pack 1-110)

Code:
[21:26:41.739 D] [Flightor] Failed ground nav from <-826.5657, 4399.348, 737.5569> to <2659.46, 1517.764, 30.31409> with status PathGenerationFailed
[21:26:41.739 D] Clearing POI: Can not navigate to current POI.
[21:26:41.739 D] Move to quest NPC POI failed
[21:26:41.804 D] Cleared POI



@Satanail I'm on win10 too

Best regards.
 
most likely its a profile issue,gimme the latest (.864) log file plz
 
Back
Top