PDA

View Full Version : ArmA2 8GB RAM Problem

Pages : [1] 2

Desert
May 29 2009, 14:37
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 im 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. Im trying to do some Screenshots later because the "print" key doesnt work.

cropduster
May 29 2009, 14:40
I don't think so. I have Vista x64 and 9 GB RAM on a i7-920 overcloccked at 3.4 GHz and it is running perfectly fine with no such efefcts that you observe.

Michael

Desert
May 29 2009, 14:53
Here are some Screens:

with 8GB:
http://img35.imageshack.us/img35/4141/arma28gb.th.jpg (http://img35.imageshack.us/my.php?image=arma28gb.jpg)

with 4GB:
http://img35.imageshack.us/img35/7127/arma24gb.th.jpg (http://img35.imageshack.us/my.php?image=arma24gb.jpg)

We have here on the armed-assault.de Forums (http://hx3.de/technische-fragen-probleme-162/schwere-grafikfehler-16290/) a few People with the same Problem, different Systems (Vista/XP/32/64bit/SP1/SP2) and GFX Cards but all with 8GB RAM.

Edit:
These are my System Specs:
Asus P5Q Board
Intel Q9300 @<hidden>,5GHz
8GB RAM
HD 4870 1GB
Vista 64bit SP2

Edit2:
When I launch ArmA2 with the 640x480 Resolution, the Textures shows normal. If i switch now to the native Resolution of my TFT (1680x1050) the Textures are still normal an they stay normal till i stop playing.

slimSpencer
May 29 2009, 17:38
Hi Guys,

same problem here...

Intel Q9550
8 GB RAM
Vista 64

black boxes everywhere and even in lowest setting, no more than 20fps...

suggest they will fix it in a patch coming soon....

regards

kreischweide
May 29 2009, 18:35
Same problem. QA didnt have machines with 8GB this time?

schuubars
May 29 2009, 18:56
Yes, like in the old ArmA 1 days mostly with ATI cards, after cutting 4gb with msconfig, the problem was gone, and the perfomance was really nice, all settings cranked up to max with 10km viewdistance and runs now great.

vista x64
Q9300 2.5GHz
8gb ram
4870 1gb

sidhellfire
May 29 2009, 18:56
Do problem exist in -window mode?
Is it possible that it's problem of 1GB videocard memory not the 8GB of DDRAM?

slimSpencer
May 29 2009, 19:01
hey schuubars,

which catalyst version do you have and in which resolution do you play?

i have 9.3 and can only play in 1440x900 to get good performance. 1920x1200 is too sluggish...

br

schuubars
May 29 2009, 19:04
I think it's just a problem in conjunction with 8gb and ati card(driver), well either Bohemia has to fix it or ATi, but i remember that some NV users had the same problems just not as many as ATi users.

Edit: @<hidden> cata 9.5, and 1680x1050, but without AA, and cata A.I. deactivated.

Revelation78
May 29 2009, 19:33
Nvidia user with 8GB of ram and a GTX285, no such problems here. I'm also running Win7 RC 64bit

slimSpencer
May 29 2009, 19:55
also guess its ati related, as in Arma 1...

Desert
May 29 2009, 20:00
I know 2 Guys with Nvidia Cards with the same Problem (1x8800GT, 1x285GTX).

craig3000
May 29 2009, 20:08
There are problems with 8GB Vista 64bit and ATI drivers go over to the AMD game forums and check it out

But I am pretty sure they fixed this problem, it wasn't just limited to one game

Maybe they didn't test for 8GB ram, so limit the amount of RAM it can use like the other guy said 3GB should be plenty for the game alone lol, although it should get fixed if it is a problem, not nice to buy 8GB and not use it properly

Desert
May 29 2009, 23:41
no Change on this Problem so far.

7
May 29 2009, 23:49
Yes, like in the old ArmA 1 days mostly with ATI cards, after cutting 4gb with msconfig, the problem was gone, and the perfomance was really nice, all settings cranked up to max with 10km viewdistance and runs now great.

vista x64
Q9300 2.5GHz
8gb ram
4870 1gb

schuubars
May 30 2009, 10:38
Usually 100% but 150 worked too.

Raggz
May 30 2009, 13:50
This happens to me to. Vista X64, 4gb Ram and GTX 280 with latest 185.85 driver.
Looks like a memory leak to me as it crashes in the end with "not enough memory" error.

Desert
Jun 2 2009, 22:27
Anything new here?

Nemesis_wales
Jun 3 2009, 01:14
i had this issue on my rig for arma 1, the beta fixed it, but then i kept getting blue screens after ATI driver change (yes i removed old ones before installing new ones) and in end game was unplayable unless i done msconfig and used 3gb of RAM. any how after constant blue screens, i got in touch with the company that made my rig and they sent me another 3 different brand cards (4870X2). all failed. ATI's advice to them to pass on was fresh vista install, making sure ATI driver was 1st to be installed, no good. so to fix it, i got a 295 GTX and aint looked back. the main reason for this, althought happens to limited n vidia users is ATI drivers being poor. i went thru weeks and weeks of crap cos of it. im currently running the last but nvidia driver, 8.3 or wot ever, as the newest 1 screwed my comp up an i couldnt b arsed with wasting time, however i have removed arma from my system totally cos it went nuts when i tried installing invasion 44 mod, so time will tell if i get the same issue again with arma 2, but i had a friend in US with a brand new alien ware pc, I7, x58 board with 12GB of ram and he had no issues at all.

GhostX
Jun 3 2009, 07:57
I had the same problem. In my case I realized that Arma2 kept detecting 128MB of video ram(I also have 8GB of RAM). Check arma2.cfg - localVRAM=128974848;nonlocalVRAM=128974848;. Also in game I was unable to increase texture details from normal quality. Manual change of values didn't help.
solution - I removed nvidia 185.85 driver, rebooted a installed older beta driver, rewrited values to 780MB of localVRAM and 2GB of nonlocalVRAM. Everything fixed ;)
on Vista buss 64-bit

Sickboy
Jun 3 2009, 08:19
Nice finds GhostX.
All fine here on Win7 x64, i7 3.2, GTX 280, 6 GB ram, 2560x1600. Using latest drivers.

