OUT FOX EM

Well it's no wonder! 32-bit XP will choke your system. It only has the ability to recognize 4 GB of RAM, total, including your video cards. I see you have two 8800 GTX's in SLI; that's 1.5 GB of RAM right there, leaving only 2.5 out of your 8 GB addressable by XP! And that has to be spread around for your OS, ArmA II, and anything else that might be running in addition. Needless to say, your performance will definitely suffer. That's not a good platform to test on.

Glad to hear that solved your problems. Nothing is more frustrating than having a good computer and not being able to use it!

Did that help at all?

And so what are your results because of it?

The AA in this game is very ineffective. Do you have Post Processing disabled? I had to enable it to Low just to get rid of most of the jaggies. If you have it disabled, put it on Low. It helps quite a bit.

It's a display error (obviously), so it won't have anything to do with hosting. I had this same exact error for awhile and couldn't figure out how to solve it, until someone mentioned that my GPU was overheating and to try lowering the clocks. I knew that was incorrect because I had been monitoring the temps and they were 58-60° C, even at full load. Temperature and cooling was obviously not the issue here. My card is a factory overclocked GTX 285, from BFG no less. I figured what the hell, I'll lower my clocks anyway down to the stock Nvidia clock speeds and see what happens. Lo and behold, I could play just fine. There were two specific places in Crysis and one in COD4 that would cause this error every single time without fail, so I was able to test it properly. Time and time again it would freeze with the BFG clocks at the exact same points. Now that I've lowered it to Nvidia's specs, I play without a single problem on stock clocks (need to update my signature). Even though your temperatures are good, try lowering your clocks to at least the stock speeds and see what happens. If you still run into the occasional error, drop them little by little until it's fully stable. It's nice to have higher clocks, but if you can't use them, what's the point? EDIT: I see you're starting to suspect SLI, so I should mention my problems came (and went) before I got my second 285. Anyway, I hope sharing my personal experiences help you somehow.

Well hot damn, that actually worked! :eek: Thanks a lot, I owe you a beer.

So I've seen a lot of threads about crashing to desktop (CTD), texture errors, and various other issues regarding performance and video memory, but I've not seen a problem similar to mine. Basically what happens is I'll be playing for about 10-15 minutes with fantastic performance (60 fps on Very High) and then I'll hit brick wall. My frames will all of sudden drop to about 5-10 fps and will never recover. All I have to do to fix the issue is save my progress, close ArmA, then reload it from my saved point and I'm good to again for 10-15 minutes until I run out of memory again. My PC specs are in my signature, and I'm currently using the EVGA fix for SLI. Settings are default Very High, except fillrate is set to 100% (1920x1200), and Video Memory is set to Very High. Obviously clearing the videocards' memory works great. Is there anyway to force the game to do this on the fly while in-game? EDIT: For the record, I've tried the 182.50 drivers and also various command line parameters (specifically -xp and -maxmem=2047).

Here's the official Nvidia link for beta drivers: Nvidia Driver Downloads Some people, like me, will only download drivers directly from Nvidia. So if you're like me, you might bookmark that site.

I get mouse lag no matter what settings unless I force v-sync off through my Nvidia Control Panel. Try doing that with your 8800 GTS, or your 4870 if ATi has such an option.

Did you try going into the Nvidia Control Panel? You can disable the 3D settings in there. Or if that doesn't work, uninstall the 3D drivers from your Window Control Panel through Add/Remove Programs (or whatever it's called in Vista now). They're separate from Nvidia's video drivers as of 186.18. So unless that's changed for the 190 beta, they will have their own listing in there too.

Update your controller drivers through the Device Manager. Tell it to search online so you don't even have to download anything. Then ArmA will recognize it perfectly, and even give you rumble.

It's a fairly common problem, unfortunately, with Nvidia cards. The Nvidia forums are littered with posts like this for all games and all cards, but no fix as been posted. Nvidia hasn't even admitted a problem. Luckily though I solved my crashes by slightly underclocking one of my cards. Also, you should update your drivers. It only takes a few minutes and might even resolve your problem altogether.

Haha wow, you registered just to insult me? I'm flattered. Anyway, I'm probably older than you, if your mental capacity (or lack thereof) is anything to go by. I'd never be caught dead playing Halo, but again, seeing your mental capacity, I'm not surprised you do. Most console games don't even have inverted controls as an option, let alone the default. Ever wonder why that is? Because hardly anyone uses it. :rolleyes: Most PC gamers use inverted controls? I surely hope that's not a serious statement. Unless you're talking about flying, which nobody has even mentioned in this thread, nobody uses inverted controls on the PC. How many PC games have you actually played? Go troll on the Halo forums.

I only have the demo, but it's under Singleplayer > Scenarios > 03: Benchmark

All it does is patch the official NVidia drivers, nothing to do with EVGA at all. Feel free to apply it to any hardware you have, regardless of the manufacturer.

http://forums.bistudio.com/showthread.php?t=73232 http://forums.bistudio.com/showthread.php?t=76703 http://forums.bistudio.com/showthread.php?t=76700 There's more, but I found those in 30 seconds.

8 GB of ram has issues with this game. There's a few threads about it on the first few pages.

Good thing I didn't opt for 12 GB of RAM for "future proofing" purposes! I'd be mad that I can only use 2 GB.

Because you're in the extreme minority. You think only n00bs use standard aiming, it's the other way around. Just realize, you're the n00b. ;)

You definitely don't need SLI at 1280x1024. That will definitely hurt performance more than it will help. Also, try -winxp, not -winzip. :confused:

Tweedle dee and tweedle dum huh? I circled more than shadows, and even mentioned it in my post. I guess it's too much to ask for you to read the post. Anyway, I found out a work-around. Not exactly a solution but it'll do for now. I had post-processing disabled to eliminate the blur and ridiculous bloom, but once I put it back on then the jaggies magically disappeared. I have it on low (and somehow the bloom is still outrageous) but at least the jaggies are gone.

I've tried forcing AA (all the way up to SLI 32xQ) through the Nvidia control panel and it doesn't change a thing. I've tried both options -- override the application setting and enhance the application setting -- and nothing changes. It only will change when I adjust the in-game settings, and of course I posted a screen shot of how well that works out. I don't know how to get this game to not be jagged.

Thanks a million for this post. It works great.

I used the EVGA SLI Enhancement and it has made quite a difference. My framerate essentially doubled in all scenarios, from the menu to the game play. I highly recommend it to anyone having issues with SLI: http://www.evga.com/articles/00463/Default.asp