New Nvidia 186.18 Drivers

[von_paulus 0]

Has anyone tried this version?

[_Cappa 10]

These literally just came out...

I'll try em and get back to you. :P

I'm testing 190.15 at the mo and performance is good.

^It is a quadro driver : - I used a modded inf from laptopvideo2go.com.

Edited June 18, 2009 by _Cappa

[ofpfreak 0]

Yep, ran fine with 186, and also runs fine with unreleased 190.15 drivers. Can't say I've noticed any performance improvements over 185.xx though.

[_Cappa 10]

ofpfreak have you tested the non quadro ones? (they only just came out) I'm installing now.

No release notes changes specific to ARMA.

Edited June 18, 2009 by _Cappa

[technologickill 10]

Installed and back to 182.50 because the 256MB VRAM bug. :mad:

My specs: Intel Q9550, 8GB RAM, 1 x GTS 250 1GB runing on WIN 7 RC 7100 64 Bit and ARMA 1.01 DE

[bangtail 0]

Installed and back to 182.50 because the 256MB VRAM bug. :mad:

My specs: Intel Q9550, 8GB RAM, 1 x GTS 250 1GB runing on WIN 7 RC 7100 64 Bit and ARMA 1.01 DE

Same perf and the same VRAM bug as the other 185/186 drivers.

Hopefully this will be addressed in the patch.

Eth

[Fansadox 0]

Im using 186.08 atm how can i see if i have the videoram bug? Graphics card is a GTX280 on Vista 64 ultimate

[technologickill 10]

Look into your ArmA2.cfg for the localVRAM entry ... should be around your true VRAM value (in byte). With the bug you also cant choose high quality settings + video memory inside the game.

Edited June 18, 2009 by technologickill

[Fansadox 0]

it says : 1057030144

[technologickill 10]

it says : 1057030144

Means you have a 1 GB gcard and no bug ... same for me with the 182.50 driver (localVRAM=1056899072). Dunno but i think its somthing wrong with the amount of physical RAM (more than 4GB)!?

[Fansadox 0]

Dont think so cause im using 6gig of ddr3 ram

[technologickill 10]

Would be nice to know something more (all) :) about your rig ... maybe its a self made bug.

[Fansadox 0]

Manufacturer:

Gigabyte Technology Co., Ltd.

Processor:

Intel® Core i7 CPU 920 @ 2.67GHz (8 CPUs), @3.6GHz

Memory:

OCZ 6140MB RAM DDR3 Reaper 2000mhz

Hard Drive:

2 TB Samsung Spinpoints

Video Card:

EVGA NVIDIA GeForce GTX 280

Monitor:

Dell 24inch @1920x1200

Sound Card:

Speakers (Creative SB X-Fi)

Speakers/Headphones:

Razer Barrcuda HP-1

Keyboard:

Logitech G15

Mouse:

Logitech G3

Mouse Surface:

Razer Exactmat X control

Operating System:

Windows Vistaâ„¢ Ultimate (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)

Motherboard:

Gigabyte EX58-Extreme

Computer Case:

Coolermaster CMS Stacker Special edition

[technologickill 10]

So it sounds like a prob with that WIN 7 RC or the 64Bit System ... so i have to wait for a workaround/patch. :(

[Fansadox 0]

Looks like it indeed. Arent you running a dual boot?

[technologickill 10]

I do with XP SP3 but if you believe different benches (here in the BIS forum) and the boost in ARMA Mark under WIN7 i stick with the older driver + WIN7 ... better than XP + 186.x drivers.

[BrunoDerRabe 0]

an outtake of an earlier post:

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.

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";

adapter=-1;

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 @ 3.0Ghz OC**************AMD PhenomII 940BE @ 3.0Ghz

8GB DDR2-1066**********************8GB DDR2-1066

2 260GTX in SLI**********************2 260GTX in SLI

X-Fi Xtreme Gamer*******************Onboard Sound Realtek High Definition Audio

Asus P5N72-T Premium****************Asrock K10N780SLIX3-WiFi

Windows Vista 64 Ultimate*************Windows 7 RC1 64-bit

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

@technologickill

---------- Post added at 03:53 PM ---------- Previous post was at 03:45 PM ----------

I do with XP SP3 but if you believe different benches (here in the BIS forum) and the boost in ARMA Mark under WIN7 i stick with the older driver + WIN7 ... better than XP + 186.x drivers. Asus P5Q // Intel Q9550 // XFX Nvidia GTS 250 1GB // WIN 7 RC 7100 64Bit // GF 182.50 // proud owner of the 256MB VRAM bug

technologickill,

do you still own the bug on Widows 7 with GF 182.50 installed?

If so I do recommend to use the driver 181,71 ( Prerelease - WDMM 1.1) for Windows7RC1 wich is mentioned in post above.

I spent days with shoting this bug, but it is still kicking.

:cool:

Edited June 20, 2009 by BrunoDerRabe

[technologickill 10]

Thanks for your info Bruno ... and no, with 182.50 on WIN 7 RC the bug isnt present anymore. For now i still dont know what causes the bug but i want to know. Is it the newer NVIDIA driver with WIN7 and 8GB or is it a bug in ARMA caused by that special system specs?