Sabre-TLA

Yes try it at 2833 as per the docs because Vaziani is about 1400+ feet above sea level and you are below the transition altitude of FL90 (9000'). Here is some info about the Transition Levels for Tbilisi region: https://airnav.ge/eaip/2020-09-24-AIRAC/html/eAIP/UG-ENR-1.7-en-GB.html If it's still a problem we will retest as ED may have made some game engine changes that effected the altitude and we can correct the trigger values in an update.

Kneeboard pics are in the kneeboard in game (k key) and all the reference docs are available under this path: <your drive letter>:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\campaigns\F-5E BFM\Doc or <your drive letter>:\Program Files\Eagle Dynamics\DCS World\Mods\campaigns\F-5E BFM\Doc

That must be something new as we did remove the triggers to stop the hard deck violation. I've seen some other user reports indicating the same thing in other campaigns so hopefully ED will make the appropriate AI changes to improve the behavior.

Fixes should be in the March 1st patch. Please report any issues after updating.

We did submit fixes to ED but it missed the last patch (we had 4 campaigns to update). Hopefully they are included in the patch planned for March 1st. After updating please report if you still see an issue.

Sorry you had so many problems with the mission. Much of it is AI related which we don't have any control over but we will retest to see why after the 5000' clearance you got a restriction failure. For the lighting you can drop flares to help with the illumination. Hopefully ED will improve the lighting going forward. We will also check the smoke on the targets. Thanks for reporting the issues. We will fix them if we can.

Yes the campaign package contains campaigns for both A-10C and A-10C II.

Ok thanks for reporting your experience. We will remove the trigger as we have no idea when ED will fix the AI.

Darn. We will have to turn off that trigger completely then as we have no idea when ED will fix the AI. Thanks for reporting your results.

Fix is in this patch update. Let me know how your experience goes.

Fix is in this patch update. Let me know how your experience goes.

Fix is in this patch update. Let me know how your experience goes.

We did a have trail formation trigger that would put the FE in trail when close to landing but with the recent AI changes this is no longer working. We have some ideas to correct it so we will provide a fix as soon as we can.

I'll have to check the log as I'm certain we had put an update in to fix it in this mission. However it's being reported more and more in other missions so we will fix it for all missions as soon as we can. We will see what we can do about including the emergency procedure details in this mission (though more emergency procedure qualification tests are included in BFT08).

No idea why your post was removed but the updates for the files were added to ED's repo on Nov 20/21st so they should be included in the next patch.

The AI behavior seems to change with each update. Normally this a good thing as we want the AI to improve but not when the change causes a collision. We will investigate and see if we can have him hold at a waypoint until you have landed.

Your most welcome. Please let us know if you have any additional feedback. We are always interested in how we can make the missions better.

This mission is to test a simulated Engine Failure After Takeoff (EFATO) so restarting the engine is a cheat as you should be trying to land with only one engine. On shutdown you should go through the normal shutdown procedure with everything turned off as per the description (however one engine will already be off). The Amplified Checklist has detailed steps for a single engine landing. Please post more questions if you have them.

Hi Everyone, ED's recent improvements to the AI have changed their low level behavior so now they break the hard-deck more frequently and cause a termination of the engagement. We have put in a fix which reduces the frequency of this occurrence however it can still occur on occasion as a hard deck violation is a valid kill. You can also still break the hard deck so watch your altitude when engaging at low level. ED have added the files into the repo for inclusion in the next patch update. Thanks.

ED has added the files to the repo for the next patch update.

ED has added the files to the repo for inclusion in the next patch update.

We will propagate the same fix we did for the F-5E Aggressors BFM campaign to this one and the FA-18C Aggressors BFM campaign as well. I'll post once the files are submitted to ED for inclusion in the next patch update.

We have developed a fix and the files have been sent to ED to include in the next patch update. We didn't remove the ability to break the hard deck but it should occur much less often. Once patched, please report if further issues are found. Thanks.

Thanks for reporting the issue. We will investigate and tweak the triggers to make it playable again. We do consider a hard deck violation a valid kill however if the AI is doing it too often then that's not realistic. Will post an update when we have a fix.

Good idea! We did retest on the weekend and though we didn't get a collision we did see the instructor get dangerously close on short final. We have some ideas to improve it so will post again once the patch is sent to ED for inclusion in the next patch release. We will propagate the fix to other missions where a similar collision risk on landing is evident.