ChillNG

There were a few ahead of me in the queue is all. Fingers crossed for February!

Going from memory, been a while since Iast flew this one... The Bekkaa valley portion is supposed to be highly dangerous though, so it is optional for that reason.

Thanks very much, appreciate the feedback and glad you enjoyed!

Just to close this one off for future reference. M2000s do not contain data link (at least not in DCS editor). Slightly modified Mystics AI behavior and shortened fail safe. Will submit for future update.

No probs

I normally stay back as far as possible whenever the migs give me trouble, just play for time. IIRC I would hang back somewhere near the Jordanian border (this will put you around the SW edge of the SA-6 threat ring at Tha'lah AB). The AI will kill the Migs for you...Link, Newt and the F15s are all set to engage them at certain criteria and there are fail-safes built in for this if the AI goes a bit funny, failsafes are around 4-6 mins from the start of the engagement.

Are you finding the migs are engaging you? (as opposed to you going to them) I've got a feeling that I set it up so as long as it's after the push time (06:20) they will focus on the Mirages, not you, so you might be able to bypass them and be ok. But I'll do some checks and at the very least shorten the failsafe time to 06:25.

Mystic will push at 06:20 as briefed, it's possible they are having issues engaging, air to air AI has been updated quite a bit since the campaign was released. There is a failsafe built in, in case Mystic's AI fails, this will fire at approx 06:30 and destroy the Migs, so you can still proceed without getting into a fight with the Migs (intention is that you shouldn't have to), although I appreciate it might be a bit of a wait for some of you. I'll run some tests in the next few days and see if there's an AI issue.

Second half of this year is my current rough eta.

No probs, thanks. Yeah he can be a little precise, something I've improved for future campaigns.

Hi, your interaction with your wingman is scripted so you will always be told when to do it, and it changes from mission to mission.

Thanks for the comments. The moving map is useful here, this will allow you to work out where you are in regards to the two approach corridors. Once in the corridors I always set a course line for the runway (centered on the Incirlik waypoint), so long as you hold the heading in the approach corridor, the point at which you intersect the course line is Falcon/Eagle. Just note that as far as I'm aware the moving map on Syria/Hornet has been bugged for ever, it worked on all scale settings early on in campaign development but has since only worked on the 5nm scale. Hope that helps!

Ok, just make sure that the radio is set up correctly - so set to MAN / PRE as required. If the problem persists would be useful to know which mission it's happening on and if possible please send a short track from the start of the mission where you're having the problem,which should make it easy to ID what's going on. And finally just to check, are you using any mods or a program like VAICOM?

Are you using the frequency in the pdf briefing/kneeboard, this is different to the stock DCS freqs you'll see in the F10 map/ingame briefing screen.

No worries, thanks for the feedback

Thanks for letting me know, should be easily fixed.

Second half of next year is a very loose working estimate at the moment.

Check out my YouTube channel for this early preview of my in development F-16 campaign, First In - Weasels Over Syria. In this video I discuss the design philosophy behind the campaign and how I intend to bring this specialized role alive through blending scripted story driven missions with dynamic game-play systems.

Check out my YouTube channel for this early preview of my in development F-16 campaign, First In - Weasels Over Syria. In this video I discuss the design philosophy behind the campaign and how I intend to bring this specialized role alive through blending scripted story driven missions with dynamic game-play systems.

Probably not at this point, it would require a full rewrite of the triggers and A LOT of testing to even work out which ones are causing it. Multicore will probably be done by then!

Ok thanks I'll check it out.

Not much more I can do my side unfortunately, I'm guessing its down to the complexity of the triggers/later on, there isn't any one process I've ever been ab;e to pin it down to. Bring on multicore!

Nice one! That's good going, I really like flying this mission, if you stay too long over the target area things start to get a bit dicey.

How long you spending on the startup? There's enough time for a decent cold start, but you can't hang around too long and need to make the takeoff time. Data link should be working as normal unless there's a new issue with the Hornet, not changed anything for this mission recently.