myHelljumper

Hi, The D2M system works just like you said, it's an IR sensor that watches for the specific light emitted by a missile solid fuel engine. It is not triggered by jet engines because the light they produce is very different from a rocket engine. The D2M warns of every missile it detects, it can't know if the missile is aimed at the aircraft or not. As you said, it can even detect your own missile shots.

The module manual covers the data cartridge, section 19-6 page 275.

As already said the graph data is not coming from a trustable source and should be discarded.

No, previous version were intermediate tuning of the engine and FM. There is no matching of the Mirage with other "competing" modules, we are only following SME feedback and comparing the FM against known data points and procedures. A SME just confirmed to me that the low altitude behavior is correct, there is nothing to tune on the Mirage FM for now.

From the document I'm referencing (HAF-F16-Supplement), the STR for the F-16C at 5000ft with F100-PW-229 engine, 0 drag index and ~27000 pounds of fuel is just above 16°/s In similar conditions (M-2000C, full internal fuel, no stores 5000ft) the Mirage does just bellow 16°/s: Close but still under the F-16. Still, we won't tune the module to match popular belief comparison of the Mirage with other aircraft. I will nonetheless talk with our SMEs about the low altitude performances to try and see if there is something to improve. Thanks.

We compared the DCS Mirage performance with the F-16C performance document available on the internet and the Mirage STR was always bellow the F-16C, I don't know how accurate the DCS F-16C FM is regarding STR but we can't adjust the Mirage FM based on other modules.

Hi, The document used as a reference on the dcs.silver.ru website is taken from an Northrop document used to sell the F-20 to Malaysia. It's an estimation of the aircraft performance made by an entity that wants to sell its product, it should not be used as reference. There is no solid publicly available turn rate data on the Mirage 2000, our model has been tuned using aerodynamic research and SME feedback. We validated it by testing known data points and procedures like break landing patterns and unpowered glide landings. While the DCS M-2000C FM is surely not perfect and might need some adjustments, we are confident that our simulation of the Mirage 2000C is the most accurate possible. I plan on adding about 27 EM chart to the manual late when I have more time so there is no need to perform time-consuming tests like the above for the users.

Do you have any sources to compare the current DCS Mirage turn rate to ?

As said previously this break procedure was given to me by an active 2000C pilot so it's not "not correct". Different break procedures are used by different pilots/squadrons, the one you describes looks like the textbook procedure.

Yes. Only minor SNA (weapon and navigation system) change were operated over the years on the 2000C and no new weapon were added. The only AG weapon changes is the adoption of the dumb and laser guided bombs of US design. Even then, IRL the aircraft is tricked and thinks that another bomb that it knows is loaded.

No problem, happy to help.

Hi, I watched your track and tried to reproduce the issue. While the track highlight the behavior you are talking about, I was not able to reproduce the issue, even using your mission. Are you sure you are using the "Magic Slave/AG Designate/INS Position Update" command and not the "Nav Update/Magic unlock" command ? That would explain the issue you are having.

Hi, We are currently working to update the sounds but it's something that takes some time so it will not be ready soon. Thanks.

Hi, What's said above is correct, you are way too heavy to land the aircraft. Try the same maneuver but under the maximum landing weight and it should work better.

Yeah everything looks correct. I will need a track/video to understand what happens. If you are doing a video, please make sure to activate the control indicator (RCtrl+Enter). Thanks

Hi, We recently updated the engine to be much more realistic in performance as well as failure and damage modeling. What you are explaining doesn't sound right, there is something wrong with your aircraft. Could you provide us with more information ? In order to help you we would need to know: Internal/External fuel and loadout at the time you did the pattern. Speed and bank angle used in the pattern and AoA on final. Warning and cautions on the alarm panel. A video or a track would be even better. I'm suspecting that your engine switched to the secondary FADEC (CALC SEC) and you didn't rearm it. Thanks.

Hi, What @kablamomansaid is correct. In priority radar ([]), the jammer will turn itself on and off depending on the situation, trying to be the most efficient possible. Priority counter-measure (PCM) is doing the same but turning off the radar when emitting. In DCS, there is a difference between PCM and [] but it's limited by DCS jamming mechanics. There is a 3rd mode, which is PCM override. This is toggled by a HOTAS command and forces the jammer to continuously jam in PCM.t

Hi, From what I understand, the ECLAIR box was mounted with the ECLAIR pod and was the only way to interact with it as it was not interfaced with the aircraft CM system. The first deployments of the ECLAIR pod were done in a hurry and sometimes the aircraft on which it was mounted didn't even have the SPIRALE system, so that's how they were able to use it. Later, the pod was integrated with the aircraft CM system and thus the box was removed.

As you can see by the buttons on the VTB, this is not a 2000C. The Mirage 2000C never received an upgraded navigation system.

This means you are in some close combat mode, press the Weapon SystemCMD Depress HOTAS command and it will return the radar to bar search.

Hi, I've added this issue to our internal bug tracker. Thanks for the report.

Hi, These issues have been fixed, moving this to resolved. Thanks.

Hi, I have added this issue to our bug tracker. Thanks for the report.

Hi, I've fixed this issue in the manual, it should be available in its next release. Thanks for the report.