Jump to content
Sign in to follow this  
Dwarden

ARMA 2: Operation Arrowhead 1.60 RC #4 (Release Candidate)

Recommended Posts

Guest

Cant wait for the final 1.60 patch and for people to get it on there servers but I do have two question, with the new FXAA feature will there be an option for it in game menu or will it remain just in the cfg file? Also what is the max number FXAA can be set to?

Share this post


Link to post
Share on other sites
Also what is the max number FXAA can be set to?

it is 17

Share this post


Link to post
Share on other sites

we are now experimenting with optional sharpen filter for the FXAA but it will be released after 1.60 (to not break something so close prior release) in 1.61 betas

so it should offer better clarity on details which are not supposed to be 'blurred'

---------- Post added at 08:15 ---------- Previous post was at 08:14 ----------

Got a strange issue with the 1.60 version of Arma 2/OA as Combined Ops.

It appears that when running the Steam version of Combined Ops, any mods in the game directory will automatically be loaded, even if 'Set Launch Options' in Steam is empty. Is this supposed to happen now? :confused:

check your arma2oa.profile file most likely You got some mods saved there from first time when Extension UI was introduced

also mods like ARMA 2, OA, BAF and PMC are inserted into registry automatically (that's main change in 1.60, no -mod= line needed for A2: CO anymore)

Share this post


Link to post
Share on other sites

I don't get these RC candidates and betas being released at the same time. Do we need to upgrade to each RC and then upgrade to the newest beta? Do the RCs have the most recent beta changes in them? Do the RCs have stuff the betas don't? Vice versa?

I'm confused with them being released concurrently.

Share this post


Link to post
Share on other sites

The betas can be used without the RC's. The RC's have data fixes that the betas don't have.

Higher build number betas have newer engine version. If higher beta build is available and you use an RC, it's recommended to use the Beta on top of it.

Share this post


Link to post
Share on other sites

The EW Receivers in various aircraft still do not work...this was broken in 1.58 and still no fix. Affected are AH-1Z, MH60, Mi-24 and MH6 family.

Share this post


Link to post
Share on other sites
The EW Receivers in various aircraft still do not work...this was broken in 1.58 and still no fix. Affected are AH-1Z, MH60, Mi-24 and MH6 family.

is it in CIT? i'm sorry this 99% can't be fixed in 1.60 cause time runs out (today must be all closed)

lets say 1.61

Share this post


Link to post
Share on other sites
is it in CIT? i'm sorry this 99% can't be fixed in 1.60 cause time runs out (today must be all closed)

lets say 1.61

No, indeed I can not find a CIT for that. Looks like we have time to look deeper into that now. It was broken with the introduction or an upgrade of BAF, and all BAF choppers work flawless. Maybe even adding countermeasures for UH-1Y and MV22 while editing the units .cfg ;)

1.61 then.

I found an old post of mine that I posted in a beta thread...seems like I simply forgot to make a CIT ticket after.

http://forums.bistudio.com/showthread.php?p=1993341&highlight=Missile+warning#post1993341

Edited by Beagle

Share this post


Link to post
Share on other sites

problem solved, feel free to delete post.

Edited by Beagle

Share this post


Link to post
Share on other sites
The betas can be used without the RC's. The RC's have data fixes that the betas don't have.

Higher build number betas have newer engine version. If higher beta build is available and you use an RC, it's recommended to use the Beta on top of it.

Thanks SB. That's what I figured but wanted to make sure.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×