Woots

Strafes turn into jerks real quick and everybody dies!

What you said is correct because for fps > 60, the output is 60 with vsync on. For fps < 60, the output is 30 fps with vsync on. I get stuttering alot and am thinking it's the 60 fps to 30 fps back to 60 fps I'm noticing. Do I have that right? I was trying to avoid using vsync by limiting my max fps to 60 using the Maxfps command, then when it did fall below 60 fps (say 45-55) I'd get a little tearing since it isn't in sync with my monitor. So basicallly I'm experimenting. Which is less distracting - tearing below 60 fps or the fall to 30 fps if I force Vsync ON. I've got the Nvidia GXT 285

That's my issue - it's not limiting mine. It still shows 64 fps even though I specified Maxfps=60 in the config file. I've used your tweak guide (thanks!) and am now > 60 fps 95% of the time. Also, you can't fix "tearing" with AA. They're not related.

My system is hovering at 62-65 fps, with occasional dips to 45-55 as I fly near big cities. I want to limit my max fps to 60 to match my monitor - I'd occasionally get "tearing" as the fps fell below 60 occasionally but I would prefer that to a drop to 30 fps if I enable Vsync. I set Maxfps=60 in the graphics config file but my fps still shows 64 fps and I get tearing. Can anyone confirm Maxfps limits their framerate correctly?

Found it

I've got the following mods - rotor blur - Arma sound pack - no head movement default (for track IR) - ancient runways - no cloud shadows

Eddie, Do you have single player versions of your missions?

Currently, central time is 6 hours behind GMT. Simply take the GMT (Zulu) time and subtract 6. Ex: Current GMT = 16:42 (4:42 pm) Central time = 10:42 (10:42 am)

They seem to show that 35 -45 ish fps I was talking about.

Tweaking "once or twice" is at odds with the rest of your sentence "when you have the desired outcome". Tweaking is a process and takes multiples of tries to get the right combo. Just look at all the threads on the subject!

So with a 60 hz monitor with Vsync enabled - all in-game fps > 60 would be limited to 60 fps. - all in-game fps > 30 but < 60 would be limited to 30 fps That sux, man. Thanks Bucic for the help.

All the tweaking in the world won't get your frame rates above 35-45 fps ish when flying over cities or taking off from a FARP with 8 helos simultaneously. Correct? If so, I can move on and enjoy the game.

I've done so much tweaking to this game that it's tiring me out. I'm like the guy who can't enjoy a 3d movie because I'm obsessed with lifting the glasses up and down to see the difference. I'm using Vsync and so am limited to my pasma TV's refresh rate (60 hz) anyway. So is it fair to say if your fps is between 50-60 your good? I'm hearing that you'll get 35-45 fps flying over cities no matter what you do anyway. That's certainly the case with me. I'm just asking if all the tweaking you're coming up with is where I'm already at. 50-60 fps 90% of the time with a drop to 45-45 fps as you fly over cities. Anything over 60 fps isn't that noticeable anyway. Great tweaking guide BTW.

I'm reading now that plasma aren't really 600 hz. They're 60 Hz but drawn 10 times/sec in "sub fields". End effect is supposed to be smoother motion. So yes, the need for Vsync is understandable now.

You misunderstand. I was complimenting your reply.

I've been taken out once or twice on the pad by someone flying into me. Might have been the server cause it happened more than once. But based on some of the flying I've seen . . . . it makes me wonder.

Wow, I ask for coffee and you whip out this gourmet sh*t on my a$$. Anyone know the movie that's from? Thanks for the reply. Nothing is as straight forward as it seems.

I'm not trying to start another fps thread, just a question on Vsync. I 'm forcing Vsync in the Nvidia setup menu and it seemed to get rid of the "tearing" I would get in the game menus and during flight. But it makes no sense why it would help. I'm using a plasma tv for a monitor with a 600 hz refresh rate, my in-flight fps are ~ 60 fps. There's no way the FPS is exceeding the refresh rate of the monitor which is listed as the reason for forcing Vsync in http://www.tweakguides.com/NVFORCE_6.html . Right?

I agree. Sent you a PM

I'm in. I was looking to join a virtual squadron (still am) but this sounds just as good. See (ah hear) everyone Sunday.

The only thing unrealistic is the game voice repeating the order you just gave. I would replace those sound files with a "blank" sound file. That way when you give the command to the VAC all you will hear back is the wingmen acknowledging. Wonder how hard it would be to make that "blank" sound file.

I can't fly in that world. I won't!!! Once I saw it at 3 there's no going back.

Yes it should (but it doesn't). Maybe reinitializing auto track would fix it - I'll try that before reseting the whole system next time.

About the only "funny" I frequently encounter is that the tracking gate stops staying fixed after shooting about 4 or so tanks. It initially holds its inertial position as I target tank to tank, then after about the 5th tank - it moves along the ground at roughly the same speed as the last tank I killed. I have to reset the targeting system to get it to stop.

3 times I've had to get out of the game and reinitialize track IR for the same reason. I'm not sure if this is what you're describing, but my track IR would act as if my head were in molasses - verrrryyyyy slow response.getting out of the game and rebooting track IR would fix it. Every time, it was the result of hitting too many F keys when cycling thru exterior views. So I've at least demonstrated there is some goofing mode where track IR response is very slowly and that it is possible to trigger it. Didn't check how the mouse behaved. Maybe you're in this mode by default?