[Serious Problem with Steam Update] Authentication timeout\Loading screen issues with new Steam update for OA

[Chris9183]

Just to make sure this problem has nothing to do with my setup, my versions, or any addons, I removed and manually deleted the leftovers of Arma 2, Arma 2 OA, and the beta from Steam, and re-downloaded all of them fresh through Steam so I'll have the most up to date versions. I then built a new Epoch test server with the latest server/client builds from epochmod.com, along with the newest versions I just downloaded on Steam. Totally vanilla build, everything up to date.

 

When I connect to the server via Arma 2 OA, it gives my player_data table the proper Steam ID (not the old player UID) and I can join. A few seconds after I join the server, I get an "Authentication timeout" error and am kicked. When I attempt to rejoin, I then get the "DayZ Epoch" loading screen, I hear the shore and birds in the background, and I can even move my character and hear footsteps, but all I see is the loading screen. If I close the server and restart it, I'm able to join without the black loading screen, but all I get is the authentication timeout error again after a few seconds, and if I try to rejoin after that, it's the black loading screen with sounds again. When I check the player_data table, I still see my correct Steam ID in there. My best guess is, there's some sort of problem between Epoch and the Steam update.

 

There are people out there claiming "it's your firewall", "it's your setup", yada yada, it's none of that simple stuff, and the more you claim those things, the more you make this problem seem less legit...this is a widespread issue happening to a big portion of the Epoch community since the Steam update, and I wanted to make this thread to make sure the developers recognize this as a legit problem, and/or at least see if anyone has stumbled across some kind of rigged fix for this until the devs release an official hotfix.

 

Since there are already several threads about these issues, we could just use this thread as the 1 big thread about these two problems.

 

Also, if anyone thinks I've just "done something wrong", I will record a video of every step I've taken to setup the server and my client, and I'll record the results and upload it to Youtube and post it here. 'Cause I'm pretty darn sure it's nothing I'm doing wrong at this point, especially since a big part of the community is having these same issues.

 

Has anyone had any lasting success in getting around these issues?

[Buggis]

People on my server got this problem aswell, i can join but others cannot.

Really sucks...

5.9.98.18:2402 Dayz Epoch NAPF

[Chris9183]

No errors in the RPT. Just a standard disconnection notice when the authentication timeout error happens.

 

Unfortunately, none of the firewall rules are related to this problem. If it were a firewall problem, you could never begin a connection to the server to begin with, much less make it far enough into the game to get the error or the loadscreen problem. For what it's worth, I've disabled all firewall/anti-malware programs I normally run while I'm working with this, and since I'm connecting to the localhost the router doesn't come into play. I wish it were that simple. Thanks though.

 

This is probably some sort of internal problem in the Epochmod that the devs will likely have to hotfix.

[Chris9183]

Just checked it...there are some geometry-related errors of some sort, but nothing that seems related to authentication or the connection/disconnection process. Thanks though.

[nathan00107]

Same issue here, when you return to the lobby and try to rejoin the game just gets stuck on loading with the number '2' in the bottom right corner. I think the devs need to downgrade arma 2 bersions.

[ricechip]

Yup same here. I've reinstalled everything, and cleaned my pc of anything dayz. I cant join any servers still, and my friends join w/o issue.

[Chris9183]

You know, if I were the developer of a mod as big as Epoch, I would keep the community updated about stuff like this. It's been 3 days without a peep from any devs about a hotfix, or even acknowledging the problem exists. Kinda poor communication. It takes 30 seconds to make a quick thread in the announcements forum about it. Just sayin'.

[Eagle]

I understand your frustration. Yelling at the mods for Epoch is not the way to go. There are plenty of servers with this update that work fine.

Ours was down for a few days due to being banned for having ACR installed.

We waited a couple of days for infistar to develop a patch and now it works great.

 

I believe this is a combination of the new BI update and the Epoch update. I am in no way a coder or scripter but there are many very talented people on these forums that will give you a hand as soon as they can.

 

Edit: Just for info I am not an admin on our server just a regular player. I do see alot of players trying to join but not able too so I believe there are still some issues to work out.

[Chris9183]

Yeah don't mean to yell, just kinda disappointed is all

[jgalla5400]

Have done some serious googling and testing on our server and got a list of steps taken from others and our own guys that seem to work for our players

step 1: go to your operation arrowhead folder

step 2: delete the Arma2OA.exe file

step 3: delete the Arma2OAserver.exe file

step 4: go into your Expansion\ folder

step 5: delete the beta\ folder and all it’s contents.

step 6: go to steam library -> operation arrowhead -> right click -> properties -> local files -> verify integrity of game.

step 7: wait for game to verify. When it’s done you will have basic arma 2 files, (Versions of these can change dependent on steam updates )

step 8: launch arma 2 oa with new files. exit the game after you see the main menu.

step 9: go to \Steam\SteamApps\common\Arma 2 Operation Arrowhead\BEsetup\ and run the Setup_BattlEyeARMA2OA.exe file, this will install the new Battleye on your machine

step 10: wait for game to update. When it’s done you will have the new steam-only version of Arma2OA.

