ChillNG

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

OK no worries, let me know if it happens again and I'll dig in a little more.

Hi mate, Just ran a quick test of that part of the mission, all worked ok for me, selected F10 option and things proceeded as they should. Only variables in that trigger are selecting the F10 menu option and the radio being set correctly, so logic would suggest it was the radio setting causing the issue - worth double checking you didn't inadvertently switch something by mistake. Hope that helps!

No it won't work I'm afraid, a lot of triggers tie in to the radio settings, which are specific to the A10.

I can check, I didn't set any rtb behaviour but worth a look.

Yeah mine's been rock solid so far in 2.8, in VR as well. F18, Harrier, F16 and A10 plus PG and Syria...no crashes at all. But I'm aware of plenty who are seeing them, I know the other campaign devs have similar issues with some users getting crashes. Most likely some instability brought about from 2.8, we'll just have to keep flagging it up so ED can ID the issue and fix.

Sorry to hear this. I've been unable to reproduce myself so will have to ask ED for some support if they can ID the reasons behind the crash. Before I do can I please just check a few things with you. First confirm if you are using any mods at all, and if you are what are they, second are you in VR? If in VR it may also be worth setting preload to max and trying again, other users have reported this having solved their crashes in VR.

Thanks for the update, glad it worked out!

Thanks, appreciate the kind words. I did wonder if was F14 related as there are two Iranian F14s active at this part, but they aren't the Heatblur model, they're the years old version from ED. If you do try delaying Overlord and the crash happens really close to whenever you make contact please let me know and I can try and pin it down further.

OK thanks, yeah it is very strange, I thought it could be a specific trigger causing it if it keeps happening at the same moment. Hard to pin down if I can't reproduce, if you can recall the exact moment it happens, dialogue etc that could be useful and I can try a make version with a modified trigger.

Thick smoke is the 150th, which is where the strike eagles attacked. The target is just NW of there.

If you look at the top of this thread there's a post marked as solution (in a spoiler), that will help you find the secondary target. If you need any more help please let me know.

Are you on the latest OB, after todays hot fix? Plus any mods installed?

No IIRC I think the revetments referred to the SA-19 common locations. Always like to throw a curve ball at you as well

Not sure why the mission score is not updating, possibly a new bug introduced in 2.8, there's nothing in the campaign that directly influences this and this is score is pulled directly from the DCS engine. It shouldn't be a factor though, so long as the result is updating correctly. As for the Mig, there's a multiple ways of ending the engagement, for example you can 'time it out' as you fight to a stalemate, and I think if you drag the Mig too far north it will will abort and run for home. Sounds like you launched right before one of these triggers fired, I'll see if I can tidy it up a bit.

Hi Ryan, File will be in : DCS INSTALL --> mods -> campaigns -> FA-18C Operation Cerberus North -> Doc

Locations are in the spoiler if you want them

Could not reproduce, if anyone else experiences this crash please let me know.

Thanks for the report, it will most likely be something introduced in 2.8, nothing in the campaign missions were changed for the 2.8 update and this in a new problem. @NineLine crash logs are attached if it helps ED pin down any post update CTDs.

I'll have a check on the tank, with 2.8 it should now be warmer at the start by default, you have to opt in to the 'cold at start setting'.

Sorry to hear that, I'll see if I can reproduce and if so I'll report to ED - this will be a bug introduced to DCS core in the latest update. If you are able I'd also encourage you to make your own report as well and provide the crash log if able, in case I cannot reproduce.

First report I've had but I'm aware the other campaign devs are seeing some CTDs on 2.8 so think there is a wider issue out there.

Honestly I do not know, I just did it this way as you were already tuned to the tower and most likely a lot of players wouldn't tune to ground on landing. I haven't included ATIS in this campaign. Thanks for the comments and the interest in the campaign!

I'm not aware of any issues here, nothing reported and no changes made to the mission. Just done a quick test at this point in the mission, set 37.6 and pressed space bar and all worked as it should. Usual culprit here is radio settings not being right, double check you're on manual not preset when changing the freq. Unfortunately paid DLC cannot be multiplayer currently, this is a DCS limitation. Thanks

Its a long way away yet, second half of next year is the current ETA. It won't be Co-op as no DLC campaigns can be currently. Like all my campaigns it will use AI controlled through the F10 menu, which gives me full control over the AI and stops the dodgy behavior you normally see.