ArmA2 8GB RAM Problem

[Dwarden 1125]

datter what size of VRAM is each 880GT and are you running it in SLI or non SLI ?

[datter 0]

datter what size of VRAM is each 880GT and are you running it in SLI or non SLI ?

Vram on each card is 512mb, and running in SLI. From what I understand it should be seeing all the vram on one card in this configuration... so the full 512, which it did prior to going to 8gb.

[W1NDOWL1CKER 10]

Post your arma2.cfg mate.

Hi.

Here is a copy of my arma2.cfg:

language="English";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1080;

refresh=60;

Render_W=1920;

Render_H=1080;

FSAA=3;

postFX=1;

HDRPrecision=8;

lastDeviceId="";

localVRAM=2139478016;

nonlocalVRAM=2139478016;

Can you help me with this?

[kklownboy 43]

ok first off is your shortcut set up to USE the beta; "C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2.exe" -mod=beta

I can see you dont have the;

GPU_DetectedFramesAhead="";

GPU_MaxFramesAhead="";

in your CFG?

On a side note try using HDRPrecision=32;

High AA is kind of a killer on the frames.

[BrunoDerRabe 0]

@ BIS: YOU ARE THE REAL CODEMASTERS

_________________________________

ok first off is your shortcut set up to USE the beta; "C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2.exe" -mod=beta

I can see you dont have the;

GPU_DetectedFramesAhead="";

GPU_MaxFramesAhead="";

in your CFG?

On a side note try using HDRPrecision=32;

High AA is kind of a killer on the frames.

Using Vista or Windows 7 you might need to change the compability setting in the files properties (right click on the file opens context menue ) for the BETA ArmA2.exe (file location: *:\*\ArmA 2\beta) to run it always as administrator.

If you fail to do this and you start the game via the BETA Shortcut ( you will find it in the game mainfolder ), you might still run the standard 1.04 patched version of the game.

If you don´t see the version number *59928 when you start the game you are NOT running the latest Beta Patch and you can´t judge on it. Result would be wrong info for the lads working on this issue. Please doublecheck.

__________________

Here my results BETAPATCH 59928:

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=2400;

Render_H=1500;

FSAA=4;

postFX=0;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=2147483647;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

__________________

AMD Phenom II 940 BE @ 3.00 Ghz 8MB Cache (2MB L2 und 6MB L3)

A-DATA DIMM 4 GB DDR2-1066 (Vitesta Extreme Edition) 2x = 8GB

Asrock K10N780SLIX3-WiFi

MAXTOR STM31000340AS ATA Device

2x 260GTX or 3x 260GTX club SLI profile 6975

Cooler Master RealPower Pro 1250W (9x PCIe, black)

Acer P241w 1920 x 1200

Windows 7 Ultimate X64

__________________

This was new after I had Windows 7 64 installed (via Upgrade)

Quote my SYSTEM:

Installed memory (RAM): 8GB (6,5 GB usable)

fixed:

Just checked the 6,5GB issue on my rig,,,, caused by an old msconfig setting I did use on Vista 64 before I removed 4 of the 8 Gb RAM lol

(because of the 8GB bug in ArmAII)

So the Upgrade to Windows 7 accepted this (hidden) setting and was using it, after I added the 4 GB again to do the testing last night :-) .... look at the quote. Did remove the setting via msconfig, now everything is as it should be.

Edited November 10, 2009 by BrunoDerRabe

[W1NDOWL1CKER 10]

ok first off is your shortcut set up to USE the beta; "C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2.exe" -mod=beta

I can see you dont have the;

GPU_DetectedFramesAhead="";

GPU_MaxFramesAhead="";

in your CFG?

On a side note try using HDRPrecision=32;

High AA is kind of a killer on the frames.

Hi kklownboy.

How do I get these GPU_DetectedFramesAhead=""; and

GPU_MaxFramesAhead=""; into my .cfg?

Thanks for trying to help.

---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------

@kklownboy:

By the way I tried the -mod=beta command, got an error and the game would not start...

Edited November 6, 2009 by W1NDOWL1CKER
wrong spelling

[W1NDOWL1CKER 10]

THANKS!!!!!!!!!!!!!

@BrunoDerRabe:

Thank you for your support through private messaging man.

