Sabre-TLA

To be determined but if needed we will recreate the campaigns including our new F-5E Aggressors Red Flag campaign that we have been working on for a long time and hope to release soon. Update: We have updated the F-5E BFM and ACM campaigns to use the new model/skins. This should be available in the next update. The campaigns will play even if you don't have the new upgraded F-5E model. We also got the ok to release FC versions of the campaigns which will be included in the existing DLC packages. We hope this will get some new players interested in the FC version and then hopefully they will decide to buy the upgraded model at some point but won't have to repurchase the campaign DLCs.

Thanks for the feedback. Unfortunately some of the issues our out of our control (like the ATC, and ILS issues). ED says they are working on the ATC system so hopefully that will improve over time. From a documentation perspective we have provided flight route and maneuver diagrams to try and explain what is required. What more can we add to make it clearer? For the manual reversion test you need to start the maneuver at a slow speed (above stall) and level flight. Then make very slow inputs to change the flight direction. This is because you are using the trim elements to fly in that condition. It takes alot of practice to get good at it. It is the most difficult situation to master in our opinion. Please continue to report any problems or issues and if we can fix them we will. Thanks.

Thanks for purchasing our campaign. If you have the FA-18C module installed and it is playable in other missions or campaigns then the campaign should be playable. Please consult this page for further information about activation problems and how to correct them. https://www.digitalcombatsimulator.com/en/support/faq/activation/#1525264 If the issue persists I recommend opening a support ticket with ED. Here is the link: https://www.digitalcombatsimulator.com/en/support/ Please report back on how it goes so we can alert other users if they have a similar problem. Thanks.

We have a fix for the radio issue and still working on the Helo problem. This also impacts TAC24 and TAC25 missions. They are all being updated with the fixes.

Fix has been created and submitted to ED to include in the next campaign/patch update. Let me know if you find any other problems with any of the missions. Thanks.

I looked into the ME lua files and I believe it's called victory.ogg located in the Sounds folder. There is also a defeat.ogg if you lose the campaign. I'm not sure if you have access to those folders or files anymore but I believe that is the one generating the sound you are hearing. I hope that helps. Recognize that all files are copyrighted so you would need to respect that if you are doing anything with those files.

Thanks for letting us know. We will investigate and make any changes necessary to get it working again.

I'll check the mission but if you can post a trk of your flight that would help me see exactly what is happening in your flight. Thanks. Update - I found the code that is causing the issue. I'll remove it and submit a fix to ED to be included in the next patch update.

Sorry but the music in the campaign is as you found it - from the default hornet menu. Was it possibly from a different campaign?

Sorry I missed this comment. We will update the missions to make them consistent. Unfortunately the AI is what it is. Maybe someday we will be able to control the amount of flares spent and how often.

Thanks for your kind words. For this mission you should try a Single Engine Landing. If that proves too difficult you could try an in-air engine restart as per the checklists but the intent is to attempt a landing with one engine out.

Likely a trigger didn't fire. Can you post a trk file of your flight? You can also consult Recon Stewarts video of the mission here: https://youtu.be/vsC2sphj75U?si=IHhxRbUyCkRZ2RwQ

They are in progress! I'll post again when I have more details to share.

This issue was reported previously and I believe it should be fixed in the next patch update. I'll link a thread for a reference if I can find it. Found it!

Thanks for reporting that. In reviewing our design decision we chose 94 for ARCO as we saw an AAR course reference to it but this was in error. I'll review the TACAN values and update the tanker references so there are no collisions with existing TACANs. We will propagate the fix to the other NTTR campaigns that make reference to it. Thanks again for letting us know.

I compared the triggers and you are correct that in the main campaign mission UZI has 127.5 set as the frequency. I'll do some testing and update both to make sure they align with the briefing docs. Sounds like you got all the targets so not sure why it didn't indicate a success for you. If the extraction is successful then the mission should be a pass. If you can post a .trk file of your flight we can review it. Thanks for reporting these issues. We have dozens of missions and can't test them all with each release but will work to fix issues when they are reported.

The correct frequency to use with UZI is TAD 12 (124) when talking to the UZI AFAC. I think ED changed the default helo frequency to 127.5 at one point so we used that in the Mission Data card as a reference for the helo pilot with 124 being the frequency for the AFAC. Both missions should match so we will check and correct them. If you use 124 for the AFAC it should work as expected.

Use callsigns PINPOINT and above and it works. Using callsigns FERRET and below and it's bugged. ED is aware so hopefully they will fix it soon.

I retested the TAC11 mission in the latest game engine version and had no problems with contacting UZI or killing the targets as expected. In some cases UZI did provide lasing but other times it was a TYPE 3 Attack so I self lased and everything worked as expected. Unfortunately it looks like ED introduced a game engine bug on the 3rd JTAC (Hammer 1-1). It shows up as Scout HWWV in the drop down menu and won't respond to the radio calls on 31.0 MHZ FM. I recommend skipping this mission for now and we will see if ED corrects it in the next patch. I suspect TAC12 has a similar issue (since the units and triggers are the similar) but I'll test that next to see if I get the same result.

The mark point gets created where the TGP is pointing so it would be the ground reference either at the target or beside it if you are not on the target itself. UZI is an FAC flying in a KIOWA so it's possible that he can't mark the target continuously. The JTAC grid references are just that so it's unlikely they would be exactly at the target itself but gives you a reference area to locate the target. If they can lase the target then it is a more accurate reference but as you indicate sometimes they cannot. If you call CONTACT once you have the TGP locked on a target the JTAC will confirm if it's the correct target or not.

Here is a good short tutorial on Mark Points: https://youtu.be/Pkpqpu7G-ug?si=Cx8P2lBCYvgKP0yc

Your procedure looks correct and it's good that you can contact UZI. There is a 10 SECONDS call you can use to inform the JTAC that you will ask for the LASER ON call within 10 seconds. Not sure if that has any specific implementation in the game but it's more true to SOP. We were able to contact UZI as well in our test with using our mic switches on the throttle so I don't think that is broken. Unfortunately we had to abort our test before we could confirm the lgb drop but I do recall the JTAC does have a time limit for lasing (so as not to burn out the laser). Will check that in our next test. I recommend you try to have him lase when you are close to the target area (within 30 to 60 seconds of dropping). I know lasers on the TGP have a 2 minute burn out time so I suspect the JTAC may be similar. The other option is that once you have confirmed the target you could set a mark point then do your LGB drop using your own laser on the TGP. You don't need to use the JTAC's laser if you can kill the target yourself. The mission only cares that the targets are eliminated but it's best to follow the JTAC recommendations for an accurate experience. Let us know how you make out.

Investigating...

Ok thanks for sharing the details. VAICOM has proven some mission issues in the past so I'd recommend trying without it and see what happens.

Thanks for reporting the issue. Are you patched to the latest version and do you have any MODS installed? Does it happen in the practice campaign mission too? Check to make sure you have the radios tuned to the correct frequency and using the correct radio when making the JTAC calls. The time spent flying to the range has detailed dialogue to explain each mission but you should know some basics like how to contact the JTAC through the F10 menu. Please post a trk file if you manage to reproduce it. We will retest to see if any recent game changes have impacted the JTAC functionality.