To access the server from Arma OA

1) Open Steam and load Arma 2: OA (non beta)

2) From the menu options, select “Expansions”

3) Make sure that the following two setup options are completed.

i) Make sure that the Expansion “DayZ Epoch 1.0.5″ is visible and active. If it is not visible, use Steam to update Arma 2: OA (non beta) and repeat step 3 (i).

ii) Make sure that the Expansion “DayZ Epoch 1.0.4.2″ has been disabled.

4) Make sure any other DayZ Expansions have been disabled, inc Arma 2 DayZ Mod.

5) Exit out of the “Expansion” Menu by clicking “OK”; Arma 2: OA should restart after a warning message.

6) Once the game has restarted, select “Multiplayer”

7) Click “Remote” and then add server address and port accordingly and click “OK”

8) You are then taken back to the server access page and select the server and “Join”

9) You should then be presented with the pre game access screen, follow the usual step to access the map.

Hope this helps

[Chris9183]

Jgalla I just did everything you listed and unfortunately the same issues are still happening. Thanks for the suggestions though.

[Creep]

This problem is caused by different beta versions used by client and server!

 

I fixxed this problem by simply using the exact same beta as the server!

 

This means, that even if u are able to join a 112555 server with the newest beta patch, you will get this error.

 

Simply start your DayZCommander, install the 112555 just like normal and join the server -> enjoy playing without errors

 

If you want to upgrade again:

 

Open steam-> Libary-> right click arma 2 oa -> propeties -> local data -> verify game files -> let it scann and download everything -> set the beta to Beta- again

(if thats allready the case and you are not able to join, set it to the 1.62 version -> let it download, then set it back to Beta- and let it download -> then join any server installed the lastest beta

[Chris9183]

Thanks Creep but that is not the problem. As you'll see if you read my original post, ricechip's post, and my response to Jgalla's post, the client and server are both using the same beta versions. Also, the latest version is not 112555, installing that with DZC would downgrade the client and solve nothing. Thanks anyway.

[Creep]

Its the lastest on DZC thats what I wanted to say :D

 

The problem is steam itself I guess, since I didnt found anything in files saying: authentication timeout

 

I used to change the cd key to my old one, which wasnt the one I currently use with steam and turned steam off, starting directly trough DZC

 

Since I've got the old CharID instead of the steam one, everything works pretty fine, I guess you just shouldnt let steam be able to interact with your game during startup

[Brockie]

Hi peoples.  Sucks that you are having problems.  I know how frustrating that can be as I've been there myself.  The first time I set up my vanilla epoch, I had the problem of being able to hear sound while stuck at loading screen.  After some time I decided try try again, so I started over from scratch.  I don't know what the issue was, or what I did differently, but it worked flawlessly.  I think maybe I deleted all the player data, character data, and logins to make it work.  In the end I have had mine running stable for about a week.

 

@jgalla5400 wrote: 

Have done some serious googling and testing on our server and got a list of steps taken from others and our own guys that seem to work for our players

step 1: go to your operation arrowhead folder

step 2: delete the Arma2OA.exe file

step 3: delete the Arma2OAserver.exe file

step 4: go into your Expansion\ folder

step 5: delete the beta\ folder and all it’s contents.

step 6: go to steam library -> operation arrowhead -> right click -> properties -> local files -> verify integrity of game.

step 7: wait for game to verify. When it’s done you will have basic arma 2 files, (Versions of these can change dependent on steam updates )

step 8: launch arma 2 oa with new files. exit the game after you see the main menu.

step 9: go to \Steam\SteamApps\common\Arma 2 Operation Arrowhead\BEsetup\ and run the Setup_BattlEyeARMA2OA.exe file, this will install the new Battleye on your machine

step 10: wait for game to update. When it’s done you will have the new steam-only version of Arma2OA.


To access the server from Arma OA

1) Open Steam and load Arma 2: OA (non beta)

2) From the menu options, select “Expansions”

3) Make sure that the following two setup options are completed.
i) Make sure that the Expansion “DayZ Epoch 1.0.5″ is visible and active. If it is not visible, use Steam to update Arma 2: OA (non beta) and repeat step 3 (i).
ii) Make sure that the Expansion “DayZ Epoch 1.0.4.2″ has been disabled.

4) Make sure any other DayZ Expansions have been disabled, inc Arma 2 DayZ Mod.

5) Exit out of the “Expansion” Menu by clicking “OK”; Arma 2: OA should restart after a warning message.

6) Once the game has restarted, select “Multiplayer”

7) Click “Remote” and then add server address and port accordingly and click “OK”

8) You are then taken back to the server access page and select the server and “Join”

9) You should then be presented with the pre game access screen, follow the usual step to access the map.

Hope this helps

 

Just wanted to say that steps 1-10, that was written by me, is a Frankenstein (because you tried to merge two different [how-to] and missed a lot of the steps) and outdated (because steam changed a little and I had to update my guide).

 

So to be clear for all you peoples...

 

This is my proper guide for updating beta patch:

 

 

Here's my rollback guide, if you wanted older versions:

 

 

