Desert

I fixed this with a reinstall, all is working finde now. :cool:

Someone know where to find the Apache or the Eagle Wing Campaign? I installed the 1.05 Patch (ingame the Version is 1.05.62017) and i cant find it? :eek:

There is an unneeded "f" ind your of. :)

Thank You, it works! :cool:

How can i use a Gasmask or Tactical Goggle?

@Sickboy a ok, i forgot, thank you to point me in the right Direction. ;) @jasonnoguchi Try this and start at Step 3: http://dev-heaven.net/wiki/six-arma-updater/Quickstart

YAY \o/ Thank You for the hard Work on this Mod. Updater is running! :D Edit: I dont have to do something with the key Files like copying in the ArmA2/key Folder or schould i let them where they are?

Thank You Pain. :)

Ok im getting it now with the Updater. But i have two Question left, can i use my lovely ArmA 2 Launcher to start the Game and select/deselect the Mods and where can i download those mysterious 7z Files for the Updater described in the Quickstart?

Yeah thats what im thinking about, dont like those Updater Tools, just release a simple Download with a .exe or a .rar/7z/whatsoever and we will be fine.

It seems that ArmA2 have the same/a similar Problem with 8GB RAM. I have some major Textureproblems with 8GB RAM (Gras is black, Trees are big Blocks and so on, Buildings are totally messed up), it looks normally only in a 640x480 Resolution. When i`m limit my System to 3328MB RAM ArmA2 works fine in 1680x1050. P.S.: Sorry for my bad english, i hope you understand what i mean. I`m trying to do some Screenshots later because the "print" key doesnt work.

CtGuy you have a PM. :)

I am playing on Win 7 Ultimate 64bit with latest Beta, no Problems here, ArmA2 is running fine.

Sir Polaris is closing his Dragon Rising Community Services too: http://community.codemasters.com/forum/showpost.php?p=5859044&postcount=1

It works!! Finally! \o/

With BetaPatch Build .59875 no Change here.

I cant tel you exactly why this works (i cant find the Link/the Post) but i remember it works because ArmA2 uses a different D3D Rendering Pipeline as without the -winxp Command.

In ArmA1 this is fixed already. Look closely, the VRAM Detection is the Problem. It happens when the VRAM goes over the 2GB Mark, like Suma said. ;)

Look at this M8:http://forums.bistudio.com/showpost.php?p=1325931&postcount=69 Im thinking that fixing this, isnt that easy as they expected. :cool:

Suggestion: Fix the 8GB RAM Problem.

No Change with Patch 1.04 here. Thats sad. :(

In .58932 they working correctly.

wheelcipher, if you like, you can put the other 4GB back in and try the -winxp Parameter in the Game Shortcut. That worked for me and i dont have to limit my 64bit System to 4GB.

DMR > M16A4 ACOG > G36 :p

With BetaPatch ARMA2_Build_58834 i see no Change here.