Justin Case

V 3.0 here -> http://forums.eagle.ru/showthread.php?t=132444

I did the same thing a month or so after release. "They broke the IFF with the last patch!…oh look at this switch!" ;)

Don't forget to flip the switch labeled "TYP 81" (IIRC), the IFF worked fine for me in MP just a few days ago.

Make sure you have not switched the AUX Inverter on, if so the sight won't work.

If you treat the thicker end of the CDI needle like you would a course needle on a western HSI, the CDI "fly left" or "fly right" indications work as you would expect. Though the flight directors only work correctly when you set the CDI the opposite way...

He didn't say that. He meant the fact that the aircraft will quite happily fly itself through the engines max Mach at altitude.

No it won't unless you let it kill you, flaring doesn't always mean stalling.

Here's a landing tutorial i made, it's in Swedish though so you might as well listen to some music instead. Practice practice practice... With 3000 hours on the 737 I find the MiG-21 quite believable in the "normal" flight regimes, can't say too much about the extremes though.

+1

True, and then the RIO knows exactly which tree among 30 you were pointing at.

"ALL, go to that tree!"

Tactical release behind the stick?

I basically did this with burner the other day, took me 2:30 or 3:00 (can't remember) from standstill to 10 000 m. Make sure you follow the true air speed indicator, otherwise your pitch will be way to low after a few 1000 meters. :)

Wouldn't the service and absolute ceilings require afterburner?

Yep. :) And I agree with you!

I guess LN already know this but it's something with DCS since the SU-27 shows the same behaviour.

I believe it's more efficient to climb at a throttle setting just below afterburner, I've only seen those 95% mentioned once in the manual but then it seemed to be a recommendation for a "first flight" smooth climb. Edit: Unless there's an engine limit I've missed.

I usually get a flameout somewhere after 21 500 meters...

I picked up a LG UM95 yesterday and I think I love it! I've only used it one evening so far so I'm holding on to any recommendations as for now. I'll write more here in a few weeks.

I'm behind Cibit on this one, use the F10 map. The kneeboard map seems to be based on real charts which doesn't match the terrain in DCS. The F10 map on the other hand is unrealistically detailed with every light pole marked out, but with a proper zoom level it's highly useable!

Thanks for the reply outlawal, I'll report back here if I decide to get an ultra wide screen. At the moment I'm leaning towards that type of monitor.

Hi guys! Could anyone with experience from it tell me their opinions on flying DCS on a 34 inch monitor? It's time for me to swap my old 22 inch monitor for something bigger, since I have limited desk space I'm not really considering a 3 display setup but an ultra wide 34 inch could be a nice option. From what I've read my GTX980 seems to be up to drive the 3440 by 1440 pixels seen on the LG UM95.

Was it just me or did the mig behave a bit calmer on takeoff today? There were also some new sounds after the patch.

I have similar issues around airports, even with Scenery set to low I see no improvement. I just learned to live with it and be happy about all the frames I get when I'm away from airfields.

It stems from a desire to create a realistic module for DCS. Because the raising the landing gear require more than one action and thought, to prevent pilots from raising it too early. I have the safety switch, landing gear three position switch, radar off/stby/on and radar ground clutter function mapped to my WH throttle. No problems. This was done with a mod which is stickied in the MiG-21 forum.