And this is instructions for reinstalling battleye for clients:

 

 

 

I recommend fresh reinstall from scratch using 1.0.5.1 with either 125402 or 125548 (those are the ones I tried and worked)

 

I did not try epoch 1.0.5.1 with 112555 but I did see some servers on commander that seem to be using it.

[jgalla5400]

Hi peoples.  Sucks that you are having problems.  I know how frustrating that can be as I've been there myself.  The first time I set up my vanilla epoch, I had the problem of being able to hear sound while stuck at loading screen.  After some time I decided try try again, so I started over from scratch.  I don't know what the issue was, or what I did differently, but it worked flawlessly.  I think maybe I deleted all the player data, character data, and logins to make it work.  In the end I have had mine running stable for about a week.

 

@jgalla5400 wrote: 

 

Just wanted to say that steps 1-10, that was written by me, is a Frankenstein (because you tried to merge two different [how-to] and missed a lot of the steps) and outdated (because steam changed a little and I had to update my guide).

 

So to be clear for all you peoples...

 

This is my proper guide for updating beta patch:

 

 

Here's my rollback guide, if you wanted older versions:

 

 

And this is instructions for reinstalling battleye for clients:

 

 

 

I recommend fresh reinstall from scratch using 1.0.5.1 with either 125402 or 125548 (those are the ones I tried and worked)

 

I did not try epoch 1.0.5.1 with 112555 but I did see some servers on commander that seem to be using it.

Thanks for the detailed update and FYI I didn't claim to have written any of it I said it was taken from others ! In actual fact I think it was on the MGT site , I thought it would be helpful to share :)

The steps were an amalgamation of 2 lots of things myself and other players on out server tried :)

[Chris9183]

Hey Brockie, thanks for that, unfortunately none of those steps are making any difference. I could roll back to an earlier version of Arma 2 OA but I'd prefer to just wait until the Epoch guys release a hotfix or an update.

[m1cr08472]

I've being having this problem, not just with epoch mod every dayz mod

 

I seemed to fix it by going into dayz commanders settings tab and ticking "replace original arma2 files with beta so steam works"

 

Now I just need to fix all the you cannot edit this mission errors :/

[RimBlock]

Not specifically for the authentication error but there is a big thread for the black screen with sound after login.

[Phobix]

I found the solution to your problem after a buddy and I spent a few hours hunting down the issue. 

In your bat file, you need to change your bat file .exe paths

This is what it currently is:

@echo off

start "arma2" /min "Expansion\beta\arma2oaserver.exe" -port=2302 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

 

This is what it needs to be

 

@echo off

start "arma2" /min "arma2oaserver.exe" -port=2302 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

The issue is that you need to use the exe in the root folder rather than the exe in the expansion folder. 

[nathan00107]

@Phobix This was the first thing I had to do to launch a server because I do not have an expansion folder. The issue still persisted using your method.

[Phobix]

Nathan, I was having the same exact issue as you and it was solved using that method. I think this points to a mismatch in versions, somehow. Since that change, my server has been stable with us playing for over 5 hours.

 

Anyway, good luck in solving the issue!

[nathan00107]

Another fix that has been working for a lot of people is this. 

 

Work Around: 

 

If you add the two endLoadingScreen; statements in your init.sqf it seems to work aorund the problem.  In no way is this a fix to the real issue.  So far in development I have not seen any issues.  I be rolling this to my prod servers tonight.

 

endLoadingScreen; // Work around for 2nd Log in hang
if (!isDedicated) then {
    //Conduct map operations
    0 fadeSound 0;
    waitUntil {!isNil "dayz_loadScreenMsg"};
    dayz_loadScreenMsg = (localize "STR_AUTHENTICATING");
    
    //Run the player monitor
    _id = player addEventHandler ["Respawn", {_id = [] spawn player_death;}];
    _playerMonitor =     [] execVM "\z\addons\dayz_code\system\player_monitor.sqf";    
    
    //anti Hack
    [] execVM "\z\addons\dayz_code\system\antihack.sqf";

    //Lights
    //[false,12] execVM "\z\addons\dayz_code\compile\local_lights_init.sqf";
    
};

#include "\z\addons\dayz_code\system\REsec.sqf"

//Start Dynamic Weather
execVM "\z\addons\dayz_code\external\DynamicWeatherEffects.sqf";


#include "\z\addons\dayz_code\system\BIS_Effects\init.sqf"
endLoadingScreen; // Work around for 2nd Log in hang

 

 

I haven't had the time to try it out but it seems to work wonders.

[xMistdemon420x]

I found the solution to your problem after a buddy and I spent a few hours hunting down the issue. 

In your bat file, you need to change your bat file .exe paths

This is what it currently is:

@echo off

start "arma2" /min "Expansion\beta\arma2oaserver.exe" -port=2302 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

 

This is what it needs to be

 

@echo off

start "arma2" /min "arma2oaserver.exe" -port=2302 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

The issue is that you need to use the exe in the root folder rather than the exe in the expansion folder. 

 

 

This Worked For Me Thank You

[jensenfern25]

where do i find my bat file

im kind of new to all this :'(