The mesh issue

[CodenameG]

Were the meshes changed for .513? Everything was working fine in .507, same zones, same quests, never tried to run up a cliff. There is no way to report all of the stucks that started happening in .513 and the introduction of native flying. Even though native flying is disabled in Pandaria (and in settings) it definitly seems it's calculating paths as if you could fly when you clearly can not.

It could be something different then a bug with native flying, but I seriously doubt all the meshes got fucked up right when .513 was released.

the last change i remember happening to the meshes where that roads where defined, but that was way before build 507, since meshes can be updated interdependently of the honorbuddy version is possible they can be updated at anytime. when some of our developers wake up, i will bring this thread to their attention.

 

[ChunkyMonkey]

I levelled two toons before this one with very few issues. For some reason on this third one HB thinks that every cliff is climbable no matter how steep. Native flying is not checked but being in Pandaria I can't fly anyway. I took the time to check my log files and it looks like I was last levelling on version 2.5.6486.512. Clearing cache and re-installing doesn't appear to do anything. Changing CCs and profiles doesn't make a difference. It appears to be any cliff so hopefully we don't have to report them all. I'm using Kick's questing profiles. Good luck!

 

[CodenameG]

I levelled two toons before this one with very few issues. For some reason on this third one HB thinks that every cliff is climbable no matter how steep. Native flying is not checked but being in Pandaria I can't fly anyway. I took the time to check my log files and it looks like I was last levelling on version 2.5.6486.512. Clearing cache and re-installing doesn't appear to do anything. Changing CCs and profiles doesn't make a difference. It appears to be any cliff so hopefully we don't have to report them all. I'm using Kick's questing profiles. Good luck!

like i said, ill see what can be done.

 

[neodite]

There are many problems with the paths, as people have already stated.

But the thing that bothers me the most, is every damn mail box it tries to run threw it instead of around

 

[ChunkyMonkey]

Mailboxes, etc are an entirely different issue neodite - please post those issues in http://www.thebuddyforum.com/honorb...tion-mesh-errors-problems-post-them-here.html

 

[Jez]

I was having this issue and a fellow HB'er mentioned switching from DX11 to 9 helped him. Guess what it helped me too.

Hope it helps you.

 

[CodenameG]

I was having this issue and a fellow HB'er mentioned switching from DX11 to 9 helped him. Guess what it helped me too.

Hope it helps you.

if you guys havent give it a shot, since its worth a try. i was botting in dx9 mode, back when i was botting in pandaria, so that might help.

 

[stejens]

if you guys havent give it a shot, since its worth a try. i was botting in dx9 mode, back when i was botting in pandaria, so that might help.

Didn't work, questing had been flawless for me on 2 characters until a few days ago.

 

[MaxMuster]

i get it guys, it sucks, but the only way we are going to get all these is if you report them, so when they go in and re-mesh the area we can make sure all the issues are taken care of.

so please follow the instructions on the thread and log the issue.
http://www.thebuddyforum.com/honorb...tion-mesh-errors-problems-post-them-here.html

You make shit and we should solved it?

With HB v507 or v512 the bot has not this problem. this problem comes with v513. so please make a roll back an everything is fine.

 

[CodenameG]

You make shit and we should solved it?

With HB v507 or v512 the bot has not this problem. this problem comes with v513. so please make a roll back an everything is fine.

its not a roll back issue. and im not asking you to solve anything, all im asking is for you to report, and if you dont want to then you dont have to.

 

[MaxMuster]

its not a roll back issue. and im not asking you to solve anything, all im asking is for you to report, and if you dont want to then you dont have to.

alter schwede jetzt muss ich es auf deutsch rauslassen, da ihr es auf englisch wohl nicht kapiert:

mit v507 und v512 lief alles ohne Probleme. Die Fehler das er h?gel usw. hochrennen will, obwohl er nicht kann, kamen erst mit v513. Demzufolge wird es wohl kaum ein Mesh Fehler sein (auser eure kompletten Meshes haben bei den Server Problemen nen Knacks abbekommen). Es wird also an der v513 liegen (bei der sich wohl ein Fehler eingeschlichen hat).

Und seit TAGEN, h?rt man immer nur: Bitte meldet doch die stellen wo er festh?ngt. Aber eine Statement ob der Bot n Knacks hat oder eure Meshes kaputt gegangen sind, gibt es nicht. Und wann n Fix kommt auch nicht.

