Bot was working till I got a DC, relogged it in manually restarted the bot, wow freezes and the bot freezes too. log attached.
changed to Dx9 the other bot bases work, but when I go to mixed and it just freezes wow and the bot. I tried, mixed mode and manually que'd for a dungeon, seem to play nice but then it just locked up completely. Log attached (had to zip log was 1.17mb) Cheers
This is interesting. This is keeps getting thrown. Code: [04:05:13.599 D] System.AccessViolationException: Could not read bytes from 01C19EFA [299]! I will leave this for Mr. CnG and hopefully he can provide a solution. I have to get some sleep. Working in the morning.
Hi, Fracture & Bambam922, That error message is a direct consequence of the WoWclient locking up. The failure mode is the same as the WoWclient disconnecting from the server, or crashing. The curious thing is that Honorbuddy continued to run and generate these log entries for a few seconds after the WoWclient lockup/crash. At least for that, we can be thankful. I'm seriously concerned this may be a hardware problem, and we need to send Fracture through the same remedy tree as Viceversa10. The apparent scope of this problem is in the Operating System/Hardware, and outside the realm of Honorbuddy. (Even if Honorbuddy is aggravating the problem, the problem lies in the OS or hardware.) As such, our ability to help here is very limited. cheers, chinajade
Cheers Bambam. Chinajade, my computer is a beast, believe me hardware is not an issue. this issue only occurs when running in mixed mode. obvious wow/bot issue.
in your mount options turn off, "use random mount" and "Find Mount Automatically" in flying mount, type in the name of the mount you want to use, try and pick something that isn't a special type of mount and give it a try see if it helps at all.
[04:04:27.182 D] [FlyTo-v241(debug) @line 2789]: Flying to '<-906.3417, 5370.583, 20.74966>': <-906.3417, 5370.583, 20.74966>. [04:05:06.451 N] Wow exited, Honorbuddy stopped! what happened between those lines? [04:05:13.544 D] System.AccessViolationException: Could not read bytes from 01C19EFA [299]! comes after Hb stops it seems
Wow locks up completely,only way to make it respond again is kill HB process or kill wow process and re-open. @ CodenameG, I was already running without random mount and automatic.
