I have a problem at the time of login. He can not enter a password to login. He stands on the login password, then closes the WoW alone, opens again, and standing still in the login screen. Log: View attachment 175881 Code error in HBRelog Code: [00:23:59] System.AccessViolationException: Could not read bytes from 00000004 [299]! em GreyMagic.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative) em GreyMagic.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative) em HighVoltz.HBRelog.WoW.Lua.LuaTable..ctor(ExternalProcessReader memory, IntPtr address) em HighVoltz.HBRelog.WoW.Lua.LuaTValue.get_Table() em HighVoltz.HBRelog.WoW.FrameXml.UIObject.<GetUIObjects>d__2.MoveNext() em System.Linq.Enumerable.<OfTypeIterator>d__aa`1.MoveNext() em System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() em System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) em System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) em HighVoltz.HBRelog.WoW.States.LoginWowState.HandleAccountSelectionDialog() em HighVoltz.HBRelog.WoW.States.LoginWowState.Run() em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse() em HighVoltz.HBRelog.WoW.WowManager.Pulse() em HighVoltz.HBRelog.TaskManager.Pulse() em HighVoltz.HBRelog.HbRelogManager.DoWork() [00:24:19] System.AccessViolationException: Could not read bytes from 00000004 [299]! em GreyMagic.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative) em GreyMagic.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative) em HighVoltz.HBRelog.WoW.Lua.LuaTable..ctor(ExternalProcessReader memory, IntPtr address) em HighVoltz.HBRelog.WoW.Lua.LuaTValue.get_Table() em HighVoltz.HBRelog.WoW.FrameXml.UIObject.<GetUIObjects>d__2.MoveNext() em System.Linq.Enumerable.<OfTypeIterator>d__aa`1.MoveNext() em System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() em System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) em System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) em HighVoltz.HBRelog.WoW.States.LoginWowState.HandleAccountSelectionDialog() em HighVoltz.HBRelog.WoW.States.LoginWowState.Run() em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse() em HighVoltz.HBRelog.WoW.WowManager.Pulse() em HighVoltz.HBRelog.TaskManager.Pulse() em HighVoltz.HBRelog.HbRelogManager.DoWork()
wow starts at least but then stops at password screen. anyone an idea? [09:32:05] System.IO.FileNotFoundException: Could not load file or assembly 'Fasm.NET.dll' or one of its dependencies. The specified module could not be found. File name: 'Fasm.NET.dll' at GreyMagic.ExternalProcessReader..ctor(Process proc) at HighVoltz.HBRelog.WoW.WowLockToken.StartWoW() in c:\Buddy\Projects\HBRelog\WoW\WowLockToken.cs:line 154 at HighVoltz.HBRelog.WoW.States.StartWowState.Run() in c:\Buddy\Projects\HBRelog\WoW\States\StartWowState.cs:line 42 at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse() in c:\Buddy\Projects\HBRelog\FiniteStateMachine\Engine.cs:line 41 at HighVoltz.HBRelog.WoW.WowManager.Pulse() in c:\Buddy\Projects\HBRelog\WoW\WowManager.cs:line 294 at HighVoltz.HBRelog.TaskManager.Pulse() in c:\Buddy\Projects\HBRelog\TaskManager.cs:line 62 at HighVoltz.HBRelog.CharacterProfile.Pulse() in c:\Buddy\Projects\HBRelog\CharacterProfile.cs:line 110 at HighVoltz.HBRelog.HbRelogManager.DoWork() in c:\Buddy\Projects\HBRelog\HBRelogManager.cs:line 86
Scroll up, I posted a full solution to this exact problem 7 posts ago: https://www.thebuddyforum.com/honor...nsource-relogger-post1922098.html#post1922098
No. Many people have asked for it, including myself. Would be happy to pay for this if it was able to log out a toon and log back in without closing WoW. Somebody stated it had to do with needing to restart HB for stability reasons but the app already does that. Don't see a reason why it shouldn't be possible but I am not the dev. Maybe Highvoltz will give this some love one of these days.
Lets fix this first!! at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.OpenProcessHandle(Int32 access) at System.Diagnostics.Process.get_Handle() at HighVoltz.HBRelog.Utility.Is64BitProcess(Process proc) at HighVoltz.HBRelog.WoW.WowLockToken.StartWoW() at HighVoltz.HBRelog.WoW.States.StartWowState.Run() at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse() at HighVoltz.HBRelog.WoW.WowManager.Pulse() at HighVoltz.HBRelog.TaskManager.Pulse() at HighVoltz.HBRelog.HbRelogManager.DoWork()
I don't think I understand the "WAIT" task right, or its not working as it should. This is with two WOW accounts. I have a Profile I'm trying to get to run Garrisonbuddy on all my accounts and characters. It starts off by launching Account 1 Character 1A. Under Tasks it goes like this: Wait 1, Random 0 Start HBRelog (Account 2, Character 2A, Garrisonbuddy) Wait 20, Random 0 Start HBRelog (Account 1, Character 1B, Garrisonbuddy) Stop HBRelog (Account 1, Character 1A, Garrisonbuddy) It seems simple to me, but maybe I'm fucking something up. It starts the Profile, logs into my first character, starts GarrisonBuddy, waits a minute, then launches second wow with account 2 and starts garrisonbuddy. That's as expected and desired. This is where it fucks up. It then IMMEDIATELY tries to launch the profile for Account 1 Character 1B. The second WAIT is still highlighted yet it runs the next task anyway. It DOESN'T run the STOP HBRelog task though... so my first profile keeps trying to log in even though it can't because the 2nd character is logged in on a 3rd WoW window. After 20 minutes it will kill the original profile... Anyone know what I'm doing wrong?
On my system HBRelog opens wow, returns a message that wow crashed (it did not and is still open and working), he then opens a new wow windows and repeate. If i manage to stopp HBRelog within 4+5 seconds i only have 20 or so wow windows open, but normaly the computer chrashes. anything wrong i am doing. EDIT: updated to latest version and now i do not have this multiple wow windows but it still not working. EDIT2: So after reading this thread i found someone that linked a new dll file, now it looks like stuff are working. HB does break after a few minutes, but i will try a clean install. [09:18:10] Garrison: Waiting for 30 minutes before executing next task [09:18:16] Garrison: WoW and HB startup sequence complete [09:18:16] Garrison: Opened communication with HBRelogHelper [09:20:17] Garrison: Honorbuddy is not responding.. So lets restart it [09:20:17] Garrison: Attempting to close Honorbuddy [09:20:18] Garrison: Closing Honorbuddy because it took too long to attach HB is not responding at this point, bot has been working for 2 minutes before it stopped.
What Dll did you use was it the "Fasm.NET.dll"? I'm still having issues with HBRelog not entering the password when logging in. Sometimes it will enter it on first run first toon but very rarely.
I tried this with a slight twist but the "WAIT" task doesn't seem to work right. This is what happens: Anyone have similar issues and find a way to resolve it?
first char is set in the logon tab then the first wait(in the task list) is the time for this char (from the logon tab) afterwards logon -> wait if you got problems with hbrelog / gb, set a blank profile in the tab and on each logon task (solved it for me otherwise >50% stucks with loading empty profile message)
Anyone able to interpret this?? By Logon Tab do you mean Account tab? If so, yes my first character is already set there. And yes I realize that the Wait is the time for this first Character... It would be 1 minute (first wait), plus 20 minutes (second wait). The second Task (Start HBrelog) is to start a second wow with my second account which does not interfere with my first account. The goal is to hit 1 profile and have it do all the garrison stuff on all 3 of my accounts (11 characters) but for now I'm starting small and building up. I do not get a loading empty profile message. That's not my problem. My problem is that it DOES NOT WAIT 20 minutes before trying to launch the next profile for my first account. It's suppose to go Launch 1st account, wait 1 minute, launch profile for 2nd account, wait 20 minutes while both of those run, then launch profile for 1st account again with second character and close this profile. Instead it launches second account (good) and then also launches profile for 1st account 2nd character without waiting - despite the 20 minute wait being highlighted as the current task.
I keep getting. Any reason for this? I dont seem to find anyone else reporting this in this thread. Edit: Nevermind I had UE on serial code.
still have a heck of a time setting up the hbrelog to use garrison buddy on each toon nvm got it going was trying to get it to run a profile for each toon and it was causing them to all open haha.
I downloaded the DLL to replace the current one. Sometimes it still gets stuck. I just wish someone would fix this.
You have a great idea but this has really poor settings. Like why have it choose the settings if it's not going to use it. Why ask the account info if it just checks the remember this account? It doesn't use the HB key I put in, it doesn't use the WoW account info I put in either. You should really fix this!
I am sick and tired of coming to my computer and wow is just saying "wow has been disconnected". What is the big deal? Why is HB Relog not ending wow and restarting it? I mean its like that every time. Why doesn't it sense that wow is not running and end the client and restart? I just want HB Relog to absolutely end wow when it disconnects with no exceptions and restart it. Does anyone have a solution to this?
