boomboomer

My game directory is huge with A2, OA, BAF and PMC. The reinforcements DVD is stand alone and I don't use any single player missions or campaigns from OA, would I be better to uninstall then install just the reinforcements DVD? This would give me access to all MP servers right? Or would I be wasting my time?

Dump Vista for a start, go back to XP SP3 for an extra 10 fps.

Confirmed, flush does not cure the flame issue - only repairing the wreck that was burning when the player entered the server removes it.

Hi all, I've read here about the ATI 4xxx cards having a problem with the default video memory setting, but I've just installed a 5770 card and getting this: http://i753.photobucket.com/albums/xx177/boomboomerboom/Image1.jpg http://i753.photobucket.com/albums/xx177/boomboomerboom/Image2.jpg Is this the same problem? Changing the memory settings to 'very high' solves it but also drops the frame rates - is there a cure? XP sp3 4gb (3.2gb in os) Q6600 5770 ArmA2.cfg language="English"; adapter=-1; 3D_Performance=100000; Resolution_Bpp=32; Resolution_W=1920; Resolution_H=1080; refresh=60; Render_W=1920; Render_H=1080; FSAA=0; postFX=0; HDRPrecision=8; lastDeviceId=""; localVRAM=1063628800; nonlocalVRAM=123076608; Windowed=0; GPU_MaxFramesAhead=1000; GPU_DetectedFramesAhead=2; winX=16; winY=32; winW=1920; winH=1080; winDefW=1920; winDefH=1080;

View distance is 3.5km, as that's what I use when playing domination servers - I take your point about lowering it for CQB but that's difficult during play. I prefer the mid settings I have which give good fps all the time, shame about the 10.2 not fixing the artifacts.

Well at least you've got something out of this - I'm staying clear of Win7 until I need something it does that XP doesn't, like if ArmA3 needs DX11. I take your point, Bench 1 gives me 40fps on Very High and on 42 on default so very little difference but every frame helps when it comes to CQB in the city. I hope Catalyst 10.2 solves the problem, came out yesterday, but I have to wait for Asus to issue their own version for the Voltage mod they include. Thanks to everyone for the help.

Thanks for your reply. Does the -winxp make any difference if I'm already using XP? I'm using the DVI connector, I'll try the suggestions and get back to you. Edit - tried all the above, no change. Also tried setting the localvram option to exactly 1Gb, no change....

I used to get the same graphics crash on my 9600gt, solved it by reducing the card overclock from 20% to 15% for both core and memory - haven't had a crash since.

Hi all, After updating to 1.05 things were fine for a while, then the crashing returned: http://i753.photobucket.com/albums/xx177/boomboomerboom/crash1.jpg Refreshing the graphics driver seems to cure it for a while, I've even replaced my 8800GTS with a 9600GT to see if that helped - it didn't. Only other weird thing is the CPU usage on all four cores is at maximum during the crash (alt-f4 to exit ArmA2 and via Rivatuner). It only seems to happen in MP, even some servers and not others.... Q6600 4Gb (3.2 visible) XP 9600GT 195.81 driver Help?

First uncheck 'automatic restart on failure' in windows system, this will then give you which driver is crashing. If the reboot still occurs with no blue screen then I'd suspect your power supply isn't holding upto the stress. Finally you should dual boot into XP to play ArmA2 and use the cpucore shortcut command to get the best from your processor.

2) - either you're going too fast i.e. over 50, or your rudder isn't configured correctly. I don't have any issues with taxi-ing on the ground unless I give it too much thrust. On the auto land - never used it myself although I've a lot of people crash with it, but thanks for sharing your fix.

Windows 7? Dual boot into XP to play ArmA2, others have done comparisons and XP wins everytime.

Uncheck the option to automatically restart on system failure in system, advanced, startup/recovery. If you are having a hardware issue this should give you the bluescreen of death that could identify the piece of hardware. If crashes still result in reboot then it could be the PSU either faulty or not able to cope - I've known several machines where a volt drop or spike resulted in rebooting.

