Florence201

I've not looked into datalinks too much, but it is set up for the UHF radio I believe

My guess here is that you didn't kill all the ground troops that are involved in this portion of the mission. I'll add a fail safe to overcome any sneaking leakers

Somehow, their landing spots have been shifted to the left. This is fixed internally and will be released with the next update. Thanks for pointing it out.

Glad this got fixed and you can continue to enjoy the campaign

I'll look into their parking spots

Glad you're enjoying it It can work seat switching, thankfully the triggers aren't affected.

Hopefully fixed in the next DCS release. Thanks for reporting this team

Don't suppose you've done any work on 2003 OIF laydown/DMPIs have you?

I've reported it internally to ED also

With the latest version released, all mission radios SHOULD NOT be on the required frequencies. This should mean, when you set them as per the comm card at mission start, the triggers should work correctly now for recognising the freqs in the radios

I'll investigate the SNAKE issue. I don't suppose you have a trk file saved off do you?

As Kharn points out, despite previous versions having the freqs already there at start up, there was a core Apache issue that meant the triggers in the ME were not picking up the radios correctly. Ai have now changed a ll pre-start freqs to jibberish, such that once you input as per the brief, all should be good. And yes, there are a number of trigger/spacebar points before you are cleared hot by the JTAC. If you do not press when required, then you will not be cleared hot (and the enemy WILL remain INVINCIBLE - Done so i can have a fire fight, but leave something for the player to still attack).

Thanks all. Definitely sounds like a core DCS issue, so reporting to them is the way forward.

Appreciate the kind words

Your pics don't seem to load for me. Any chance you can DM details, as i'm interested.

Relevant weapons were selected when the missions were built. Currently there is no warehouse to allow changes.

Hi, Did you by chance save the trk file from M12 so i can investigate? I did look into something similar and there should've been a fix released as part of yesterday's update. i'm pleased you enjoyed the campaign and really appreciate your feedback. It makes it all worth while when i receive kind words about my work/efforts. The four horsemen (well maybe not all of them) will ride again soon......

I'm sorry you feel that way, but as a campaign designer, i cannot be held responsible for a core DCS issue. Have you reported it to ED? Have you attached a screenshot or trk file for them to take a look at, or is it just at me you're venting?

Score and result are 2 different things. Score is what the game registers based on what you've hit and destroyed Result is based on designer's triggers and what needs to be accomplished to pass the mission

Please post in the Fight's On Four Horsemen area https://forum.dcs.world/forum/1255-dcs-ah-64d-the-four-horsemen-campaign/

TRYING to work out and fix why this is happening with mission results. I believe it to be a core DCS error. As for "You may shutdown or exit". you should get that at the end of every mission, as i know some players like to complete full start up and shutdown. If you exit instead, you will not penalised. I have a specific Four Horsemen forum for bugs/comments https://forum.dcs.world/forum/1255-dcs-ah-64d-the-four-horsemen-campaign/

Hopefully fixed in the next update

Please submit this as a core DCS issue, with a screenshot of the issue. I have doubled checked all M2 triggers. If you score >51 then you progress, that's standard DCS campaign scoring/progression.

OK, there's a debrief in my feedback area of the Fight's On discord. But BLUF Are you pressing SPACEBAR when told to inform JTAC that you're in hot? If not, then the visual firefight triggers i have set (so you get good visuals and still have targets to engage) will not fire. When working with JTACs you MUST follow their instructions.

Yes. You need to go to and hold at, the sneaky WP until told otherwise. The sneaky hold point is in the FP