Vibora

Thanks for your report. Fixed internally.

We can't reproduce it. We tested jumping into an AI F1 and AUF2-GBU-12 works. We would need a short trk recorded in Caucasus, please. Thank you.

Fixed internally.

Added.
Thank you for your feedback and cooperation.

Thank you for the trks. After watching them, we've identified the issue.
Recently we’ve added a condition for acquisition mode, in which a target is not attempted to be locked if it is at more than 1.5 km away from the strobe current position. This condition, that reflects real behavior, was intended for manual acquisition (when there’s an attempt to get a target locked from normal search mode). And, due to a bug in the code, the same condition was applied to automatic acquisition modes, where the strobe is actually almost 7 km (6600 meters) long and where this condition should not be a factor.
It is already fixed internally.
BTW, the range for automatic acquisition modes is from 400m to 7Km, not 7 NM, and this is correctly described in our manual (page 108), as you mentioned.
Also, not breaking lock using the "telemeter/zo ne scanning switch - CENTER (OFF)" input, is a correct behavior. The lock is retained when switching to/from an auto acquisition mode. To break lock you should press the unlock button (“Backspace”).
Again, thank you all for your reports and compliments! Specially Tiromir and Kerosene, you’ve been fast catching it!

Done. It will be available in next DCS update for third parties.

We have made a new 3D model and for now it has only blue skin by default. We have sent it to ED to make it operational, so that depends on them.

Yes, we've updated the templates, you can download them in the link below (remove https://), they should be available in ED's web page shortly as well.
www.alasrojas.com/Upload/Mirage_F1_Template.rar

Right, we are working on it. It shouldn't take too long.

This is OK in our internal version, so it shouldn't be an issue next time we provide an update to ED.

This bug slipped in last update. We noticed it but windows to commit for next update are strict. It is OK in our internal build.

Fixed it. Now "Throttle Idle Detent - STOP" will only move the throttle to the "Stop" position, and "Throttle Idle Detent - IDLE" will only move it to "Idle". I.e. neither is now toggle command anymore. "Throttle Idle Detent - Idle/Stop (2 pos switch)" is also fixed. You'll obviously have to wait for a next DCS update.

Fixed the startup mission not advancing when moving the throttle from idle to stop.
Thanks for your report.
It will be included in a next DCS update.
 

This was fixed when it was reported. I've added a fixed tag to this post.

Thank you for your report. We'll take care of it.

The lights on the autopilot panel of all the versions we have implemented are different from the French ones. Same happens with many other systems. See the attached pics.
The only thing that we need to fix is the letters' colours when the buttons are illuminated, as buttons are painted white, so they should show white when buttons are off but dark when on.
nullnull

Hi Sknusk. Txs for your report, but I'm unable to reproduce it (Caucasus and Marianas maps). Maybe your aircraft is on a damaged area?

We have just added it to our internal version. It should be avialable in next standard update (not a hotfix). Thanks for your feedback.

This is already fixed and will be included in next OB update. First click on mode selector will switch to the next position.
It is normal that it jumps from one indication to another when switching the system on, as it's a magnetic indicator.

Fixed internally. Txs for your report. 

We have fixed internally the change of afterburner visual effect with engine power. We'll take a look at heat blur effect. Txs for reporting this bug.

The M never carried that configuration. That picture was made by one of our SME, that was an experiment let's say,  but it was never implemented.

Thank you Coragem for your feedback.

Thank you for your report. We'll fix it.

Thanks for reporting, we'll add it.