ARMA 2 Free

[PuFu]

- minus the campaign, HD graphics and support for user-made addons and mods.

Does this mean that the system requirements will drop?

My question is simple. Does this mean that system requirements will be lower? I don't ask what no hd graphics are. Clear enough for you?

my bad..
HD graphics = texture maps file size = smaller file to load from HDD = possible less stutter (doubtfully). Since everything else seems to be exactly the same, i see no reason to have small requirements. The only plus could be more stable FPS (GFX related anyways).

@PuFu

Do you have it already?

We will get to know once it is available.

how can i help you?

[.kju [PvPscene]]

No, you can't combine A2 free with OA in order to get CO

This may not be true. Or do you have A2F already?

[Hamm]

@PuFu

Do you have it already?

We will get to know once it is available.

PuFu is right, we actually already know...

http://community.bistudio.com/wiki/A...ageCombination

Read through this, A2F can't be used for any CO version.

[PuFu]

This may not be true. Or do you have A2F already?

here is one reason.

In terms of MP, read a few posts above yours, BOTA:16. It will not be able to play with OA, BAF or PMC content, however.

more info on biki
I see no reason why BI would give away a possible buy allowing OA users to combine with A2Free into CO...of course, i might be wrong

edit: ninja'd

[birtuma]

PuFu is right, we actually already know...

http://community.bistudio.com/wiki/A...ageCombination

Read through this, A2F can't be used for any CO version.

As we know BIS you can probably rename arma2free.exe to arma2.exe and voila, you can install OA over it to get CO...

[.kju [PvPscene]]

@ Hamm

The BIKI site does not say that.

It says it does not contain OA files, nor BAF or PMC
(nor is the A2 engine obviously able to run OA/BAF/PMC content).

The A2F exe seems to disable modfolder use,
yet how should BI stop you from loading the A2F pbos in OA?
It would require a new PBO format to stop this.

Even more a CO lite (OA + A2F) is a very sensible addition.
It will finally unify the OA MP community (everyone on CO lite or full) and
it would only continue the lite compatibility approach BI started with the DLC.

If people want to have CO full, they need A2 full of course.

[Hamm]

As we know BIS you can probably rename arma2free.exe to arma2.exe and voila, you can install OA over it to get CO...

Eh? It's not the .exe that matters, it's what .pbo(s) are loaded. It seems like BIS is gonna disallow mod-loading through something in the registry for ArmA 2 Free (they've implemented this via beta patch already). In fact all we might be waiting for is that patch, then again this is just speculation. In anycase, from the BIKI article, it seems A2 cant be substituted by A2Free for A2:CO.

[.kju [PvPscene]]

The registry additions are to automatically run A2+OA+DLCs from different install locations
(mainly to sort the steam issues). It has not relation whatsoever to pbos or to disallow anything.

And no, beta patches have no disallow mod-loading capability.

And no the BIKI article does not imply that.

[Hamm]

The A2F exe seems to disable modfolder use,
yet how should BI stop you from loading the A2F pbos in OA?
It would require a new PBO format to stop this.

Do you see CO:Lite in the list of possible combinations or title distributions? I'm sure a list as thorough as that won't miss something this significant.

And no, it wouldn't require a new PBO format, BIS could simply disallow loading A2Free .pbo(s) in OA via the same method they're using to diallow non-BIS .pbo(s) in ArmA 2 Free. This would come in the next patch.

Read up more here:

http://www.arma2.com/beta-patch.php

[79768] New: Mods can be configured using Windows Registry.

[.kju [PvPscene]]

Talk to Dwarden about the registry path referencing feature or just wait for future patches.
You don't get the idea of it sorry.