Hey Raphus, Here is the log file taken from the log folder, it has nothing more than we just posted as text before. Please if you need more infos (like the OS, the buddypath in xml file used or the exact version of HB used because some may have the release 5354 and some are using HB test version 5387, i tried both, and none of them work as intended) when you added a delay on HB launch, have you changed the code for HB path reading ? is it possible to push a version without the delay, just to know if it fixes this bug ? Just some thoughts which may or may not help with the debugging...
Indeed Infernik, Arelog disconnects you when not ingame instantly. Raphus, thanks for fixing the HB restart problem, can you please check if the 30 sec delay code (when not ingame) is added on this latest version ? because it has now the same issue as it was on version 1.0.1.8. This change is missing or not working anymore : Changelog 1.0.1.9 : Added a 30 sec delay to disconnect check so it does not recognize the loading screen as a disconnect.
seriously this is the last time im asking for logs. Reports without logs will just be ignored from now on
Here's the log Raphus, sorry for not posting a log. It's because the issue has already been posted and fixed on version 1.0.1.9 and on 1.0.2.0 it came back again, which means either the ingame delay check code is missing now or it is broken somehow. Thanks again for your help.
ARelog v1.0.2.1 is pushed. Changelog Restarting WoW and HB on loading screen is fixed yet again. (Delay has been increased to 60 seconds to be sure)
e1. Added 2 log files (same thing . stuck on terminating... (nothing happens, and arelog gets stuck. close all or close on specific bot aren't working))
Hey raphus, since you are in "updating mood", can you please increase the the time Arelog waits before killing HB, thinking it crashed? When my internet connection is weak or auth is slow, it kills HB before it can load. Thanks in advance.
db00, you log is from version 1.0.1.9, please update to last version, test it, and post a new log. Good Job Raphus, but you partially fixed the 60 sec ingame delay check bug. Now it does a check for a delay of 60 seconds on the first loading screen and it works correctly. But on the next loading screen it shuts down WOW client and HB. I think the bug is this : you have a timer that checks for a delay of 60 seconds when not ingame, but it seems it doesn't reset and stop after you get back ingame (after the loading screen finishes). So on the next loading screen it instantly closes WOW and HB because it finds the timer value greater than 60 sec. A log is attached and shows some of my accounts doing what i described above. To test it, you can launch a bot and do a BG BOT beta, which has loading screens on each BG game. Waiting for your reply and help, thank you
hi i have a dc after each bg (Bg Bot) since the relogger update.. View attachment 08.10.2011_04_29 6932 Log.txt View attachment 08.10.2011_02_07 5092 Log.txt View attachment 08.10.2011_08_50 4384 Log.txt View attachment 08.10.2011_06_10 6900 Log.txt View attachment 08.10.2011_03_36 4516 Log.txt View attachment 08.10.2011_01_09 4976 Log.txt View attachment 08.10.2011_07_55 6488 Log.txt View attachment 08.10.2011_05_33 1680 Log.txt View attachment 08.10.2011_03_03 4476 Log.txt View attachment 08.10.2011_00_31 6820 Log.txt View attachment 08.10.2011_07_21 1808 Log.txt View attachment 08.10.2011_04_50 1988 Log.txt View attachment 08.10.2011_02_18 5652 Log.txt View attachment 08.10.2011_09_07 6236 Log.txt View attachment 08.10.2011_06_23 5524 Log.txt View attachment 08.10.2011_03_55 6164 Log.txt View attachment 08.10.2011_01_32 7080 Log.txt View attachment 08.10.2011_08_19 6216 Log.txt View attachment 08.10.2011_05_38 5600 Log.txt View attachment 08.10.2011_03_17 6768 Log.txt View attachment 08.10.2011_00_44 5252 Log.txt View attachment 08.10.2011_07_31 2412 Log.txt View attachment 08.10.2011_04_56 4980 Log.txt View attachment 08.10.2011_02_20 5088 Log.txt View attachment 08.10.2011_09_10 7060 Log.txt View attachment 08.10.2011_00_02 3740 Log.txt View attachment 08.10.2011_06_35 7000 Log.txt View attachment 08.10.2011_04_17 3104 Log.txt View attachment 08.10.2011_01_52 4788 Log.txt View attachment 08.10.2011_08_34 7036 Log.txt View attachment 08.10.2011_05_56 2244 Log.txt View attachment 08.10.2011_03_34 6032 Log.txt View attachment 08.10.2011_00_51 5656 Log.txt View attachment 08.10.2011_07_44 7160 Log.txt View attachment 08.10.2011_05_09 3768 Log.txt View attachment 08.10.2011_02_46 1988 Log.txt View attachment 08.10.2011_09_22 1012 Log.txt View attachment 08.10.2011_00_03 5616 Log.txt View attachment 08.10.2011_07_00 6984 Log.txt
It kills wow when I logout and back in with HB attached. Only attached an HB log since ARelog hasn't created a new one. Last created log just says Code: [9:36:04:346] Starting ARelog v1.0.2.1 [9:36:04:347] Succesfully updated to v1.0.2.1
You probably did this, but are you sure your HB path is spelled correctly? So not ending like; Honoorbuddy.exe, honorrbuddy.exe, honorbuddy,exe?
Used to run really stable, now I'm getting a huge error message upon trying to start arelog. then it crashes. :/
Something is wrong in your monitors.xml file, did you edit it manually? i edit my monitors manually with an xml editor and i always get that error and it is often when i forget something < > = " " / or what ever Also loom it say line 1 pos 1, there is the proiblem.
Awsome relogger Having one annoying error though when HB gives me the error "process must have frozen or gotten out of sync" which usally causes or is caused by wow freezing is there a chance you could have it restart both hb and wow when it happens since now it just restarts hb and since wow has crashed/frozen it just sits there doing nothing here is the error I get from HB
