Process must have frozen or gotten out of sync: InjectionFinishedEvent was never fired Bot Stopped! Reason: Process must have frozen or gotten out of sync: InjectionFinishedEvent was never fired It seemed fine yesterday but I havent been able to get on all day. I downloaded a fresh copy of HB and I still get the same error ? Anyone else got this ?
from what I can see the only Dif from yesterday to today is that I let windows 7 perform its updates and restart at 3am. Could this have an effect on HB running ?
Hi, Raz0r, Please attach your full log, so we can look for trigger conditions. Ref: [Guide] How to attach your log cheers, chinajade
Hi again, Raz0r, and many thanks for the logs. Two things: Your ProfessionBuddy is damaged. I'd delete it until you get this problem resolved. [09:59:22.116 N] Compiler Error: c:\Users\Testing\Downloads\Honorbuddy 2.5.7094.573\Bots\ProfessionBuddy\SVN.cs(2,1) : error CS0116: A namespace cannot directly contain members such as fields or methods Your Singular is damaged. Not quite certain how this happened--maybe a misstep in updating Singular? [09:59:30.310 N] Compiler Error: c:\Users\Testing\Downloads\Honorbuddy 2.5.7094.573\Routines\Singular\Managers\MovementManager.cs(62,47) : error CS1061: 'Singular.Settings.SingularSettings' does not contain a definition for 'AllowMovement' and no extension method 'AllowMovement' accepting a first argument of type 'Singular.Settings.SingularSettings' could be found (are you missing a using directive or an assembly reference?) At this point, its probably best if we do a 'clean install'. Instructions here: HelpDesk: "Clean installing" Honorbuddy Don't install anything else until we get you going again, please. cheers, chinajade
Cheers for given me the advice above. I did a fresh install and the only thing that I added new to this was the HB key that I use. Same error. I checked to make sure that Professionbuddy wasnt in the bot folder. Seems to log in fine. Singular finds me and loads the correct CC. When I click the start button it tells me that process froze. any other ideas ?
Hi, Raz0r, and thanks for the fresh log. Try switching the WoWclient from DX11 to DX9, and restart the WoWclient. Please show us another log, if you're not off and away. Failure modes sometimes change with changed configurations. cheers, chinajade
Hi ChinaJade, Relaunching the wow Client using DX9 appears to have it connected and working with Singular. I will swap it over to the other CC that I prefer to use when playing my Monk. Ill let you know if it breaks again for something else. Thanks for all your help today
Changing to DX11 fixed this issue for me to. Maybe this can be added to an FAQs for problems with the new HB?