Vibora

Fixed internally. It will be available in a forthcoming update.

Fixed internally. It will be available in a forthcoming update.

Right, it should be usually released in that update.

Thanks for reporting it. Done. It will be available in a forthcoming update.

This was fixed according to the description shown in the following post:
https://forum.dcs.world/topic/372604-some-options-are-always-read-from-the-mission-now-dcs-29159408

Thanks for reporting it. Fixed. It will be included in a forthcoming update.

Thanks for reporting it. Fixed. It will be included in a forthcoming update.

Txs for your report. This will be fixed in a forthcoming update.
Description of this fix:
Now global options will be taken from the server mission only for F1BE in multiplayer, and when it has 'Solo Flight' option disabled. In all other cases the options will be read locally. And of course, when a track is played, options will be read from the track.

Engine sound improvements and partial rework are planned.

Fixed internally. It will be available in a forthcoming update.

You're starting with throttle at idle. It should be in the cut position. If you had the throttle at idle, before pressing the start button, you should set it to cut and make a crank before attempting the engine start.

It is fixed, see this report:
 

This is fixed. Thank you.

Thanks for your report. Fixed. It will be included in a next update.

Fixed. Thanks for your report.
It will be included in a next update.

Try the attached mission. ED must have changed AI tanker behaviour. Now, when the first waypoint (wpt 0) coincides with the orbit initial waypoint (at least in racetrack pattern) the tanker performs a turn to re-enter the orbit. What I did was adding a new waypoint (wpt 1) where the racetrack is started.
Thanks for reporting it.
The new modified mission will be included in a next ED's update.Instant_Action_Mirage_F1EE_refuelling.miz

Thanks for your report. The BE doesn't have that switch, so there should be no binding for it in that version. Fixed internally.

Fixed internally.

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.