So you know that the moment you apply a RC or Final patch on arma games and the addons are changed there is no going back unless you have kept a backup or reinstall. Open then a devheaven ticket to ask for a feature to uninstall patches.
So you know that the moment you apply a RC or Final patch on arma games and the addons are changed there is no going back unless you have kept a backup or reinstall. Open then a devheaven ticket to ask for a feature to uninstall patches.
What on earth does that mean? We have to roll back to 1.59?
Dwarden, please would you state to which version(s) a patch should be applied?
Having just rolled back 1.61 RC1 to 1.60 & re-patched with 1.61 RC3, & it being clear from Krem's post that this new patch will not work with 1.61 RC3, I have no idea what to do next. And I do want to aid in testing...
I understand Beta’s and the ‘be it on your own head’ type thing that goes along with them, that’s fine. I'm playing back upto Beta 94444 as it seemed to me the best place to sit tight for a while. I also understand the dangers that can be involved in using the RC, I put 1.61 in, after first backing up, then after viewing 1.61, went back to 1.60, I got a little worried things were wondering slightly, textures etc..
However I’m a little confused that in essence this new patch 1.62 is actually going to be the sequel, if you like, to patch 1.59, as it says its not compatible with 1.60 or 1.61, therefore have we done a Bobby Ewing, and come out of the shower with a chunk of time missing/forgotten about, i.e. 1.60 + poor old 1.61, which really didn't go anywhere much, both just sort of never happened.
(your probably all too young to understand the ‘Dallas’ analogy, still)
Don’t mind reinstalling I have all hard copies, so there is no issues if I have problems with my backup process, but when I saw “not compatible with 1.60 or 1.61” it sort of surprised me...
Of course it could just be me getting old![]()
Rigs - Smart AI - Skirmish - AI find cover- Heavy firefight -
ai PBO - PBO - A2 ai - A3 ai - 'Khushab'
He means that you can't play on 1.60 or 1.61 servers once you apply the patch (or if you apply this to a server, people with 1.60 and 1.61 will not be able to join!). If you have applied 1.61 RC1 or 1.61 RC2 you need to roll back to 1.60 before applying this patch.
EDIT again ----> Just to let people know, I have applied it to my 1.60 base install and it all seems fine so far!
Last edited by Jedra; Jul 19 2012 at 19:57.
Jedra's Addons
Arma 2 : Enhanced Skills Slider
Take On Helicopters : Take On Taxi | Jedra's Time Trials | Weapon Indicators | No Radar
We would make it easier, if it would be reasonably possible, but we see no easy option how to do this. Currently you have following options, which do not seem quite difficult to me:
- do not test full RC, test a beta only (the beta can be tested alongside with a stable version)
- before testing RC do a full copy of the game installation so that you can revert the RC if needed
Ondrej Spanel, BIS Lead Programmer
You need to have legitimate install 1.60 to be able to upgrade to 1.62. It is as simple as this. It is already extremely complex process to handle and we are always absolutely clear how Release Candidates work. There is not easy way for us to handle it differently in the existing system so you either can live with it (the easiest way is to simply create full backup of the Arma 2 OA install folder somewhere else...) or not. If not yous simply should skip RCs and wait until the final patches and maybe use betas that are more flexible alongside the stable game. We of course appreciate help of our users with finalizing the updates and without release candidates this would not be really possible for us to release further updates to the game that is as moddable and open as this.
Few notes:
* we had to raise the version number to 1.62 as there are several low level incompatibilities between some 1.61 builds that lead into CTD to clients and servers
* we had to remove the ACR lite content from the patch as some of it requires Arma 2 present and there is atm no robust way of handling the dependencies. Instead, we are going to release ACR Lite as full free optional DLC to allow all our users to be at the same compatible level without enforcing purchase of DLC pack
We certainly hope this 1.62 is the final patch iteration and we have no intention opening it again unless a serious regression is found.
Marek Spanel - CEO www.bistudio.com
Thanks to the Spanel family for the answers, that's clearer now![]()
Yes yes, too late I know, but:
unit addMagazine[name, ammoCount,multiplier]
Optional Multiplier.
eg this addMagazine ["30rnd_556x45_STANAG,30,6]; to add 6 30 round, STANAGs to a unit.
-k
ARMA 2 Mission packs:LITE Coop mission package + LIMA coop mission package (ACE + ACRE) + More ACE + ACRE missions. + Aliabad coop Mission Package+ Fireforce Takistan NEW
ARMA 3 Mission packs:Fourplay Coop Mission Pack NEW
Kill things, break stuff. Repeat as necessary.
Thank you, that answers my question. Off to download, will roll back & patch tomorrow evening
BTW, today I started experimenting with the FXAA/SMAA/ATOC settings & the Reinhard & Filmic tone mapping - not finished but on Chernarus I'm getting another 2-3 FPS plus it looks better. Nice developments, with the new commands & the new addons dependent on them such as TPWC AI suppression, the 1.62 patch will be a milestone. Thanks to all at BIS for your hard work.