Woots

I too noticed some strange flight behavior post patch. Turned out that my realism options had defaulted back to "arcade" mode. Once I fixed that, everything was as before (velocity line < 50 kph, auto hover, turn to target, etc).

The default is green as green can get. You must have used a NVG mod to get it grainy white. That's what I did - I modded mine to a whitish color. Get the mod from lockonfiles.

FD mode is not something that you can just try for a few minutes. It's a whole different mode of flying. That it felt awkward would make sense. You'd have to get used to flying with FD mode engaged just as you got used to flying without it. I didn't mean to stomp on this thread by bringing up FD mode. I only mentioned it so you know there's another mode (FD) that doesn't give you the Alt hold hassle you mentioned earlier.

I fly in flight director mode 95% of the time. Don't have to hassle with the above alt hold issue plus other benefits (no heading hold, constant re-trimming, etc). Once I'm ready to hover I disengage flight director mode, engage auto hover, engage turn to target etc. Once I need to fly off again - I re-engage flight director mode. I've gotten so used to doing this its now automatic. The alternative is to not use flight director mode but constantly hold and release the trimmer (and hassle with alt hold).

I flew two missions back to back. In the first attempt, I remembered telling my wingman to go to combat spread as we flew to the target. Once at the target, he would not engage and I died. In the second attempt, I didn't give him any formation commands as we flew to the target. Once at the target he would engage and he died. Asking him to go to combat spread is the only difference between the two attempts. I wonder if I had him "rejoin formation" prior reaching the target area he would have engaged in the first attempt.

I don't know which is more stupid. Especially after the 1.02 patch. I restarted Deployment campaign after the patch and my wingman has been acting like a UN observer. He calls out contacts automatically now (new in 1.02?) but WILL NOT engage when ordered. Says unable or negative while we're both getting shot at. Anyone else notice this?

I went ahead and removed them. Takes away all the white noise and you're left with the thump thump thump of the rotors. Kinda soothing actually. It all boils down to personal preference.

The cranes moved in 1.01C too.

That was it! Thanks all

I installed over 1.01 but noticed something strange. Both Auto hover and Turn to target don't work anymore. I engage autohover < 5 kts (as I've always done) and get no help from the autopilot. I drift as if it wasn't engaged. Also, turn to target won't point the nose at the targeting recticle. BUT, if I engage route mode my nose swings around to the route heading like a bat outta hell. All three are different behaviors than before. I really don't want to uninstall and start from scratch but this is weird. Anyone else notice anything close to the above? EDIT: Here's a track file dap modes.trk

I've been reading about how the new patch causes cloud flicker and other annoying symptoms that people have fixed thru mods. Just a reminder - you don't need modman for alot of the mods. You can simply open the .zip or .rar file of the mod and drop the included file manually into the appropriate. directory (after backing it up first). I've already done this twice - open NoCloudShadows.zip and drop CLOUDSHADOW.TGA into bazar/TempTextures - open cockpit mouse view and trackIR fix.zip and drop View.lua into Config/View Fixed these two issues for me.

Your counter says it's your second post :smilewink:

"Bistro" is Russian. You understand that:)

I agree. I'm using D3Doverrider to force triple buffer and I don't think it's doing squat. BS is already forcing it for you. I'll disable D3doverrider, one less utility to be running in the background.

I have it assigned to my spacebar since it was the most convenient key for me. My thumb is resting on it, so it doesn't take any hand movement to hit it. I tap spacebar once and the "+" mouse cursor appears. I click the switches I need I tap space bar twice and the "+" goes away. Rinse and repeat as necessary :) This is of course just a workaround, hopefully in a future patch the "+" will disappear on its own after a few seconds of inactivity. That would be the better answer.

I'd get rid of the "+" whenever possible. Huge distraction.

We all get what you're saying. You're not getting that it has nothing to do with this thread, learn to stay on topic.

Let me get this straight. You won't use labels but using ZOOM is just fine. That's rich! :music_whistling: LMAO. I bet your cockpit's not even in Russian! Airtom, chill out. We're all impressed that you don't use labels. Give it a rest. This is not a thread to discuss the use of labels - it's already been done to death. Watch the video and move on already.

No, I'm more serious with them off:megalol:

Oh yeah. A direct hit from an enemy helo tends to do that:)

I had the same problem. I've got the demo version of fraps so can only record 30 secs of footage but it was HUGE. So a buddy turned me on to anyvideoconverter. You can get it here http://www.any-video-converter.com/products/for_video_free/ Use this to convert it to a MUCH smaller size. Here's the result I posted on youtube http://forums.eagle.ru/showpost.php?p=872167&postcount=1

At least I didn't blink first

I have an I7 860 (2.8 Ghz) and overclocked it to 3.6 Ghz. The only graphics options I dumbed down are water=1 and shadows = planer. The lowest frames I've seen are 30ish. Yours seem pretty low (I'm sure I've flown over Krasnodar but will check). Wonder what the difference is. Win 7/Win XP/ram/GPU must be a factor.

Got it, thanks all!

So there is a way (kinda). You simply replay the .trk file while recording it with FRAPS. That's not so hard.