Woots

I use to experienced that from time to time also, sometimes still do. I'd lock a target in AUTO hover with "turn to target" on then lean down to focus on the SHKVAL to zoom in and identify the target. Right before I fire I see the "X" in the shkval and think WTH, lean back to see out the front window and my nose is 40 deg to the right. The shark had been drifting in yaw the whole time. I read somewhere that you should hit the trim button after going into an AUTO hover. This did seem to help.

Think of that + as a little yellow middle finger, sitting in the corner, flipping you off and mocking you as you fly. I can't fly like that . . . I won't:)

I compared the Hokum sound mod to the Arma2 sound mod. They are close but I prefer the Arma2 engine noise. Just a personal preference, they're both great. Actually, I opened both the Hokum and Arma2 .zip files and dragged and dropped the individual sound files to make my own personal mix. Just open each .zip file in a separate window and click to play identically named sounds files back to back so you can compare each. Pick the one you like best and drop it in the effects folder. I'm currently flying with my own blend. Give it a try (keep the original files in case you want to go back).

That doesn't stop the motion glitches. LALT + C simply cycles thru the three modes, two of which enable view control with the mouse! Basically, when using trackIR, you NEVER want the mouse to control view inside the cockpit or it fights with trackIR. The "cockpit mouse and trackIR fix" mod does that. See http://forums.eagle.ru/showpost.php?p=774537&postcount=9 Even with the "cockpit mouse and trackIR fix" mod, I still use LAlt + C to get a clickable cockpit with a "+", then LAlt + C (twice) to remove the "+" when I'm done. Using the mod allows you to cycle thru the three modes with view control always disabled. It would be great if the "+" would go away on it's own after say 5 sec of non-use. Then I wouldn't need LALT + C at all, the "+" would automatically appear when I moved the mouse and disappear automatically on it's own.

Could you point me to sharkpit V3x? Never mind, found it!

Will sharkpit work w/Russian fonts? http://forums.eagle.ru/showpost.php?p=833245&postcount=54

I downloaded V2a from lockonfiles. Can I still use it if my cockpit (sorry, my sharkpit) is in Russian?

Thanks all!

I've had the "full screen mode" option checked in the options page for a while now. I unchecked it to see what it would do. NOTHING - the game still takes the whole screen (not windowed like I thought it would). Which option should I be using because I can't tell a difference. Is it better for FPS with it checked or not. I've got the 16x19 option checked becuase I'm using a plasma tv as a monitor, if that affects this.

I was watching some flight footage of the shark and noticed how much flame accompanies a Vikhr launch. Now that would be a cool mod. Anyone got skills? http://www.aviation.ru/www.rusarm.ru/video/Ka-50.wmv (Right click and save to desktop to play)

I was just tuning my axis controls last night and ran into what you described. I don't have access to the game at the moment so am going from memory, but I went into the command list and found the group that controls flight inputs - it's something like command axes or something. Once you select that group, the axis-tune will become lit and you can fine tune the desired axis. My joystick has a twist grip with about a 10 deg slop around neutral (the springs have worn down and don't return the grip to exactly center). I created a deadband to account for this. Hope this helped.

Take a chill pill Maio. No one's fighting.

What lesson? Indenting code while programming? Uhhh, that's nothing new. I'm just making an observation it case Maiochine wanted to fix his post. It was obvious to me, maybe not to others.

Good stuff thanks! JTLYK, if you follow the above exactly, you'll end up with } } } }, which is one too many.

As far as using multiplayer maps for practice, they work just fine as single-player maps (no need to "host" a multiplayer session to play them). After playing on the rookie server this weekend, I copied the .miz files from the temp directory and renamed them. I then flew them solo by selecting them from the mission menu. They worked just fine.

As for the reason for the thread, setting Maxfps=60 DID limit the frame rates. It just limited it to 64 FPS and I was expecting 60.000. I tried Maxfps=30 to verifiy and it limited it to 33ish. So it's trying, it just isn't exact so I thought it wasn't working. But I'm glad it got us all talking. It is a bit confusing, I'll go with the above theory about the variable FPS. It would explain why the stuttering isn't too sever when my FPS drops < 60 and also why the game FPS is reporting a variable FPS around 41-48 when it does (and not exactly 30). BTW, this is really maddening. With Maxfps=0, I get variable rates between 70-110 FPS 90% of the time. That makes me feel better about spending all that $ on this rig. Large towns and other complex scenes HAMMER the CPU down to 45-50 fps. Mix that with a 60Hz plasma and I get the stuttering. It's a 60 in screen though and looks absolutely stunning at 1920x1080. So, question, would you kick out a pretty girlfriend (60" plasma tv) for smoking in bed (being only 60 Hz)?

What kind or problems? You can still play online right?

Uhh . . because the mouse and TrackIR fought each other for control, kinda like I said. Alot of people use it.

Must be Eastern European Union humor.

Is there a mission that starts you off near Maikop?

Ancient runway mod adds grass in the cracks and black tire marks on the runway ends. It makes the runways look more realistic IMO. I also use the "cockpit mouse and trackIR" fix. This prevents the mouse from controlling your view inside the cockpit - without it the mouse view "fights" the trackIR and you get motion glitches. Very annoying.

No one said otherwise. Welcome aboard. My in-game fps is oscillating around 60 fps (from 58-65 fps) as I clearly stated. With Vsync on, that makes the refresh rate oscillate from 60 to 30 to 60, i.e back and forth as stated in your chart. Then they should label it max FPS variation limit! But they didn't, so if it's really variation that changes everything. ________________________________________________________________ Negative - it's a plasma TV, the refresh rate is 60 Hz. Like I clearly stated, the FPS indicator is showing 45-55, that's not a value slightly off 30. Bucic thanks for the help, but really. . .we're going in circles. - I have a 60 hz plasma for a monitor - my in-game FPS is from 55-65 fps 95% of the time - my in-game FPS is 45-55 fps 5% of the time Why would I need Vsync ON if I can use maxfps setting to limit the in-game FPS to 60 WHICH WOULD BE IN SYNC WITH MY MONITOR! AND IF THE GAME FELL < 60 FPS THAT 5% OF THE TIME I WOULD GET TEARING WHICH I CAN DEAL WITH. If Maxfps is the range of variance, not a cap on the FPS magnitude that's the key. It's the first I heard of it - I don't think alot of people realize that.

Ha! I was going to refer to that thread myself. Frazer, with Vsync ON, your update rate is limited to be a multiplier of your monitors refresh rate. I don't confess to understand it, but I've read that from several sources. But we digress. For a 60 Hz monitor, limiting my FPS to 60 using MAxfps in graphics.cfg should get rid of tearing without the need to use Vsync. Someone show me where I'm wrong please.

Thanks

Ok, sorry to beat a dead horse but I'm missing something. Here's my assumptions With Vsync ON the game refreshes my monitor at either 30 or 60 fps - period, regardless of what the physical in-game FPS is (so I don't understand when you say "the lowest frame rate doesn't really change no matter if you have Vsync on or off). If I can get the game to limit my FPS to 60 FPS (to match my 60 Hz monitor), THAT would prevent tearing as long as the in-game FPS didn't fall below 60 fps. If it did fall below 60 fps, only then would I get tearing (but I would be seeing 45-55 FPS update).