ChillNG

Maybe not as a designed function, but in the past I've seen different mods conflict with random seemingly unconnected units in DCS and cause all manner of problems. Mods have many unexpected and weird effects in DCS, it's not past the realm of possibility that a weather mod is having an unexpected and unintended impact on the weather in a mission, especially right after an update. Then again of course it could be a different mod, or even a combination of mods. If anyone else has any input that is more experienced with mods than I'm sure OP would appreciate it.

I'd be highly surprised if it wasn't the weather mod having some effect, it's not an issue I've ever heard of anyone else having and it seems like too much of a coincidence. As to why it's persisting, I'm not sure, have you tried uninstalling and reinstalling the campaign as opposed to a repair?

Good to hear, thanks for the update.

Hi, glad to hear you're enjoying the campaign! The wind in this mission is set to around 25 knots at altitude, I've checked the editor settings and the update hasn't affected anything there. I've also just run a test where I let the mission play for over an hour in accelerated time, and saw no change in the wind. Do you have any mods installed? These can cause all sorts of weird unrelated effects in DCS.

Campaign Updates 24/12/24 DCS: F-16C First In Weasels Over Syria Campaign All missions - Fixed static object locations following updates to H4 airbase. Mission 10 - Added failsafes to prevent AI mid air collision triggering a mission fail. DCS: F/A-18C Operation Cerberus North All missions - Minor adjustment to campaign ATC Mission 1 - Revisited mission for various minor updates and fixes.

Found a slight trigger vulnerability - a 12 second gap where you could potentially trigger both outcomes. It's possible this is what happened so tightened the trigger up for future update.

Possibly an issue at your end if it took so long to quit/crash. There is a debrief error that can be the mission designers fault (if using certain words/symbols used in lua) but I don't think this applies here as the mission hasn't had any sort of update like this recently. If it happens repeatedly might be worth posting your logs and I can ask someone at EDs end to take a look.

If using the F10 menu it will only be at moments I've scripted for (note please make sure you are using the F10 option within the radio menu not the F2 wingman option - a common mistake), you'll be notified on a message in the top right if wingman commands are available. If you're using the correct menu and have any specific examples of an attack not working let me know and I'll take a deeper look and make sure all is working ok.

Ok thanks I'll take a look. The fight should only trigger depending on your position so wonder if you just caught the edge of the zone as you egressed. I'll check through and put more safeguards in.

Ok thanks for reporting, I'll check it out.

Try setting through the ICP instead, should be no need to ever use the backup panel.

Nothing to do with the campaigns, there's a Viper bug where sometimes data link takes a while for the AI to appear. Bogey Dope video might be out of date now, theres been some updates to the Viper since then. Don't turn on the data link and Mids switches until your INS is aligned, after that data link should work fine. I've never needed to mess with GPS time, that was a workaround for an old bug I believe.

Glad you're enjoying, great to hear! Hmm good question, if the TOT allows it I think it will probably be ok, you might be able to catch Arco running parallel to the coast on the way in. The mission triggers usually progress as you enter zones at the Silver corridor/ enter the mission area etc so you might get away with it on some missions. Worth a try, but of course its not been tested so be prepared for any ensuing problems .

They're randomised, a mix of different Sams and/or locations to keep you on your toes

Ah ok I got you, yes IIRC you must have done something slightly off during the first phase, so a 'consequence' of that is less cover on your turn to attack. It's a nice simple attack if they are around, and a very cool watch when all the AAA turns on them and opens up a path for you.

Thanks very much! Glad to hear you're enjoying! For mission 5, during the attack on the SA-6, one of the other Sword flights (Sword 3 I think) will run in and distract the AAA while you make you attack run, there is an option/space-bar press to order them to start their run, which makes things somewhat safer . Hope you enjoy the rest just as much, in my opinion the best missions are still to come!

Yeah I think it will be, I've heard of some weird graphical glitches here and there since the update.

Sounds like you didn't reply to Warden's requests so they aborted the strike. To reply you just had to press space-bar, I gave the payer the option of choosing when to reply instead of doing it automatically as chances are you could be engaged with a SAM as Warden calls you. If you don't reply at all the strike will be called off (you have 3-4 mins of leeway to respond). Hope that helps!

Thanks! Glad you're enjoying!

Lol no worries, easily done. Glad FIWOS working for you .

Excellent glad you enjoyed! There aren't any points for altitude/glide path, you must have missed something else, but if it's only 1 point it's probably in the ATC system. Full score guide is available in the vault on www.groundpoundersims.com.

Think you're talking about a different campaign...

Yes I think that's correct, TMS down x2 works as well I believe.

Hi glad to hear you're enjoying! To answer your questions: 1. Don't RTB until the mission tells you, the comms should always be clear and there will be message in the top right when it's time to leave. This will be either on the completion of the mission (successful or not) OR if you select the abort mission option form the F10 radio menu. 2. This is how the Viper works, when you slew the TGP or radar if applies an offset to the sensor point, this offset also affects your waypoints so all the symbology on the HUD will be way off. To fix it simply press CZ (cursor zero) on your HSD and the offset is cleared. 3. All H4 comms will be on COMM 2 (VHF freqs), so possible you were on the wrong radio? Cheers!

@mla306 All fixed in the latest patch, apologies once again we had to go through this.