Sabre-TLA

Not sure of the failure - typically it's because you didn't kill one of the briefed targets. Since you are calling BDA on the Arty target you don't have to kill everything there either. Just make sure you don't forget to clear the F-15Es for their strike and make sure you complete the BDA calls (via F10 menu). With respect to the datalink ID for the JTAC at the time the campaign was created the 01-01 IDs were the most reliable. The mission doesn't require it though but if playing in multiplayer with JTACs you might find using different ids will now work.

That's correct. You are to search for the targets identified in the briefing package (2 tank platoons and an arty unit). The FE is in UZI 1-1 OH-58 now and is watching your performance with the wingmen. The challenge is you don't have any weapons so you need to use the SADL datalink to send the targets to the wingmen and order them to attack once the targets are located. Success is getting your wingmen to kill the briefed targets. Then you call BDA for an F-15E flight which will strike the arty unit once you give them clearance.

Will check your track later today and retest the mission to see if we can reproduce the issue. Since even the practice mission isn't working right for you I suggest you try a DCS Repair as it may correct any corrupted files.

You have to have the systems setup in CCRP mode but it works best when you drop when right over the target (as opposed to trying to drop where the CCRP cue is pointing). As long as you drop within a 1nm radius of the target then it will be considered a successful drop.

Confirmed. It looks like ED pushed their altitude trigger changes into the 1.5.8 release so for now fly about 500' lower than the FE instructs for all altitudes and you should hit the triggers appropriately. We will provide updated missions to ED soon with the new altitude trigger values that we have already determined for the 2.5 release so they can get them into a future patch update.

Reviewed the track (but tracks are not reliable in many cases) and what we observed was that you got all the SAM site targets except #5. You should use your TGP to review the SAM site and ensure all units are eliminated. If you do you will hear the FE say: "SHACK! That's SIERRA HOTEL!" and then next he will say: "COLT 1-1, COLT 1-2. Good strikes on the target. The target has been terminated. Cleared to proceed to IP ADDER for your next tasking." We didn't see that in your replay but as stated the replays are not always reliable. We later heard the FE indicate you got an UNQUALIFIED so once you hear that you won't hear anything more after landing. Hope that helps. If you still have trouble email us at mapleflagmissions@gmail.com and we can help you out. BTW - really nice missile evading but watch out over the SAM target area as there is both a ZSU and a SA-9 that will engage if you get too far south of the SAM site.

Ensure you are wings level on the 060 heading at 6000' and close to 220 knots. There is a trigger that is testing for that and I suspect if you are not wings level it's not getting triggered. We are updating all the missions for the 2.5 release so will be updating the mission so it will continue even if the wings level trigger doesn't fire. Report back if you continue to have problems as recent game engine updates may have broken the trigger logic.

You can test if your switches are working properly with the Interactive Shutdown Trainer Tester mission. It will highlight the switch if it's not in the correct position within 10 seconds. It's the same checks used in that mission as in all the missions. You could try toggling the switch a few times to see if the game engine will register it. Also try a DCS Repair in case your mission file is corrupted.

Not sure why the altitude trigger wasn't working for you. I know ED is changing the altitude triggers for the 2.5 release and we are updating all the values to work with the new trigger logic. Maybe some of the changes leaked into this release - we will retest. If an update is required we will get the files fixed and sent to ED so they can release it in advance of the 2.5 release. You can compare your flight to this video (as it was originally designed):

Sounds like you got all the targets. Make sure you shut down your battery switch as that's the trigger to indicate shutdown. Not sure why it didn't work in your case. UZI should have responded on 124Mhz AM unless he already RTB'd since you went with Moonbeam first. You don't need to contact both, either one can identify the targets. You can compare your flight to this video:

The flares drop straight down as they don't have the same kinetic energy as a bomb so you are best to drop them when right over the target. You have to be within a 1nm radius of the target as well. You also have to be below 6000' as the flares will burn out if dropped higher and above 5000' or you break the Hard Deck limit. Press and hold the release button until you hear '2 Away' then keep it pressed down and if you are in the correct parameters you will hear "Well done! Target in sight". Unfortunately ED removed the flares from the bomb in zone condition so the mission has to test for your altitude and location at weapon release to register a successful flare release over the target area. We are updating the missions for the 2.5 release so we will try and improve the trigger mechanism for the flare release detection. You can replay the missions using the mission editor and locating the folder that contains the mission files. Typically its: <your disk letter>:\Program Files\Eagle Dynamics\DCS World\Mods\campaigns\A-10C AAT

No it defines a cone of fire between the two degrees. If your nose it outside the range then you won't be cleared hot as you could be pointing at a friendly or facing some other threat. So if given a FAH of 30 to 270 then make sure your attack run is on a heading between those two values. You may have other instructions for heading off the target after the attack has been made given other threat locations. With respect to the VUL time there is some wiggle room in that if you are engaging a target and the FE says your VUL time has expired you can still finish off your target engagement. In real-life the JTAC might cancel the engagement but that's not modeled in DCS from what we can tell.

Not sure why ED made that change but you can still open the missions on the D or other drives using the Mission Editor.

