ChillNG

The times are given in local, but sounds like you've got zulu time showing in the jet.  Can't remember how to switch between the two in the Hornet, but local for Syria is +3 hours to Zulu.
So:
 
Takeoff at 01:17 = 22:17 Z
Your TOT is 01:59 = 22:59 Z
End Vul is 02:11 = 23:11 Z
 
Hope that makes sense!

No probs, I've hosted all the docs here:
https://drive.google.com/drive/folders/1FZ8rmCuqe-pe_Ob87fLqBVXmn4SfGWb2?usp=sharing

Data link is a Viper bug in the recent update, I'll link the fix below.
As for M8, I've just trawled through the triggers and it looks like you missed the comms with Sentinel after killing the second SA-8.  Kills seems to have been triggered as the F10 options were removed and comms triggered, after this you would have had a message to contact Sentinel and press spacebar, I would guess you either missed this or accidentally cancelled it (which it is possible to do if you press backspace).
 
 

Good spot!  That one seems to have been missed by everyone for months.  Thanks for pointing it out.

From the looks of it the mission is detecting some units as killed instantly on mission start, I've seen this a few times before and every time it is has been down to mods causing a conflict with the units in the mission.  Try removing all mods and running a repair and it should solve it.  If not please come back to me and we can dig deeper.

From experience I've seen this before from mods causing conflicts with the units killed.  If you have any mods installed, please remove them and run a repair and try again.  If you don't have any mods installed or that doesn't fix it please come back to me and I'll do some investigating.
EDIT - I have just checked the mission myself as well and this didn't happen to me so I suspect a mod issue.

HI thanks, I'm glads you're enjoying and thanks for the feedback!  IIRC the intention was for you to backtrack up the runway, just an omission in the comms.

Most likely your SPI is still set to wherever you (presumably) boresighted your mavs, 2.9 introduced new SPI/SOI logic.  Go back onto TGP/WEP and TMS down a few times to clear it.

You can align once airborne without any issues, I'm currently doing it once at cruise altitude and on the way to the mission area.

No the new data link settings aren't implemented yet, they will be in the next update.  The TDOA feature (triangulation) will only be of limited use in the campaign, as it wasn't in DCS when the campaign was built so the missions aren't set up to make use of it, we use other more engaging ways of finding sams instead 🙂.

Hi, please make sure you are on the latest open beta version, sounds like that's the most likely problem.

Thanks very much, glad you're enjoying!
Overhead break is fine, but you need to avoid overflying Ruwaished at less than 7500 (IIRC) feet as per noise abatement procedure.  Violating that will cost score.

I suspect you might need to update, judging from the unknown module message on the log.  I saw the same prior to the update when the campaign was available for download in the testing branch but not yet released.  If there's a reason you're not updating I'd suggest raising a support ticket with ED to see if they can rectify it.

My pleasure, hope you enjoy the campaign!
No the new data link settings aren't in at launch, but I have updated them all today so they should be in the next patch.  Until then the data link network will work just like before the update so there won't be any issues.
TDOA however will need some testing before I implement it, my main concern is how the TDOA request affects the AI when it is sent to them.  If their assigned task is disrupted will they go back to the original task without any issues, and will it affect the timing of their tasks, which can be important.
But with all that said, as TDOA wasn't in DCS when the campaign was built there aren't actually all that many opportunities to use it, due to flight sizes and assigned roles.  So I'll see where testing goes and take if from there.

https://www.digitalcombatsimulator.com/en/shop/campaigns/f-16c_first_in_weasels_over_syria_campaign/
Should be here, it's in the e-shop but not the product section on the left of the menu bar.
 

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.