Solved it, started taking everything apart bit by bit and found it was the overclock on the GFX card that was causing the problem. Only a 20% overclock with extra cooling fitted, didn't seem to extreme but not acceptable it would appear. Difficult to pin as all other games and 3D tests were fine, it was just ArmA2 that crashed. It may even be that the PSU is unable to provide the full current at overclock, even though the dual 12v rails are well over the minimum for the card. Found by turning shadows off gives the same performance boost as the overclock so its now always overcast, even if the sun is shining, in my games.

How exciting are you finding the freetrack system when splashproof is a bonus? lol I wimped on the build and bought a hat from the guy on the freetrack forum, very nice and professional, looks like a normal baseball hat with the IR led's only just visible and a single AA battery by the rear fastner.

One thing that I found reduced crashes, although mine happened from 20 mins onward, was the temperature of the mobo chipset. Mine was passively cooled and had never been a problem but after a while of playing ArmA2 the heatsink nearly burned my finger. The bios said the mobo was only 40 deg C, but I think the chipset was well over 60 deg C. Now it has a flexible fan pointing at it I've not had a crash, so might be worth a look on yours?

Set your joystick button using the 'next target' command near the bottom of the list, not the bottom - there are two for some reason - only one works.

No, that isn't right. Setting next target key does not work for any control other than the tab button. It's because there is a bug, there are two 'next target' controls, one near the top and one near the bottom of the list. Set your joystick button for the one near the bottom and it will now work.

Do you have all the advanced video settings to minimum/off and a low screen resolution? Your PC meets the minimum spec to run the game but it's a good way short of the recommended spec. My kid's old PC was about the same spec and with the gamebooster app turning every off, before starting ArmA, the game was just about playable - but only with all the video settings at minimum. If you have any other services or programs running your PC will not cope with ArmA, same with increasing any video settings.

Hi guys, tried the autoupdate option - it got to 100% complete but then sat there forever. Just downloading the update.exe now manually. Great work though - it's brought ArmA back to life and thanks for all your time and hard work.

I wouldn't say OFP was any better than ArmA for bugs, I can remember spending hours in gamespy trying to start a server, only to find the game crashing everyone out within minutes of starting - very frustrating. The highspec hardware at the time couldn't play OFP at anything over low/medium settings (sound familiar?) although things were considerably simpler back then with only a few flavours of graphics cards to test on. It was until about a year after release that the game became really playable. ArmA is about there now, things should become easier from here - until the next game appears and we start all over again.

After having a few crashes I started setting the core affinity for arma.exe to use just one, the fourth, instead of all four. Been playing for many hours since without any lockups. Q6600 8800GTS 320mb 4Gb (3.2 in OS) XP 32bit

Okay, been playing for a while now and started getting an old bug again - where the screen freezes for about 20 secs then upcomes a random bitmap i.e. a tree or bush, while the last sound played loops. Alt-tab to desktop, then back, fixes it but I think a Nvidia driver update cured this last time. Current driver is fine in 1.14 but not the 1.15 beta. 32bit XP Q6600 4Gb ram (3.4 in OS) 8800GTS 320Mb

Why not install 32 bit XP on your second HD then boot into XP just to play ArmA? It was never coded to run on Vista or x64.

Most Nvidia driver updates usually list a shed load of fixes for different games and usually only games by the monster developers. So you maybe surprised by how many game 'bugs' are really due to the hardware drivers cutting the standards too fine. ArmA is written to comply with the Direct X standards, they can't hit the hardware directly anymore, so if BIS had made a mistake (like the fog bug on 8800 cards) everyone would have the exact same symptoms on a particular card. With our various hardware/driver/software combos we all experience the game slightly differently which makes pinning down problems very hard. You also can't expect other games to exhibit the same issue - their graphics engines will be very different to the ArmA one, what may crash ArmA might not bother BF3 at all.