Getting this error [8:40:25 PM:641] Starting ARelog v1.0.2.7 [8:40:25 PM:644] Checking for updates. [8:42:28 PM:961] System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at System.Xml.XmlDownloadManager.GetNonFileStream(Uri uri, ICredentials credentials) at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials) at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn) at System.Xml.XmlReader.Create(String inputUri, XmlReaderSettings settings, XmlParserContext inputContext) at System.Xml.XmlReader.Create(String inputUri, XmlReaderSettings settings) at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options) at System.Xml.Linq.XDocument.Load(String uri) at ..()
[1:48:56 PM:14] [PID: 6412] Please make sure you selected Wow.exe as the WoW Path. If you did so ARelog doesn't support DirectX11 on WoW. Please set Graphics API to Directx9 in WoW video settings before using ARelog. I am 100% sure I am putting Wow.exe as the WoW path and WoW is on DirectX9. What's wrong?
Awesome work on this thingie. Was reluctant to try it for a while. One thing I'll note: it's kind of unintuitive that you have to double-click to get a file browser in the PATH fields. (I only noticed it after I entered the whole data in the fields, as I'm mostly a keyboard user and tabbed from field to field)
today when i update arelog plugin he HB wont to start see what he give me: Initialization complete. Honorbuddy is up-to-date Starting the bot! Tilemap is null!
Great work. So far one bug: It does not always detect WoW crash windows, so that window is not closed and the wow client is not restarted.
I'll second this.. the old method worked fine for me and took less than 2 mins to log all my accs in.. and now the new method is getting on for 15 minutes.
... And you are complaining why? That's still 15 minutes you didn't have to manually click anything. I see no reason to complain when all you did was hit a single button after the initial setup.
Hello my name is "insert your name here" I like to leech flame and complain about all things going on on this forum. guess what? Don't like it - Don't use it!
[1:48:56 PM:14] [PID: 6412] Please make sure you selected Wow.exe as the WoW Path. If you did so ARelog doesn't support DirectX11 on WoW. Please set Graphics API to Directx9 in WoW video settings before using ARelog. I am 100% sure I am putting Wow.exe as the WoW path and WoW is on DirectX9. What's wrong?
Raphus, Thanks for making a new version that works better at some point. The real remaining bug now is to add a fix for a problem that occurs exactly when a server is full and has a waiting queue (which happens everyday at this time on some EU servers) The relogger keeps spamming the realm server selection screen until Arelog crashes (this happens always when it switches from Server "not full" to Server "full with waiting queue"), and if i manually close the wow window quickly to avoid that crash, Arelog restarts that wow account then after passing the login screen it stops and waits for the server waiting queue to finish then enters normally to the server (which is acting ok in this specific case) Another problem with your latest version is that it acts sequentially and makes things worse, because as long as there is a waiting queue on the first account for example that takes between 5 to 20 minutes, all the remaining accounts won't launch and keep waiting for the first one to login which becomes a bitter problem I'm suggesting two fixes which would make this work flawlessly (but you should know better how to deal with this) : 1- To add a check when changing realm servers on the server selection screen (if it spams a server for an amount of time like say 5 to 10 seconds and doesn't enter the character selection screen, it can close wow window to avoid arelog crash), you can quickly test this on EU servers by creating a character on any server with the level of population "LOCKED" which happens everyday at this time i'm posting. 2- Adding another check just after entering the login + pass info when the waiting queue window shows up, and if it takes more than 30 seconds to enter the character selection screen or the server selection screen (which means it is waiting in queue), Arelog can start launching the other accounts. P.S : if you can't make a fix for the option 2 (i don't mind having to wait for 20 minutes), at least if you could think about a fix for option 1 because having Arelog crashing makes all the account's schedules list reset and it becomes much more problematic to handle when you have different schedule tasks for each account. Thanks again for your hard work.
ARelog not close wow and buddy and not doing the next scheduled task, please see the hour, help manual closing wow and Buddha. This only happens sometimes not always. Please help. Code: [23:19:46:54] Starting ARelog v1.0.2.7 [23:19:46:57] Checking for updates. [23:19:46:286] ARelog is up-to-date [23:19:50:2] Starting WoW [23:19:50:4] Waiting for WoW to idle [23:19:55:731] [PID: 4092] Moving WoW Window to: 1576, 0 - With size: 336x294 [23:19:57:102] [PID: 4092] Hooking EndScene and starting Lua [23:20:00:700] [PID: 4092] Selecting character and entering world. [23:20:12:627] [PID: 4092] Logged in! Waiting on loading screen. [23:20:12:627] [PID: 4092] Disposing hooks [23:20:12:628] [PID: 4092] Starting Honorbuddy [23:20:25:490] [PID: 4092] Current Task: Botname: ProfessionBuddy - ProfilePath: - Finish Time: 2012-01-17 00:55:50 [00:55:52:966] [PID: 4092] Reached end of task. Terminating. <---------------------------------------> WoW and Buddy is still run <-------------------------------------------------------------------> ------->[05:44:34:261] [PID: 4092] Current Task: Botname: ProfessionBuddy - ProfilePath: D:\Miranda\Bots\ProfessionBuddy\Profiles\[PB] AH.xml - Finish Time: 2012-01-17 01:13:52 <------- [05:44:34:261] [PID: 4092] Reached end of task. Terminating. [05:44:39:262] [PID: 4092] Current Task: Botname: ProfessionBuddy - ProfilePath: - Finish Time: 2012-01-17 07:20:34 [05:44:39:262] [PID: 4092] Restarting WoW + Buddy [05:44:39:262] Starting WoW [05:44:39:284] Waiting for WoW to idle [05:44:48:688] [PID: 3504] Moving WoW Window to: 1576, 0 - With size: 336x294 [05:44:49:756] [PID: 3504] Hooking EndScene and starting Lua [05:44:56:85] [PID: 3504] Selecting character and entering world. [05:45:08:231] [PID: 3504] Logged in! Waiting on loading screen. [05:45:08:231] [PID: 3504] Disposing hooks [05:45:08:231] [PID: 3504] Starting Honorbuddy
Changelog v1.0.2.8 Sequential Login setting has been added for user that want to switch between the new and old logging method.