Desert
Jun 3 2009, 09:58
I had the same problem. In my case I realized that Arma2 kept detecting 128MB of video ram(I also have 8GB of RAM). Check arma2.cfg - localVRAM=128974848;nonlocalVRAM=128974848;. Also in game I was unable to increase texture details from normal quality. Manual change of values didn't help.
solution - I removed nvidia 185.85 driver, rebooted a installed older beta driver, rewrited values to 780MB of localVRAM and 2GB of nonlocalVRAM. Everything fixed ;)
on Vista buss 64-bitI tried this but the VRAM Values on my System seems ok so it did not help. :( I really think we have to wait for a Fix from BiS for this Issue.

mr.g-c
Jun 3 2009, 10:10
I ordered another 4GB Ram with a HD4890 exclusively for Arma2 and now i read within two days that both devices will cause very bad "bugs" like we had them in Arma1?!?! :rolleyes::(

Is there a ticket about it already? I think this is really important to fix with the next patch!

RKSL-Rock
Jun 3 2009, 10:18
I think it's just a problem in conjunction with 8gb and ati card(driver), well either Bohemia has to fix it or ATi, but i remember that some NV users had the same problems just not as many as ATi users.

Edit: @<hidden> cata 9.5, and 1680x1050, but without AA, and cata A.I. deactivated.

Actually i get the "black grass" bug when i update to the latest Nvidia drivers. Ive reverted to an earlier build and its all fine. IM getting 30-60fps most of the time.

C2D 8400 @<hidden>
8Gb PC6400
EVGA 8800GT KO 512mb on Forceware 178.24.

I upgrade to 185.85 and its black grass and no textures.

Suma
Jun 3 2009, 10:23
For your information: All my ArmA 2 development is done on Vista with 8 GB RAM and I periodically switch between nVidia and ATI cards to make sure there are no obvious compatibility issues this time, like they were in ArmA. I think I can therefore say at least the basic compatibility level should be there this time.

mr.g-c
Jun 3 2009, 10:28
For your information: All my ArmA 2 development is done on Vista with 8 GB RAM and I periodically switch between nVidia and ATI cards to make sure there are no obvious compatibility issues this time, like they were in ArmA. I think I can therefore say at least the basic compatibility level should be there this time.
I had this in mind as you were posting that earlier, hence thats why i am a bit shocked by these player reports...

But you confirm that this is a bug and the people reporting it, are not just "conceive" something? :p

Nemesis_wales
Jun 3 2009, 11:17
i honestly think its all down to Graphics drivers. as ppl have said, there system runs with 8, 12 gigs and no problem, nvidia seem to have the edge with the driver sover ati, but there not imune. if i get any bugs/glitches after i have already played it fine ill just b reverting back to older GPU drivers so at least th egame splayable, and wait the newer ones again

echo1
Jun 3 2009, 11:32
Was planning on upgrading my gaming PC from 4GB to 8GB, but after seeing this, I think I'll pass.

Nemesis_wales
Jun 3 2009, 11:45
if u want/need it go for, there always work arounds, i cure my issues simply by scrapping the 4870X2 and using 295gtx, that was it, game worked fine with max RAM on normal and beta with arma 1, im not expecting much different at all from 2, if anything screws me up its gonna b drivers

Desert
Jun 3 2009, 11:51
For your information: All my ArmA 2 development is done on Vista with 8 GB RAM and I periodically switch between nVidia and ATI cards to make sure there are no obvious compatibility issues this time, like they were in ArmA. I think I can therefore say at least the basic compatibility level should be there this time.Which Catalyst Version you have installed?

andawra
Jun 3 2009, 12:40

-winxp

to the arma2.exe command line parameter (shortcut)

example : "D:\ARMA II\arma2.exe" -winxp

and you wont have to care for any of these workarounds

Commando84
Jun 3 2009, 12:48
hmm is it only happening on windows 64 versions?

Desert
Jun 3 2009, 13:23
Yeah, because 8GB RAM on a 32bit Machine is useless ;) but on the armed-assault.de Forums is a Post from a User with 8GB RAM on Windows XP 32bit with the same Issue, i dont know why he has 8GB RAM on a 32bit Machine Oo. Im triying the -winxp thingy now. I have tried the Catalyst Versions from 8.12 to 9.5 today and the Problem ist still the same with every Version.

Suma
Jun 3 2009, 13:35
But you confirm that this is a bug and the people reporting it, are not just "conceive" something? :p

How can I know? All I know is that ArmA 2 runs fine on all 8 GB Vista systems I have tested so far. I cannot rule out a possibility that some combination of components we did not test is still handled bad on our side.

RKSL-Rock
Jun 3 2009, 13:35
For your information: All my ArmA 2 development is done on Vista with 8 GB RAM and I periodically switch between nVidia and ATI cards to make sure there are no obvious compatibility issues this time, like they were in ArmA. I think I can therefore say at least the basic compatibility level should be there this time.

Suma can i ask what Nvidia card and drivers you are using?

The reason i ask is that ive just tried ArmA2 on the same PC with two different cards.

My 8800GT KO runs well on 178.24 but goes black on 185.85
My friend's 8800GTX does the same.

So is it just a driver issue?

Leopardi
Jun 3 2009, 13:38
Suma can i ask what Nvidia card and drivers you are using?

The reason i ask is that ive just tried ArmA2 on the same PC with two different cards.

My 8800GT KO runs well on 178.24 but goes black on 185.85
My friend's 8800GTX does the same.

So is it just a driver issue?

Obviously it is? nvidia drivers can't be trusted especially when it comes to ArmA.

Desert
Jun 3 2009, 13:45
That -winxp Parameter solve the Problem here!! :yay: What exactly does that Parameter?

RKSL-Rock
Jun 3 2009, 14:05
Obviously it is? nvidia drivers can't be trusted especially when it comes to ArmA.

Ok let me be clearer. Obviously it is drivers. I was wondering how much has changed in those individual drivers that would have an affect on ArmA2. Is it down to the driver or the game?

echo1
Jun 3 2009, 14:43
Obviously it is? nvidia drivers can't be trusted especially when it comes to ArmA.

Well, they seem to be faring better than ATI ones if people's problems with ATI cards are anything to go by.

andawra
Jun 3 2009, 15:52
That -winxp Parameter solve the Problem here!! :yay: What exactly does that Parameter?

it solves problems.

Desert
Jun 3 2009, 16:05
That wasnt my Question.......

Sniperwolf572
Jun 3 2009, 16:14
That wasnt my Question.......

This (http://forums.bistudio.com/showpost.php?p=1291704&postcount=22) might be.

Desert
Jun 3 2009, 17:41
Thank You, thats what i wanted to know. :bounce3:
Now we have to wait for a Fix.

kuss
Jun 3 2009, 19:07
That -winxp Parameter solve the Problem here!! :yay: What exactly does that Parameter?

it makes the game think u only got 3-4gig of ram

Desert
Jun 5 2009, 11:22
No Change here, even with Final 1.01 Patch.

BangTail
Jun 5 2009, 22:39
No Change here, even with Final 1.01 Patch.

Same. The game is NOT detecting the available amount of VRAM properly.

My Videocard is detected as 256 MB when it is in fact 1 Gig.

There doesn't seem to be any way around this and using the -winxp switch ruins my sound, so it's not an option.

Eth

Desert
Jun 5 2009, 22:45
You can try to limit your System to ~4GB (3328MB) with msconfig, if you have 8GB of RAM.

Leopardi
Jun 7 2009, 15:26
Well, they seem to be faring better than ATI ones if people's problems with ATI cards are anything to go by.

I go by my own experiences, and with nvidia drivers ArmA was a nightmare, crashing, memory leaks, gfx bugs etc. then with AMD card ZERO PROBLEMS.

Supernova
Jun 13 2009, 18:57
Nice finds GhostX.
All fine here on Win7 x64, i7 3.2, GTX 280, 6 GB ram, 2560x1600. Using latest drivers.

Tested with 12GB G-Skill DDR3-1333 kit on my Core i7 system and all is fine as well.

Snake_61
Jun 13 2009, 22:45
Hi Guys,
texture problems...well I had this fight too!
Vista64 GTX285 and FORMERLY 185.85Drivers!!!
Even the new 186.08 didn't help!
Problem solved - switched back to 182.50 Drivers and no more Textureprobs...!

Desert
Jun 15 2009, 20:32
After downloading and (clean)installing the Catalyst 9.6, i have to inform you that the Problem is still there. Looking forward to Friday and Patch 1.02. Maybe it will be fixed then. :o

mr.g-c
Jun 16 2009, 09:08
Same Bug here.... tztztzt fresh ordered Stuff is making these errors with 8GB Ram:
bYmi0rwtlQM

Its a real shame because with this toxic radeon card and 4GB Ram i can set *nearly* everything to very high and it runs fluid and its sooo beautiful....
WinXP Parameter did solve the iussue but it seems to me that it runs a bit slower now and that is of course not a real solution....
I hope this will be fixe by a patch soon!

Sniperdoc
Jun 17 2009, 00:00
Nvidia user with 8GB of ram and a GTX285, no such problems here. I'm also running Win7 RC 64bit

Running 185.85 drivers on Windows 7 with two GTX280s (non-SLI)

Thrawn123
Jun 19 2009, 02:47
I am also having this issue. It looks like everything is missing textures. Grass shows up as black blocks for example.

Vista SP 2 Ultimate 64-bit
8 GB RAM
Nvidia 8800 GTS 512

the -winxp switch fixed the problem for now.

Richey79
Jun 19 2009, 09:50
Hi all.

I had this problem for a time. Seemed to be related to crossfire. When I had two cards in my mobo and selected crossfire off in Catalyst, the texture problem happened.

So, I come to upgrade my graphics card (all of these ATI), and for a time have only one card in (HD 4870). The texture problem came back, and I couldn't fix it without the -winxp fix. Now, with only a HD 4870 x2 in, Arma 2 works fine without the -winxp fix.

So, this probably doesn't suggest to anybody a fix; but somebody clever might be able to narrow down where the problem lies. I'm running Vista Ultimate x64 and have 8Gigs RAM, by the way.

Hope this helps someone.

Hazzamon
Jun 19 2009, 16:39
I am getting this exact issue also.

Intel Q9550 @<hidden> 2.83Ghz (Stock)
8GB DDR2-800 4-4-4-12
Asus P5Q-E
Asus Xonar D2X
Windows 7 RC1 64-bit

Setting VRAM to 'Very High' does not fix the issue. The -winxp switch works however.

mark
Jun 19 2009, 21:34
sorry i dont understand how to put in the winxp to the shortcut can someone tell me how please

echo1
Jun 19 2009, 21:41
Right click on the shortcut on your desktop, select properties. Go to the end of the "Target" field, and type "-winxp". Make sure there is a space between it and the location of the .exe file. So it should look like

C:\Program Files\...\ArmA2.exe -winxp

goldkid80
Jun 19 2009, 21:43
c:\progr...\bohemia interactive\arma2\arma2.exe" -winxp

Sam75
Jun 19 2009, 21:45
-maxmem=2047 not this one ?

echo1
Jun 19 2009, 22:24
I'm pretty sure there's a winxp flag that limits RAM to 3GB or something like that.

mark
Jun 20 2009, 00:38
cool thanks works now

Desert
Jun 20 2009, 01:26
No Change on this problem with the 1.02 Patch.

BrunoDerRabe
Jun 20 2009, 05:51
This 8GB issue anoying as hell, please get it fixed ....

older driver version works fine [ 182.5 for Vista 64 and 181,71 ( Prerelease - WDMM 1.1) for Windows7RC1]

After the nvidia GPU driver downgrade I always install the PhysX_9.09.0428_SystemSoftware from the driver package 186.18, no need to keep an older version.
You will find the PhysX_9.09.0428_SystemSoftware from the prior 186.18 installation in: C:\NVIDIA\DisplayDriver\186.18\International ( example from Windows 7 RC1 )
If you haven´t installed 186.16 on the PC before, you can start an installation of it , cancel it after the files were extracted on your harddrive.

Here a suggestion:

Is there no way for example to implement a checkbox in the grafic options, to force the game to drop or ignore the VRAM check/driver info dialog .... then it would be possible to set up the game properly with the amount of <=4GB RAM or an

older driver version wich works fine [ 182.5 for Vista 64 and 181,71 ( Prerelease - WDMM 1.1) for Windows7RC1], tick the box and add the rest of the RAM or update the driver?

Certainly a 64 bit arma2.exe would be great to run the game as a native 64bit application. I am aware about the needed efforts to get this job done.

If you want to compare your arma2.cfg with this example look for it in: C:\Users\*username*\Documents\ArmA 2

You need to open the file with an editor to see these values.
I have edited FSAA=0 to FSAA=4 to set the antialiasing value in the game to very high.

The Render_W=2400 and Render_H=1500 are a result of me using the 3D resolution ( fillrateoptimization) of 125% for 1920*1200 in the gamesettings.
The ingame postprocess setting of high is simular with postFX=2 .

language="German";
3D_Performance=100000;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=2400;
Render_H=1500;
FSAA=4;
postFX=2;
HDRPrecision=8;
lastDeviceId="";
localVRAM=924581888;
nonlocalVRAM=2143780864;

Everytime the game shuts down the two last lines will be updated and overwritten. With 8GB RAM and some driverversions the driver interfears with the game in a bad manner and as a result the VRAM will be detected wrong and the ingamegrafics srew up. If you count only 8 digits in the localVRAM and nonlocalVRAM values nevertheless you running uptodate hardware you know the bug strikes again.

Arma2 is played here with Track IR and the resolution set at 1920*1200 - memory and GPU´s are swapped as needed between the 2 PCs

Intel Q6600 @<hidden> 3.0Ghz OC**************AMD PhenomII 940BE @<hidden> 3.0Ghz
4GB DDR2-1066@<hidden>**************4GB DDR2-1066
1 260GTX **************************2 260GTX in SLI
X-Fi Xtreme Gamer*******************Onboard Sound Realtek High Definition Audio
PSU Xilence 750W Gamer Edition********PSU Xilence 750W Gamer Edition
Windows Vista 64 Ultimate*************Windows 7 RC1 64-bit

ArmA2 (1.02), BIOS, drivers and OS are up to date

Thrawn123
Jun 20 2009, 19:53
Confirmed issue is still happening in 1.02. :mad:

technologickill
Jun 21 2009, 09:25
same here with all driver versions newer than 182.x :(

BrunoDerRabe
Jun 23 2009, 03:01
THE SOLUTION

8GB on Windows7 RC1 NVIDEA 186.18 2 260GTX in SLI AMD PhenomII 940BE @<hidden> 3.0Ghz were used for the test

The reward of using the up to date NVIDEA 186.18 version with an higher amount of RAM is a performance increase and a better imagequality COMPARED to the driverversion NVIDEA 182.50 .

msconfig 4096MB = shows after reboot 3071MB in the taskmanager detected localVRAM=924581888
msconfig 6144MB = shows after reboot 5119MB in the taskmanager detected localVRAM=1217781761
msconfig 7168MB = shows after reboot 6143MB in the taskmanager detected localVRAM=1754652673
msconfig 7424MB = shows after reboot 6399MB in the taskmanager detected localVRAM=1888870401
msconfig 7680MB = shows after reboot 6835MB in the taskmanager detected localVRAM=2117459969
msconfig 7804MB = shows after reboot 6779MB in the taskmanager detected localVRAM=2088099841
msconfig 7936MB = shows after reboot 6911MB in the taskmanager detected localVRAM=4911104= NOT GOOD

With the value of 4069MB for systemstart via msconfig an amont of total 3GB physical memory only are shown in the performance tab of the taskmanager.

With the value of 6144MB for systemstart via msconfig an amont of total 5GB physical memory only are shown in the performance tab of the taskmanager.

With the value of 7168MB for systemstart via msconfig an amont of total 6GB physical memory only are shown in the performance tab of the taskmanager.

With the value of max. memory for systemstart via msconfig an amont of total 8GB physical memory are shown in the performance tab of the taskmanager.

It looks like that decreasing the amount of RAM via msconfig to a lower value than the installed 8GB makes sure that 1GB is hidden somewhere, and ArmA2 and the new driverversions team up correctly.
With other games the 8GB is no issue, so I think the new drivers have seen a change somehow to handle the growing amount of Memory, but it and/or the OS change the handling of it with 8GB detected and on top of that ArMA2 delivers not the nessecery ignition to OS/ drivers as they desire like other games do.
Time to see the mechanic ;-) .....

language="German";
3D_Performance=100000;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=2400;
Render_H=1500;
FSAA=4; [manualy edited by me - with patchlevel 1.02 the standard value is 0 ( disabled )]
postFX=2;
HDRPrecision=8;
lastDeviceId="";
localVRAM=1754652673;
nonlocalVRAM=2147483647;

detected VRAM with Nvidia 182.50 (8GB RAM; *msconfig value default*) = 924581888
detected VRAM with Nvidia 186.16 (8GB RAM; msconfig value 7168MB ) =1754652673
detected VRAM with Nvidia 186.16 (8GB RAM; msconfig value 7680MB ) =2117459969
Arma2 is played here with Track IR and the resolution set at 1920*1200 - memory and GPU´s are swapped as needed between the 2 PCs

Intel Q6600 @<hidden> 3.0Ghz OC**************AMD PhenomII 940BE @<hidden> 3.0Ghz
4GB DDR2-1066@<hidden>**************4GB DDR2-1066
1 260GTX **************************2 260GTX in SLI
X-Fi Xtreme Gamer*******************Onboard Sound Realtek High Definition Audio
PSU Xilence 750W Gamer Edition********PSU Xilence 750W Gamer Edition
Windows Vista 64 Ultimate*************Windows 7 RC1 64-bit

ArmA2 (1.02), BIOS, drivers and OS are up to date

Phr34k
Jun 24 2009, 09:17
Bruno, ive read your post 3 times now, but im still not sure what you mean.

I have now forced my Vista64bit 8gb ram down to 5gb and it work fine.
Is your post saying that if i put it back on 8gb and change he localVRAM it should work?

How do i get the correct VRAM with Ati?

Suma
Jun 24 2009, 15:41
8GB on Windows7 RC1 NVIDEA 186.18 2 260GTX in SLI AMD PhenomII 940BE @<hidden> 3.0Ghz were used for the test

msconfig 4096MB = shows after reboot 3071MB in the taskmanager detected localVRAM=924581888
msconfig 6144MB = shows after reboot 5119MB in the taskmanager detected localVRAM=1217781761
msconfig 7168MB = shows after reboot 6143MB in the taskmanager detected localVRAM=1754652673
msconfig 7424MB = shows after reboot 6399MB in the taskmanager detected localVRAM=1888870401
msconfig 7680MB = shows after reboot 6835MB in the taskmanager detected localVRAM=2117459969
msconfig 7804MB = shows after reboot 6779MB in the taskmanager detected localVRAM=2088099841
msconfig 7936MB = shows after reboot 6911MB in the taskmanager detected localVRAM=4911104= NOT GOOD

Great observation, you did really good debugging job. It seems there must be some more 32b overflow, as what you observe is exactly when detected localVRAM goes over 2 GB. I think finding and fixing this should be easy now.

Jun 24 2009, 15:58
I have no problem like this
Phenom II 3GHZ
8 GB DDR2 A-DATA
ATI HD 4850
WINDOWS 7 RC1 7229

Desert
Jun 24 2009, 16:41
@<hidden>
Yeah you can limit your System to ~4GB to get ArmA2 working correctly or you can use the -winxp Parameter in the ArmA2 Shortcut to play without limiting your System to 4GB completely.

@<hidden>
I have a 4870 with 1GB RAM, whem i´m backup my .cfg and start ArmA2 without the -winxp Parameter and with 8GB RAM the Autodetect shows this:
localVRAM=3768256;
nonlocalVRAM=3768256;

With the -winxp Parameter and 8GB RAM it shows:
localVRAM=2134048641;
nonlocalVRAM=2147483647;

Is the non functioning Autodetect the Cause for this Problem, like Bruno describes?

Survey78
Jun 24 2009, 18:21
Doing as bruno suggested and limiting ram "msconfig 7804MB" fixed the problem in win 7 rc x64 with the 186.18_desktop_win7_winvista_64bit_english_whql driver.

Just wanted to confirm it since it's such a simple fix, thanks.

BrunoDerRabe
Jun 24 2009, 23:40
Bruno, ive read your post 3 times now, but im still not sure what you mean.

I have now forced my Vista64bit 8gb ram down to 5gb and it work fine.
Is your post saying that if i put it back on 8gb and change he localVRAM it should work?

How do i get the correct VRAM with Ati?

The idea is to avoid the bug , but to use more than just 4GB of the total installed 8GB RAM while playing ArmA2 1.02 with the NVIDEA 186.18 driver as you might have to cope with while using other workarounds, if they work at all.
On my Windows 7RC1 the peak of RAM for a good result to set in the advanced startoptions is 7680 MB.
If you add more, the direction changes very soon and it will turn around into a disadvantage.
As a result VRAM detection screws up.
You DONT have to change the value of VRAM in the ArmA2s config. This is done by the game, depending on the amount of reported RAM.
THe VRAM value in the test #detected localVRAM=2117459969# is the result of choosing the amount of 7680 MB in the advanced startoptions in the msconfig .
With this setting the taskmanager reports after a reboot 6835MB total physical memory ( in the testresults above ).

Because the detected localVRAM=2023088129 and nonlocalVRAM is 2147483647 in my config with above settings (7680 MB , taskmanager now shows 6655MB of total physical memory ) I am not going to change it soon.

Depending on the choosen amount of RAM in MB in the advanced startoptions of the msconfig,
the reported MB of total physical memory shown in the taskmanager will be different, this all is managed by the OS.
The VRAM detection of the application ArmA2 1.02 depends on the above settings.
According to them the amount of detected VRAM is reported to the config of ArmA2.
That means you can check via the config (detected localVRAM=? after ending the game) if you have set an amount of RAM to start Windows Vista/7RC1 with, without spoiling the VRAM detection of your so loved game.

Does the bug strike you at all? Did you check the VRAM in the config? For Nvidia users it depends on the driverversion. Please read last posts. Best you try it youself and please tell us the results.
Detailed info about the used PC and ATI driverversion is always helpfull.

@<hidden>

Thanks mate, I have tried that all and more ;-) ...
The -winxp parameter in the ArmA2 shortcut doesn´t work on this rig.
I also wanted to narrow down the source of it.

---------- Post added at 11:40 PM ---------- Previous post was at 11:07 PM ----------

Great observation, you did really good debugging job. It seems there must be some more 32b overflow, as what you observe is exactly when detected localVRAM goes over 2 GB. I think finding and fixing this should be easy now.

@<hidden> Suma

Thank you for the recognition. :bounce3:
My pleasure.

Desert
Jun 26 2009, 14:47
Installed the 1.02.58134 patch, deleted my old ArmA2.cfg, removed the -winxp Parameter from my Shortcut aaand the Problem is still the same.

The VRAM parts from the 1.02.58134 generated ArmA2.cfg and 8GB RAM:
localVRAM=3768256;
nonlocalVRAM=3768256;

The VRAM Parts with the -winxp Parameter and 8GB RAM (no Problem):
localVRAM=2140766144;
nonlocalVRAM=2140766144;

The VRAM Parts with 4GB RAM (msconfig, no Problem):
localVRAM=1068449792;
nonlocalVRAM=1475870720;

technologickill
Jun 26 2009, 15:25
Confirm that the prob still exists while testing with the latest nvidia driver 186.x and the new updated patch ... so we should go back to 182.50 ?

overkill1
Jun 26 2009, 15:36
Same Bug here.... tztztzt fresh ordered Stuff is making these errors with 8GB Ram:

Its a real shame because with this toxic radeon card and 4GB Ram i can set *nearly* everything to very high and it runs fluid and its sooo beautiful....
WinXP Parameter did solve the iussue but it seems to me that it runs a bit slower now and that is of course not a real solution....
I hope this will be fixe by a patch soon!

Thats something Ive had before in other games, have you tried disabling Catalyst AI?
It has to be something to do with your graphics settings as I have 8GB DDR2, and an HD3870 and its fine

Jun 26 2009, 15:38
Installed the 1.02.58134 patch, deleted my old ArmA2.cfg, removed the -winxp Parameter from my Shortcut aaand the Problem is still the same.

The VRAM parts from the 1.02.58134 generated ArmA2.cfg and 8GB RAM:
localVRAM=3768256;
nonlocalVRAM=3768256;

The VRAM Parts with the -winxp Parameter and 8GB RAM (no Problem):
localVRAM=2140766144;
nonlocalVRAM=2140766144;

The VRAM Parts with 4GB RAM (msconfig, no Problem):
localVRAM=1068449792;
nonlocalVRAM=1475870720;

Same here mate :(

Gino
Jun 26 2009, 15:53
I have exactly the same issue: the first screen of Desert in first page is what I see in game...

Vista x64
Intel Core 2 Duo E8400 @<hidden>
8 Go RAM
Nvidia 8800GT /512mb

The workaround -winxp fixed it.

Phr34k
Jun 26 2009, 17:27
Problem remained for me aswell :<

Thrawn123
Jun 26 2009, 23:32
Hey man,

I had the same issue and the recent 2nd 1.02 patch still didn't fix it even though there was some blurb in there about it. However, I found two ways of fixing it from browsing the forums here!

#1 - Add -winxp to the end of the Arma 2 shortcut (that will limit the game only only seeing 4 GB of memory I think).
or
#2 - go back to older Nvidia drivers. I just uninstalled the 186.16 Nvidia drivers and installed an older version 178.24. That 100% fixed my issue and Arma is working with all my memory now with NO -winxp switch.

***EDIT 182.50 Nvidia drivers are also working correctly***

(So this really seems like an issue between this games and recent drivers? Wierd... at least it's working with no missing texture crap)

Intel q9450
8 GB RAM
Vista Ultimate 64
Geforce 8800 GTS 512 OC

themaster303
Jun 26 2009, 23:50
i also have still less vram with the new version. bug is still there. was so happy when i read the 8gb fix.

anyway they will fix ;)

survey
Jun 26 2009, 23:55
Just to be clear, -winxp didnt fix anything for me, forward on i will presume you all have 8gigs of ram.
I have the latest nvidia drivers running but i limited my amount of ram through msconfig just like bruno said, i tried a few diffrent settings of the amount of ram and well they all helped from the main problem wich was getting huge amounts of non textured objects in the game, for example grass that was huge black blocks.

Choose "run", type in msconfig, click boot and choose advanced options, once there, you should have maximum memory, click the checkbox and type in 7680, reboot and start arma2, if it works fine, run it like this until we get a fix.
If it doesent work, just redo the same procedure but click the checkbox to uncheck it, you will again use the full amount of ram, restart and well wait for next patch.

hannibal636
Jun 27 2009, 00:36
i have 8gigis of ram.
Vista x64
i also patched up to the newest 2nd edition of 1.02_58134
i get the block like graphics with the new Nvidia driver v186.18
i rolled back to version 7.15.11.8250 (3/27/2009)

and the graphics look great again...

WTF!!!!
the game looks awesome, but I CAN NOT run this in triplehead 4320x900 !!!!!!!!!!!!!!!!!!
i want my extreme setup to workkkkk

Desert
Jun 27 2009, 09:25
Just to be clear, -winxp didnt fix anything , i will presume you all have 8gigs of ram.It is a temporary Solution for this Bug. In some Cases, like mine, it works and i dont have to limit my System through msconfig. I think you can try -winxp, before you limiting your complete System. :cool:

survey
Jun 27 2009, 18:20
Yeah should have typed "didn't fix anything for me", thanks for correcting.

Clydesdale
Jun 27 2009, 19:42
Using MSconfig fixed it for me it seems, but it will not let me limit the memory to 7680, it seems changing it to 3072 for some reason.

BrunoDerRabe
Jun 27 2009, 21:50
Using MSconfig fixed it for me it seems, but it will not let me limit the memory to 7680, it seems changing it to 3072 for some reason.

After changing the limit of the memory to 7680 MB via msconfig, reboot, and DON´T check the amount you have choosen in the msconfig itself, you will always find some number there as you mentioned 3000 something, that´s just an suggestion by windows for a reboot with limited RAM( would fit 32Bit applications ) - better have a look into your taskmanager, the total amount of physical RAM is your point of interest. For me it counts 6655 MB. Wich is good.
:bounce3:

Clydesdale
Jun 28 2009, 20:27
After changing the limit of the memory to 7680 MB via msconfig, reboot, and DON´T check the amount you have choosen in the msconfig itself, you will always find some number there as you mentioned 3000 something, that´s just an suggestion by windows for a reboot with limited RAM( would fit 32Bit applications ) - better have a look into your taskmanager, the total amount of physical RAM is your point of interest. For me it counts 6655 MB. Wich is good.
:bounce3:

That did it! Odd behavior..it would not change to anything else until I unchecked it, rebooted, then checked it again. Didn't even think to use taskman, duh...

Thanks!

mr.g-c
Jun 30 2009, 01:22
Like confirmed before, the bug is still there in the lastest 1.02.
I can only play the game with "-winxp" switch on my 1GB HD4890 Toxic and 8GB Ram on Vista X64, but with this flag/switch the performance goes down like 10FPS compared to without flag and 4GB Ram pulled out of my system.

AstrO_Beta
Jun 30 2009, 02:01
I'm also experiencing this 8GB of RAM problem, although the "-winxp" is working as a fix for now. I also have problems with ArmA, unless I limit my ram (using MSConfig).

System...

Windows Vista Ultimate x64 + SP2
Intel Q9300
8GB DDR II (G.Skill)
ATI 1GB HD4890 (HIS), CCC v9.6, 1920x1200

Playing with the ArmA Demo version 1.02.

jeffqwer
Jun 30 2009, 14:36
at least, BI didn't fixed 8G RAM VRAM detection at all!

Ver. 1.02.58134

182.50 without RAM Limited(SLI doesn't work)=fixed

186.18 without RAM Limited=Still Have Issues

186.18 with RAM Limited=fixed

hope BI fix this problem ASAP...

RooK80
Jun 30 2009, 16:13
Same problem here, my gear is:
Q9300 / MSI P7N SLI Platinum / 8GB A-Data DDR2 800Mhz / 2*9800GTX (SLI)/ Windows Vista 64 home premium

HHawk
Jun 30 2009, 19:36
Same here. See specs below.

qwertz
Jun 30 2009, 21:57
Same here. VRAM is detected at 494MB in DXDIAG, and 250-something MB in ARMA. Limiting RAM in MSCONFIG fixed this.

This seems to be a general NVIDIA Driver problem as memory detection is borked in DXDIAG already.

i920@<hidden>
EVGA Classified x58
12GB PC3-1600
EVGA GTX280 HydroCopper, driver 186.18

Bullseye112
Jul 2 2009, 18:48
I'm running Vista Ultimate x64 and have 8Gigs RAM, by the way.

Hope this helps someone.

I'm running vista 64bit also and 8gb Ram and getting the same problem. if you take 4gb of ram off your board it works fine, put 4gb back to make it up to 8gb then it has a dicky fit again. must be related to the amount of memory on your system.

This is my shortcut path for the game and i not sure how to insert the winxp switch as mine is through steam???

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 33920

Any ideas

Private Plowjoy
Jul 2 2009, 19:04
I'm running vista 64bit also and 8gb Ram and getting the same problem. if you take 4gb of ram off your board it works fine, put 4gb back to make it up to 8gb then it has a dicky fit again. must be related to the amount of memory on your system.

This is my shortcut path for the game and i not sure how to insert the winxp switch as mine is through steam???

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 33920

Any ideas

AFAIK just add an extra switch, so it looks like..

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 33920 -winxp

Yoma
Jul 2 2009, 19:07
I can also confirm that on this driver 186.18 the video memory detection works good with 4 GB physically installed and does not work good (detects double the amount that's on the card) with 6 GB installed.
Windows Vista x64 GTX285.
Is this an explanation for tons of CTD's some users are experiencing? e.g the game tries to access memory that's not available after a while?

Bullseye112
Jul 2 2009, 19:18
I can also confirm that on this driver 186.18 the video memory detection works good with 4 GB physically installed and does not work good (detects double the amount that's on the card) with 6 GB installed.
Windows Vista x64 GTX285.
Is this an explanation for tons of CTD's some users are experiencing? e.g the game tries to access memory that's not available after a while?

Thanks To All I Added The -winxp switch and it works fine full specs finally i can play the game without having to take memory out of my pc

Cheers

BangTail
Jul 2 2009, 20:16
Same here. VRAM is detected at 494MB in DXDIAG, and 250-something MB in ARMA. Limiting RAM in MSCONFIG fixed this.

This seems to be a general NVIDIA Driver problem as memory detection is borked in DXDIAG already.

i920@<hidden>
EVGA Classified x58
12GB PC3-1600
EVGA GTX280 HydroCopper, driver 186.18

QFT.

This is NOT a BIS problem. It's a known problem with the newer Nvidia drivers and the way they communicate with DX.

Simple solution - Don't use beta/rc operating systems as your main OS.

• NVIDIA TurboCache
Windows 7 now controls the allocation of system memory to the GPU for TurboCache functions. The Windows 7 Display Properties pages show the shared system memory (SSM), or how much memory is allocated for NVIDIA GPUs to use for TurboCache. For more information on graphics memory reporting under Windows 7, visit http://www.microsoft.com/whdc/device...icsmemory.mspx.

Eth

survey
Jul 2 2009, 23:32
ethne, perhaps i'm missing somekind of logic here but win7 latest nvidia drivers works fine with other games right? If so there is a problem with nvidia and bis and not win7 and nvidia. (btw haven't i seen the same reports regarding 64 vista/xp in this thread? regarding the "don't use beta/rc os")

Is arma2 using some aspect of the dx that the rest don't , or perhaps the first ones that takes advantage of the higher amount of ram available, since most games is still coded in a "everybody uses a 32bit os" perspective i presume that could pose somekind of problem.

I'm having a hard problem seeing it's a win7 problem though , since most people are running earlier versions of their drivers with 8gig ram with sucess.

Just don't like the claim "this is NOT a bis problem" since i want them to look into it.

BangTail
Jul 2 2009, 23:40
ethne, perhaps i'm missing somekind of logic here but win7 latest nvidia drivers works fine with other games right? If so there is a problem with nvidia and bis and not win7 and nvidia. (btw haven't i seen the same reports regarding 64 vista/xp in this thread? regarding the "don't use beta/rc os")

Is arma2 using some aspect of the dx that the rest don't , or perhaps the first ones that takes advantage of the higher amount of ram available, since most games is still coded in a "everybody uses a 32bit os" perspective i presume that could pose somekind of problem.

I'm having a hard problem seeing it's a win7 problem though , since most people are running earlier versions of their drivers with 8gig ram with sucess.

Just don't like the claim "this is NOT a bis problem" since i want them to look into it.

It isn't BIS, look at what I pasted directly from Nvidia. It causes problems in GTA IV as well (and I am sure others that I am not aware of). Sorry you "don't like it" but facts are facts.

Secondly, Win 7 is not released so there is no expectation of support. Don't run beta/RC operating systems and then start whinging.

Thirdly, I run A2 under XP64 with absolutely no performance problems to speak of, so it is not a 64 bit problem.

Cheers,

Eth

survey
Jul 3 2009, 00:07
Ok, then it's an nvidia problem and hopefully it will get fixed.
I'm not whining since the game runs fine after limiting ram under win7.

Just have to ask, do you have 8 gigs of ram? since no one claimed it was a 64bit problem but they claimed it was a 8 gig ram problem.

edit:
Oh yeah if you commented on the 32bit os perspective i just meant that if you presume that most people are using an os that only uses around 3,2gigs ram max that could create some problems.

BangTail
Jul 3 2009, 00:18
Ok, then it's an nvidia problem and hopefully it will get fixed.
I'm not whining since the game runs fine after limiting ram under win7.

Just have to ask, do you have 8 gigs of ram? since no one claimed it was a 64bit problem but they claimed it was a 8 gig ram problem.

edit:
Oh yeah if you commented on the 32bit os perspective i just meant that if you presume that most people are using an os that only uses around 3,2gigs ram max that could create some problems.

Hey mate,

I have 12 gigs of RAM. It doesn't cause any problems for me in XP64 and it isn't a problem in Win 7 either but XP64 provides MUCH better performance in my experience.

Cheers,

Eth

survey
Jul 3 2009, 01:39
No black block textures whatsoever in arma2 you say with 12gigs of ram and latest nvidia drivers? Then, is it specific 8gigs of ram that creates this and above 8 goes beyond a certain threshold. Since i havent heard of any reports from people that i can remember using more than 8gigs of ram. (if i scroll back in thread perhaps?).

BangTail
Jul 3 2009, 02:05
No black block textures whatsoever in arma2 you say with 12gigs of ram and latest nvidia drivers? Then, is it specific 8gigs of ram that creates this and above 8 goes beyond a certain threshold. Since i havent heard of any reports from people that i can remember using more than 8gigs of ram. (if i scroll back in thread perhaps?).

No black textures or any other performance related problems. I use 182.50 and not 186.18.

Dungeoncrawler
Jul 3 2009, 03:51
Running Vista 64, couple gtx 280's (186.18), and 8gb of ram with no graphic anomolies.

claus.valca
Jul 3 2009, 05:04
There is no evidence that it is not a BIS problem. When ArmA had problems with 8GB of RAM the symptoms were similar, updating to more recent NVIDIA drivers caused an issue in ArmA, mainly textures not loading in the game with messed up verts and such. People swore up and down that it had to be NVIDIA's fault because previous drivers worked fine, then Suma (I believe) posted that they had found a bug in their code that caused systems with 8GB of RAM to detect no video memory. It was fixed in the next patch (1.14.or 1.15).

So, Bohemia may have a bug in their code that is causing this problem. I'm sure it will be resolved though.

Desert
Jul 3 2009, 05:24
The Problem affects ATI Users too. Take a look at this Post (http://forums.bistudio.com/showpost.php?p=1323164&postcount=67) and this one (http://forums.bistudio.com/showpost.php?p=1325931&postcount=69), it seems that the Autodetect for the NVRAM Values dont work properly atm. You will see the same Behaviour on a affected ATI System, no matter wich Catalyst is installed (i tried 8.12 to 9.6).

BangTail
Jul 3 2009, 05:27
There is no evidence that it is not a BIS problem. When ArmA had problems with 8GB of RAM the symptoms were similar, updating to more recent NVIDIA drivers caused an issue in ArmA, mainly textures not loading in the game with messed up verts and such. People swore up and down that it had to be NVIDIA's fault because previous drivers worked fine, then Suma (I believe) posted that they had found a bug in their code that caused systems with 8GB of RAM to detect no video memory. It was fixed in the next patch (1.14.or 1.15).

So, Bohemia may have a bug in their code that is causing this problem. I'm sure it will be resolved though.

Actually, there is. Nvidia posted it in the driver's readme and I pasted it a few posts back. It affects GTA IV as well and is rumoured to be fixed in the next driver release.

I'm talking about the game detecting the available memory erroneously and disallowing you from selecting certain menu options. This is a direct result of the new way Win 7 communicates memory size through DX.

Cheers,

Eth

Yoma
Jul 3 2009, 05:50
I have 6 GB of memory on Vistax64.
My "localmemory" gets detected wrong when on nvidia driver 186.12 (the game works fine though,except crashes a lot more then usual)
If i remove 2GB of memory the localmemory gets detected correctly and the game crashes a lot less...

With driver 182.5 my vga memory get's detected correctly by Arma2 on both 6GB or 4GB.

I'm starting to think that this is in fact a fuckup by Nvidia and not by BIS.
Could others test this too?

Desert
Jul 3 2009, 06:39
This Problem affected different Systems with different Hard- and Software, like i said in my second Post on the first Page of this Thread, so i really think this is a "BiS Problem" and we have to wait for a Fix.

StormbringerGT
Jul 3 2009, 18:32
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 im 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. Im trying to do some Screenshots later because the "print" key doesnt work.

I have 8gbs RAM in my system, how do I limit my system RAM to 4gb to fix the problem?

Unless you are talking physically taking the RAM out.

BangTail
Jul 3 2009, 18:42
I have 8gbs RAM in my system, how do I limit my system RAM to 4gb to fix the problem?

Unless you are talking physically taking the RAM out.

Run ---->
type : msconfig (You can also type this in the search box if you don't have "run" enabled in the start menu)

Go to the "Boot" tab, then select "Advanced options".

Check the maximum memory box.

Type in 7804.

Click on "OK"

Reboot.

NB : Do not return to the advanced options page after you have set the amount of memory as it will change the memory size to ~3GB

Eth

StormbringerGT
Jul 3 2009, 18:59
Run ---->
type : msconfig (You can also type this in the search box if you don't have "run" enabled in the start menu)

Go to the "Boot" tab, then select "Advanced options".

Check the maximum memory box.

Type in 7804.

Click on "OK"

Reboot.

NB : Do not return to the advanced options page after you have set the amount of memory as it will change the memory size to 3xxx GB.

Eth

Thanks I will let you know of my findings!

Also I dunno if this helps anyone, but I am having a very similar issue in Empire Total War. I am using the newest NVidia Drivers.

Alright! I did two things, I went back to 182.50 drivers. I also limited my memory as per your guys suggestions.

The game runs great! I got everything cranked on Very High and I get a very playable 30 FPS (my game was saved in the middle of a large firefight and it runs great) I'd make a video and show it, but FRAPs ruins framerate and ruins the point of my video.

Its also worth noting that after doing both of those my Empire total War problem went away as well!

BangTail
Jul 3 2009, 19:50
Thanks I will let you know of my findings!

Also I dunno if this helps anyone, but I am having a very similar issue in Empire Total War. I am using the newest NVidia Drivers.

Alright! I did two things, I went back to 182.50 drivers. I also limited my memory as per your guys suggestions.

The game runs great! I got everything cranked on Very High and I get a very playable 30 FPS (my game was saved in the middle of a large firefight and it runs great) I'd make a video and show it, but FRAPs ruins framerate and ruins the point of my video.

Its also worth noting that after doing both of those my Empire total War problem went away as well!

Great news :)

ste4lth004
Jul 3 2009, 20:24
Im using 6gig, but its only showing 2.99 gig ram, but i have no graphic probs, so must be the 8gig only bug, by the way im using 185.85 driver, and havent installed the latest version of 1.02 patch, im only using the first 1.02 not worried about added aa.

BangTail
Jul 3 2009, 20:49
Im using 6gig, but its only showing 2.99 gig ram, but i have no graphic probs, so must be the 8gig only bug, by the way im using 185.85 driver, and havent installed the latest version of 1.02 patch, im only using the first 1.02 not worried about added aa.

XP32 will only address up to 4 Gigs, usually allocating ~1.0 - 1.5 for the system and leaving you with about ~2.5 - 3 gigs

StormbringerGT
Jul 4 2009, 03:04
It appears I can get way better framrates, if I set my textures to normal. They still look good and in a firefight you don't notice a difference. Some people may want to try lower the textures, that helped with stuttering and "texture pop inlag" not sure if I described that right. Think Unreal engine texture problems. :D

btbalance
Jul 4 2009, 20:34
I had a similar problem when I went from 3gb to 8gb yesterday. I didn't see the dark textures but every time I would look at a tree, for example, I would see a very low rez version of the tree which would then shift to mid-rez and then high-rez. Nearly everything was doing this and would continue to do so when I turned around.

Reverting my GTX275 to the 182.x drivers fixed it.

Rhodite
Jul 5 2009, 22:57

My System - 8GB on Windows7 RC1 Build 7100, NVIDEA 186.18 2 8800GT (512mb) E6600 CPU were used for the test.

I used the msconfig 7804 "fix" suggested and it worked.

Still only get 20fps from the ingame test but I have set all settings to high, so I am quite happy.

Dungeoncrawler
Jul 5 2009, 23:59
I'm talking about the game detecting the available memory erroneously and disallowing you from selecting certain menu options.

I stand corrected. I just noticed that I'm restricted on a couple of my graphic options with 8gb of ram.

Update: Setting my ram to 4gb has enabled the texture detail and Video memory to be set to higher values than normal. Definately something
up regardless of which type of gpu you are using. Thanks for the tip!

Update2: Unfortunately I seem to get worst performance with this workaround :(

-s!Gm4-
Jul 6 2009, 10:15
I stand corrected. I just noticed that I'm restricted on a couple of my graphic options with 8gb of ram.

Update: Setting my ram to 4gb has enabled the texture detail and Video memory to be set to higher values than normal. Definately something
up regardless of which type of gpu you are using. Thanks for the tip!

Update2: Unfortunately I seem to get worst performance with this workaround :(

Sorry to use your post for a quote lad, but I thought your words brought it out most clear:

So, the disability to set Videocard-Memory and Texture-Detail to higher levels _in the game_ are prevented by having 8 GB of RAM - do I get this right?
And this can be fixed by either that workaround (limit the amount of RAM allocated to 4 GB / whatever) or sitting it out and waiting for the next patch from nvidia as well as the BIS devs?

Now, that are quite good news, I think. At least there is a silver streak on the horizon.

Now, nevertheless I got another question.
Is the fact thtat my gfx-card (along with its VRAM) get detected incorrectly also related to this 8GB RAM thingy?
As you can see in my sig I use a gtx285 with 1 GB VRAM - but initially the arma.cfg only detects 256 MB.
I circumvent that with manually configuring the .cfg but was not getting any obvios results...

BrunoDerRabe
Jul 6 2009, 13:39
Hi all, I understand that it takes some time to read all the posts here in this threat.
I do see people still looking for help.
Yes, the 8GB problem with the newer driverversions ( NVIDIA 186.18 ) still exists, just want to confirm that.
Folks, I did spend lots of time with debuging this issue - and weeks ago I found invent the workaround setting the RAM in the advanced startup settings of the msconfig to the value of 7680MB - bringing the best results, as it is confirmed by other forumusers.
Why not using this workaround for now?
As a reminder, if you change the value of the RAM in your msconfig to 7680MB,
don´t have a look in the msconfig after the restart, use the taskmanager instead. Check the total amount of total physical memory there.
It might be around 6655MB, wich is O.K. .
Using the NVIDIA 186.18 driver with altering the amount of RAM to 7680MB in the msconfig solves the problem and will give you best results in level of details and performance using 8GB RAM.

Dwarden
Jul 6 2009, 14:09
i get multiple reports that users on Windows 7 fixed these issues by falling back to v181 drivers ...

on other OSes and some certain configs stable driver builds vary ...

so if someone want to try it ... feel free

Desert
Jul 6 2009, 15:15
Yeah thats a good Idea, but for ATI Users doesnt exist a Nvidia Driver :p
We can use the -winxp Prameter or the msconfig Workaround. :cool:

ron mexico
Jul 6 2009, 20:28
Hi all, I understand that it takes some time to read all the posts here in this threat.
I do see people still looking for help.
Yes, the 8GB problem with the newer driverversions ( NVIDIA 186.18 ) still exists, just want to confirm that.
Folks, I did spend lots of time with debuging this issue - and weeks ago I found invent the workaround setting the RAM in the advanced startup settings of the msconfig to the value of 7680MB - bringing the best results, as it is confirmed by other forumusers.
Why not using this workaround for now?
As a reminder, if you change the value of the RAM in your msconfig to 7680MB,
don´t have a look in the msconfig after the restart, use the taskmanager instead. Check the total amount of total physical memory there.
It might be around 6655MB, wich is O.K. .
Using the NVIDIA 186.18 driver with altering the amount of RAM to 7680MB in the msconfig solves the problem and will give you best results in level of details and performance using 8GB RAM.

Bruno, I have tried all of the troubleshooting and quick fixes, but yours has helped me the MOST!!! THANK YOU VERY MUCH!

claus.valca
Jul 7 2009, 07:37
i get multiple reports that users on Windows 7 fixed these issues by falling back to v181 drivers ...

on other OSes and some certain configs stable driver builds vary ...

so if someone want to try it ... feel free

I am on Windows 7. I use the 181.71 from NVIDIA's site. They do fix the 8GB bug, just like the 182.50s do for Vista. I just use those instead of limiting my memory.

svedge
Jul 7 2009, 09:42
I have a AMD Dragon (http://en.wikipedia.org/wiki/AMD_Dragon) platform with 8GB RAM and Vista x64. No problems here.

-s!Gm4-
Jul 7 2009, 11:51
I am on Windows 7. I use the 181.71 from NVIDIA's site. They do fix the 8GB bug, just like the 182.50s do for Vista. I just use those instead of limiting my memory.

Now, I can confirm that!
Damn it, I never thought that a earlier _beta_driver would be the solution for a problem like this (which btw should be finxed in later releases! o_O )

I hope that this driver also doesnt crash like the others. Will report back after some testing.

BrunoDerRabe
Jul 7 2009, 15:07
Bruno, I have tried all of the troubleshooting and quick fixes, but yours has helped me the MOST!!! THANK YOU VERY MUCH!

@<hidden>!Gm4- I do not understand why people refuse to use this workaround.
Using `only´´ 7680 MB of avaible 8192 MB is not such a big deal, on the bright side of it you can use the latest drivers with the latest enhancements.
:bounce3: :bounce3: :bounce3:

-s!Gm4-
Jul 7 2009, 15:25
I do not refuse it. But testing the 181.71 also gave me the opportunity to see if this driver isn't crashing.

It does, so to me its quite the same if I run the latest driver WITH workaround or an earlier version w/o workaround ;)

So, anyway - with or without workaround I just have to take care of this driver-still-crashing-issue -_-

Anyway, I appreciate your help and definitely _will_ revert to your workaround if I have to install newer drivers and this bug still exists :)

BrunoDerRabe
Jul 7 2009, 15:48
Thank you, just want to save the people using 8 GB of RAM and having problems to get lost here in the estimated 130 or more posts.

frag85
Jul 20 2009, 10:49
nothing too major hindering the game's playability here besides the CO30 Evolution mod missions bugging out after 6-8hours after start.

with nvidia 186 and 190 drivers localVram always detects 2x what i have; 1792 detected vs 896 actual. nonlocalvram is also always at 1792. i notice no difference forcing localVRAM to 896 (939524096), and nonlocalvram from 0GB to 6GB.

since i bought ARMA 2 last week off steam (version 1.02) i have found that 99.9% of everything posted on forums and word of mouth regarding "performance tweaks" either A) do not effect performance or B) actually reduce performance for my setup. the game behaves the same as ARMA on my system for whatever reason so i guess i am fortunate and lucky that i have not had any issues. if i didn't personally know people having problems i would say all these issues are user error or just a bunch of bull, but it seems like a lot of people have been having issues. i found settings that give good performance and visual quality and they work fine for me. i had the game running for 8+ hours the other day (yes i took several breaks, just never shut the game down) playing Evolution Red .9 and it never glitched or slowed down at all.

the only crashes and glitches i get is when i set "Video Memory" to Very High or Default. this only occurs if i do not occationally alt-tab or use the flush command. also when changing -maxmem= to over 2000 i get a random CTD with the "failed to commit" error window. if i am travelling at a high rate of speed through a town after about 10-20 minutes; flying very low, full speed in vehicles.

the only performance hitch i have is with AntiAliasing and Shadows set to High or Very High the game stutters and is not smooth enough to enjoy even with 80+ PFS on my GTX275. a clanmate is having the same issue with an almost identical system except for his 295.

My system:
Win 7 RC
Core I7 @<hidden> 4.2ghz
275 896mb w/ Beta 190.38 drivers. 760core/1620shader/1332memory
6GB 3x2GB DDR3@<hidden> 8-9-9-18
WD Raptor
WD AAK

ArmaIImark: 5700-5900 (1st run), 6600-6800 (2nd, 3rd+ run)

Dispaly Res: 1280x1024
Rendering Res: 1704x1364 (133%)
view distance: 3000 (or 2000 when in a larger city)
Texture: High (or normal depending on if i'm on the ground vs. air)
Video Mem: High
AF: Very High
AA: High
Terrain: Very Low
Object Detail: Normal (or high depending on coop vs. pvp for better framerate)
Post Processing: Low (or off, motion blur gives me a headache)

Albert Schweitzer
Jul 20 2009, 10:55
I have an additional question here, with

Vista, q9450 and a 4890 would it make an impact to upgrade von 4gig to 8?:)

SimonJames
Jul 20 2009, 14:12
This is all a lot to take in especially as I'm not all that computer savvy. I've tried all sorts of configurations of these fixes listed and am still getting random CTD.

My CTD are preceded by loss of textures and slow down in FPS, I noticed windows side bar clock shows 42% of my RAM being used and it stays filled even after CTD for the duration until I reboot.

Has anyone with these problems and similar specs to mine found a "fix" I could try. I have the following so the 8GB fix would need to be altered to suit my RAM ?

Core i7 920@<hidden>
6GB DDR3 tri chan RAM@<hidden>
GTX260(216) 896MB(Factory OC) - GPU: 621MHz, Mem: 1000MHz, Shader: 1350MHz
nVidia Driver Version 186.18 (roll back did not fix):(

Arma 2 config:
language="English";
3D_Performance=100000;
Resolution_Bpp=32;
Resolution_W=1600;
Resolution_H=1200;
refresh=60;
Render_W=1600;
Render_H=1200;
FSAA=0;
postFX=1;
HDRPrecision=8;
lastDeviceId="";
localVRAM=1745850369;
nonlocalVRAM=2147483647;

I've tried all sorts of fixes listed already but no combination seems to work, what should I concentrate on. Not knowing what I'm doing, I may make things worse adding the wrong switches and/or trying fixes I should not be using ?

Edit for more clarification: I tried in-game GFX on low, medium and high setting and different combo's. The 'Shift -FLUSH' command works but I can't always catch it in time before I CTD. Frames rates are good at higher settings but CTD are more frequent. The larger map also suffers more frequent CTD as does fast ground speed, whether in fligh or on the ground.

Private Plowjoy
Jul 20 2009, 20:12
Here are some Screens:

with 8GB:
[IM]http://img35.imageshack.us/img35/4141/arma28gb.th.jpg[/IMG] (http://img35.imageshack.us/my.php?image=arma28gb.jpg)

with 4GB:
[IG]http://img35.imageshack.us/img35/7127/arma24gb.th.jpg[/IMG] (http://img35.imageshack.us/my.php?image=arma24gb.jpg)

We have here on the armed-assault.de Forums (http://hx3.de/technische-fragen-probleme-162/schwere-grafikfehler-16290/) a few People with the same Problem, different Systems (Vista/XP/32/64bit/SP1/SP2) and GFX Cards but all with 8GB RAM.

Edit:
These are my System Specs:
Asus P5Q Board
Intel Q9300 @<hidden>,5GHz
8GB RAM
HD 4870 1GB
Vista 64bit SP2

Edit2:
When I launch ArmA2 with the 640x480 Resolution, the Textures shows normal. If i switch now to the native Resolution of my TFT (1680x1050) the Textures are still normal an they stay normal till i stop playing.

Just want to chime in here.

I had exactly this problem last night. My story is as follows...

1: On Vista 64bit with all windows updates done, I was running Arma2 with almost all settings on Very High (selected in game).

2: I lowered my resolution to 1680x1050 and lowered all my in-game settings to at best Normal. I did this to fall in line with ArmaII-Mark standards.

3: I ran ArmaII-Mark for an hour, to get my consistent mean results back.

4: I attempted to switch the in-game settings back up to Very High and found that I could not push Texture and Video Memory above Normal.

5: Uninstalled Arma2 and reinstalled. Same.

6: Uninstalled Arma2 and manually removed all leftover files and folders before reinstalling. Same.

7: Uninstalling my Nvidia drivers, cleansweeped and reinstalled. Same.

8: Uninstalled both Arma2 and Nvidia drivers. Performed manual removal of files and folders, alongside multiple cleansweeps and multiple PC restarts. Reinstalled everything. Same.

9: Formatted my C drive and reinstalled Vista 64bit. As soon as the OS was back up, I got the soundcard drivers on there, Nvidia drivers on there and installed Arma 2. SAME RESULT. I could not push Texture and Video Memory above Normal.

10: Uninstalled Nvidia drivers and installed 190.38_desktop_win7_winvista_64bit_english_BETA. Fired up Arma2 and found that whilst I could now select Very High Textures and Video Memory, I had exactly the problem on the screenshot where all the in-game graphics were pretty much flat colour grey and black.

At this stage after spending 4 hours+ trying to get this thing working, I gave up. I was seriously angry and starting a brand new job in 6 hours time....

11: Today, after getting in from the first day in my new job :D I decided i'd do a Windows Update to completion, as I hadn't done that after the Vista 64bit reinstall. After SP2 was installed I thought i'd give the game another try.

LO AND BEHOLD. IT WORKS!

Seriously, I changed nothing else on my system. The Nividia drivers are the same Beta as installed last night. All i've done is Windows Update until there was nothing left to update.

All I can suggest is that you give this a try.

frag85
Jul 20 2009, 21:35
My CTD are preceded by loss of textures and slow down in FPS, I noticed windows side bar clock shows 42% of my RAM being used and it stays filled even after CTD for the duration until I reboot.

open up the task manager and End the ArmA2.exe proccess.

i probably shouldn't have said anything about the game running well, it must have crashed over a dozen times in an hour today and nothing has changed. then all of a sudden it decides to work and it went 4 hours untill i had to go to work.

wills
Jul 21 2009, 00:45
nvidia 295gtx windows rc 64bit? runs blocky with 8gig of ram? ok with 4

Suma
Jul 21 2009, 12:54
8GB on Windows7 RC1 NVIDEA 186.18 2 260GTX in SLI AMD PhenomII 940BE @<hidden> 3.0Ghz were used for the test

While I was able to reproduce this issue, it seems it is gone with nVidia 190.38 drivers.

BangTail
Jul 21 2009, 13:05
While I was able to reproduce this issue, it seems it is gone with nVidia 190.38 drivers.

It is but these supposedly "WHQL" drivers (as of today) introduce new problems that are unrelated to A2. On certain cards , the fan speed is being forced to 100% and does not revert to non gaming speeds when you stop playing.

Nvidia seems to be having considerable "driver woes" at the moment.

Revelate
Jul 21 2009, 14:02
Here are some Screens:

with 8GB:
[IM]http://img35.imageshack.us/img35/4141/arma28gb.th.jpg[/IMG] (http://img35.imageshack.us/my.php?image=arma28gb.jpg)

with 4GB:
[IG]http://img35.imageshack.us/img35/7127/arma24gb.th.jpg[/IMG] (http://img35.imageshack.us/my.php?image=arma24gb.jpg)

We have here on the armed-assault.de Forums (http://hx3.de/technische-fragen-probleme-162/schwere-grafikfehler-16290/) a few People with the same Problem, different Systems (Vista/XP/32/64bit/SP1/SP2) and GFX Cards but all with 8GB RAM.

Edit:
These are my System Specs:
Asus P5Q Board
Intel Q9300 @<hidden>,5GHz
8GB RAM
HD 4870 1GB
Vista 64bit SP2

Edit2:
When I launch ArmA2 with the 640x480 Resolution, the Textures shows normal. If i switch now to the native Resolution of my TFT (1680x1050) the Textures are still normal an they stay normal till i stop playing.

Jsut wanted to put my 2 cents in as well ive read a few posts here. Im trying the Demo as some mates of mine have said its worth a go. But I Have EXACTLY that issue. My Machine is nothing short of half decent and should be able to run this game almost flawlessy at the best graphics and I mean Almost, not quite system specs as follows;

AMD Phenom II 940 Black Edition
780G AMD Chipset MB
8gig Kingston Hyper X @<hidden> 1066mhz RAM
Vista Ultimate x64

Why should I have to go into the config and have to change the Memory to 4gig or a tad less everytime I want to run this game then have to go back and change it restart my machine to be able to run 4 or 5 Virtual Machines for business, waste of time. If they dont fix the Demo why should I bother buying the full game. Id like to be able to run it at 1680x1050 for Screen Res and 3D graphics I shouldnt have to piss fart around with my memory its rediculous. I assume some of you are having this problem with the full release is that right?

I may have missed a post from BI are they going to or have they addressed this issue because I had a look at V1.2.5 patch notes and looks like they did nothing about it.

Im not buying this game as I said if the Demo doesnt work so why bother wasting money on the full release. The Demo is meant to be a demonstration of what the game is meant ot be like. Well to me it looks like rubbish like Im playing some old 16bit game with new polygons. No thanks...

I hope they fix it, if they did theyd probably sell mroe copys Im sure of it.

Cheers!

mr.g-c
Jul 23 2009, 14:05
So Suma, you could replicate it for Nvidia Users that is very good at least, but what is with us ATI users?

Will it remain once again like it was with Arma1, that you will only have disadvantages with ATI Cards?
Must i feel cheated again having thrown my hard earned cash out of the Window, in my tiny hope that i had actually bought a GOOD Graphics Card for Arma2 this time?

Looking at your latest changelog Placebo made Public recently, i cant notice any of those 8GB-Issues fixed.
I wonder what is more important to you, pleasing the crowd with Analogue Throttle Support or investigating and finally fixing the really important issues which making the game UNPLAYABLE in the first place for some of us?

We bought 3 copies of Arma2 here in my Family, 2 People can't play it properly at all because of having a top-notch graphics card and 8GB Ram.

Do i have to mention that Arma2 has already dropped over 40% in Price for a new version and on eBay you can even get it for 10-15 bucks already, while the Forums are full with complains about those serious issues making the game almost impossible to play...

I hope and really urge you with this post to fix those important issues for the upcomming patch.
Thanks!

Hotel
Jul 23 2009, 18:27
Yes, like in the old ArmA 1 days mostly with ATI cards, after cutting 4gb with msconfig, the problem was gone, and the perfomance was really nice, all settings cranked up to max with 10km viewdistance and runs now great.

vista x64
Q9300 2.5GHz
8gb ram
4870 1gb

Im sorry but you said your game runs great with all settings cranked with 10 KM draw. Your game actually runs good with 10KM draw..... Find that really hard to believe man. The draw distance depends a lot on CPU and with a 2.5 i just see how its possible.

psychedelic
Jul 23 2009, 20:46
I'm having exactly this kind of issue. I recently upgraded my computer with EVGA GTX285 and added 4GB of RAM for a total of 8GB. Now, my game is unplayable, with all this graphics problems. I'm going to try and remove 4GB and see if that's causing the problem.
Will report back.

kklownboy
Jul 23 2009, 20:53
Im sorry but you said your game runs great with all settings cranked with 10 KM draw. Your game actually runs good with 10KM draw..... Find that really hard to believe man. The draw distance depends a lot on CPU and with a 2.5 i just see how its possible. bet he doesn't use AA... and is playing at 1400/900

Malecite
Jul 24 2009, 02:30
Yep 8 gigs of RAM here and my graphics get all fuzzy and blocky when I attempt to go near buildings, the FPS also drops to around 10.

maka12
Jul 24 2009, 07:13
my specs
phenom2 x4 955 be
crosshair iii
8gb ram
os windows vista64 ati gamer
ati sapphire 4870x2 2gb
i tried the winxp trick after the arma2.exe and improved everything, still not perfect but 10 times better than it was, it playable now and got most settings on very high, where before they were on low, the game must not like 8gb of ram, also try installing amd fusion got a extra 5fps from it if your amd ati..

AnthonyTheAussie
Jul 25 2009, 13:06
Yo guys I had the same problems but I worked out how to fix it, waht you do is you turn every thing off or to its lowest ( I mean everything) then you exit the game then click on the shortcut to start up arma2 again then you can turn everything to its max and not have the blocky and no texture problem. It works for me so it should work for you.

skypine27
Jul 28 2009, 06:08
To all:

I was playing the game fine on my fairly high end system (see sig) under Vista 64. I did a clean install to Windows 7 64 and the newest nvidia drivers, I get the problem you guys are having (missing textures, flashing white windows, etc).

I tried the -winxp fix and the game now works fine. BUT, what does this fix do? Is the the same as "disabling" 4 GB of ram?? I dont want my performance to suffer by using this fix.

Anthony, maybe I will try your suggestion and see if that works (and not use the -winxp flag)

Bulldogs
Jul 28 2009, 06:11
It tells the game to use the windows XP directx (DX 9) instead of Directx 10 (I'm pretty sure that's what it does), effectively this should raise performance at the cost of a few effects, although if you have post processing disabled you probably won't notice the difference between the 2.

skypine27
Jul 28 2009, 06:20
Bulldogs:

Thankx for the info. I had post processing set to Very High, and was playing fine (agian, under Vista 64). I guess I will have to play the game with the -winxp line, until nvidia and/or BIS fix this issue. (Im not removing 4gb of ram to play this! :-)

Edit: The "-winxp" command seems to not help with the super bright whites. For example, anything white gets a bright, halo, type glow around it.

Anthony:

Your fix sort of works for me. Its a one time fix, as in, you have to go thru the process each time you load the game. Not workable.

Ollem
Jul 28 2009, 11:18
@<hidden>: same for me: one time only fix.

Reducing 8 -> 7 Gb memory trick using msconfig solved the issue for me too.

Windows 7 64bit
e8400
HD4890 (1 Gb mem)
8 Gb mem

skypine27
Jul 28 2009, 14:02
Ollem:

What is the 8 to 7GB msconfig trick?

That sounds like it might be worth trying until a fix comes out.

kklownboy
Jul 28 2009, 14:26
Ollem:

What is the 8 to 7GB msconfig trick?

That sounds like it might be worth trying until a fix comes out.

Thanks in advance. you open up msconfig, and set the BOOT, Advanced, MAXIMUM MEMORY to less than 8GB.

BrunoDerRabe
Aug 2 2009, 22:44
While I was able to reproduce this issue, it seems it is gone with nVidia 190.38 drivers.
8GB on Windows7 RC1 NVIDEA 190.38 2 260GTX in SLI AMD PhenomII 940BE @<hidden> 3.0Ghz were used for the test

Hi Suma,

on my testsystem the 190.38 driver is not the cure for the 8GB issue.
After reading your post I did upgrade the testsystem once more to 8GB RAM, with the hope I could CONFIRM that the issue seems to be gone with nVidia 190.38 drivers. But unfortunately it isn´t like that on my testsystem. At the Moment I´m setting the amount of RAM in the msconfig to 7680MB.

The two last lines of the arma.cfg
before changing the amount of RAM in the msconfig to 7680MB:
localVRAM=4911104;
nonlocalVRAM=4911104

The two last lines of the arma.cfg
after changing the amount of RAM in the msconfig to 7680MB:
localVRAM=2085285888;
nonlocalVRAM=2085285888;

Greetings, Bruno

ArmA2.cfg:

language="German";
3D_Performance=93750;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=2400;
Render_H=1500;
FSAA=4;
postFX=3;
HDRPrecision=8;
lastDeviceId="";
localVRAM=2085285888;
nonlocalVRAM=2085285888;

---------- Post added at 09:49 PM ---------- Previous post was at 09:20 PM ----------

nothing too major hindering the game's playability here besides the CO30 Evolution mod missions bugging out after 6-8hours after start.

with nvidia 186 and 190 drivers localVram always detects 2x what i have; 1792 detected vs 896 actual. nonlocalvram is also always at 1792. i noticedifference forcing localVRAM to 896 (939524096), and nonlocalvram from 0GB to 6GB. no

since i bought ARMA 2 last week off steam (version 1.02) i have found that 99.9% of everything posted on forums and word of mouth regarding "performance tweaks" either A) do not effect performance or B) actually reduce performance for my setup. the game behaves the same as ARMA on my system for whatever reason so i guess i am fortunate and lucky that i have not had any issues. if i didn't personally know people having problems i would say all these issues are user error or just a bunch of bull, but it seems like a lot of people have been having issues. i found settings that give good performance and visual quality and they work fine for me. i had the game running for 8+ hours the other day (yes i took several breaks, just never shut the game down) playing Evolution Red .9 and it never glitched or slowed down at all.

the only crashes and glitches i get is when i set "Video Memory" to Very High or Default. this only occurs if i do not occationally alt-tab or use the flush command. also when changing -maxmem= to over 2000 i get a random CTD with the "failed to commit" error window. if i am travelling at a high rate of speed through a town after about 10-20 minutes; flying very low, full speed in vehicles.

the only performance hitch i have is with AntiAliasing and Shadows set to High or Very High the game stutters and is not smooth enough to enjoy even with 80+ PFS on my GTX275. a clanmate is having the same issue with an almost identical system except for his 295.

My system:
Win 7 RC
Core I7 @<hidden> 4.2ghz
275 896mb w/ Beta 190.38 drivers. 760core/1620shader/1332memory
6GB 3x2GB DDR3@<hidden> 8-9-9-18
WD Raptor
WD AAK

ArmaIImark: 5700-5900 (1st run), 6600-6800 (2nd, 3rd+ run)

Dispaly Res: 1280x1024
Rendering Res: 1704x1364 (133%)
view distance: 3000 (or 2000 when in a larger city)
Texture: High (or normal depending on if i'm on the ground vs. air)
Video Mem: High
AF: Very High
AA: High
Terrain: Very Low
Object Detail: Normal (or high depending on coop vs. pvp for better framerate)
Post Processing: Low (or off, motion blur gives me a headache)

Hi frag85,

you are not running 8GB RAM, your post seems to be off topic for me.

Quote: i notice difference forcing local VRAM to 896 (939524096), and nonlocalvram from 0GB to 6GB
Answer: The two last lines of the ArmA2.cfg are more for your information and not to force something.
*If you set the CFG file to read only it doesn't overwrite.*
O.K., let say it this way,,,, it will be ignored. If you change it to read only, in this case it is like an effort to ignore, that the efforts to get it right, had no success so far ....

Quote: with nvidia 186 and 190 drivers localVram always detects 2x what i have
Here an outtake of my previous post #67 in this thread from 06-23-2009, 03:01 AM that might help you to understand:

msconfig 4096MB = shows after reboot 3071MB in the taskmanager detected localVRAM=924581888
msconfig 6144MB = shows after reboot 5119MB in the taskmanager detected localVRAM=1217781761
msconfig 7168MB = shows after reboot 6143MB in the taskmanager detected localVRAM=1754652673
msconfig 7424MB = shows after reboot 6399MB in the taskmanager detected localVRAM=1888870401
msconfig 7680MB = shows after reboot 6835MB in the taskmanager detected localVRAM=2117459969
msconfig 7804MB = shows after reboot 6779MB in the taskmanager detected localVRAM=2088099841
msconfig 7936MB = shows after reboot 6911MB in the taskmanager detected localVRAM=4911104= NOT GOOD

---------- Post added at 10:07 PM ---------- Previous post was at 09:49 PM ----------

07-23-2009, 02:05 PM #142
So Suma, you could replicate it for Nvidia Users that is very good at least, but what is with us ATI users?

Will it remain once again like it was with Arma1, that you will only have disadvantages with ATI Cards?
Must i feel cheated again having thrown my hard earned cash out of the Window, in my tiny hope that i had actually bought a GOOD Graphics Card for Arma2 this time?

Looking at your latest changelog Placebo made Public recently, i cant notice any of those 8GB-Issues fixed.
I wonder what is more important to you, pleasing the crowd with Analogue Throttle Support or investigating and finally fixing the really important issues which making the game UNPLAYABLE in the first place for some of us?

We bought 3 copies of Arma2 here in my Family, 2 People can't play it properly at all because of having a top-notch graphics card and 8GB Ram.

Do i have to mention that Arma2 has already dropped over 40% in Price for a new version and on eBay you can even get it for 10-15 bucks already, while the Forums are full with complains about those serious issues making the game almost impossible to play...

I hope and really urge you with this post to fix those important issues for the upcomming patch.
Thanks!

Hi mr.g-c,

no offense, but why don´t you just calm down, read the solution offered here ( it is avaible since 06-23-2009, 03:01 AM #67 ) and make the 2 People who can't play it properly at all because of having a top-notch graphics card and 8GB Ram smile again.

Greetings, Bruno

... setting the RAM in the advanced startup settings of the msconfig to the value of 7680MB - bringing the best results, as it is confirmed by other forumusers.
Why not using this workaround for now?
As a reminder, if you change the value of the RAM in your msconfig to 7680MB,
don´t have a look in the msconfig after the restart, use the taskmanager instead. Check the total amount of total physical memory there.
It might be around 6655MB, wich is O.K. .
Using the NVIDIA 186.18 or 190.38 driver with altering the amount of RAM to 7680MB in the msconfig solves the problem and will give you best results in level of details and performance using 8GB RAM.

---------- Post added at 10:22 PM ---------- Previous post was at 10:07 PM ----------

I have an additional question here, with

Vista, q9450 and a 4890 would it make an impact to upgrade von 4gig to 8?:)

With a 64 Bit Version of Vista it could.

msconfig 4096MB = shows after reboot 3071MB in the taskmanager detected localVRAM=924581888
msconfig 7680MB = shows after reboot 6835MB in the taskmanager detected localVRAM=2117459969

The detected an USED localVRAM (local video RAM / perhaps extended with some amount of the system RAM ) will be increased. One bottleneck of the usage might be also the narrow 256 Bit memorybus of your ATI 4890.

Greetings, Bruno

---------- Post added at 10:34 PM ---------- Previous post was at 10:22 PM ----------

This is all a lot to take in especially as I'm not all that computer savvy. I've tried all sorts of configurations of these fixes listed and am still getting random CTD.

My CTD are preceded by loss of textures and slow down in FPS, I noticed windows side bar clock shows 42% of my RAM being used and it stays filled even after CTD for the duration until I reboot.

Has anyone with these problems and similar specs to mine found a "fix" I could try. I have the following so the 8GB fix would need to be altered to suit my RAM ?

Core i7 920@<hidden>
6GB DDR3 tri chan RAM@<hidden>
GTX260(216) 896MB(Factory OC) - GPU: 621MHz, Mem: 1000MHz, Shader: 1350MHz
nVidia Driver Version 186.18 (roll back did not fix):(

Arma 2 config:
language="English";
3D_Performance=100000;
Resolution_Bpp=32;
Resolution_W=1600;
Resolution_H=1200;
refresh=60;
Render_W=1600;
Render_H=1200;
FSAA=0;
postFX=1;
HDRPrecision=8;
lastDeviceId="";
localVRAM=1745850369;
nonlocalVRAM=2147483647;

I've tried all sorts of fixes listed already but no combination seems to work, what should I concentrate on. Not knowing what I'm doing, I may make things worse adding the wrong switches and/or trying fixes I should not be using ?

Edit for more clarification: I tried in-game GFX on low, medium and high setting and different combo's. The 'Shift -FLUSH' command works but I can't always catch it in time before I CTD. Frames rates are good at higher settings but CTD are more frequent. The larger map also suffers more frequent CTD as does fast ground speed, whether in fligh or on the ground.

Hi SimonJames,

you are not running 8GB RAM, your post seems for me to be off topic too.
But certainly I would like to solve your problem.
In your case the detected VRAM is O.K..
First I ask you to run your overclocked Core i7 920@<hidden> at its native speed @<hidden>,666GHz.
This needs to be done with your RAM or whatever is overclockeded too.

Greetings, Bruno

---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------

Jsut wanted to put my 2 cents in as well ive read a few posts here. Im trying the Demo as some mates of mine have said its worth a go. But I Have EXACTLY that issue. My Machine is nothing short of half decent and should be able to run this game almost flawlessy at the best graphics and I mean Almost, not quite system specs as follows;

AMD Phenom II 940 Black Edition
780G AMD Chipset MB
8gig Kingston Hyper X @<hidden> 1066mhz RAM
Vista Ultimate x64

Why should I have to go into the config and have to change the Memory to 4gig or a tad less everytime I want to run this game then have to go back and change it restart my machine to be able to run 4 or 5 Virtual Machines for business, waste of time. If they dont fix the Demo why should I bother buying the full game. Id like to be able to run it at 1680x1050 for Screen Res and 3D graphics I shouldnt have to piss fart around with my memory its rediculous. I assume some of you are having this problem with the full release is that right?

I may have missed a post from BI are they going to or have they addressed this issue because I had a look at V1.2.5 patch notes and looks like they did nothing about it.

Im not buying this game as I said if the Demo doesnt work so why bother wasting money on the full release. The Demo is meant to be a demonstration of what the game is meant ot be like. Well to me it looks like rubbish like Im playing some old 16bit game with new polygons. No thanks...

I hope they fix it, if they did theyd probably sell mroe copys Im sure of it.

Cheers!

Hi Revelate,

you can use the amount of 7680MB ( may be a wee bit less/7424MB for example - which is best depends on the chipset too ) stop moaning, start playing the game and you will probably be able to do your business and run your 4 or 5 Virtual Machines.

Following Quote is edited by me ( driverversions ):

Hi all, I understand that it takes some time to read all the posts here in this threat.
I do see people still looking for help.
Yes, the 8GB problem with the newer driverversions ( NVIDIA 190.38 ) still exists, just want to confirm that.
Folks, I did spend lots of time with debuging this issue - and weeks ago I did invent the workaround setting the RAM in the advanced startup settings of the msconfig to the value of 7680MB - bringing the best results, as it is confirmed by other forumusers.
Why not using this workaround for now?
As a reminder, if you change the value of the RAM in your msconfig to 7680MB,
don´t have a look in the msconfig after the restart, use the taskmanager instead. Check the total amount of total physical memory there.
It might be around 6655MB, wich is O.K. .
Using the NVIDIA 186.18 or 190.38 driver with altering the amount of RAM to 7680MB in the msconfig solves the problem and will give you best results in level of details and performance using 8GB RAM.

I got feedback by some forumusers during the last weeks that for some motherboards the amount of 7424MB is the better choice (OS/chipsets/drivers).

Greetings, Bruno

Desert
Aug 5 2009, 20:35
Even with 1.03 the Problem is still there. . . :(

kklownboy
Aug 5 2009, 21:34
hmmm well then it may be upto a driver update... ATi is in a couple of weeks, a beta nvda maybe out at the same time...

Bigtnaples
Aug 5 2009, 22:27
Even with 1.03 the Problem is still there. . . :(

Fiya
Aug 5 2009, 23:01

Yes, because it must be something extremely simple, that requires almost no effort or time. Even though I believe their is a DIY fix already. Compared to many things which do not.

You did not play the original Arma did you?...

Shataan
Aug 6 2009, 00:32
I have a BFG 295 GTX, and my swapfile is set to 8092 min/max. What should I set my local and nonlocalvram to? Thx .

-s!Gm4-
Aug 6 2009, 10:12

I think they had a closer look to issues with the engine, like physics, faulty animations, faulty behaviour of vehicles/buildings/AI and so on.
Personally I think the'll take a look to the technical side with the next patch or several hotfixes...

Note that I dont want to defend'em. I want to use my whole 8 Gigs of RAM also - without any errors.

XZeal
Aug 7 2009, 17:06
I got the same problem, and I kindly ask Bohemia to pay more attention on this problem, to solve in proper way/

Sn@keByte
Aug 8 2009, 15:21
Bug is still present in 1.03:

Win7 RC1 x64
8 GB DDR3
ATi 4890 GS-Edition

Can still be fixed with -winxp parameter.

nuggetz
Aug 11 2009, 00:33
Just tried to reboot with all my RAM and I too confirm that BIS didn't even think about fixing this awful problem in 1.03.

datter
Aug 11 2009, 12:50
Since moving to 8GB from 6Gb I'm seeing related problems as well. This needs to be kept bumped up for the sake of all those with needless amounts of ram like us. :)

L33t-krew
Aug 19 2009, 14:22
Since moving to 8GB from 6Gb I'm seeing related problems as well. This needs to be kept bumped up for the sake of all those with needless amounts of ram like us. :)

Bump by me.

I had 4Gb Dominator 1066mhz working fine yesterday. Another 4gb came in the post today and its hit the corruption lark.

Disappointing it hasnt been fixed tbh.

Rikqi
Aug 19 2009, 22:17
I have the same problem. Running Win 7 64bit.

NV 190.38 drivers and Arma 2 Steam copy (so it is automatically the latest update).

My rig is a E8400, 8GB RAM, 9800GX2.

Only way I can get around the texture issue is by playing in windowed mode, but performance is sluggish.

I tried two previous driver releases from Nvidia and nada...

From the looks of this thread, the developers do know about this issue, but dont appear to have it high on their priority list.

This is obviously unprofessional. They should come out and acknowledge the problem officially and say whether they can or cannot fix it.

I don't consider msconfig fixes and the like to be acceptable after months of waiting. This game has allot of potential, but after spending my hard earned money to support this kind of unprofessional behavior, I simply can't recommend it to friends and family.

Developers, please honor your end of the deal and fix the problem. Everyone in this thread has honored their part by not only paying upfront for this product, but also investing our time in documenting and writing about the texture issue.

Thank you.

Desert
Aug 20 2009, 16:47
With BetaPatch ARMA2_Build_58834 i see no Change here.

nyran125
Aug 20 2009, 17:17
Get rid of Vista for gaming. fullstop :):). wow DX10, DAMN dx9 people are missing some slight visuals, what a shame. Id rather my games run better than have to go out an buy 6gb 's of ram just to play my games properly , screw that. Why bother?

datter
Aug 20 2009, 20:48
Get rid of Vista for gaming. fullstop :):). wow DX10, DAMN dx9 people are missing some slight visuals, what a shame. Id rather my games run better than have to go out an buy 6gb 's of ram just to play my games properly , screw that. Why bother?

Win7 64bit and 8GB ram here... why bother? 3d animation, HD video editing. etc.

http://finaldog.com/gallery/lg/reawakening.jpg (finaldog.com)

There is more to life than game playing, and it's rather silly that just having 8GB causes issues for those of us to have/need it. Frankly I'm getting sick of this entire thing, I hardly touch ArmA2 anymore and that's surprising.

Drasta
Aug 20 2009, 21:14
Then just rename arma2.exe to crysis.exe and add -winxp and you can play ArmA2 without problems... It worked for me.

shuurajou
Aug 26 2009, 16:03
While I was able to reproduce this issue, it seems it is gone with nVidia 190.38 drivers.

Hi Suma,

This still seems to be an issue.

My specs are...

GFX: BFG GeForce GTX 285 OCX
Sound: X-Fi Fatal1ty
Mobo: ASUS P5N-T Deluxe (BIOS 1303)
CPU: Intel Woldfale E8400 Intel Core 2 Duo
Cooler: Tuniq Tower 120 (on the CPU)
Case: Cosmos S
Keyboard: Microsoft Natural 4000
Mouse: Razer Diamondback
OS: Windows 7 Ultimate 64-bit Final RTM Build
RAM: OCZ Reaper HPC 8GB (4x2GB) DDR2 PC-8500C5 @<hidden> 1066MHz
Display: Dell 2005FPW
PSU: Hiper Type M 880W

My findings...

Using 190.62 drivers, with 2x 8800 GTXs in SLI, no command line arguments and no msconfig modifications, Arma 2 detected 2GB localVRAM.

Using 190.62 drivers, with 1x BFG GTX 285 OCX, no command line arguments or msconfig modifications, Arma 2 detected 200MB localVRAM. Also had white textures.

Using 190.62 drivers, with 1x BFG GTX 285 OCX, with the -winxp command line arguments and no msconfig modifications, Arma 2 detected 2GB localVRAM.

Using 190.62 drivers, with 1x BFG GTX 285 OCX, with the -winxp command line arguments and 4GB msconfig memory limitation, Arma 2 detected 1002MB (essentially correct) localVRAM.

This is with Arma v1.03. Same applies with 190.38.

kklownboy
Aug 26 2009, 17:18
..

Using 190.62 drivers, ... suma; "..with nVidia 190.38 drivers"

datter
Aug 26 2009, 17:36
shuurajou, you're an inspiration as to how to stay positive about this stuff. I've about given up and gotten rather down on things... but at least what you're doing lately is constructive.

For me (Win7 64 bit, 8GB ram):

Dual 8800GT's, with 190.62 and command line arguments (-winxp) or NO command line arguments... localvram is detected at 213mb with eventual texture issues in game.

Same set up, with or without command line and in game texture memory settings set to low, medium, high, very high or default all result in the same thing... 213mb detected, plus eventual texture issues in game as above.

Frustrating.

kklownboy
Aug 26 2009, 17:42
shuurajou, you're an inspiration as to how to stay positive about this stuff. I've about given up and gotten rather down on things... but at least what you're doing lately is constructive.

For me (Win7 64 bit, 8GB ram):

Dual 8800GT's, with 190.62 and command line arguments (-winxp) or NO command line arguments... localvram is detected at 213mb with eventual texture issues in game.

Same set up, with or without command line and in game texture memory settings set to low, medium, high, very high or default all result in the same thing... 213mb detected, plus eventual texture issues in game as above.

Frustrating.your 3D cp setting for ARMA2 is local and set to multigpu? single display?

datter
Aug 26 2009, 18:32
your 3D cp setting for ARMA2 is local and set to multigpu? single display?

Sir, yes sir.

shuurajou
Aug 26 2009, 19:00
suma; "..with nVidia 190.38 drivers"

The behaviour is the same for 190.38.

DesertJedi
Aug 26 2009, 22:01
I tried the -winxp fix and the game now works fine. BUT, what does this fix do? Is the the same as "disabling" 4 GB of ram?? I dont want my performance to suffer by using this fix.

I want to use my whole 8 Gigs of RAM also - without any errors.

For perpspective, those of you running 8GB under Vista 64-bit or Win 7 64-bit might want to try this...benchmark your games with 8GB of RAM installed and then yank 4GB and run the same benchmarks with only 4GB. When you see the identical performance results, you might view this problem in a slightly different light.

Those of you with 6GB in Tri-channel might see some added benefit simply from having the RAM run in Tri-channel mode (added memory bandwidth), not from the actual amount of memory.

I put an extra 4GB of RAM in my box but it was sort of for future-proofing but mostly because it was dirt cheap. To me, it's not really serving any purpose and I may pull it to use in a test-bench setup.

Win7 64bit and 8GB ram here... why bother? 3d animation, HD video editing. etc. There is more to life than game playing I think you've got a whole 1% of this forum covered with that one but I hear ya...I do a lot of photo editing and some video editing as well.

wheelcipher
Aug 29 2009, 00:34
For what it is worth at this point (and that may not be much), I bought and installed the game today and got the exact same results as Desert did in the very first post in this thread. After jerking around with the video settings for a bit, I came here and found this thread. I removed 4G of RAM and the problem is fixed. I now have all settings at "Very High" with no issues other than I am down to 4G RAM from 8G. My specs are below:

VIDEO:
HIS (ATI) Radeon HD 4890 Turbo Video Card
1024MB DDR5, PCI Express 2.0 x16 900Mhz core

MEMORY:
Patriot Viper 4096MB PC12800
Dual Channel DDR3 Memory - 1600MHz
Four sticks of 2Gigabytes (8G total)

OPERATING SYSTEM:
Windows Vista Ultimate (x64) Service Pack 2

MOTHERBOARD:
MICRO-STAR INTERNATIONAL 790FX-GD70 (MS-7577)
Bus Clock: 200 megahertz
BIOS: American Megatrends Inc. V1.4 07/02/2009

PROCESSOR:
3.40 gigahertz AMD Phenom II X4 965 AM3
512 kilobyte primary memory cache
2048 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
Multi-core (4 total)

MONITOR:
Dual Samsung SyncMaster 23.1"

SOUND:
Creative SB X-Fi Fatal1ty

Desert
Aug 29 2009, 10:28
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.

shuurajou
Aug 29 2009, 11:37
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.
The only problem being in that case I believe VRAM detection will still be broken and the 'default' setting won't result in the optimum performance of his 4890. May be different with ATI though.

kklownboy
Aug 30 2009, 18:16
Th... May be different with ATI though. It is.

Aria
Aug 31 2009, 06:15
Ummm ok dumb question here but is there anyway to fix this problem without doing something crazy to the computer like messing with the MSconfig etc? I mean only asking cause I don't want to screw my computer up just to get ARMA II to run. :confused:

That being said if it was already posted as far as a solution goes I'm sorry to asking.

In anycase to verify that this is indeed the problem, my computer was being worked on for several weeks so natrually I got online to get new drivers now ARMA II looks exactly like what everyone is describing.

My computer Specs are:

EVGA GTX 285
8 GB of OCZ DDR3 Reaper Memory
Striker II Extreme Mobo
Intel Q9650 3.0 GHZ

Running Vista-64 bit.

-s!Gm4-
Aug 31 2009, 07:20

You can either try the command line tag -winxp , which limits the RAM used to ~2GB, or you can manually remove (thats what I did) some RAM.

shuurajou
Sep 1 2009, 10:05

You can either try the command line tag -winxp , which limits the RAM used to ~2GB, or you can manually remove (thats what I did) some RAM.

VRAM detection is still broken even if you use -winxp.

mlenser
Sep 1 2009, 10:25
You can either try the command line tag -winxp , which limits the RAM used to ~2GB, or you can manually remove (thats what I did) some RAM.Taken from the ARMA II Startup Parameters Wiki Page HERE (http://community.bistudio.com/wiki/Arma2:_Startup_Parameters)

-winxp= use it in Vista/Windows 7 to enable multi-GPU support (Arma2)
-maxmem= Limit memory allocation (in MB). 2047 is hardcoded maximum at the moment (Arma2 1.01 final, anything higher falls back to 2047).

When running on Win7 64-bit I use -winxp -maxmem=2047 -nosplash (and if I'm testing a beta build -cpucount=4 as I have an i7) and i don't get any texture issues.

shuurajou
Sep 1 2009, 10:36
Taken from the ARMA II Startup Parameters Wiki Page HERE (http://community.bistudio.com/wiki/Arma2:_Startup_Parameters)

-winxp= use it in Vista/Windows 7 to enable multi-GPU support (Arma2)
-maxmem= Limit memory allocation (in MB). 2047 is hardcoded maximum at the moment (Arma2 1.01 final, anything higher falls back to 2047).

When running on Win7 64-bit I use -winxp -maxmem=2047 -nosplash (and if I'm testing a beta build -cpucount=4 as I have an i7) and i don't get any texture issues.

That may be true, but if you look at the nonlocalVRAM & localVRAM parameters in your ArmA2.cfg are they accurate (convert bytes to megabytes)? If they are inaccurate and then you are likely getting performance that isn't taking full advantage of the RAM on your video card.

mlenser
Sep 1 2009, 10:50
No mine aren't correct either, Arma 2 auto detects:

localVRAM=1947303872;
nonlocalVRAM=1947303872;
Should be 6Gb DDR3 and 896MB Video memory. I read somewhere that you can edit the file yourself and make it "read only" if its a concern to you.

shuurajou
Sep 1 2009, 11:34
No mine aren't correct either, Arma 2 auto detects:

localVRAM=1947303872;
nonlocalVRAM=1947303872;
Should be 6Gb DDR3 and 896MB Video memory. I read somewhere that you can edit the file yourself and make it "read only" if its a concern to you.

Even if you set the read as read only ArmA 2 only writes to those parameters to help with debugging, it doesn't read from them so you can change them to 2MB and it won't help.

Sniperdoc
Sep 1 2009, 12:57
While I was able to reproduce this issue, it seems it is gone with nVidia 190.38 drivers.

Negative. I have them on my setup and am experiencing the same texture problems as in the OP's screenshots. Bushes and trees = non-textured squares, heads of characters as white model heads, and untextured vehicles/buildings.

I have the latest Win 7 RC. I'm running two GTX280's in SLI with PhysX enabled and have the 190.38 drivers.

I was running the 186's? before and had no problems with everything maxed out at 1680x1050. I did the upgrade to the 190.38 drivers and got hit with that texture bug.

I can run the game with the -winxp switch and it seems to correct it, but I know I'm not getting the most out of my system. I've tried renaming the .cfg file to .back and having A2 recreate the file for re-detection of RAM, but it didn't help. Going to try setting memory in Win7 startup.

See system specs in sig.

mlenser
Sep 1 2009, 13:15
I just did a bit of monitoring of my video memory usage while running Armamark and it appears that it was using about 620-630mb of LocalVRAM and 8mb of Non-LocalVram although without Arma running its already reporting 7.7mb being used.

Desert
Sep 15 2009, 13:39
No Change with Patch 1.04 here. Thats sad. :(

datter
Sep 15 2009, 17:04
At least that means I don't have to bother patching I suppose. Sadly, shelved until this is resolved.

Ruges
Sep 15 2009, 19:18
I saw there was a new patch today and was like ohhh, maybe I can start playing the game again. Nope not fixed. Seems like this is an important issue that would be resolved asap.

Ohh well shelfed till hopfully next patch, it can sit next to HOI3.

Aria
Sep 17 2009, 08:32
Yep same I've shelving ARMA II alongside the other failed game, HoI III.

Heading over to the Operation Flashpoint: DR forums and maybe informing them of the issue that this game has, not that they use the same engine but just to make Codemasters aware of the issue, so it won't happen to them.

Trunkz Jr
Sep 17 2009, 08:37
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.

Yep this is what I did, my desktop shortcut looks like this:

"C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -winxp (now my graphics look much better)

Mine works fine, no way I'm taking out 4gig of ram just to play anyway, you shouldn't have to in the first place, I payed for the extra anyway so Might as well keep it in (even if it doesnt make a difference then 4)

mlenser
Sep 17 2009, 08:40
Aria & Ruges. Let me get this straight, you two are shelving the game because you can't be bothered putting -winxp -maxmem=2047 in the shortcut ?????? :j:

Sniperdoc
Sep 17 2009, 16:08
They're shelving the game because it's not functioning as it was intended to.

Do this for me:

Restrict yourself to only using the lowest option even though you'd get much better results blending smoothies at a higher setting

You might still have a smoothie, but it could be a hell of a lot better if you put it on a higher setting.

Same concept with Arma2. Why do I have to go into MSCONFIG, manually change from maximum ram to less than 8GB just to get the game to function properly? Same with the -winxp fix. Why drop your allotted amount of memory to less than 4GB with that option when you have 8GB?

Kind of a crappy work-around... I think it's an issue with the nVidia drivers myself. I had the 186somethings and had no problem with 8GB and was running everything just fine. I upgraded to the 190.38's and "BAM!" I got stuck with that 8GB no-texture issue.

I can totally sympathize with their frustration since BIS isn't conveying any validation of that issue or any steps to mitigate that problem with nVidia.

kklownboy
Sep 17 2009, 19:02
T...since BIS isn't conveying any validation of that issue or any steps to mitigate that problem with nVidia. why do you say that? The have even posted about it. But i'am not your google/ search guy, do your homework first.

Sniperdoc
Sep 17 2009, 19:26
If they acknowledged it, then I haven't seen any semblance of validation from BIS about the matter.

It seems to be a very large issue. If I was BIS, I'd be stickying that on the top of the forums. I'd put a sticky for BIS known issues, so that visitors don't HAVE to search.

I did and found nothing from any dev about acknowledging the issue and how they plan to resolve it.

About the homework comment, don't presume to know what I have and haven't done. I'm quite versed in the Advanced Search Maybe next time it won't make you look like an ass.

_Hurricane
Sep 17 2009, 23:42
Arma2.exe is a 32-bit application. Which means it won't use more than 2GB RAM whether or not you have 4GB or 8GB in total! Putting in the -winxp parameter fixes your problem and ArmA will still not use more than 2GB RAM!

BangTail
Sep 18 2009, 00:35
They're shelving the game because it's not functioning as it was intended to for them

Fixed that for you.

I have it running on 1 x 12 gig machine, 1 x 8 gig machine and 1 x 6 gig machine on Win 7 64.

No problems to report.

I realise this is frustrating for some people who can't get it working, but it is not universally applicable.

That is all,

Eth

Dwarden
Sep 18 2009, 01:30

OS builds
driver builds (GPU/soundcard)
mainboard model/chipset
GPU
audiocard
+ anything specially special :)

BangTail
Sep 18 2009, 02:05

OS builds
driver builds (GPU/soundcard)
mainboard model/chipset
GPU
audiocard
+ anything specially special :)

Np mate

Machine one is in my sig

Machine 2 is :

i7 940 @<hidden> stock
Gigabyte EX58 Extreme
8 GB Mushkin DDR3 1600
EVGA 285 Factory OC
Auzentech Home Theatre 1.3
Etc

Machine 3 is :

i7 920 @<hidden> 3.33
Gigabyte EX58 Extreme
6 GB Corsair DD3 1600
BFG 280 (Factory OC)
SB X-Fi gamer
Etc

All Win 7 64 (Retail - MSDN) (but worked well with XP 64 before)

Latest driver builds/BIOS on all boxes. Using -winxp & cpucount=4 on all boxes

Cheers

Eth

mlenser
Sep 18 2009, 05:28
They're shelving the game because it's not functioning as it was intended to.Adding these command line switches doesn't limit the game or make it run with less function than it was designed to do??? In fact it makes it run AS it was designed!

Why do I have to go into MSCONFIG, manually change from maximum ram to less than 8GB just to get the game to function properly? Never heard the need to edit MSCONFIG to run Arma2.exe - why do you do that when the command line switches fix the problem?
Same with the -winxp fix. Why drop your allotted amount of memory to less than 4GB with that option when you have 8GB?Adding the -winxp doesn't limit system memory in any way so what are you going on about?

Arma2.exe is a 32-bit application that cannot address more than 2047mb no matter how much ram your system has installed or what command line arguments you pass it. Doesn't matter if you use 32-bit or 64-bit OS, XP, Vista or Windows 7 it cannot use more than 2047mb on anyone's system - period.

About the homework comment, don't presume to know what I have and haven't done. I'm quite versed in the Advanced Search Maybe next time it won't make you look like an ass.From your own mouth.

shuurajou
Sep 18 2009, 10:49
Np mate

Machine one is in my sig

Machine 2 is :

i7 940 @<hidden> stock
Gigabyte EX58 Extreme
8 GB Mushkin DDR3 1600
EVGA 285 Factory OC
Auzentech Home Theatre 1.3
Etc

Machine 3 is :

i7 920 @<hidden> 3.33
Gigabyte EX58 Extreme
6 GB Corsair DD3 1600
BFG 280 (Factory OC)
SB X-Fi gamer
Etc

All Win 7 64 (Retail - MSDN) (but worked well with XP 64 before)

Latest driver builds/BIOS on all boxes. Using -winxp & cpucount=4 on all boxes

Cheers

Eth

So, with the -winxp command line argument, looking at your localVRAM parameter, it has correctly detected your video card memory on all machines? Might be useful to paste your localVRAM & nonlocalVRAM detected parameters for each machine.

Adding these command line switches doesn't limit the game or make it run with less function than it was designed to do??? In fact it makes it run AS it was designed!
Never heard the need to edit MSCONFIG to run Arma2.exe - why do you do that when the command line switches fix the problem?Adding the -winxp doesn't limit system memory in any way so what are you going on about?

The command line argument -winxp does not fix incorrect VRAM detection in the scenario of having 8GB+ RAM. On some setups it can change the VRAM detected so the game runs without graphical glitches but it still detects it incorrectly. MSCONFIG does help with this.

BangTail
Sep 18 2009, 11:17
So, with the -winxp command line argument, looking at your localVRAM parameter, it has correctly detected your video card memory on all machines? Might be useful to paste your localVRAM & nonlocalVRAM detected parameters for each machine.

Yup, detects the RAM correctly. It didn't detect properly with certain drivers (Although the game played fine - 186.xx's were a big culprit).

Eth

shuurajou
Sep 18 2009, 11:26
Yup, detects the RAM correctly. It didn't detect properly with certain drivers (Although the game played fine - 186.xx's were a big culprit).

Eth

For me I've found with or without the -winxp parameter, when using the BIS recommended NVIDIA drivers (e.g. latest) my VRAM is detected incorrectly (specifically VRAM, not RAM). Limiting to 4GB in MSCONFIG or removing 4GB resolves this detection issue for me.

datter
Sep 18 2009, 12:05
For me I've found with or without the -winxp parameter, when using the BIS recommended NVIDIA drivers (e.g. latest) my VRAM is detected incorrectly (specifically VRAM, not RAM). Limiting to 4GB in MSCONFIG or removing 4GB resolves this detection issue for me.

As said many times elsewhere, I've got exactly the same problem.

Sniperdoc
Sep 18 2009, 12:23
Yup, detects the RAM correctly. It didn't detect properly with certain drivers (Although the game played fine - 186.xx's were a big culprit).
My system ran fine with the 186.xx's. It was the 190.38's that caused me the 8GB problem. This was a brand new Win7 64-bit build. Why were the 186's so bad? I didn't really notice anything major? At least no different than the 190s using the MSCONFIG fix?

Adding these command line switches doesn't limit the game or make it run with less function than it was designed to do??? In fact it makes it run AS it was designed!

Never heard the need to edit MSCONFIG to run Arma2.exe - why do you do that when the command line switches fix the problem?Adding the -winxp doesn't limit system memory in any way so what are you going on about?
Using MSCONFIG is probably a bit more "natural" to the game. If they INTENDED for the game to run properly by running the switches, why didn't they just add the -winxp as a default startup? But instead you have to fudge with your system for hours, try to figure out how you can get it to do what it's supposed to, and then you shortcut yourself by running -winxp.

Arma2.exe is a 32-bit application that cannot address more than 2047mb no matter how much ram your system has installed or what command line arguments you pass it. Doesn't matter if you use 32-bit or 64-bit OS, XP, Vista or Windows 7 it cannot use more than 2047mb on anyone's system - period.
Really? That's strange, because I thought there wasn't any limitation at all...??? Actually, just to educate you a bit. It's all dependent on how the application was programmed to run with the OS and how the OS was programmed to handle memory addressing.

Just because something is a 32-bit application does NOT mean it is limited to 2048MB of RAM. For example:

Windows Server 2008 Enterprise 32-bit can address up to 64GB of memory.
Windows Server 2003 Enterprise 32-bit can address up to 64GB of memory.

So, going on from there, if you'd run a program such as MS SQL Server, you'd really benefit from using as much of the 64GB of memory as possible. But again, SQL server was written to address that much memory.

Now, I have yet to see a post by a BIS developer stating that Arma 2 was built to run with only 2048GB of memory. If that is the case, once again, why did they not hardcode the -maxmem=2047 switch right into game. I'll tell you why... it addresses more than just 2047MB. Whether they implemented a good detection algorithm or not is another matter. 32-bit applications, by physical limitations of hardware, are limited to 4GB of memory, per process... not 2. [more patronization]Just FYI, Arma.exe would be considered a process.[/more patronization]

Fact of the matter is, there's a problem with Arma 2 and the video drivers and it's up to BIS to get a dialog started with nVidia/ATI to figure out how to resolve this issue as I think it is causing a lot of the performance issues.

I had no texture or LOD issues running the drivers before 190.38. It wasn't until I used the 190.38 drivers that the LOD/Texture problems started showing up. It is all dependent on how the drivers decide to offload memory requirements to non-VRAM memory. I use driver and registry cleaners when I install drivers, so I know it's a clean system. I've been working with computers for 17+ years and it's what I do for a living.

I'm really saddened by the fact that in Arma 1, the game had inherent flaws with LOD and texturing that was never really resolved and now here we have this "improved" Arma 2, that supposedly has been made better, and those same LOD and texturing flaws have carried over. Personally, I think it's a huge slap in the customer's face that they didn't address that issue.

Running this on a system like mine, Frame rate, LOD and textures should not be an issue.

Although it does seem that 1.04 did clear up some frame rate issues, because it doesn't seem to react as slowly going left to right and vice versa. On my system it looks as if motion blur was reduced a bit? I hadn't checked if my Arma 2 configuration settings have been changed due to the latest update.

Desert
Sep 18 2009, 12:46
If they acknowledged it, then I haven't seen any semblance of validation from BIS about the matter.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:

Sniperdoc
Sep 18 2009, 14:52
I've seen that several times... but it isn't a validation of what the problem is about and what could be causing it. They've also not written anything about how they're wanting to address it.

I agree with you though... I don't think they know HOW to fix it since that problem has been there since Arma 1. :(

shuurajou
Sep 18 2009, 15:09
Dissapointingly I've had a ticket open with IDEA games (publisher and our 'official' way to get support) since the 28th of August and I was told today that they recommend I return the game for a refund. This is after quite a lot of time providing dxdiag, specs etc to help them pass the issue onto BIS to troubleshoot and being told it was passed onto the developers... doesn't fill me with confidence this is going to get fixed if the publisher is telling users to get refunds.

Sniperdoc
Sep 18 2009, 15:26
DANG!!! How about that being a slap in the face. Funny... cause if you get/got it through Steam... forget the refund. Sounds like finger pointing to me.

"It's not our problem, go to the retailer."

Sucks if the retailers have a "no refund" policy. Pretty much only Walmart will let you get refunds on software.

shuurajou
Sep 18 2009, 15:47
Coincidentally I bought mine on steam.

The publisher did say they are apparently working on it but it's not easy to fix.

datter
Sep 18 2009, 16:02
I wonder why this is an issue for ArmA and ArmA2 but not for any other game I've ever heard of?

Desert
Sep 18 2009, 17:17
In ArmA1 this is fixed already.

I've seen that several times... but it isn't a validation of what the problem is about and what could be causing it. They've also not written anything about how they're wanting to address it.

I agree with you though... I don't think they know HOW to fix it since that problem has been there since Arma 1. :(Look closely, the VRAM Detection is the Problem. It happens when the VRAM goes over the 2GB Mark, like Suma said. ;)

Sniperdoc
Sep 18 2009, 18:14
Well, I understand the issue... that's the problem here. The problem is that I don't even know if they've taken this up with nVidia at all. I had no issues when I was running 186 drivers. Once I switched to the 190s is when the problem cropped up. That leads me to believe that Arma 2 does not play well with driver changes. So, we need to narrow down where the disconnect is here. Not just the VRAM detection, but how it detects the VRAM and how it decides to assign a certain value to that VRAM variable. I'm sure that the drivers themselves play a role in that.

datter
Sep 18 2009, 18:18
I had no issues with 190.38 when I had Win XP 32bit and 2gb. It was when I moved to Win7 64bit and 8gb plus the 190.38's that this problem cropped up. I suspect it might be something more than just the drivers... but whatever it is, I hope it gets fixed eventually.

willgimmence
Sep 18 2009, 20:26
Well, I understand the issue... that's the problem here. The problem is that I don't even know if they've taken this up with nVidia at all. I had no issues when I was running 186 drivers. Once I switched to the 190s is when the problem cropped up. That leads me to believe that Arma 2 does not play well with driver changes. So, we need to narrow down where the disconnect is here. Not just the VRAM detection, but how it detects the VRAM and how it decides to assign a certain value to that VRAM variable. I'm sure that the drivers themselves play a role in that.

I have an ATI 4870 1GB and am having the same problems so I don't think contacting nvidia is the answer :) It is something arma 2 developers need to sort out!

Sniperdoc
Sep 18 2009, 20:36
Well... it has to do with how it addresses memory at 8GB and above. I still see this issue with Arma 1. At least the texture/LOD issue. So... it's a problem that's persisted since Arma 1. I'm very perturbed this issue is still around as they've hand ample time to resolve this.

@<hidden>:
Absolutely, sorry didn't mean to infer it was purely nvidia related. I just personalized the issue since I have two GTX280's.

datter
Sep 18 2009, 23:04
... since I have two GTX280's.

I've often thought that might have something to do with it as well. I have dual 8800GT's. Maybe it's 8gb + SLI?

Sniperdoc
Sep 19 2009, 01:22
I tried it without SLI turned on first. I've tried several combinations:

No SLI with PhysX
No SLI without PhysX
SLI with PhysX
SLI without PhysX

Pretty much same results concerning the LOD/Texture issues.

kklownboy
Sep 19 2009, 02:05
Sli or not IN SLi wont make the OS behave any different in how it allocates virtual ram for each device. The real test on the dual cards and 8GB would be to pull one to see if it makes a difference... Not that you want to play with only one card... but just to see if it is a dual card issue for you NVDA guys. There was a 4GB+ issue with ATI and A1 with the 1.14 patch, it was when Bis did there so called virtual Address space hack for 32bit Os's. It borked ATi cards, but to be fair there was also a fragmentation issue with GDDR5 at the same time, both where fixed in 1.16beta, and a new driver. But nvda users have posted they then had issues... And it seems the whole RAM problem has now been pushed out to 8gb on non i7/x58 platforms.... i blame the hack, 32bit OS's and NVDA.

Bulldogs
Sep 19 2009, 02:28
Is the problem only apparent on Vista 64bit and Windows 7 64bit or is it effecting Windows XP, and Vista 32bit/Win7 32bit as well?

mlenser
Sep 19 2009, 04:57
Is the problem only apparent on Vista 64bit and Windows 7 64bit or is it effecting Windows XP, and Vista 32bit/Win7 32bit as well?I would think that because 32-bit OS's cannot even address more than a little over 3gb? even when more ram is installed then they shouldn't be effected. My 32-bit XP reports only 3gb ram and has done so while having 4gb and now 6gb installed.

_Hurricane
Sep 19 2009, 18:11
I've often thought that might have something to do with it as well. I have dual 8800GT's. Maybe it's 8gb + SLI?

Don't think so as I had the problem too when I installed an extra 4GB RAM last week (now 8GB total). I fixed the issues with the -winxp parameter though.

Sniperdoc
Sep 21 2009, 13:02
I would think that because 32-bit OS's cannot even address more than a little over 3gb? even when more ram is installed then they shouldn't be effected. My 32-bit XP reports only 3gb ram and has done so while having 4gb and now 6gb installed.

Just curious... Are you using 6GB with a 32-bit OS because you have a dual boot system? I would consider it a huge waste if you're not dual booting or running an OS that can address the 6GB.

mlenser
Sep 22 2009, 04:59
Just curious... Are you using 6GB with a 32-bit OS because you have a dual boot system? I would consider it a huge waste if you're not dual booting or running an OS that can address the 6GB.Yeah I found that out the hard way some time back when I upgraded my 32-bit Xp from 2gb to 4gb and only could use 3gb. When I recently upgraded my CPU, MB and Ram I also went dual boot with Windows 7 64-bit. I can't say I've seen any apps really use much of that ram yet but then as its the trial pre release of Windows 7 which will stop working in 5 months so I haven't installed many apps that will really benefit from the extra ram. I figure I'll wait until after October 22(?) for the full version to go on sale before I spend a lot of effort installing all the big apps again. I am personally getting better speeds with Arma 2 in 32-bit XP over 64-bit Windows 7 so the dual boot will stay for some time I guess.

Sniperdoc
Sep 22 2009, 20:02
Hehehe... I'm ready for my reformat :) All of my Steam games sit on a separate drive. So, once I reformat the OS with the retail Win7 I'll just need to install the Steam to the same location and viola! All my games will be ready to rock and roll.

I just have to remember to copy over the MY DOCs folder that sits on the C drive. For some reason, even though I redirected my Documents folder to the other drive, some programs and games didn't see that as a proper location and still put savegame and config files in C:\users\%username%\documents folder...? Probably a 7100 build bug of some type, cause it worked fine in Vista and XP.

lupomax
Sep 22 2009, 20:21
Hi all,
my configurations is this:

CPU: Intel Q9550 @<hidden> 2.8 GHz
Mobo: Intel X48
Ram: 8 GB DDR3 @<hidden> 1066
Video: Asus Nvidia EN260 GTX - Driver 190.62
HDD: 4X500GB SataII Raid 10 on 3Ware 9650S

O.S. Win7 64 - DX 11 Update Aug.2009

I can confirm that there are problem with texture on terrain, vehicles and bodies!!!
I hope there will be soon a fix, even because, it was a very bad surprise see that :(

Bye bye

InFireBaptize
Sep 22 2009, 20:38
can someone tell me why is it freaking hard to code for a computer with 8-12GB of memory? I know it's 32 bit application but in PR you can modify the exe with LAA through EDITBIN to make it work, why we can't do the same thing with ArmA2? My ArmA1 still CTD after the latest patch, what a fiasco!

lupomax
Sep 22 2009, 20:48
Hi all,
my configurations is this:

CPU: Intel Q9550 @<hidden> 2.8 GHz
Mobo: Intel X48
Ram: 8 GB DDR3 @<hidden> 1066
Video: Asus Nvidia EN260 GTX - Driver 190.62
HDD: 4X500GB SataII Raid 10 on 3Ware 9650S

O.S. Win7 64 - DX 11 Update Aug.2009

I can confirm that there are problem with texture on terrain, vehicles and bodies!!!
I hope there will be soon a fix, even because, it was a very bad surprise see that :(

Bye bye

OK Now, i've Found a fix.
Use the option "-winxp" to launch the arma2.exe file, and everything will be fine!

Have a good time!

tomcatfp
Sep 24 2009, 03:31
It's something with the Nvidia 190.XX and above drivers. I went back and installed the 186.18 and everything worked perfectly. Something Nvidia changed in their 190 drivers is causing the texture issue

SimonK
Sep 26 2009, 09:55
SOLVED

I'm having this error too! Dammit, these are my config specs:
SO: Windows 7 Ultimate x64 (Build 7600)
Processor: Intel Core 2 Quad Q9550 2,8 GHz
VGA: Nvidia GeForce 9800 GX2 1 GB (SLI)
RAM: 8 GB (4x2Gb, Kingmax @<hidden> MHz)
Motherboard: Asus P5K-SE @<hidden> bus

What is the problem? I have the original game, so I'm going to tell you the high requirments:
CPU: Quad Core 2,8 GHz (ok)
RAM: 2 Gb (ok)
Video: Nvidia GeForce 8800 GT SM3 512 MB (ok)
OS: XP or Vista (I don't think the problem could be Windows 7)

Maybe the problem is that I have 64-bit Windows 7 edition?
I dunno, I tried all the game settings, low settings too. No way, the strange no-texture buildings, ugly character models and all the rest have ugly textures. My video-card is fast enough, but that's not the problem: in this thread there are users with GTX 2xx in SLI, so I REALLY DON'T THINK THE PROBLEM IS THE VGA. Maybe the problem is the engine... I'm gonna buying Operation Flashpoint 2, the graphics are not so good as ArmA 2 but it works 100%...

---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------

It's something with the Nvidia 190.XX and above drivers. I went back and installed the 186.18 and everything worked perfectly. Something Nvidia changed in their 190 drivers is causing the texture issue

My cousin has an ATI HD 4870 GDDR5 2 GB and he's having this error too! So I don't think is "Nvidia" or "ATI" or other vga manufacturer the problem here! :(

datter
Sep 26 2009, 13:13
Adding the -winxp switch will likely sort you out, though there is no guarantee it will fix it properly. That might correct your odd graphics, but chances are it's still going to detect your video ram incorrectly as you have 8gb of system ram.

Add -winxp to the shortcut and see how it goes. It will likely be an improvement, if not a complete fix.

SimonK
Sep 27 2009, 08:36
Adding the -winxp switch will likely sort you out, though there is no guarantee it will fix it properly. That might correct your odd graphics, but chances are it's still going to detect your video ram incorrectly as you have 8gb of system ram.

Add -winxp to the shortcut and see how it goes. It will likely be an improvement, if not a complete fix.

It worked! But why? I mean, why the game doesn't make the shortcut adding "-winxp" automatically? If you're on XP the "-winxp" will not change anything, if you're on Vista/7 it will let you play fine!

Thanks anyway! This game's great, I putted all to Very High on 1400x900 @<hidden> Hz, it rocks! :) The only thing missing is the AntiAliasing :( ...

That's what I did:
Installing last Nvidia drivers, Installing the Nvidia SLI update (xml) and adding "-winxp" to the shortcut launch parameters...

... but chances are it's still going to detect your video ram incorrectly as you have 8gb of system ram ...

What does that mean? The game uses 4 Gb of RAM and not all 8 Gb? I hope it supports SLI, then! XD

Kunda
Sep 27 2009, 09:14
I post this tomorrow until i finally saw this topic!
Now i give a try adding -winxp- string and let you know.
This is really strange, why 8gb Ram can do this?

Goodmorning guys!
Love Arma II but i choose to take a break from the game for almost two months.
Yesterday I finally have the right time to invest in the game, dowloaded the latest patch (1.04) and the 191.03 driver for my Nvida Geforce 9800.

So, with a grin on my face i double click on the game's icon and launch ArmaII.

With my horror what i see is not what i saw the last time i run the game. Until yesterday my ArmaII work very well, almost everythings on high and 30 solid FPS (except in some very small area on the map) but now the graphics look all messed out, there's not texture and everything look like... cell shaded!

Here some examples:
http://i37.tinypic.com/34sm2xl.jpg

Killer7: ArmaII

http://i34.tinypic.com/2pzct4p.jpg

I try to reinstall the game and put only 1.3 patch but the problem persist.

Other games on my HD like The Witcher and Empire Total War work really well, especially now with 4 more gb of ram (this is the only difference on my rig made after the long break with the game)

This is my spec:
Geforce 9800 1gb
8Gb Ram
Vista Ultimate 64

SimonK
Sep 27 2009, 12:25
I post this tomorrow until i finally saw this topic!
Now i give a try adding -winxp- string and let you know.
This is really strange, why 8gb Ram can do this?

Is the engine's fault. It doesn't support 64-bit systems, so more than 4 Gb of RAM. Or maybe it just tries to support them but there are these strange errors and bugs. Let me help you:
Add the "-winxp" string to the shortcut then ArmA 2 will run perfectly 100%, I was having this error too. I fixed it just 6 hours ago following the "datter" user's suggestion. Of course, now it uses only 4 Gb of RAM, but it's working fine. Maybe if it was using 8 Gb of RAM the FPS would arrive to 50-60, but I'm playing it at 35-40 FPS and I love the graphics. The human eye can perceive 18 FPS, the rest is just "precautionary" ... ;)

PS These are your screenshots? Are you italian? No, I'm asking cuz I'm italian and I saw the words like "Cosa?" that's "What?"... xD

Kunda
Sep 27 2009, 17:43
Yeah, with the string "-winxp" the game run perfectly.

SimonK the pics are mine, i'm italian too. :yay:

Desert
Sep 27 2009, 21:55
It worked! But why? I mean, why the game doesn't make the shortcut adding "-winxp" automatically? If you're on XP the "-winxp" will not change anything, if you're on Vista/7 it will let you play fine!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.

SimonK
Sep 28 2009, 14:02
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.

Thank you for answering. I know that ArmA 2 uses a different Rendering Pipeline but I didn't know this "-winxp" string can resolve one of the most discussed and annoying problem in the world! XD

Now that I'm thinking on this error, a lot of games requires strings like this: Gmod for the console and the applaunch (steam), Prototype for the language (yes, I was adding the lang string to the shortcut, but then I discovered the key in the registry and modified it! XD)... But I'm sure a thing: I can play ArmA 2 now and I love the graphics and the gameplay. Thank you all so much!!! :)

---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------

Yeah, with the string "-winxp" the game run perfectly.

SimonK the pics are mine, i'm italian too. :yay:

What a mess.. emh.. cioé che strana cosa trovare un italiano qui, tutti visitano il forum Bohemia e trovare un italiano tra tutti gli utenti è come cercare un ago in un pagliaglio! xD

^ This was the italian shit, sorry ^

Sniperdoc
Sep 29 2009, 13:57
Well, for me when I ran the -winxp switch the game DISPLAYED properly... but performance was worse. So, the one way I resolved this issue was to use Windows' MSCONFIG function and lower the maximum ram just a hair below 8GB. Someone listed the actual number to use somewhere near the beginning of the thread. This way I get the fixed LOD/Texture issues AND it'll perform fine too.

Liquidpinky
Sep 29 2009, 14:08
Well, for me when I ran the -winxp switch the game DISPLAYED properly... but performance was worse. So, the one way I resolved this issue was to use Windows' MSCONFIG function and lower the maximum ram just a hair below 8GB. Someone listed the actual number to use somewhere near the beginning of the thread. This way I get the fixed LOD/Texture issues AND it'll perform fine too.

Just out of interest what sort of increase did you get?
I am running pretty similar rig using the -winxp command.
Specs: QX9650@<hidden> 1337 FSB(couldn't help myself) 2xGTX285 and 8gb RAM. OS is Vista 64bit.

Sniperdoc
Sep 29 2009, 14:11
Overall smoothness of gameplay. When I used the -winxp it was very choppy. Going to the msconfig solution appeared to resolve that issue. Best way I can explain it, the game would run smooth for 1-3 seconds, and freeze for 1/2 a second, then smooth for 1-3 seconds and freeze for 1/2 a second, such and so forth.

kmconstable
Sep 29 2009, 16:35
I am not sure I understand the -winxp command thing. I need a step by step to understand this. Do I just add -winxp to the wording of the .exe by clicking on it until I can type or do I have to open something else on the .exe to modify it. Thanks for any response.

kklownboy
Sep 29 2009, 17:04
I am not sure I understand the -winxp command thing. I need a step by step to understand this. Do I just add -winxp to the wording of the .exe by clicking on it until I can type or do I have to open something else on the .exe to modify it. Thanks for any response. Make a shortcut. Then put in the parameters.If dont know what shortcut is go google.

"C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2.exe" -mod=beta -nosplash -maxmem=2047
"C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -winxp

allways a space between the commands,arguments

Sniperdoc
Sep 29 2009, 17:42
Just to be clear. Use the other switches such as:

-mod=
-nosplash
-maxmem=

if you want to use those features. You do not have to use them. The -nosplash is fine because it removes the splash screens when Arma2 starts.

So, in this case, if you have a shortcut to Arma2 on your desktop you can:
Right-click it
Go to Properties
For TARGET put the switch after the quotes with a space

So, in my case it'd be:

Hope that helps

astral54r
Oct 5 2009, 06:38
Same problem, :(
q6600(3.0), 8gb ddr2(800), 8800gt 512(190.62), Win7x64(7600_retail)

arma2.exe -nosplash -mod=beta -cpucount=4 -profiles=profiles -showScriptErrors

Liquidpinky
Oct 5 2009, 09:28
Same problem, :(
q6600(3.0), 8gb ddr2(800), 8800gt 512(190.62), Win7x64(7600_retail)

arma2.exe -nosplash -mod=beta -cpucount=4 -profiles=profiles -showScriptErrors

Either add in -winxp to the list or edit you available RAM in msconfig to be lower than 8gb. Then you will get your textures showing up.