Jump to content
  • 0

[HOW-TO] Rollback Arma 2 Beta Patch


Brockie

Question

This is not my fix, I'm just posting it here for people as there seems to be a lot of bad information out there.  This fix requires the steam version of arma 2.

 

1. First go into your Arma 2 OA folder and delete all the exe files (ArmA2OA, arma2oaserver, Arma2OA_BE)

 

2. Open the Expansion folder and inside delete the folder called 'beta'.  If you are running a newer version you might not have a beta folder and you can skip this step.

 

3. Now go into your steam library and right click on Arma 2 OA -> properties.  Select the beta tab and pick 1.62 - older version of the game.

 

4. Again in properties choose local files tab and verify integrity of game.  This will bring you back to 1.62.95248

 

5. Now you can open DayZ Commander and install any patch you want, no more error about 1.63 being newer then 1.62.

 

Hope that helps.

Link to comment
Share on other sites

16 answers to this question

Recommended Posts

  • 0

patch 1.63 is getting more and more annoying, i have all automatic update disabled in steam arma 2 OA, the both methods worked great for me for months, but then ~

 

about 2+ month ago I could downgrade 1.63 Arma2 in the easy way:

- Delete the exe's, verify in steam, start, install 103718(1.62) in dayzcommander

 

1+ month ago, the method stopped working, so I had to start to do this:

- Delete the exe's, BUT now I had to choose in steam arma2 OA properties under beta the 1.62 older version, verify, start, install 103718(1.62) in dayzcommander

 

2-3 week ago, it stopped working again, and now i had to combine the methods in this forum:

- Delete the exe's, shut down steam, delete regedit arma 2 OA, start steam, choose in steam arma 2 OA properties the beta to 1.62, verify, start, and install 103718(1.62) in dayzcommander

 

1 week ago, also this stopped working, now steam won't start arma OA with beta 1.62, now i had to:

- Delete the exe's, shut down steam, delete regedit arma 2 OA, start steam, choose in steam arma 2 OA properties the beta to 1.62, verify, BUT NOW arma 2 OA in beta 1.62 state won't start, but "try to start" was enough so dayzcommander recognized arma2 OA, install 103718(1.62) in dayzcommander, but since steam 1.62 version wont start, i had to put back arma 2 OA to "normal" none beta state, WITHOUT verify, now arma 2 OA starts again, also in dayzcommander, but if I verified arma 2 OA in "normal" non beta status, it switched back to 1.63, even I had 103718(1.62) installed in dayzcommander

 

1 day ago, it...yeah you know, stopped working...

But this time, i dont have a solution.

 

If i set arma OA back to "normal" no beta, it instant update to 1.63 even having autoupdate deactivaded

If i leave 1.62 beta, it won't start, unless u start it without battle client, but it will not allow u to play on dayz mod's without battle client.

 

 

The reason why i had to switch versions, was simply searching new dayz servers over weeks, some have 1.62, some have 1.63, and now im defeated by 1.63, but really want go back to 1.62 without reinstall

 

I sent steam a report, they shall communicate with arma 2 support, and make beta 1.62 version work again, or even better find a solution for a simple down grade in dayzcommander, like it was always possible earlier time long ago.

Link to comment
Share on other sites

  • 0

You realize that you don't really need to switch versions?

 

There are 2 Arma2 executables:

  • the one in the Arma2OA directory, that is used for connecting to the up-to-date (not the 112555) 1.63 servers
  • the one in the expansion/beta/ directory that you get when you downgrade to 1.62 and use DZC to patch to 103718

Switching the version to a current 1.63 in Steam does not delete your 1.62.103718 version. I'd recommend not to delete it manually for the time being.

 

So, all you need to do is to

  • use DZC to connect to 1.62.103718 servers (the exe in expansion/beta/)
  • use Steam to start the 1.63 version and there connect via the Arma multiplayer menu

I myself prefer to use bat files for this, see my post #29 in

 

The bat file cited there is for connection to our Chernarus 1.63 server, atm I don't have access to a file in the 1.62 version, but you could connect to tsde1.vilayer.com:10005 , and open the file browser of the 'wait for admin channel' for Overpoch. There you'll find a bat file designed to connect to our Overpoch server that is still running 1.62.103718 because it has another hoster than the other servers.

 

Edit: I've edited that post to show an example for a 1.62 bat, too.

Link to comment
Share on other sites

  • 0

you realize that newer version don't really have expansion beta folder?

 

i dont have expansion/beta, where is it located in newer? Its not in steam folder, or anywhere in C:/User

i never heard i dont need to switch version, but maybe you are right, who knows, things happens.

 

but since I and others dont have expansion/beta, your help is sadly no help. But i really appreciate the try :)

 

But doesnt matter anyway, my post was more as an info for others reading this solutions having same problems, and see they are not alone, I put all my hope in steam fixing the 1.62 unable to start problem. Because if i can start it again, no more problem.

Link to comment
Share on other sites

  • 0

You'll have expansion/beta (again), as soon as you use steam to reconstruct the 1.62 version and then use DayZCommander to install 103718(1.62).

 

At least, after doing this, I myself got back the expansion/beta I had faithfully deleted following the advice one of the how-to-update threads in these forums gave (thus sadly depriving me of the means to admin the one of our servers that hadn't been transitioned, yet) ;-)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Discord

×
×
  • Create New...