ChillNG

All my missions are designed to be really flexible in how you play them, to allow you to take different approaches, screw up, run low on fuel, get damaged. There's almost always an option available to abort the mission and RTB. So I would argue more scripting is better as it gives more player choice and reduced the chances of you getting stuck at any point. If you think you've got a specific issue with this mission if you can provide a bit more detail on what you did I'll happily run some checks.

If it helps, every single time I've had reports of triggers activating when they shouldn't it's been caused by a mod - they affect things in many mysterious ways.

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

Have you tried running a repair, or uninstalling the campaign from your module manager and then downloading again. Is there a particular doc you want?

Should be in DCS INSTALL>mods/campaigns>Cerberus North>Doc

Oh dear that is an unfortunate crash! But sounds like a good mission performance . Glad you enjoyed!

Yes the actual in game kneeboard file is embedded within the mission file itself. You can usually open the mission.miz file with WinZip (or similar program), although as campaigns are encrypted I don't know if this will still work.

See this video on how to set, IIRC wp59 is set as the bullseye automatically

It's hard to talk you through exactly, as there is quite a lot of randomization in the mission and plenty of mission reaction to what you do...so things can play out differently each time. Very broadly speaking save Rotors HARMS for when you really need them, a HARM shot will have an effect, it will either kill the target or shut it down. Once an emitter goes active try to locate it before having Rotor fire a HARM, that way if it shuts down you can follow up with a kill shot. Also avoid getting too close to a SAM unless you're going in for a kill, the jamming should reduce the engagement range to help.

Sounds like you misinterpreting the instructions. The intercept isn't on bearing 291, its 291 from bullseye (portal), this puts its inbound across the med northeast of Cyprus.

Hi thanks, great to hear! You'll find all campaign documentations at: (DCS Install location)>Mods>Campaigns>F16C First In Weasels Over Syria>Doc

Campaign Updates 22/02/24 Operation Persian Freedom: Mission 2 - Updated radio freqs. Mission 6 - Updated radio freqs. Mission 14 - Fixed radio comms issue with Miller. Operation Cerberus North: Mission 4 - Added AI unlimited fuel. Mission 5 - Modified AI behavior in CSAR task. Mission 7 - Minor adjustment to target waypoint location. Mission 8 - Modified AI behavior in Mig engagement. Mission 11 - Added AI unlimited fuel. FIWOS: Mission 1 - Reduced accuracy requirements to register kill on simulated Fan Song. Mission 5 - Fixed error in comms timing with Sentinel if player was late to check in. Mission 9 - Fixed minor error in loadout.

Do you use TACVIEW? Always useful to track where the bomb went

Hi thanks for the comments, yes if you get the 'secondary hit' message then you have achieved a kill (and scored for it). Not positive about the LGBs but sounds like one of 2 things in my experience...either missing the target so maybe a laser issue or possibly a fusing issue where there's a delay on the fuse for example and the bombs burying itself.

No problem

Why not skip the task? it is a challenge, which is why I made it optional so you won't get stuck and can still proceed with the mission.

Try either dropping a pair of bombs, or check your fusing is for tail and not nose or nose/tail. Ideally want some penetration on the bomb IIRC.

No issues, you'll either be missing a step (not setting battery to main power is a common one) or have something installed that is conflicting. Check out Bogey Dope's tutorial and make sure you're doing things the same way, if you've still got an issue after that come back to me and we'll look into it more.

Lol thanks, it's been picked up already, should be fixed in the next update

That's an Ugra thing though I'm afraid, not anything I can do about it other than add in a manual TACAN like I already have done.

I don't know if they have them in real life but the airbase doesn't have them in DCS, however there is a manually added TACAN beacon at H4 that I've put in for the campaign, it's listed in the SPINS and knee boards.

Thanks for the feedback, glad you enjoyed. Let me know if you can remember the mission the AI went a bit funny and I'll take a look. Sounds like an AI bug, but the backup triggers kicked in to compensate and make sure the mission still progressed.

So the SA-6s will shut down when the SEAD flight attacks, but will randomly reactivate later so you will need to keep an eye out for them popping back up on you. Recommended attack is to attack with Newt... I've always used a string of retarded Mk-82s on the FMA with good effect, don't like being too high over this target as it's pretty dangerous.

Fix should be in the next update, shouldn't stop you finishing the mission though in the meantime.

T-72s are as shown in the spoiler, just track north from the BMP position for about 2 miles. SA-6 will only come into play if you get out of position, stay south of phase line orange and you will be well out of it's range. On the final task when you support the TIC make sure you attack from the south as directed and avoid overflying the troops position (so fire then immediately break east) and this will keep you out of range.