MavericK96

I think I'd have to disagree with this; I've tried running this game at that res "almost maxed" with one GTX 280 and it's unplayable. But my SLI setup chews through this game pretty good. I think things are more or less CPU-bound on my end.

I assume you mean you have HyperThreading off in BIOS, and you should leave it off because it is not useful and is sometimes even detrimental to performance in gaming. Having a quad-core, your exThreads is set to 7 automatically unless you specify otherwise. And it should be utilizing all cores; it does for me and I have a similar rig.

I can honestly say I've never once had an issue with clicking RMouse vs. holding it, bringing up optics vs. zooming respectively. I think the system works great. If it is thinking you are holding the button when you click, you might want to see if your mouse is working properly.

Pretty much my feelings in general as well. I have to admit I was disappointed at how many "no" answers there were. I was hoping OA was going to change a lot of major things but it kind of seems like just a direct content addon more than anything now. I did wonder about how the overall "improvements" would work beyond the beta patches, because it doesn't make sense that OA would be at any level beyond them.

Yeah I was testing on Utes as well, which is why it was so jittery (very high framerates there). The up and down was the part I had the problem with mostly as well, but I hope it can/will get sorted out in a future release. :cool:

You shouldn't need to set cpuCount with the latest beta(s). It sets it to "4" automatically for quad-cores.

All you need to do to "uninstall" is delete the beta folder. No real reason to do anything else.

Let's just wait and see what they release and then decide whether or not to bitch and complain. /thread (lol)

I'm all for DLC if it provides a decent amount of content and also helps BIS to continue to give us awesome support for this game. Honestly I think they've done so much for just the cost of the game alone, I feel like I should be paying more for it anyway. :cool: People are turned off by the idea of paid DLC because usually it's one or more of a few things: 1) Expensive for what you get 2) Total money-milking crap 3) Released instead of free DLC, not in addition to 4) Lack of modding support due to paid DLC milking efforts I can't see BIS doing any of this, so I'm not worried. I've always thought the pricing on their products has been extremely reasonable.

Looks like it works pretty well for you, and at 10 Hz, too? What settings are you using? Also, do you see any degradation in performance using VSync? I've always had it off because I've heard people say that it degrades performance in ArmA2 and I've personally noticed a significant drop in average framerate with it on, though that could be due to the fact that it caps the framerate at 60, so the overall high values are not included in the average.

I posted a CIT issue about this awhile back. Seems to be fixed in the latest beta patch, so maybe give that a shot.

Lol. It's a pretty good rig. You should check out the beta forum/CIT and see if you get any of the same issues that I do with the game, just out of curiosity.

Omg, they showed a biplane in that video. Awesome. :cool:

Definitely do some research on overclocking if you've never done it before. You don't want to boost speed (or especially voltage) too much unless you want a dead CPU.

http://www.arma2.com/beta-patch.php

Also because unless you're doing stuff like graphical rendering, encoding, and/or distributed computing, there's really no reason to use it.

Yay! http://www.arma2.com/beta-patch.php Interesting new threading options. I'm hopeful for some good performance increases!

Just pre-ordered from Newegg myself. Good price, free 3-day shipping. Operation Arrowhead Combined Operations

What I'm most impressed by is your personal benchmarks, because like you said, the _FPS_6 bench does not show a lot of variance between betas, where your benchmarks definitely do.

jpinard, your link doesn't work but WOW. Amazing work. Thank you for this. :) EDIT: Spreadsheet link, that is. This one works: http://www.jeffpinard.com/ArmA2%20Benchmarks-1.xls

Ah, finally, I figured out what was wrong with it. For some reason my exposure was turned up super-high, and even uninstalling the webcam software that controls it didn't fix the problem. I had to go into the settings and manually mess with it to get it working. Now I get 30 Hz. :cool: Will test to see how this affects gameplay. ---------- Post added at 08:19 PM ---------- Previous post was at 08:04 PM ---------- I think I know why I still get massive jitter when I look up and down but not left and right. I'm guessing it has to do with framerate in-game versus the framerate of the program. Since the webcam is only running at 30 FPS, and the game can be running at around the same framerate when looking at normal terrain, you don't get as much stutter. However, if you look up or down you get a massive framerate boost (since you're essentially looking at nothing) and since the camera is still stuck at 30 FPS, you get this crazy jitter back and forth. I'm not sure how you would fix this issue, though. I've tried cranking the smoothing way, way up with no success. How does FreeTrack work so smoothly with 30 FPS cameras?

After playing this build a bit longer (online MP in ACE, mind you) it seems to have considerably lower framerate, or at least more stutter than previous builds, but I haven't gotten a single crash or "Receiving..." screen the entire time I was flying around in an A-10, so that's a plus. One weird thing was when I was going in for a landing, I blew up for no apparent reason (could have been AA though, who knows) and then suddenly the game sort of locked for a little while, and when I respawned all the textures were gone, replaced by blocky, single-color ones and the game was going at about 5 FPS. I couldn't hit ESC to get out of the game and I had to close it directly from the task manager. Never had that issue before, but overall stability has improved greatly, though perhaps at the cost of framerate/stutter.

It might, though I don't think you're going to see much of a difference between a 2.5 GHz dual core and a 2.66 GHz quad core, TBH. If you overclock it like you said, probably then you will see more of a difference. I can pretty much max the game out at 1920x1200 on my rig, but I've got a much faster processor. Your GPU setup is better than mine, but this game really loves CPU power. Also, there is a sticky thread for posts like this: http://forums.bistudio.com/showthread.php?t=72181

I tried disabling my webcam's software, but I still only get 15-20 Hz. Any other suggestions? According to the HeadTrack demo I should be able to get 30 Hz at least.

1: Supposedly, yes. By default the game now uses exThreads=7 with a quad-core processor. 2: You can always try it, but in my experience exThreads=7 was better. 3: Quote from Dwarden in another thread: Also, the game now sets cpuCount=4 to quad-core processors by default as well. ---------- Post added at 06:45 PM ---------- Previous post was at 06:19 PM ---------- I did some flying around over Chernogorsk in this beta, and though there seems to be more stutter when you fly at a very low altitude than past betas, I did not get any "Receiving..." screen or "Out of Memory" errors at my usual settings, nor have I gotten any crashes so far in my basic benchmarking with this beta. Granted, I only flew around for 10 minutes or so, but it usually happens by then. One thing I did notice is that when I restarted the mission (just a one plane flying mission over Chernogorsk in the editor) the "Receiving..." screen was up for much longer than before. So I guess maybe more of the loading is done pre-mission rather than having the screen pop up in the middle of the mission now. But hey, that works for me. Waiting a bit longer to load is much improved over flying a plane and having the screen black out, causing me to crash into the ground. EDIT: I forgot there was something else I wanted to mention. It seems like, in general, what is causing the most stutter for me is when trees/objects change to the highest LOD while in a fast-moving plane. It seems to be speed and altitude dependent, being that the lower you are and the faster you're going seems to produce more stutter (because of all the high LODs trying to load very quickly). I would almost say that, like with the grass, BIS should look into making the highest LOD models/textures not appear while in a fast-moving aircraft, even when fairly low to the ground. You're going too fast to really tell the difference anyway, and I think it would improve performance a lot.