The beta patch now works fine, framerate approx. 6-15 fps higher with everything on highest settings, running smoothly!!!

Thanks a lot for your effort mate.

Also a big Thank You to Liquidpinky, Kju and kklownboy.

It's nice to know that there are people on this forum who really try to help.

Edited November 7, 2009 by W1NDOWL1CKER
mention higher framerate

[Falke1976 10]

Good evening gentlemen,

download that beta release now,

if i understood it right, i need to adjust my shortcut and set the beta.exe as administrator runed?

language="English";
adapter=-1;
3D_Performance=46875;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=1920;
Render_H=1200;
FSAA=1;
postFX=2;
HDRPrecision=8;
lastDeviceId="";
localVRAM=2137714688;
nonlocalVRAM=2137714688;

this is my prepatch config.

Running in -winxp as i now do is quite horrible 5-10 fps...

ill edit this post when i tried it again.

Here we go,

patched to 59928, set arma2.exe to start as admin, changed shortcut to -mod=beta

and getting an error box:

Error compiling pixel shader PSSSSMSpecularAlpha:1

config file after patch

language="English";
adapter=-1;
3D_Performance=93750;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=1440;
Render_H=900;
FSAA=2;
postFX=2;
HDRPrecision=8;
lastDeviceId="";
localVRAM=4386816;
nonlocalVRAM=4386816;

MSI K9N2 Diamond, Phenom I X4 9850, 8 GB Ram PC 6400, Asus ENGTX285, X-Fi Extreme Audio PCIe, Windows 7 Ultimate 64

Edited November 7, 2009 by Falke1976

[Deadfast 43]

Post the 'Path' and 'Start in' lines from your shortcut.

[Falke1976 10]

hah, got it sir....

forgot to add "beta",

now it is:

"F:\Program Files (x86)\Bohemia Interactive\ArmA 2\beta\arma2.exe" -mod=beta

and

"f:\Program Files (x86)\Bohemia Interactive\ArmA 2"

which nvidia driver is recommended? i am on beta 195.39 now but 59928 does not seem to work for me :S

---------- Post added at 06:04 PM ---------- Previous post was at 05:22 PM ----------

It works works

Dunno why, think i misunderstood my own shortcuts ^^

So any advice for pimping my config?

language="English";
adapter=-1;
3D_Performance=93750;
Resolution_Bpp=32;
Resolution_W=1920;
Resolution_H=1200;
refresh=60;
Render_W=1920;
Render_H=1200;
FSAA=2;
postFX=2;
HDRPrecision=8;
lastDeviceId="";
localVRAM=1054539776;
nonlocalVRAM=2147483647;
GPU_DetectedFramesAhead="0";
GPU_MaxFramesAhead="0";

Edited November 7, 2009 by Falke1976

[cross 1]

Great information. I am adjusting the VRAM heuristics to handle your situation better (revision 59949). The problem was when you have really lot of RAM and only 512 MB or less of VRAM. I think even with the values detected above the game should work quite well, still I guess fixing it will only make it better.

Hey Suma...

With the BetaPatch 60000, Arma recognizes the VRam properly on my Win7x64 + 6GB RAM + 8800 GTS 512k rig.

GJ

3D_Performance=-4194304;
Resolution_Bpp=32;
Resolution_W=1680;
Resolution_H=1050;
refresh=60;
Render_W=1680;
Render_H=1050;
FSAA=0;
postFX=1;
HDRPrecision=32;
lastDeviceId="";
localVRAM=519634944;
nonlocalVRAM=2147483647;

[themaster303 22]

hi suma.

i still have the problem with crashing. before it was around 1.2 GB (beta59924) ram-usage. now its between 1.3 GB and 1.4 GB ram usage (beta6000).

i have to look all the time on my second monitor to look and type "shift"+"-" and flush before it reaches the values pointed before it crashes.

think there is still someting wrong. i also tryed -maxmem. nvidia driver 191.07

is used.

thx for help and the best game ever, even when it crashes ;)

-------------------------------------------------------------------------

Microsoft Windows Vista Ultimate 6.1.7600

Motherboard:

QuadCore Intel Core 2 Quad Q9550, 3400 MHz (8.5 x 400)

