Vibora

We found the issue. The problem can be reproduced only if you have the tanker frequency set at channel 20 of TRAP-137B in the mission radios presets. Fixed internally. Thank you for your report.

Thank you for your reports. The bugs in Barax lights animation, as well as the problem with IFF lights, are now fixed internally.

It is a great video. Congratulations and thank you!

Thanks for the report. You may keep providing us further feedback, though we know what the issue is for long time, and we reported it, as it must be fixed by ED. It's not at Third Party devs side.

It was fixed some time ago and implemented in last update, so it is available in current Open Beta version.

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.

Glad to see you solved it.

You are welcome. Yes, we are working on Mirage F1M, though we can't provide any timeline yet.

Unable to reproduce it. We don't see any bug with communication with tanker using easy comms. The radio changes radio settings (selected radio and frequency) in easy comms.

Hi CommandT. Yes, of course we'll implement a pilot body. And external sounds improvements are in our to-do list as well.

Great. Thank you!

OK, thank you for your report. Can you report it to ED and let us know? Thank you as well.

Thank you for your report. We have fixed internally the parking brake and ADI issues.

Fixed internally.

Thank you for your report, we'll fix it.

We are unable to reproduce the bug. Please reinstall DCS completely without any mods and report us back if the problem persists. Thank you very much.

You should just feel the resistance to displacement in the stick, without any "shocks". We are investigating it and will try to find a solution ASAP, as there seems to be really an issue with FFB.

Thank you for your report, please keep us informed, providing further feedback after your configuration changes.

It should change automatically from 4L to 1L, and from 30° to 60° scan. We have fixed this internally. It will be available in a next update.

Right, edited my post.

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!

Please provide a short trk recorded in Caucasus. Thank you.

Yes, we had seen it and ofc we also fixed it.

Thank you for your report, we'll take a look at it.

This is fixed since last August 9 update.