Ramsay

Be aware the cockpit button triggers may have changed, IIRC a DCS quirk was that to check for say, button 40, you used to test argument 41 (i.e. 40+1). That seems to have changed, either due to a DCS update or the Mirage rework, and now you use argument 40 for button 40, etc. I've only looked at/tested the "INS update" training mission in detail (checks for REC and VAL button presses), but it's possible the same is true here and mission trigger(s) need to be updated. Unfortunately I'm a little busy ATM, so don't have the time to look at the Coup d'etat mission in detail. YMMV. PCN, etc. button ID's are listed in "DCS World\Mods\aircraft\M-2000C\Cockpit\clickabledata.lua" PCN Button ID's

... or have a crosswind where the headwind component is at least ~6 knots i.e. a 60° / 12 knot crosswind is equivalent to 6 knot wind blowing down the runway centerline. The exact wind value(s) require a little experimentation/testing as it varies between airports.

As said, check the wind direction and strength, there's a long standing ATC/ILS sync bug introduced with DCS 2.5.x where (most) ATC's active runway and active ILS direction desync for moderate headwinds (1-6 knots). I had no issue with Paphos RWY 29 ILS when wind was set to zero or 6 knots towards 114°T. However as expected (due to the bug), with a 4 knot wind towards 114°T, Paphos turned off it's ILS even though RWY 29 was still ATC's active runway. Tested using F-16C and DCS Open Beta 2.7.2.8494

In general HUD reflections seem improved/gone while in the air (not sure which ED patch toned it down) and are similar in strength between first and second runs of a mission. However there's a strong HUD reflection the ground. IIRC it's dependent on the lighting conditions i.e. it's not usually as noticeable. There wasn't a strong (any ?) HUD reflection until after landing. After turning off all the lights and power the HUD reflection is still there, so it looks like a bug but perhaps not the same one. Tested DCS Open Beta 2.7.3.8494 M2K HUD Reflections after landing, 2_7_3.trk

Why do you assume that, since the DCS AV-8B now carries a 4th gen TPOD, GBU-54, APKWS, etc. A cursory glance at the 2015 Marine Aviation Plan (page 44) shows the inclusion of the 4th gen TPOD and GBU-54 suggest some elements of H6.1 (2015) are now modelled in DCS.

Something looks "wrong" with the Steam pricing, AFAIK (i.e. ED store prices) the Hind and Syria map should have 20% and 30% Early Access discounts but instead of keeping their existing discount, the Summer Sale has removed them, making these "Early Access" modules, full price ? Only the Channel map has retained it's Early Access discount on Steam.

Steam's Summer Sale is said to start tomorrow - June 24 (at 10am PT / 1pm ET / 6pm BST) and end on July 8. You'll have to wait until then, to see if DCS World has any Steam discounts.

There's nothing special about the Mirage, when orienteering in my youth we used decimal degrees. For DCS, +/- 1° of the runway's true heading is more than close enough (subtracting 6° from the magnetic heading meant the player's CP (RH) true heading was 12° in error and their HUD's synthetic runway misalignment with the real very obvious). As the ADI bars and auto-pilot use the ILS signal, they are unaffected.

This was fixed in one of the recent ED updates, do you bother to check DCS before posting ? Tested Open Beta 2.7.2.7910, Single Player, Caucasus map. https://youtu.be/u7DykwYQ7bQ

Is this an intermittent bug or has it never worked for you ? I flew a 240 km route visiting all the airports round Cyprus and the moving map worked perfectly. Perhaps test a hot started Mi-24P and if it works, see if there's anything you've missed i.e. in a hot started Mi-24P, "Airspeed to Doppler" is DOWN. I 've also flown circuits around Batumi doing attack runs on targets south of the river that caused the "+" position marker to drift north of Kobuleti. As I've heard the DISS-15 loses track with steep bank angles, I assumed that was the cause but haven't investigated further*. *IIRC I set "Airspeed to Doppler" UP, which explains what I saw

