2.5.7861.660 Crashes after about 10min *Still not working :/* Hi. Using the 2.5.7861.660 version of HB since EU using #17359. But every time I start the bot it runs for about 10min then Wow and HB crashes. It's the same every time I try. Im attaching the latest log. Any ideas? //A
Hi, HB2807Z57, and many thanks for the log! Your Honorbuddy is having problems communicating with the WoWclient. Let's try switching the WoWclient from DX11 to DX9, and restart the WoWclient. No joy? Reboot the machine. cheers, chinajade
Thanks! Ill try changing to DX9. Edit: Im sry to say that it didn't work. Crashes again. Tried to reboot also. //A
Doesn't look like it crashed from your log looks like you exited wow which cause hb to not be able to attach to the process. From your logs: [10:05:47.464 N] Wow exited, Honorbuddy stopped! [10:05:47.464 D] Stop called! [10:05:47.465 Q] Bot Stopped! Reason: Wow exited, Honorbuddy stopped!
When the HB crashed (Not answering) I get a window from Wow saying it crashed and asks me me if I want to send a report. So Wow is not exiting. Im gonna take a print screen next time it crashes and update here. //A
Should of been more clear next time as all you said was HB was crashing not really sure but try restarting your computer then after do a clean HB installation
Hi again, HB2807Z57, and thanks for the fresh log. A pattern is starting to emerge... in both your logs, the WoWclient craters right after you mount. The problem may be WoWserver-side. A while back Bliz installed some code server-side to defeat teleport haxx. On occasion, this code would falsely trigger right at mount time on a boundary condition. The bug looked something like this: The WoWclient would start the mount, and the mount would complete If the toon moved--even slightly--right as the mounting completed, the WoWserver perceived this as your moving at 400% while 'on foot', and triggered its anti-teleport haxx code. The WoWclient would then send the 'mounting complete' update message to the server, but it was too late. By that time, the WoWserver had already made its 'teleport haxx' decision. The bug was repaired at one point, but may have crept back in. If you look in the Bliz forums this latest patch is fraught with problems like this (and graphics issues, too). Changing your selected mount to something else may help alleviate the problem. This is an old WoWserver bug that may have crept back in. More info here., and here. Although, you're the only one that has reported this fingerprint with the latest drop. I would expect to see a *lot* more reports about this, if it were in fact the issue. Time will tell. I'll see if I can get someone from the Development team to give Honorbuddy a look about this, too. In the meantime... Please see if using a mount *other* than a Griffon eliminates the problem. cheers, chinajade
Thanks for the info. It seems that it works for now. Cross my fingers. Edit: Spoke to soon :/. Still wont work. It crashes and then want me to install .NET Framework 3.5 even though I already have it.
go to your programs and features in the control panel and remove it, restart your machine then re-install that framework. there's obviously something up with it.
