MavericK96

BIS claimed that they are working on adding a object LOD view distance option to the game, so hopefully that will help the vehicle LOD swapping. I, too, get tired of seeing a weird-looking blocky helicopter way up in the sky that looks like the rotors aren't attached.

I just put in the parameters, like for instance: -nosplash -world=empty Just like that.

The manual OA patch messes up the Steam version of OA. AFAIK, using the manual 1.07 patch on the Steam version of ArmA2 (though it's already patched on Steam so I don't see why you would) should work fine. The problem with the OA version right now is that it messes with the Securom copy protection when you use the manual patch. It expects a DVD to be in the drive when, because you have a Steam version, there is none. Besides, in another thread, BIS already confirmed that the "latest" build in the manual patch is unnecessary for Steam, in that it doesn't really make any major changes over the Steam version.

Well, if you understand how a RAMdisk works, from where you run the RAMdisk program makes no difference. All the RAMdisk software does is create a virtual drive using RAM instead of your HDD or SSD. So, with your 12 GB of RAM, you could create a fairly sizable RAMdisk. Then, you copy over parts of the game you want run off the RAMdisk, preferably the ones that get a lot of I/O usage (see the rest of this thread for details). You can try installing the game itself to its own SSD, though I don't think it would be any faster necessarily (if at all) than running the game on your RAID 0 SSD setup. What settings are you using in-game? Your rig should be tearing this game up. Though it could be Crossfire-related, I hear the game does not work so well with Crossfire. Try using one GPU instead of both just to see what happens.

Alternately, you can: 1) See my thread here. 2) Use the new 258.69 beta nVidia drivers, which have a profile for OA.

Anything above Normal pretty much kills my performance, likely due to the SSAO, which, while looking decent, does not add a whole lot more to the game. Basically just adds some additional ambient shadowing to grass and such. I think I am using Low or Very Low at the moment. I like some of the blur/bloom effects but it gets somewhat overdone the higher you go.

Gotta agree with jpinard here. 2.8 on an i7 920 from 2.66 stock is not going to be noticeable. If you have decent aftermarket cooling (even on air) and decent case airflow you should be able to pull at least 3.5 GHz out of any i7 chip. I got 3.8 GHz out of mine with barely changing any voltages or anything else at all, pretty much right out of the box with a Vigor Monsoon III cooler.

I think he means: (in the .ini) GPU_MaxFramesAhead=1; GPU_DetectedFramesAhead=1; Max Rendered Frames Ahead (or whatever) in nVidia Control Panel = 2

I think you're misunderstanding the difference between RAM and a HDD/SSD. ;) Hint: A RAMdisk does not "go on" an SSD.

I think you're being a little hard on BIS. Trying to get things pushed through Steam is not always easy, since you're dealing with a third party distribution system, and all changes have to go through Valve. The temporary fix that BIS has provided works just fine for me; all I have to do is put a shortcut on my desktop to the batch file, and run it like I would anything else. Works every time. I, too, would like to see a more permanent solution implemented, but for now this is perfectly acceptable. I also have confidence that BIS will get it sorted out relatively soon.

Well, for whatever reason after installing the new beta drivers both my ArmA2 and OA profiles don't show up as being "auto-detected" anymore. I can just select "Show all Games", though, and edit the profiles that way, and they seem to work just fine.

Good to know, thanks. :cool:

Read the thread and you will have your answer.

OA. Since you can include ArmA2 content in OA, but not vice-versa.

It does? Good to know. I haven't installed those yet. I will give them a shot and report back.

Looks like I spoke too soon; got the driver death again playing the Laser mission. Recovery given by Liquidpinky worked but I lost a lot of performance (i.e. it stopped using SLI or something). At least I was able to save the mission before closing. Not sure whether or not to report this as a CIT ticket since it's an unofficial SLI workaround, though I have a feeling that's not really what's causing the problem.

I don't think there should have to be a new download. Should just be able to have a gameplay option that automatically uses the correct parameters.

I don't think it is in OA. Only since the recent 1.07 ArmA2 patch is it set by default, but OA is only at 1.52 so far.

So adding the .exe for OA to the ArmA2 profile seems to be working better than making a seperate profile for it. No clue why, but I haven't gotten a driver crash yet and I've been playing a fair bit.

Honestly, I had a similar issue in ArmA2 and changing Video Memory from Very High to Default pretty much fixed it for me. LOD switches aren't instantaneous but they don't stay at a low LOD as long when you zoom in/get close to them now.

All this does is revert the game back to the previous version, though. Yes, it allows you to play the game, but there is no way to manually patch to the latest version, even with turning off Steam auto-update. Still wondering what the ETA is on a Steam update to the latest version.

Are you using Hyperthreading? My guess is that the automatic cpuCount=4 is not yet implemented in OA as it is in the latest ArmA2 patch, so you have to set it manually (for now).

Is there an ETA on a Steam version of the latest build?

No, exThreads=7 doesn't mean it uses 7 cores. That would be something related to the cpuCount parameter. Take a look here: http://forums.bistudio.com/showthread.php?t=100519

Interesting, I'll try that, thanks. :cool: And yeah, it could be the drivers, because the game continues to run in the background while the display fails. I might be brave enough to try the new beta drivers that just came out, though it seems unlikely that they fixed the issue. Who knows, though? ;)