Sabre-TLA

It's a US Navy training manual for the T-2C. If you use your search engine for 'BFM' you might find a reference for it.

The TIC calls are the priority for TAC19. The other flights are there so you can get some experience working with other assets besides your own flight. The mission success is measured against the TIC targets destruction. For FORD flight you can detect the target they are attacking on the TAD and then slew your TGP to it so you can give BDA (via the F10 menu) - similar to TAC18. For BOAR and SPRINGFIELD flights you can clear them when desired but remember you don't want too many assets in the AO at the same time as the risk of a mid-air increases with the number of aircraft in the area. We recommend that you clear FORD flight after you have completed all the TIC targets first and then let BOAR and SPRINGFIELD fly as cleanup (since they will attack other targets of opportunity).

We were finally able to reproduce the issue that causes no response at the first waypoint. If you fly a more aggressive climb 12-15 degrees and get to altitude sooner you will hit the appropriate trigger that will give the turn instructions. We found that if you make a slow gradual climb to angels 6 it's possible to miss the trigger that supports the turn instructions. We will submit a fix to ED so that in future it won't matter what rate of climb you decide. With respect to the AI and ATC, we don't have much control over that but I can confirm that the ATC will respond to the takeoff request if you are stopped at the runway threshold. Further back you won't get a response. Also the AI will start taxiing as soon as you request clearance for taxi so you should not call for taxi clearance until you are ready to taxi and then proceed immediately. Likewise when requesting takeoff it appears the AI will start moving as soon as the ATC responds so if you watch you can avoid him running into the back of you by taking the runway as soon as you hear ATC say you are cleared. If you wait for the full ATC message before moving then the AI will run into the back of you.

You can still complete the mission if you make sure you are flying 1g level flight at moderate speed with flaps up and restrain stick to lateral neutral while actuating the flight control mode switch. Also note that in Man Reversion mode you have to use the trim to steer the aircraft. Using the joystick will cause control issues. Use very small changes. Flying in manual reversion mode is very hard so practice often but eventually you will find out what works. You can read about others who have completed it in the comments section of Recon Stewart's video (you can compare your experience to his to see how he did it).

What does the mission log say? If the downed pilot is killed you should see a log reference indicating so. I believe the night version has a few other enemy units compared to the day version so check the area closely but also listen to Chevy as they will call out threats if they see any.

Not sure why but check your FPS. We found that if it is below 8 I think then the mouse is not visible. Adjust your graphics settings to get better than 10 and you should be ok. Las Vegas seems to be the cause of the fps drop. Once you are airborne fps improves. EDIT: We also found once in the cockpit move the mouse around and that can make the blue cross visible. If you don't move the mouse first it might not appear.

You should study the killbox diagram and recognize where the boundaries are. Any targets within the boundaries are fair game. If you engage targets outside the killbox then you should hear a message when you do and it will impact your qualification.

That's great!

That's great news! Thanks!

Sorry we couldn't reproduce your issue. In our attempt he took off from runway 3R, turned towards FLEX climbed to 8000' and entered an orbit waiting to join on us (see screenshot below). Hopefully the DCS Repair or updated drivers will correct it for you. You said you uninstalled and reinstalled the campaign - did it redownload the files?

Have you updated your video card drivers and or done a DCS Repair? The AI can do funny things at times but certainly having him crash isn't desired. We will retest and see if we can reproduce it. I assume you are using the latest 2.5 OpenBeta version?

If you fly straight and level you should hit the INDIA trigger point. We just retested in the latest 2.5 OpenBeta and it worked ok for us. Maybe try updating your video card drivers or a DCS Repair or reinstall the campaign. Here is a screenshot.

We have a few other projects in the pipeline at the moment but it's still on our list. We have confirmed that it is possible to migrate the missions to the NTTR map though (without having to redo them from scratch).

Do you get the same response on the practice mission? The triggers are the same so if it's a bug in the mission you would see it in both.

Did you have the altimeter set to 2992? I think normally you get a warning then you get the terminate call 10 seconds later. There could be a small delay from when you hit the peak altitude that fires the trigger and the time you hear the call so you might have reduced altitude at the warning message and was much lower when the terminate call was actually heard. We use a formula to determine the upper and lower ranges but some tweaking might still be necessary.

Not sure what else could be the problem. Please post a trk or video of your next attempt. That might help us understand why it's not playing as expected on your system.

Yes the flight freq is 127.5 but the TAD 12 freq used for the training missions is 124. Use 124 when you want to contact UZI 11 for AFAC work.

Here is a list of items/actions that users have reported contribute or corrected trigger problems (latest at the top): 1. Icontrol DCS appears to have issues with some of the shutdown triggers. We have a mission to test your shutdown if anyone is having problems so email us at mapleflagmissions@gmail.com. Using the mouse for shutdown seems to work reliably. 2. VIACOM - user reported that JTAC would not respond when VIACOM was used. Without VIACOM JTAC responded as expected. Not sure if this contributes to other voice over response issues. 3. Video Card drivers outdated - update your video card. 4. DCS Update/Repair. 5. Reinstall the campaign. Best advice is to compare your experience to the videos and if things are not matching up check/action the items above.

Not sure why yours isn't playing the same as others. Here is BeachAV8R's writeup of the mission in 2.5. One user reported that VIACOM was causing the JTAC to not respond in a different mission. Not sure if that is a cause here.

The H's should work on the targets that are illuminated by the parachute flares (since they track optically). If you use the D's on the first 2 targets then use the H's on the remaining targets you shouldn't have to change the loadout. However the flares will die fairly quickly so you need to be quick with your targeting. Since the MAVs are fire and forget you can start turning to the other target area as soon as the MAV is locked on and fired.

Are you using Icontrol DCS or some other mod to perform your shutdown? We recently found that the Icontrol DCS has issues with the shutdown triggers - if you use the mouse they work properly. If not, try a DCS Repair, update your video card drivers or reinstall the campaign - that seems to have helped others with trigger problems.

Are you properly shutting down? Make sure you park and complete your shutdown procedure - including turning the battery off. You should be able to park anywhere on the airfield but the ending is controlled by the shutdown.

Did you shutdown by turning the battery off? In the advanced missions it's assumed you know how to shutdown the bird so make sure you park and complete your shutdown procedure - then you should hear some appropriate dialogue.

Sounds like your logbook got messed up somehow. You can manually update your logbook to restore your status following the instructions in this post. Email us at mapleflagmissions@gmail.com if you need help getting it sorted.

Yes unfortunately it missed the cutoff for the March 14th patch update as we just found it on March 13th. It should be in the next patch update though.