Sabre-TLA

Where were you in the mission when this happened? The altitude triggers were adjusted for the 2.5 release so you should fly at the instructed altitude. If you can record a trk file or video that would be helpful. We don't have any current bugs reported against the BFT05 mission.

Thanks for reporting that!

Good news! We found the bug that was impacting BFT04 and it also appears in BFT09. We have a fix and will be submitting it to ED for the next patch update. Thanks to all that reported it!

Try a DCS Repair as something does seem off with the way your game is performing. We recently retested TAC 11 in 2.5 and the JTAC responded fine. We intend to produce new 2.5 videos of all the missions so users can compare their experience to how the missions should play.

Ok thanks for reporting that. We will retest and see if we can reproduce it. In manual reversion you can't use the joystick to control flight only the trim. Just checked the amplified checklist and there is this note related to manual reversion: "Restrain stick to lateral neutral while actuating flight control mode switch" I suspect if your joystick is not centered then it could cause what you are describing.

Try a second call to the JTAC. Not sure why they won't respond on the first call but they typically respond on the second call (could be the game engine is still trying to figure out what to respond with). You should use TAD 12 during the mission as it's the Tactical frequency. In the early missions the FE is also your wingman (so TAD 15 would also work) but that changes later in the campaign.

The practice missions are still there. This thread explains the changes.

Not sure why it would play fine one time and then not the next. If you are late for your takeoff time you will hear the message about missing your departure time. Do you restart your computer before you try the mission? Try and limit the number of programs you have running in the background when playing as it may interact with the memory and cause the triggers to mis-behave (it only takes a 1 bit flip in the memory to have the triggers fire incorrectly). You can compare your flight to Recon Stewarts (they haven't changed much for 2.5):

If this is in 2.5, this thread has instructions how to update your logbook. If in 1.5 then the first post in this thread has similar instructions. No you don't have to have all the previous passed missions in the logbook to continue in the campaign. You could edit your logbook and start at the final mission if that was desired. Review the thread above and email us at mapleflagmissions@gmail.com if you still need help getting it sorted.

Great!

Good call! The TIC calls are the highest priority. You can send your wingmen to attack targets of opportunity if desired but the TIC calls must be addressed to pass the mission.

I believe the trk files are saved in your My Games or Saved Games folder for the version you are playing. Make sure your campaign version has the Mission Success Criteria section in the briefing. If it doesn't then re-install the campaign. You have 3 activations but they regenerate after 31 days: https://www.digitalcombatsimulator.com/en/support/faq/564/

No problems here. Try a DCS Repair.

Yes I think it will. I have no explanation for why the triggers aren't working on your system. Maybe before reinstalling play the mission again and record a trk or video and we can review it.

Make sure your video card drivers are updated and if the triggers still are not working properly try a DCS Repair or uninstall and reinstall the campaign. We just recently flew the mission in 2.5 and it worked fine on our system.

No the current coordinates in the mission briefing documentation are correct. When the campaign was initially released we had an issue with the MGRS coordinates so they were updated and corrected. If I recall you have to do a TMS Forward Long to set the SPI then you will get the Azimuth Steering Line (ASL) to indicate heading to target. The designated target SPI will also have a SPI locator line extending from it to the TVV or the TVV will have a SPI locator line extending to the target if the SPI targets is within the HUD field of view. Then you fly to align the CCRP Projected Bomb Release Line (PBRL) with the ASL and then the Time To Release Numeric (TTRN) will indicate how long until bomb drop.

HIKO isn't a specific NAV point, it's a town. So if you fly due EAST you will see it. This would be visual navigation and not something you can use the TACAN for (though Student Gap is in the same general direction so you could use that as a heading reference). When you create your own mission a line will be drawn between your aircraft and your next waypoint. Depending on where you placed your waypoint you could get nav info for it if the waypoint was placed close to a known NAV point. For example when you takeoff from Nellis you could have a waypoint at 12 nm on heading of 090. Then you could set your TACAN to reference Nellis and fly the reciprocal 090 heading until you hit 12nm. Since the F-5E doesn't have a navigation HUD it's a little more challenging but once you learn TACAN you can pretty easily get yourself to any point on the map knowing the heading and distance from a known nav point.

The 1.5.8 version was updated for the altitude triggers fix so the missions should play ok. I'm not sure if 1.5.8 will get anymore updates with 2.5 released now so any future fixes will likely only be for the 2.5 release.

We are doing some tests to see if we can improve the VR performance at Nellis for these missions. So far it appears it may be the direction the aircraft are facing at start-up (looking at Vegas) which seems to be the problem. We really want the Aggressor aircraft to take off from the real Aggressor parking area so we will keep testing to see what can be done.

Just retested BFT01 in the latest 2.5 version and shutdown worked ok for us. Email us at mapleflagmissions@gmail.com and we can help you figure out which switch is causing you a problem on your system.

Have you tried the interactive shutdown mission or the practice mission? The triggers are the same in those so it might be one switch you are having a problem with.

Congrats Max! You have a strong supporter in MFM.

Thanks for the report. We will retest and see if we can reproduce it.

No there is only the vul period time limit. We just checked the mission and the Jaguar units have Invisible(ON) so they should not be targeted. Is it reproducible? Try flying the mission again and if it still continues try a DCS Repair or re-install the campaign module and report back. It could be something changed recently in the game engine to break that trigger.

Our deepest condolences to his family and friends. He will be missed.