Gigabyte GA-X48-DS5 (2 PCI, 3 PCI-E x1, 2 PCI-E x16, 4 DDR2 DIMM, Audio, Gigabit LAN, IEEE-1394)

Motherboard Chipsatz: Intel Beachwood X48

Arbeitsspeicher: 8192 MB (DDR2-1066 DDR2)

Grafikkarte: NVIDIA GeForce GTX 295 (896 MB)

3D-Beschleuniger nVIDIA GT200-400

Monitor Samsung SyncMaster 245B/245BW (Digital) [24" LCD] (HS1PC05185)

Multimedia: Soundkarte Creative SB X-Fi XtremeMusic/Platinum Sound Card

------------------------------------------------------------------------

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=1920;

Render_H=1200;

FSAA=0;

postFX=1;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=2147483647;

-----------------------------------------------------------------------

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: arma2.exe

Anwendungsversion: 1.4.0.60000

Anwendungszeitstempel: 4af2b01b

Fehlermodulname: arma2.exe

Fehlermodulversion: 1.4.0.60000

Fehlermodulzeitstempel: 4af2b01b

Ausnahmecode: c0000005

Ausnahmeoffset: 0062309a

Betriebsystemversion: 6.1.7600.2.0.0.256.1

Gebietsschema-ID: 1031

Zusatzinformation 1: 0a9e

Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789

Zusatzinformation 3: 0a9e

Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789

Edited November 9, 2009 by themaster303

[Dwarden 1125]

i suggest You try upgrade to 195.xx beta drivers from NVIDIA ...

there are some irks in 191.xx

btw. anyone with dual/triple/quad SLI tried yet 60k build ?

[DOA 20]

i suggest You try upgrade to 195.xx beta drivers from NVIDIA ...

there are some irks in 191.xx

btw. anyone with dual/triple/quad SLI tried yet 60k build ?

I am stuck at work until 5 PM EST (GMT-5) I will be trying beta 6000 when I get home tonight. I'm running ArmA 2 on an Alienware Area 51 X58 Wartime PC.

Dual Quad Core I7 3.06 GHZ, 12 Gigs RAM, Dual nVIDIA GTX 250 overclocked version in SLi mode, Win7 64 bit OS.

My issue is that since upgrading to Win 7 (11/07/2009) ArmA2 runs and looks great for a few minutes then frame rate starts to drop, graphics start to white a little and then Crash to desktop. I'm sure this is the too much RAM issue. I am hopeful that the beta 6000 will resolve this issue. I will post results here as soon as possible. Thanks.

Edit: I forgot to mention I will try the 195 beta drivers also.

[BrunoDerRabe 0]

i suggest You try upgrade to 195.xx beta drivers from NVIDIA ...

there are some irks in 191.xx

btw. anyone with dual/triple/quad SLI tried yet 60k build ?

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

Will do this later tonite [ have to grab the other pair of RAM (4GB) from my second PC and add it to the SLI PC. Will post the results here.

Edited November 9, 2009 by BrunoDerRabe

[Dwarden 1125]

ok try it also with just the 4GB for sure ... (if it caused before any issues)

[BrunoDerRabe 0]

4GB and 8GB with NVIDIA 191.07 and 8GB with NVIDIA Beta 195.39 are having no issues with beta 6000 running on 2x260GTX in SLI mode

3829 DISTANCE OF VIEW, POST PROCESSING OFF, EVERYTHING ELSE MAXED OUT

4GB

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=2400;

Render_H=1500;

FSAA=4;

postFX=0;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=1878618112;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

8GB

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=2400;

Render_H=1500;

FSAA=4;

postFX=0;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=2147483647;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

More good news:

the new beta 6000 in combination with the new beta driver from NVIDIA BETA 195.39 and 8GB RAM make things even better as there was an issue with the postprocessing in the past

3829 DISTANCE OF VIEW, EVERYTHING MAXED OUT

language="German";

adapter=-1;

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=919994368;

nonlocalVRAM=2147483647;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

__________________

AMD Phenom II 940 BE @ 3.00 Ghz 8MB Cache (2MB L2 und 6MB L3)

A-DATA DIMM 4 GB DDR2-1066 (Vitesta Extreme Edition) 2x = 8GB

Asrock K10N780SLIX3-WiFi

MAXTOR STM31000340AS ATA Device

2x 260GTX or 3x 260GTX club SLI profile 6975

Cooler Master RealPower Pro 1250W (9x PCIe, black)

Acer P241w 1920 x 1200

Windows 7 Ultimate X64

__________________

tested while hosting a multiplayer games with the map - Tschernarussland Mission #3 [bLUEFOR/ slot 2 - LMG-gunner (always new game) 50 playerslots/PROFI ]

Edited November 10, 2009 by BrunoDerRabe

[themaster303 22]

4GB and 8GB with NVIDIA 191.07 and 8GB with NVIDIA Beta 195.39 are having no issues with beta 6000 running on 2x260GTX in SLI mode

3829 DISTANCE OF VIEW, POST PROCESSING OFF, EVERYTHING ELSE MAXED OUT

4GB

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=2400;

Render_H=1500;

FSAA=4;

postFX=0;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=1878618112;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

8GB

language="German";

adapter=-1;

3D_Performance=93750;

Resolution_Bpp=32;

Resolution_W=1920;

Resolution_H=1200;

refresh=60;

Render_W=2400;

Render_H=1500;

FSAA=4;

postFX=0;

HDRPrecision=8;

lastDeviceId="";

localVRAM=919994368;

nonlocalVRAM=2147483647;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

More good news:

the new beta 6000 in combination with the new beta driver from NVIDIA BETA 195.39 and 8GB RAM make things even better as there was an issue with the postprocessing in the past

3829 DISTANCE OF VIEW, EVERYTHING MAXED OUT

language="German";

adapter=-1;

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=919994368;

nonlocalVRAM=2147483647;

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=3;

__________________

AMD Phenom II 940 BE @ 3.00 Ghz 8MB Cache (2MB L2 und 6MB L3)

A-DATA DIMM 4 GB DDR2-1066 (Vitesta Extreme Edition) 2x = 8GB

Asrock K10N780SLIX3-WiFi

MAXTOR STM31000340AS ATA Device

2x 260GTX or 3x 260GTX club SLI profile 6975

Cooler Master RealPower Pro 1250W (9x PCIe, black)

Acer P241w 1920 x 1200

Windows 7 Ultimate X64

__________________

tested while hosting a multiplayer games with the map - Tschernarussland Mission #3 [bLUEFOR/ slot 2 - LMG-gunner (always new game) 50 playerslots/PROFI ]

for how long did you test ? please try to fly over the whole island Tschernarussland and watch the ram is used (in taskmanager). the ram-usage

is going to be higher and higher, when it reaches 1.4 GB it crashed on my sys.

its takes about 10-15 min to fill up ramusage by flying over island and BIG towns. viewdistance was 4600m on my rig. rest of my rig see my last post.

would be nice if you try this, so i have a reference. big thx to you !!

greetz

the masty

[DOA 20]

Beta 6000 .exe works for me in Sli. with no switches or limiting RAM in msconfig etc. :)

Also: My 12 gig RAM issue seems to be resolved by adding these switches to the current public .exe: -winxp -nosplash -world=empty -maxmem=2047 -cpuCount=2

I run the same switches with the Beta .exe and I pick up about 5 FPS. I have not loaded the nVIDIA beta 195.x drivers yet. I get smooth play and average 25 - 30 FPS with view distance ~3250 M.

I have played for about an hour with no crash but I did not fly all over the island I was on foot most of the time. I will try flying all over the island and report back if I have any issues.

Thanks!

System specs:

Alienware Area-51® X58 Wartime

Processor: Intel® Core™ i7-950 3.06 GHz 8MB Cache

Alienware P2 Chassis: Alienware® P2 Chassis with AlienIce™ 3.0 Video Cooling

Alienware P2 Chassis Upgrades: Alienware® Approved CPU Liquid Cooling

Power Supply: Alienware® 1000 Watt Multi-GPU Approved Power Supply

Graphics Processor: Dual 512MB NVIDIA® GeForce® GTS 250 -Superclocked Edition - SLI Enabled

Video Optimizer: AlienAdrenaline v1.0: Video Performance Optimizer - More Info

Memory: 12GB DDR3 SDRAM at 1333MHz - 6 x 2048MB

Motherboard: Alienware® Approved Intel® X-58 Motherboard- Socket 1366 Core i7 Ready, Dual Triple Channel DDR3 Memory

Operating System: Windows 7 Ultimate

System Drive: Single Drive Configuration - 750GB SATA 3Gb/s 7,200RPM 16MB Cache

Sound Card: High-Definition 7.1 Performance Audio

Keyboard: Standard Keyboard - Standard Keyboard

Mouse: Standard Mouse - Standard Optical 3-Button Mouse with Scroll Wheel

Edited November 10, 2009 by DOA

[BrunoDerRabe 0]

for how long did you test ? please try to fly over the whole island Tschernarussland and watch the ram is used (in taskmanager). the ram-usage

is going to be higher and higher, when it reaches 1.4 GB it crashed on my sys.

its takes about 10-15 min to fill up ramusage by flying over island and BIG towns. viewdistance was 4600m on my rig. rest of my rig see my last post.

would be nice if you try this, so i have a reference. big thx to you !!

greetz

the masty

The memory usage (private workingset) doesn´t exceed here 1.075.372K with the settings above.

With visibility 10000 memory usage rise but the game is still running rock stable.

Checked out different settings of visibility / with always highest avaible details ( did run each at least for 20 minutes or longer). No issue like yours on this machine.

Just once while TAB in TAB out to watch the memory usage the game wasn´t accesible anymore, memory usage was about 1.300.000k ....

Tried very hard to reproduce this ``hang``, but no luck ( or better I am lucky that I couldn´t manage) - but the game never used that amount of memory later again - always stayed around 1.200.000K .

I recommend you first to undo the OC. Run the CPU with standard settings @ 2833 MHz(myself very familiar with OC).

All drivers up to date?

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProductID=2578&DwnldID=10884&strOSs=All&OSFullName=All%20Operating%20Systems〈=eng

May be it is worth to check this out as well:

http://www.duplexsecure.com [sCSI Pass Through Direct (SPTD) layer]

Edited November 11, 2009 by BrunoDerRabe

[kklownboy 43]

for how long did you test ? please try to fly over the whole island Tschernarussland and watch the ram is used (in taskmanager). the ram-usage

is going to be higher and higher, when it reaches 1.4 GB it crashed on my sys.

its takes about 10-15 min to fill up ramusage by flying over island and BIG towns. viewdistance was 4600m on my rig. rest of my rig see my last post.

would be nice if you try this, so i have a reference. big thx to you !!

greetz

the masty

I do not have this issue of a RAM cutoff then crash...

Ati hardware. Xp64, V64.

[themaster303 22]

The memory usage (private workingset) doesn´t exceed here 1.075.372K with the settings above.

With visibility 10000 memory usage rise but the game is still running rock stable.

Checked out different settings of visibility / with always highest avaible details ( did run each at least for 20 minutes or longer). No issue like yours on this machine.

Just once while TAB in TAB out to watch the memory usage the game wasn´t accesible anymore, memory usage was about 1.300.000k ....

Tried very hard to reproduce this ``hang``, but no luck ( or better I am lucky that I couldn´t manage) - but the game never used that amount of memory later again - always stayed around 1.200.000K .

I recommend you first to undo the OC. Run the CPU with standard settings @ 2833 MHz(myself very familiar with OC).

All drivers up to date?

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProductID=2578&DwnldID=10884&strOSs=All&OSFullName=All%20Operating%20Systems〈=eng

May be it is worth to check this out as well:

http://www.duplexsecure.com [sCSI Pass Through Direct (SPTD) layer]

thank you for checking so exactly !! was very helpfull. it was not the OC it was the nvidia driver. i had troubles with the first english 195.39 beta and switched back to 193.07 whql. now with the intenational beta it work now.

still have to test more, but it even didn´t crash on 1.5 GB. will report tomorrow when i test more.

if this helps i am really happy that the crashes are gone. will report tomorrow.

greetz

masty

[wills 10]

8 gig doesn`t work on my machine ? all blocky? 4 gig works fine ? nv 295

[_Hurricane 0]

Search the forums...

Use the -winxp parameter, or install the latest beta patch.

[kklownboy 43]

Search the forums...

Use the -winxp parameter, or install the latest beta patch.

he is in the right thread... He doesnt need to search...

:eek::confused: