MavericK96

True. It said they used "maximum details" with AA on "high" for the tests. I don't know what exactly that entails, but based on the scores I'm guessing it was CPU-bound at that point. The 480 is considerably faster than the 5870 in most games, and at least marginally (5-10%) better in pretty much all games.

Well it's not like ArmA2 is super GPU-dependent...

Same problem. i7 / 6 GB / 2 GTX 280s in SLI / Win7 x64

Hey, if you get it running with 6 GB, let us know what steps you took if you don't mind. I'd like to see a decent guide on running a RAMdisk with ArmA2 with less than putting the entire game folder on a RAMdisk. :D

I pulled this out of the ArmA2.RPT file: Exception code: C0000005 ACCESS_VIOLATION at 0043F4DE graphics: D3D9, Device: NVIDIA GeForce GTX 280, Driver:nvd3dum.dll 8.17.11.9675 resolution: 1920x1200x32 I don't know if that's what caused the crash, but that's what it looks like. Any ideas? My video cards are definitely not overheating. Here's some more I found: Exception code: C0000005 ACCESS_VIOLATION at 00A216A6 Error during v-buffer creation: error 8876017cError during v-buffer creation: error 8876017cError during v-buffer creation: error 8876017c Error during v-buffer creation: error 8876017c ((<------It says this over and over and over)) Error during v-buffer creation: error 8876017c graphics: D3D9, Device: NVIDIA GeForce GTX 280, Driver:nvd3dum.dll 8.17.11.9675 resolution: 1920x1200x32 Also: Prev. code bytes: 72 CC F3 A5 FF 24 95 54 17 A2 00 8D 49 00 23 D1 Fault code bytes: 8A 06 88 07 8A 46 01 C1 E9 02 88 47 01 83 C6 02 Registers: EAX:00000002 EBX:00000072 ECX:000000E2 EDX:00000002 ESI:00000000 EDI:2811AF8E CS:EIP:0023:00A216A6 SS:ESP:002B:2434E3D8 EBP:2434E3E0 DS:002B ES:002B FS:0053 GS:002B Flags:00010202 ======================================================= note: Minidump has been generated into the file C:\Users\MavericK\AppData\Local\ArmA 2\arma2.mdmp Hope that's helpful.

I was wondering about this as well. I'd rather not have to buy another 6 GB RAM if I don't have to... ;) Also, can anyone comment on the frequency of crashes when using the RAMdisk as opposed to not?

I keep getting crashes frequently as well. Typically when flying in a heli, what will happen is I will be looking at the ground, and then suddenly the ground area will turn a light grey color (artifact?) and then the game will lock up and crash to desktop, with a "ArmA2.exe has caused an error", with the error being APPCRASH. I've never gotten any "out of memory" errors or anything like that, it's always just this one type. Sometimes it happens after 10 minutes, sometimes after an hour or so. My settings in-game: Everything Very High, except: Video Memory - Default Antialiasing - Low View Distance - ~4000 (max before not allowing Very High terrain detail) The game runs fine with playable framerates, but will just crash once in awhile. It happens basically every time I play the game, regardless of how long the game is. Running Win7 x64.

I get the same thing as the OP, especially if I look at the ground for 2 seconds and then look back up. Even if you're not looking directly at the sun, the sky becomes blindingly bright. I understand the concept of HDR but it's just way overdone in this game.

Sadly, I have been considering buying another 6 GB of RAM to do the same. :P Oh, the things we do for games...

I don't know about anyone else, but going up to 10k VD, I don't really get a framerate drop per se, but I do get MASSIVE hitching/freezes as I rotate the view around. Like, on the order of a second or two per instance. Additionally, if I move forward a bit and/or zoom in and out again, I will get the same massive hitching. Obviously this is due to having to load and then dump TONS of models/AI/whatever over and over in an instant, but it's certainly not playable this way, regardless of the framerate when it's not hitching.

Weird, I did the same procedure and it works fine. Did you also download the .bisign files and put those in the addon folder? I did that too.

I tried to take a screen cap, but it wouldn't work. But my Video Memory drop-down menu looks like this: Low Normal High Very High Default I had it set to Very High originally, and had massive texture LOD swapping, even at point-blank range. Changed it to Default, and now it's way better.

Did you try what I said/read that thread I posted? Try setting Video Memory to Default instead of Very High (which seems like max, but Default is actually below it (as in, a "higher" setting) and works a lot better). I'm guessing this is because Very High limits the video RAM to something like 512 MB, whereas I have 2x 1 GB cards, and Default is more like an auto-detect that could potentially use more than Very High.

Oh, no, I know it's easy to change. I guess I didn't see that you were left-handed and remapped the controls. I was mostly just looking for some advice on what button to map that would not already be mapped in the default controls (because this game has so many as is). Like I said, side mouse buttons would be ideal, but VAC doesn't support them. I guess I could remap a command to the side buttons in-game and then set VAC to whatever that key was...

I've been having similar issues with LOD, and I tried those PROPER view distance patches, which seem to sort of help objects further away, but sometimes I will get LOD swapping even at super-close range. For instance, I will be standing right next to a squad member, and their uniform will look blurry and low-quality. Then, when I zoom in super-close with Mouse 2, it renders into a more high-quality texture. The LOD shouldn't be swapping like this at point blank. Is there any particular reason for this? Are you talking about the object detail setting, or the visibility slider? I have my object detail set to Very High, and the visibility is around 3000. ---------- Post added at 04:06 AM ---------- Previous post was at 03:51 AM ---------- Well, I tried messing around with it a bit, and also reading an older thread about the issue (http://forums.bistudio.com/showthread.php?t=73323&page=4) and found that changing Video Memory from Very High to Default (the next option down) seems to have helped the problem substantially. Also, I'm still using the PROPER addons, which seem to help draw distance of objects/vehicles/buildings.

I've been trying to use this but even after training the Windows Speech Recognition thing for 1-2 hours, it still doesn't seem to want to work all that accurately for me. :\ EDIT: I had been using a Bluetooth headset as a mic, but I tried switching to a desktop-mounted regular Creative boom mic I had laying around, and it seems to work a LOT better now. Not sure what the deal was with the headset, maybe it just wasn't high enough quality. Gonna go try out VAC now! ---------- Post added at 02:06 AM ---------- Previous post was at 01:40 AM ---------- Okay, I tried it, works pretty good now! One question: Is there a reason you used NumPad . as the activation key? For me, that brings up the command view. Are there any buttons that you know of in-game that are not bound? Ideally, I would use the side mouse button, but VAC doesn't seem to support those natively.

Very helpful, thanks! I was thinking the training might be necessary, but I wasn't sure how completely VAC interfaced with Windows.

Yeah, I never really understood why they changed it from an easy-to-use system to an obfuscated and unusable one.

I couldn't figure out how to configure my mic in VAC. Does it just use the default Windows settings? I tried this out in the VAC tester, and it seemed like a lot of the time it didn't recognize the proper command, even when I was speaking loudly and clearly. Is there any way to "train" it to your voice, or any suggestions on how to improve recognition of commands?

Wow, that's cool! I want to try that as well.

What's strange is that my friend has the same retail copy of the game and runs it through Steam with no problems. I seem to recall running it through Steam before, as well, with no issues. @Master gamawa: I have not tried that yet. I could give it a shot, but that sounds like a huge pain if I have to do that every time I restart the game.

Hello, I've recently been trying to play some ArmA2, and the first time I start up the game, it will run fine and everything is great. Some random crashes once in awhile, but nothing serious. However, if I quit the game and start it up again, sometimes when I am in-game, I am not able to move (WSAD does not work), and I can't even access the menu via the ESC key. I can, however, rotate the mouse, aim, and shoot. I think what is happening is that somehow the keyboard stops working in the game. If I reboot my machine, the problem goes away for the first load, but if I try to load again after that the same issue occurs. Has anyone else gotten a problem such as this? I used to play this game a lot more often, and I never had this issue, but it's been awhile and I've upgraded to Windows 7 from Vista since then. My specs (if relevant): Core i7 920 @ 3.8 GHz 6 GB DDR3-1600 2x nVidia GTX 280s in SLI Windows 7 Business x64 Running the game at 1920x1200, most details Very High, AA at Low. No problems with framerate. Thanks for any help! :)

Nope, I am not. ---------- Post added at 03:22 AM ---------- Previous post was at 01:35 AM ---------- UPDATE: I think I may have figured it out. It seems to only be happening when I run the game through Steam. It's not a Steam-bought copy, but I registered the shortcut as a non-Steam game in Steam so I could use the interface. That must be what's messing it up. This doesn't really make a lot of sense, though, since you can get the Steam version of the game which undoubtedly has the Steam UI, and it should work just fine.