Page 1 of 1

Crash at EULA screen

Posted: Sun Oct 29, 2017 8:10 pm
by Freakzilla
I can launch fine...get to the warhammer main title screen with the words LOADING, at the top of the screen, then it switches to the EULA screen i think....im not sure because it just vanishes as soon as it gets to that screen. I have looked at the stickies, watched the youtube videos, changed folder permissions, checked my dxdiag, read thru alot of these other posts. I downloaded the 5 part zip file from mega download, for my client. Dont know what else to do. I'm old and need a hand with this.

Thx

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 4:25 am
by Freakzilla
I found this in one of the logs...

[2013/12/19 18:43:39] libpatchclient initialized.
[2013/12/19 18:43:39] Currently running as [C:\Program Files\Electronic Arts\Warhammer Online - Age of Reckoning\testpatch.exe]
[2013/12/19 18:43:40] Currently running as [C:\Program Files\Electronic Arts\Warhammer Online - Age of Reckoning\testpatch.exe]
[2013/12/19 18:43:40] Notification of restart with alternate filename
[2013/12/19 18:43:41] libpatchclient initialized.
[2013/12/19 18:43:41] Currently running as [C:\Program Files\Electronic Arts\Warhammer Online - Age of Reckoning\testpatch.bin]
[2013/12/19 18:43:51] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 50331651
[2013/12/19 18:43:51] MythLogin::LoginClient::ReportTimeout: Unrecognized expected reply type: -227432511
[2013/12/19 18:43:55] Failed to send HTTP request for file [http://patch.warol.net:1380/warpatch2/p ... r.prod.sig]
[2013/12/19 18:44:09] Failed to send HTTP request for file [http://patch.warol.net:1380/warpatch2/p ... r.prod.sig]
[2013/12/19 18:44:23] MythLogin::LoginClient::Teardown: Exhausted all servers in cycle.
[2013/12/19 18:44:23] Failed to send HTTP request for file [http://patch.warol.net:1380/warpatch2/p ... r.prod.sig]
[2013/12/19 18:44:38] Failed to send HTTP request for file [http://patch.warol.net:1380/warpatch2/p ... r.prod.sig]
[2013/12/19 18:44:38] Failed to retrieve remote file [patcher.prod.sig].
[2013/12/19 18:44:38] Failed to read remote product check.
[2013/12/19 18:44:38] Failed to patch patcher product.

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 4:46 am
by wargrimnir

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 4:55 am
by Freakzilla
Ive downloaded the launcher twice and followed those instructions. Also, I have no option to click Unblock on the General tab. I also have problem with unchecking the Read Only on the warhammer folder. I have full control as admin, Ive went into the powershell and did the recommended get-childitem "E:\Warhammer Online - Age of Reckoning" -recurse | unblock-file -confirm, but it still is marked as read only. I have a suspicion that perhaps the download package i did from the mega download may have been corrupted, but im not doing it again...it took a full day to download all those things, and I do not own the internet at my current location, and data is limited. I also downloaded the hotspot VPN, however it requires a credit card.

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 5:10 am
by wargrimnir
I'm not sure where you got those logs from, but they're dated 2013. They indicated you were using warpatch.exe to start the game. I suppose this isn't the case.

If you grabbed the rest of the files from the launcher download, your mythloginserviceconfig.xml file should have '<Address>46.105.54.77</Address>' in it.

The only other things that really give us issues are antivirus software that is aggressive about the patcher using memory injection to interface with war.exe. Occasionally we've found that your ISP may be blocking a connection to our site, which is why a VPN is recommended as a troubleshooting step. There are free ones out there.

Some people unfortunately, be it their specific system setup, anti-virus, ISP, or other unknown factors, simply are unable to get the game to work. We don't often do deep dives into specific installs these days, as we have a long list of know issues related to the client. Discovering new issues generally falls on the users who are experiencing them, and have figured out a solution.

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 5:20 am
by Freakzilla
I completely understand. Im a little confused about the directx 9 .dll in the folder. Im currently using dx12 on windows 10. Im not sure if I need to downgrade or what. dxdiag shows dx12..however there is a dx9.dll in the war folder. Im also searching for the unpacked launcher download. I will also look for a free vpn, and keep working on it. Thx for your attention.

ps I dont know where to get the error logs. this is the only log i can open that has a current date.

[2017/10/30 00:01:27] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2017/10/30 00:01:27] Attempting authentication using session token
[2017/10/30 00:01:27] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2017/10/30 00:01:27] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2017/10/30 00:01:27] Active Sockets: Host [0] Client [1]
[2017/10/30 00:02:05] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2017/10/30 00:02:05] Attempting authentication using session token
[2017/10/30 00:02:05] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2017/10/30 00:02:05] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2017/10/30 00:02:05] Active Sockets: Host [0] Client [1]
[2017/10/30 00:08:20] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2017/10/30 00:08:20] Attempting authentication using session token
[2017/10/30 00:08:20] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2017/10/30 00:08:20] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2017/10/30 00:08:20] Active Sockets: Host [0] Client [1]
[2017/10/30 00:22:05] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2017/10/30 00:22:05] Attempting authentication using session token
[2017/10/30 00:22:05] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2017/10/30 00:22:05] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2017/10/30 00:22:05] Active Sockets: Host [0] Client [1]

Re: Crash at EULA screen

Posted: Mon Oct 30, 2017 5:42 am
by wargrimnir
That's a network issue then.

WAR uses DX9, it's not a downgrade, just a different version of DX, they're independent of each other. If you have other games installed, you probably already have the required stuff for it.