Dudikoff

IMHO, it's more likely that it makes no sense for the MiG-29A given its short range, only 2 BVR missiles and the G-limits with an asymmetric R-27 loadout. It's more than enough to guide it to a single target via GCI that it will engage with both BVR missiles and finish off or engage any targets of opportunity with Archers before turning back as it's running out of fuel already.

I only mentioned it because R-27 was always advertised as a modular missile where you could easily swap between IR and SARH seekers on the same missile body so I suppose the same would probably work between older and newer SARH seeker heads. I mentioned Artem as they used to advertise exporting R-27 missiles. Not sure where Poland, Czech Republic and Slovakia are getting their R-27 stocks from, but I would expect it's Ukraine rather than Russia.

So you have two receiver standards, one for the original set of channel/frequencies, one for the modified. Is there a compatibility problem in combining an ER body with the original R-27R receiver if the missile is as modular as advertised? In any case, I can understand if the Russians wanted to sell the new missile only as a package with the radar upgrades, but there's nothing stopping e.g. Artem from Ukraine to offer R-27ERs compatible with the original radar sets.

What's to adapt? There's only the difference of some receiver component in the seeker head. We have an export variant here and a plausible scenario here is that they used the older spec seeker for export to owners with unmodified N019 radars.

The R-27 is a modular missile, so you could just use the R-27R seeker on the R-27ER body (if the illuminating channels couldn't be modified differently). I don't see this as a reason for not having the R-27ER on the 9.12A (depending on the scenario timeframe, naturally).

Ulan Ude factory in Russian SFSR was producing the UB variant from the start, so it wasn't really a big issue for them.

AM Dawn, perhaps?

I feel it could have been cheaper given how a bunch of stuff was already developed/researched with the FC3 and how relatively simple the plane is avionics wise. I'm planning to buy it, but I do hope the radar and IRST systems are not just copy/pasted from the FC3 with some HUD updates. Lastly, it would be great if the avionics developed for it would pave way towards some other FF FC3 modules in the future(like e.g. Su-25A and Su-27S, eventually).

I guess any powered USB 3.0 (3.1/3.2) should work, but the power adapter should have a proper power adapter connection (e.g. a 12V one) and not some USB style power connection (5V) as those are amp limited usually. For example, the MIP worked for me on a Sabrent 16-port hub and on a TP-Link UH720. Didn't work on some 7-port 3.1 hub which didn't come with a power adapter and had a USB micro 2.0 style input for extra power for charging (only two screens powered up out of three).

I've bought the same for my modded TM Cougar (NXT Ultra 2, IIRC) and it seems that the NXT provided base top is a bit tighter than the TM one (or perhaps the TM Cougar one was tighter than the Warthog one) as the adapter doesn't fit all the way in. Instead of sanding the sides of the adapter down, I've tried to simply remove the screws and connect the modded plug (as shown in the first post) directly to the base and then to tighten everything up and it works pretty well as luck would have it. This way, if/when I switch to Moza, I won't have to buy another adapter. The provided extension actually makes the whole thing more precise and it's not too tall (as other adapters go) so hopefully the added strain won't be too much for the springs (still on the original set I've received when I bought the used NXT Ultra II, but I'm not flying much). I've recently switched to a center mounted stick as I reused my Monstertech mount for the stick to mount WinWing MIP on it (gives better screen angles compared to the stock Winwing mounts, plus it's all connected together now; the only problem is where to store the thing when not in use) so this AVA adapter is a godsend (30 degree offset is just perfect for my usecase). Just posting in case anyone has a TM Cougar base still (and/or NXT Ultra II mod)..

I would add Czechoslovakia (plus Czechia, Slovakia for post Cold War period) to that list. They had interesting camos, reminiscent of the DDR ones, but different.

I'd presume the primary reason was that they didn't even have any aircraft capable of firing them in service, except for like two dozen MiG-29's of 9.13S standard.

I thought MiG-31 only used R-40TD missiles (so, IR-guided) as a backup in case the target can't be locked by radar due to heavy jamming? I don't remember seeing any reference mentioning R-40RD and I don't really see the point from an operational perspective.

Any chance the exports for pilot's radar screen and RWR could be added soon?

DCS Main Menu, e.g. F/A-18, a control change causes a reload of DCS on my system. But in any case, let's say I change something regarding the display settings, I will get into a same problem loop where a DCS will restart and then the menu will get messed up due to the Winwing display config getting messed up by DCS. Maybe instead of DCS automatically reloading, we could have a popup asking us if we want to reload and if we choose not to, it will say that the changes will only get applied after a restart. That way we (e.g. Winwing MIP owners that presumably have similar issues) could do all the changes, quit when we're done with all the changes, reapply the Winwing config, start the game.