Volator

Problem persists in newest patch DCS 2.7.17.29493.

I agree with everything written above. It's not a perfect module, but pretty much none are in DCS. The MiG-21 has a lot of character and is fun to operate because you really have to work a little bit as a pilot and actually fly that thing. Odd things are the gunsight which is a little bit off, some switches/systems aren't (fully) implemented, and FM-wise take-off and landing behaviour are a little bit annoying as the DCS MiG-21 - like some other DCS modules - tends to be glued to the ground, so performing a proper take-off rotation or a smooth landing on the main wheels and perfoming aero braking isn't working well/at all. Further development / bug fixing seems somewhat slow, but at least it does still get some attention by the devs, even though they are quite busy with developing new modules. You should definitely get it if you are into Soviet aircraft and like steam gauges and lots of switches to play with and planes that really need to be flown in an old-school way.

Sound bug not fixed with the latest patch (DCS Open Beta 2.7.17.29140)

So your likes and dislikes define what's realistic and what's not... 'nuff said.

I beg to differ, can't share the enthusiasm. Pitch oscillations are totally overdone now. I'm no aerodynamics nerd, I just fly planes, so can someone show me why it is supposed to be more realistic that the MiG-19 (like other DCS MiGs used to, MiG-21 seems to have improved a little, just checked again) now wobbles in pitch if you pull a little harder on the stick (without getting to "extreme" AOAs of 18° and above). Got any video of any other plane doing that in a hard turn? You can see it in most slightly harder turns or pull-ups that the nose initially starts to move fast or rather bumps up, then there's a bump down, then the nose accelerates again and now maintains its speed, despite stick pressure being quite constant. The faster the MiG-19P gets, the less the problem, ok, but an 9 tons dart going at 500-600 km/h should still not behave like a tumbleweed. MiG-19P_AOA_wobble.trk

Question: What's the difference between "delete" (tick a module and click "delete selected") and "remove" (click the trashcan icon) in the modules manager? I would like to remove/delete two maps to free some space, so I want them gone from my HD. Which one is the correct option to achieve this?

It does take its time. Unfortunately nothing new with the latest update (2.7.17.29140)

Same thing with SAU in Auto mode. SAU holds glide path nicely regardless of flight director indications though, that is until 200m altitude, there it starts descending well below the glidepath. MiG-21_PRMG_Anapa_002.trk

For me it always shows pitch up command regardless of where I am on the glideslope. MiG-21_PRMG_Anapa_SAU_Direct.trk

My observation as well. Take-off feels very weird in the Yak, and landing isn't much better either. Once in the air it flies ok, aerobatics can be flown quite well with it.

It has been some time, but I finally checked, it's gone. Thx ED! Not sure I understand you here, a loop would be a constant repetition of an audio file, isn't it? I only work with looped morse codes on my radio stations/beacons.

I'd rather favor a 1980s/1990s livery like OP...

Sure thing. So what he meant was not "realistic ASP AND CCIP", but "realistic ASP and NO CCIP". Got it?

There is no CCIP for the MiG-21.

Some additional tests at Krymsk, Maykop and Mozdok: Krymsk, wind 220/3 --> RWY04 Krymsk, wind 220/4 --> RWY22 Maykop, wind 220/3 --> RWY04 Maykop, wind 220/4 --> RWY22 Mozdok, wind 080/3 --> RWY26 Mozdok, wind 080/4 --> RWY08 So it seems every airport has a main runway that is assigned by ATC regardless of wind direction up to 3 m/s. That means in certain wind situations you will always get a tailwind take-off and landing at 3 m/s or less. At 4 m/s the correct runway will be assigned. Krymsk_wind_runway_001.trk Krymsk_wind_runway_002.trk Maykop_wind_runway_001.trk Maykop_wind_runway_002.trk Mozdok_wind_runway_001.trk Mozdok_wind_runway_002.trk

At Anapa it seems ATC always assigns runway 22 regardless of wind direction up to 3 m/s. At 4 m/s or higher, at respective wind direction, runway 04 will be assigned. Is that a bug or intentional? At Sochi the same issue appears, but like in real world here it makes sense due to the mountains at the end of runway 06, so even with a tailwind a takeoff in direction 24 is desireable. For Anapa however, I cannot see any particular reason why you would want to take off with a tailwind component. Even more so, a take-off on RWY22 means you take off towards the beaches and hotels, which most probably wouldn't be very desireable with regards to noise, and certainly would not justify a tailwind take-off, so I'd assume this is a bug. Tracks attached. Anapa_wind_runway_001.trk Anapa_wind_runway_002.trk Anapa_wind_runway_003.trk Anapa_wind_runway_004.trk Anapa_wind_runway_005.trk Anapa_wind_runway_006.trk

+1

Fantastic, thank you! It is a great map already, and it becomes even better.

That's a real nuisance that drove me nearly mad when trying to design own missions for MP. I was cursing the Mi-8 ADF system and my own capabilities to operate it until I saw this thread. Did some more tests and can confirm Alpenwolfs findings. Thanks for adressing this, Alpenwolf. @Flappie or @BIGNEWY, please forward this to ED, it is rather important to fix this.

I think the -bis was the best choice of all available variants to bring into DCS as a first MiG-21 - still a classic MiG-21, but capable enough for late Cold War, a good variety of a2a and a2g ordinance, sufficiently multi-role employable, and used by quite a lot of air forces around the globe. So before anything else a MiG-21bis 2.0 should be the primary goal to aim for. With the upcoming early F-4E I do see a reasonable demand for an earlier North Vietnam AF MiG-21 variant as an independent module though.

There's never "too many" of those lovely GDR skins. Just a small detail for any future GDR skins: Can you make the pilot's flight suit in a grey-blue colour? This is what they looked like:

I've tried various NDBs now on Caucasus, and while I still sometimes have a good signal strength but no morse code, this seems to be related to not having hit the right frequency perfectly well. It's odd that the signal strength is maxed out then though. On tracking Gaudata NDB though, I was able to track it well with the needle, tracks attached. Not sure what caused the problem you described. MiG-19_NDB_ADF_Gaudata.trk

In general the virtual Mi-8 crew could provide more help. Most important would be calls from the gunners or the co-pilot regarding enemy fire, like incoming missiles or gun fire, also reports on enemy aircraft approaching, but calls like mentioned in OP would certainly be welcome.

I've had similar issues, but I still haven't fully tracked them down. Sometimes I get a full signal strenght of an NDB, but no identifier/morse code, and thus no direction finding. Did you switch the RSIU-4V radio to "Radio Compass" (#2 in manual)?