TL;DR: Thank you, you've obviously put a lot of work and thought into these. I'd suggest rewording the "Page Header" conversion to • "MAGNETIC to TRUE in 2015-2025 +10 deg" to make it easy/constant with converting your chart's magnetic bearings to true and do the same for your other maps/tables. Detail Unfortunately I haven't "felt" comfortable using of your charts as, although using magnetic headings through out, the page header at top of each page lists the TRUE to MAGNETIC conversion (which wouldn't be used with your own chart/table MAGNETIC bearings) i.e. Nevada "TRUE to MAGNETIC in 2015-2025 -10 deg" ... I fear this may cause confusion* when a player unfamiliar with DCS/MagVar uses your tables to calculate a true heading, as it's easy to think True = Chart figure -10°. I'd suggest rewording the conversion to • "MAGNETIC to TRUE in 2015-2025 +10 deg" to make it easy/constant with converting your chart's magnetic bearings to true. Alternatively, perhaps make it clear that -10 deg (TRUE to MAGNETIC) only applies when converting from the F10 map ruler to MAGNETIC, however IMHO that would be less constant with the rest of your chart which uses magnetic bearings. Obviously, these are your charts and you are free to design them how you like, this is just a little (perhaps pedantic ) feedback. Notes: *Only seen one case were a player did this for the Mirage's synthetic runway i.e. CP/PD (RH/DS) input uses the runway's true heading.

AFAIK setting dead zones near the top and bottom of the Fuel Control's axis should be good enough i.e. Slider checked, deadzone = 5, Saturation X = 95

The JF-17 was released " feature complete", waiting 6 months won't bring anything to the module, you should decide based on how interested you are in the aircraft and your wallet. I haven't flown mine much (~12 hours) but that's down to the number of modules I own, rather than anything being "wrong" with the JF-17 - it's performed well in all the missions I've created for it and has some nice/unique features. It just isn't as iconic/familiar (or have the same number of DCS bugs) as the M-2000C, F/A-18C, AV-8B, etc., so doesn't get the attention it deserves from me. YMMV.

The NS430 2D "popup" works with the Hind already. Press LShift+LAlt+B and test. Eventually the Mi-24P will likely be added to "Options>Special>NS430" and you'll be able to disable the NS430 but until then, by default "LShift+LAlt+B" will always be available to call up the 2D NS430 if both modules have been installed. Support is not discontinued but the NS430 seems to have a low priority and very little (if any) resources devoted to it. Realistically the best you can hope for is an updated entry.lua, etc. to add the Mi-24P to "Options>Special>NS430" so the NS430 can be disabled if desired.

Is this not perhaps the result of a collective correlator increasing/decreasing engine RPM ?

No problem here after editing your flight's start time i.e. Mission Started at 10:00 but flight wasn't available to fly/test until 12:00 ? The Aux. UHF radio (LShift+NUM-) isn't applicable as in your mission no channel has 251.7 MHz stored. VHF/UHF Radio worked • Channel 8 8 > VLD (Radio displays "FF P 008", top display above ADI reads "128.00") or • VHF frequency 12800 > VLD (Radio displays "FF 12800", top display above ADI reads "128.00") or • UHF frequency 25170 > VLD (Radio displays "FF 25170", top display above ADI reads "251.70") then • VHF/UHF Radio Transmit Main UHF/VHF Radio Select (LShift+Num+) ... to contact Akrotiri ATC Note: The above was tested without Easy Coms enabled but Easy Coms was also test - it worked using "/" (# on UK keyboard) to contact ATC

Has the Localiser "flag" cleared on the HSI ? It sounds like the ILS signal isn't transmitting/being received. Didn't have a problem using 0 wind, would need to see the mission/track to help further. Notes: DCS still has issues turning on ILS for 1-6 knot headwinds, use zero or +6 knot headwinds when testing i.e. there is NO ILS with a 2 m/s (4 knots) wind towards 120°T There's also a known bug with the HSI GS flag in the current build but ILS still works. Shouldn't be required if the landing waypoint was created in the ME and been selected prior to the approach i.e. CP/PD (RH/DS) are auto filled for the ME "landing waypoint". If that was the issue, the synthetic runway would be missing but the ADI's ILS guidance would still work. Tested Open Beta 2.7.2.7910

AFAIK top speed (in level flight) is correct (~225 km/h), the Viviane sight adds weight and drag. IIRC the M's "high lift" blades have a speed penalty and DCS's L, Mistral and Minigun versions while having reduced weight, use the same flight model. Ka-50, Hip and now Hind, have always been faster than the Gazelle in DCS. IMHO having a UHF radio to contact AWACS, a good RWR and the NADIR more than makes up for the speed penalty. Eurocopter https://web.archive.org/web/20130219043750/http://www.eurocopter.com/site/en/ref/1967:-SA340_464-133.html

Perhaps voice/systems are WIP (it seems strange to need 115v for the EGT gauges, etc.).

Had the same, think it was due to being aggressive when applying the collective and the main rotor/engine rpm dropping and causing the generators to drop out (just like they will in the Mi-8 but there we get "generator failure" from the RI-65). I quickly adjusted my flying style, so it hasn't been a problem since.

I've flown the DCS Mi-8 for a few years and am aware of it's quirks, the main issue is when returning with Huey and Gazelle muscle memory. I find the DCS Mi-8 particularly sensitive to descent speed when transitioning to a stationary IGE hover. In the past I was able to use the variometer but these days it seems slower to react and the helicopter seems to perhaps enter a "reverse" ground effect - I know it sounds stupid but, in the past, we've seen such things (bugs) in the F5 and F/A-18C flight models. The best graph of how the current DCS VRS "feels" (to me) is this one from the Russian forum (red is DCS, blue is real). https://forums.eagle.ru/topic/95108-bagi-problemy-velikolepnoj-vosmerki/?do=findComment&comment=4678200 As a workaround for the slow variometer and VRS sensitivity (~2m/s) in certain phases of a landing, I found knowing the Mi-8's IGE Hover Rotor Blade Pitch Angle a good predictor (much in the same way you'd use torque in the Gazelle or KW).

The sound files (e.g. 'Spud 03 1s.ogg') are packed inside the .miz When DCS plays a mission the mission's files, pictures, sound files, etc. are unpacked in a temporary folder.

Same, I find making note of the blade pitch angle req'ed for IGE hover helps

DCS's AWACS BRA calls use True. So • BRA, 348 for 110, at 25000, flanking ... will be at 348°T i.e. as measured on the F10 map. However the Mirage Heading tape and radar use magnet bearings, so the contact would be seen/detected at 342°M* * Assumes a Caucasus MagVar = +6°E The kneeboard page "KNEEBOARD\IMAGES\Kneeboard_2.jpg" has a typo in the ILS frequency, can't say I noticed it as I've always referred to the briefing pages (LAlt+B).

IRL it takes 2 differently scaled paper maps, cut into 220×168mm sheets so they cover the required zone. There's a moving "+" fitted to a transparent tape that's driven by the doppler radar system. You set the scale appropriately, position the "+" at your current location on the map, the doppler system then moves the "+" as the aircraft flies. If the doppler system drifts to much, you'll adjust the "+" to be closer to your current location i.e. using visual landmarks. DCS is modelling most of the system. As it's a paper map IRL - DCS also shows the waypoints/route drawn on the map. DCS Screen shot In the above example the route leg is distance (km) 20.0 km --------------- HEADING = -------- 130° time (minutes) 04 min ? More detail about the moving map here: https://forums.eagle.ru/showthread.php?p=4456963#post4456963 In operation https://youtu.be/DH_FNrZXgms?t=1007