Manchmal frag ich mich echt: Was machen die Devs den ganzen Tag? In der Nasebohren?

Wenn ich ein Unternehmen h?tte wie ihr und es derartige Probleme mit dem BOt gibt, dann wird 24/7 durchgearbeitet, bis das Problem behoben ist. Aber in letzter Zeit kommt immer mehr so r?ber: Ach Bezahlt haben se e scho, da k?nnen se au Warten.

 

[Tony]

alter schwede jetzt muss ich es auf deutsch rauslassen, da ihr es auf englisch wohl nicht kapiert:

mit v507 und v512 lief alles ohne Probleme. Die Fehler das er h?gel usw. hochrennen will, obwohl er nicht kann, kamen erst mit v513. Demzufolge wird es wohl kaum ein Mesh Fehler sein (auser eure kompletten Meshes haben bei den Server Problemen nen Knacks abbekommen). Es wird also an der v513 liegen (bei der sich wohl ein Fehler eingeschlichen hat).

Und seit TAGEN, h?rt man immer nur: Bitte meldet doch die stellen wo er festh?ngt. Aber eine Statement ob der Bot n Knacks hat oder eure Meshes kaputt gegangen sind, gibt es nicht. Und wann n Fix kommt auch nicht.

Manchmal frag ich mich echt: Was machen die Devs den ganzen Tag? In der Nasebohren?

Wenn ich ein Unternehmen h?tte wie ihr und es derartige Probleme mit dem BOt gibt, dann wird 24/7 durchgearbeitet, bis das Problem behoben ist. Aber in letzter Zeit kommt immer mehr so r?ber: Ach Bezahlt haben se e scho, da k?nnen se au Warten.

English plz

 

[WoWuser123]

I was having this issue and a fellow HB'er mentioned switching from DX11 to 9 helped him. Guess what it helped me too.

Hope it helps you.

No change from this. Started questbot in combat, smooth fight ... but a few seconds after combat ended it ran into a cliff trying to get on top which was clearly impossible.

 

[starl1te]

last week I finished leveling 2 chars by questing, and overall never noticed any stuck problems.

Now I'm leveling two more, and in the last couple days they are getting stuck EVERYWHERE, any zone any level. Every little tent, log, bump - the toon has a high chance to be simply sitting there running against it, doesnt seem to try to unstuck.

In pandaria there is a constant issue with "can't generate a path to X" doing quests, the toon just sits there in place targeting the quest mob nearby, but cannot move to it. Again, a couple weeks ago leveling 85-90 I didnt notice this at all.

All these times the questbot just stops and has to be manually unstuck, moved, or the quest just done by hand. Can't afk at all.

 

[ChunkyMonkey]

English plz

It's actually better that it not be translated... I'll try running with DX9 and see if that resolves the issue.

Edit: Nope it didn't. I just watched it try to unstuck for about 5 minutes. Running against a cliff that was nearly vertical. I'm not seeing tons of reports and therefore I have to assume that this is a rare issue?

 

[Tankpal0207]

Obviously something has changed.

Considering how widespread the problem is -it would seem there are two possibilities:
1) There is a problem with how the meshes are generated
2) There is a problem with how the bot is interpreting that data

I really don't see how the version of DX you're running could have anything to do with this - the topography of the zones doesn't "change" depending on the version of DX.

 

[CodenameG]

You have no idea how bad games would be if cheats..hacks & bots were 1 click..

Think BGs are overpopulated now..the game in general..the auction house..ain't seen nothin' yet..

there still has to be some work put into it, doesn't matter if your doing it or a developer is, ether-way your ether spending time playing the game, or spending time making sure your setup is good enough to not have problems, no effort 1-90 isn't possible, you still have to try.

 

[CodenameG]

Obviously something has changed.

Considering how widespread the problem is -it would seem there are two possibilities:
1) There is a problem with how the meshes are generated
2) There is a problem with how the bot is interpreting that data

I really don't see how the version of DX you're running could have anything to do with this - the topography of the zones doesn't "change" depending on the version of DX.

i told our developers, and they are on it.

 

[tumbum]

they are right, there are a lot of problem with the movement, posted something in the Mesh/Navi Thread. But the Problem about that a Toon is falling down a cliff or gets stuff at corners are from beginn the same, the meshs around corners or cliffs are not correct, there are situations where you fall down and maybe there situation it doesnt happens. i dont know how the mesh are get generated, but test this meshes always with the biggest race Tauren / Draenei or Worgen.