We just reviewed your track and it was a good attempt. You killed 6 of the 7 targets required for the mission. It appears Target 4 wasn't killed as it didn't show in the log and we suspect you killed a target close to it instead. When you hear "SHACK" that's a good indication you hit the correct target. If you don't hear that then you likely hit the wrong target. The JTAC will say that is your target but when targets are close together they can sometimes get it wrong. It's best to check the actual MGRS coordinates too. We noticed that you couldn't detect a laser on one of the targets you had in the TGP. That's a good clue that you are looking at the wrong target even though JTAC will say that is your target. The terminate occurred because you exited the range before killing all the targets or before playtime was over. The FE indication that targets were remaining was likely in reference to Target 4. You still had time to kill it before the overall mission was over but thinking that you already had killed it would have been a challenge to find it again. A few suggestions but this is the way we play vs others so to each his own: 1. Use WILCO and CANCEL when given a target tasking. WILCO to acknowledge the tasking and CANCEL to remove the target triangle on the TAD. With lots of targets it can get confusing when there are too many target triangles in close proximity. 2. When you don't get a target triangle make a WAYPOINT at the MGRS coordinates given in the nine-line. Set your STEER POINT DIAL to MISSION and select the new WP you just created. Then it's easy to slew your TGP to that area and you know you are looking at the correct MGRS coordinates (provided you entered them correctly). You could do this for all target taskings as it's a good way to verify you are looking at the right area. 3. I believe it is possible to burn out the JTAC laser as it does have a timeout (not sure exactly what it is) but your first GBU drop it appeared the JTAC stopped lasing before the weapon impacted so that might have thrown it off. The second GBU drop indicated an AUTOLASE FAILURE so likely there wasn't any laser energy detected for it to follow. You should hear the JTAC say "LASING" when they are lasing - nothing if they are not. You can self lase the target too as the mission only cares that you kill the targets. You can burn your own laser out if you have it on for too long though. 4. Given that you only have 15 mins with each JTAC you have to be efficient with your target setup and flight path. Get the TGP on the coordinates as quickly as you can while setting up for your attack run - easier said than done. Time spent on re-positioning or in searching for targets will eat into that 15 min VUL period increasing the pressure to get all the targets before the VUL period expires. You have to be quick with all your techniques. There are practice missions for each TAC mission that start at the range so you can get a sense of what is expected in each qual mission without the lengthy start-up and flight to the range. These can help improve your efficiency before flying the qual missions. Overall it was a very good attempt and I'm sure you will ace it on the next try.

Sounds like you missed some targets from the earlier JTAC engagements. We'll review your track and give some feedback. In the meantime you can compare your flight to Recon Stewart's video (the targets should be the same):

Likely you dropped while flying over an urban area. As per the brief: "Weapons release is not permitted in these zones unless specifically authorized." The triggers are setup on weapons release. Check your position before weapons release to ensure you are outside any urban areas.

Sorry you feel that way. These campaigns are Qualification campaigns so they are testing your knowledge and abilities. If you were expecting hand holding then these are not for you. Maybe with more practice you would have more success.

For heavier payloads make sure you have Water enabled.

Just replayed the mission in the current DCS WORLD release and it played fine. I had no problem picking up the laser from UZI 1-1 (very cool and it played the way I hoped it would with the FAC - Kiowa able to lase the targets). Looks like all TAC Types (1, 2 and 3) were represented as well which is exactly what we wanted when it was originally designed. Make sure you hang around CHEVY (IP) and don't zoom in too close to the target to give the TGP a chance to detect the laser energy after you call LASER ON. Once DETECT is visible on the MFCD then select SPOT and it will guide the GBU-12 right onto the target once you drop within CCRP parameters. I forgot how much fun that mission is when it works properly. Please try our suggestion and see if you can get the laser detected by staying close to CHEVY.

It should be a type 3 like in Recon's video. There could be some recent game engine changes that now allow the Kiowa's to lase but we will have to retest to be certain. The mission doesn't care how the targets get destroyed, only that they do so if you can kill it by whatever means possible the mission will continue. What version of DCS did you detect this in? Was it the OpenBeta?

We do plan on porting our F-15 BFT campaign to the NTTR once the Caucasus map version is available. It's still being developed but watch our blog for updates. You might want to check the user files section for any other F-15 training missions that others have done.

That's great!

Yes for the F-5E the comms menu can be opened with R-alt \ where in other modules comms menu is just \. Not sure why it's different. I believe the OP is reporting that the F10 menu items are not showing up not a problem with the actual comms menu itself but it's a good point to consider.

The trk replays are buggy and usually don't play properly. Yes you can try a reinstall of the campaign - you will lose an activation but they get replaced every month. Do you have any MODS installed as that can effect some modules including campaigns. Also make sure your video card drivers are up to date as that has been shown to cause issues with mission triggers. I really don't know why it's not playing properly on your system. You should open a support ticket with ED so they can investigate if the above actions don't resolve it.

Just retested in the lastest 2.1 version: 2.1.1.11762 and the F10 menu was present. The F10 menu will show after the first Radio Check call is given. Check to make sure you don't have any MODS installed that could effect the comms menu.