ChillNG

Have you tried without the mod?  Even the most unrelated mods can cause random issues.  If we eliminate that as the cause I'll have to ask ED to look at the crash logs.

No you're doing it right, they are set to move off every time, it's a challenge to get them all.
However...
 
But as always in my missions you can progress without killing them all, just need them all for max score.

Hi, hot topic of discussion this one...I have a feeling the SA-18 has become more dangerous in an update since the campaign was built...but no proof of this lol.  There is quite a bit discussion on it, I and others give advice on it here:
As for F-16...see here, my campaign is almost complete:
 
 

No it is as described.  The pipes can be hard to spot though depending on FLIR settings so I put more men on the rooftop to aid spotting.
 

This was debated during testing, as the moving cloud update landed just after the mission was built.  There is an element of luck depending on how long it takes you to get to this point of the mission and how much the cloud has moved.  You can wait it out as well, if the current CAS task allows you to, and it will move on.
Final feedback from testers was we should leave as is, it's appropriately difficult for the penultimate campaign mission.  But more than happy to look at again if there's a consensus among the community.

Hi, just rechecked, all worked ok for me, so not sure what the issue is for you.  You still have to press enter on the UFC after selecting the channel to make the option add to F10 menu.  Had a check through the triggers to see if I could see any errors that would cause this but to be honest all looks fine.
If it keeps happening let me know and I'll see if we can dig deeper.

You're right they were missing.  Corrected for next patch, thanks for flagging up!
If anyone needs in the meantime - first elevation (given by Chieftain) is 5423 feet MSL.
Second (from Wolf) is 5618 feet MSL (note not all players will see this set of coordinates).

No in the last week I found an error with Spartan, problem used to be hidden away so we missed it in testing but the last update seems to have brought it to the surface.  Already fixed internally so should be in the next patch.  However this is only cosmetic, they aren't really doing the jamming, that's done under the hood in the DCS editor so the mission will still work as if they were still there.  If you're getting engaged then your either not in the jamming area of effect or you got too close to the SA-15.

Hi I couldn't replicate the issue, just tested and all worked as should.  Also checked a play-through on YouTube and that showed correct behavior as well.  The trigger conditions for this are pretty simple, it is just the radio setting so I can only assume the issue lies with this (unless you accidentally pressed backspace when the press space-bar command was awaiting input - this cancels the spacebar command I believe).  The Growlers should not be able to be shot down, did some checking and that's an error in the mission so will be corrected asap.

Are you on the open beta version of DCS? On steam you need to select this manually under properties.
 

Hi, had a look through the mission triggers, was wondering if I'd set another condition that triggers the abort...but nope nothing in there that would do that.  Is there any possibility you may have accidentally selected the abort option, or do you use anything like voice attack that would select an F10 option for you?  Only other possibility would be DCS randomly turning a trigger on on it's own, which I wouldn't rule out but I've never seen happen.

I'll have a check, there's a new bug affecting the AI when using certain weapons so I'll see what's going on.

Hi, the blind call means the JTAC can't see you, which is because you are too high and above the cloud layer.  Get below the clouds and all should be ok.  Only thing to bear in mind is that since the mission was designed moving clouds were introduced so if the clouds were actually still blocking his line of sight I don't know...might require a slight suspension of belief if not.

You should be able to spot on your TPOD, make sure you are coming in from the briefed direction as the mountains make it more challenging to get the correct viewing angle.  Higher is better as well to look over the peaks.  Exact location in the spoiler if you want it.
 
 

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 for letting me know, should be easily fixed.

Most mission you will need to hit the zone around waypoint 1 to get started.  Once handed off by departure at 25 (I think) miles you'll get a message saying go to waypoint 1.  Once you arrive there you and the wingman or flight lead will the communicate and things will get moving.  Don't skip WP1 as it will break most missions.

Hi, it should be fine, I don't think it will break anything.

Hi, apologies looks like there was a small error in the scoring trigger that slipped through the net, the trigger for arriving early was firing regardless of what time you arrived.  Fixed for a future update, thanks for reporting!

Just tested, could not reproduce.  There is nothing in the takeoff trigger that is influenced by the optional dialogue.  I wonder if you forgot to request taxi in all the excitement?  For the takeoff trigger to be added to the F10 menu you need:
- To have requested taxi (so you are assigned a runway)
- To be at the hold short for the instructed runway (05 in this case)
- be on tower frequency

I've just checked the mission, the trigger is set so that you need the radio to be set to Shadow 2-6 when you select the F10 option.  It won't activate unless the radio is set, just tested and it worked ok.  I think the problem is the message telling you to contact Devil 1-1 is a little ambiguous, D1-1 actually switched freq earlier to Shadow...so the message is technically correct but I can completely see how it would catch people out and they would attempt contact on the Devil flight channel.  I've adjusted the text for a future update.
Unfortunately you can't set the F10 option to work with just the correct comm menu.  It's easy enough to build the triggers, but the F10 menu doesn't update when its open, so pressing the correct button would open the menu and add the F10 option, but it wouldn't be visible until closing and reopening the menu, which would be too problematic I think.

The campaign folder has the 'briefing pack', which is almost identical to the kneeboards (just missing the threat pages at the end).  If you really want the kneeboards as well, I put them here a while ago when someone else asked:
https://drive.google.com/drive/folders/12MDCwnVET87R5yMe3TScbAj0DLWATZu4?usp=sharing

Bugged on Syria unfortunately, been like that for about a year now.  Used to work when the map was released.

Hi, glad to hear you're enjoying the campaign.  You have to do a bit of work to locate the Bravo 4 freq, the KB just references the freq range they are operating in, you will have to search for the exact frequency (it's only a  small range to search through - the briefing mentions searching in .100 blocks).  The freq range is on page 1 of the KB:

The exact frequency you need is hidden below:
Thanks!