MavericK96

Just FYI, changing this value in the config does nothing. Using the beta patch and changing in-game settings is what helped.

This is for ArmA2. Not OA or CO.

Good luck to him on that. Almost never happens.

I may have to pick up a PS3 Eyetoy, it sounds like. I still can't get this to be smooth with my VX-6000 webcam. I have a PS3 anyway so it wouldn't be a totally absurd purchase. :cool:

So it's one dud beta release in a long, long line of awesome ones. Big whoop. :rolleyes: You should thank BIS for continually releasing these betas to users in the first place.

I'm guessing since the errors involved "engineer", this is an attempt to add the new engineer gameplay from the upcoming BAF DLC? Or am I completely off-base? :P

"Highly experimental"...oooo...exciting. :cool:

I think that only changes the weapon, not the ammo type.

1. The beta patches have been great (for me, anyway). Give them a shot. 2. I haven't noticed a major difference, but ArmA2 has had more patches/time to be perfected so it may run a bit better, depending. OA has less foliage in the levels so that also can allow for better performance. It all depends on the circumstances. 3. Generally, yes.

All of the red values you've placed are generated by the game and changing them has no effect (confirmed by Suma in another thread). As for the bold values, you shouldn't need to change refresh unless your monitor can't do 75 Hz. FramesAhead is subjective, and some people like using 1. Use whatever gives you the best performance. (I think 1-3 are valid values for that one)

I think it's unlikely that more patches will be released for ArmA2, but if the issues are severe enough, maybe a smaller patch will be released at some point?

Sounds about right. In the campaign you're always going to get some slowdown.

Umm, take a screenshot of your video options, please. I don't believe this is the case at all.

Not sure what you mean by that. Post Processing is a setting in the game itself and has nothing to do with CPU.

A lot of people just aren't a fan of the overall "blur" effect. Makes it sort of hard to discern targets in the distance, for me anyway.

I was using external view. No FPS change.

Yeah, it's definitely not just you and it's not a hardware issue. I don't get this problem in any other game or app.

Did you guys try changing the Post Processing settings? That was the main thing that helped for me, but to get it totally stable I ended up having to downclock (even though my overclocked settings were 100% stable in Furmark and every other game but OA.) EDIT: Here's the thread I created - http://forums.bistudio.com/showthread.php?t=103671 And here's the CIT ticket if you want to vote it up/add comments and .RPT files - http://dev-heaven.net/issues/11742

Ohh...a laptop. I'm afraid you're not going to have too much luck then, since yes, the 9600M is quite a bit weaker than a desktop 9600 GT, which in itself is a fairly dated card. Overclocking probably won't be an option on a laptop, either, since they already get pretty hot and you can't really add a better cooling solution.

Default *should* work properly with virtually any amount of VRAM, since it is supposed to detect the correct amount available and use that.

1. Are you using ArmA2 or OA? Or both? 2. What in-game settings are you using? 3. With your rig you should be able to play on medium settings I would think. The SP campaign is always going to be slower than anything else due to the number of scripts/AI running, but you should be able to get it playable. I would suggest overclocking your CPU if you can, and upgrading your video card.

RE: The driver crashes, I posted a thread about this awhile back and no one replied. Also, there is a ticket in the CIT about it that I posted (called [OA] Game causes driver to die). I found that a combination of downclocking my GPUs to near-stock levels and turning Post Processing to Low (anything below Normal really) has "fixed" the issue for me. Not a real fix, but a workaround anyway.

Just tried your repro in Combined Operations with the latest beta patch (72418). No real change in FPS other than when driving and loading new terrain. Turning shadows to Disabled (from Very High) caused a gain of only a few FPS, and I didn't notice any significant drop while moving versus not moving.

This doesn't belong in the Beta Testing forum.

Should make zero difference, and you don't need to add exThreads=7 since it automatically goes to that (with quad-core and up, at least). You only really need to add cpuCount=6 if you have a six-core processor. Dual- and quad-cores are set automatically.