ChillNG

Ah ok fair enough, sometimes I'm never sure what's an actual bug in the Viper against something we're all doing wrong as there's that many opportunities to make mistakes in these things. By the way if you want to know where the CP is...

HTS nothing to do with having the ECM active was it? Seem to recall the ECM can interfere with the HTS but could be wrong.

@BIGNEWY or @NineLine have you guys ever come across an issue like this before? Seems to be only affecting a small number of users so I'd be surprised if it wasn't mod related, but Zachi says he has done a slow repair, and even a full re-install of DCS. We've even tried with a new version of the mission in question, with changed weather, but no success here either. Any suggestions on next steps?

For anyone reading...spoilers . So for this one the idea is to come up with an attack plan and stick to it, position is everything. The SA-6s are in a protective ring around the SA-11, but positioned carefully so that you can peel them back and create an opening. My personal method was to target the north eastern SA-6 with a mav and open a door towards the SA11. If you need to, take out the south eastern SA-6 as well and you then have most of the East side free of threats. Just be wary of going too far South towards the Golan or too far north towards Khalkhalah airbase. And stay east now, consider the line connecting the waypoints on the HSD as your safe zone, go east of here and you are back in safe territory. Now you have a route to the SA11, this is a sneaky crew, they will only activate the radar when you are in firing range, so one method is to play the bait and have Boomer hit the radar with a Harm, don't attempt this without taking out the east SA6s as you'll have too many threats otherwise. The jamming also lets you get closer to the SA11, so you can maybe send a mav it's way or lob the cbu. Don't rush, there is lots of time to do this mission, and only a short hop home so you can push it on fuel. If you wait long enough then Shade finally arrives, and more HARMS become available to help you. Hope that helps!

So I still can't reproduce this effect, can anyone try rolling back the last update and see if the same happens on the previous version?

Check out the mission 1 demo, available at www.groundpoundersims.com.

Ok thanks.

Ok thanks for letting me know, any mods in use? If so might be helpful to compare with Zachi.

I usually stay out of burner as much as possible, shouldn't need it on takeoff as the runway is nice and long. I usually climb at mil power, trying to maintain mach 0.7. I'm sure there's someone who knows a more fuel efficient way to climb in a hornet, but that's how I normally do it.

Yeah it's weird, to be honest neither do I. Obviously the missions not set at that, nor can we make winds that high in the editor so it's a bit of a mystery. Also strange that you get it after a reinstall, so wondering if something in your config/saved games is corrupted, as this wouldn't reinstall with DCS as it's a separate file location. I'll send you a different version of mission 7 in the next day or two and see if that's affected, then we'll take it from there.

There seems to be a Viper bug where the rest of your flight takes some time to appear on the data link, but so long as you set it up correctly they will appear after a while (10-20 minutes into the mission possibly). Shouldn't need to do the GPS clock fix, just during startup don't turn on the Data link or mids switch until the INS is aligned and set to Nav.

For UHF comms you need to use the the older UHF radio, not the ARC-210, this is due to the the new radio being introduced after the campaign was built and the re-assignment of lua commands associated with each radio. From your picture it looks like the UHF radio is set to the correct frequency but not set to manual, you have it on PRESET. Flick the switch to MAN and should work ok.

Following the introduction of the ARC-210 radio after the campaign was built and due to the way the campaign was originally programmed you will always need to observe the following rules: - All Comms listed as VHF AM should be done through the ARC 210 radio. - All Comms listed as UHF should be done through the original UHF radio. Do not use the ARC 210, the mission will not detect UHF frequencies on this radio. - The VHF FM radio is unchanged.

Join us on the Ground Pounder Sims YouTube channel at 18:00 UTC on New Years Day, where the Operation Cerberus North 2 official reveal will premier. There's some exciting features planned for this campaign, can't wait to share them with you!

No, so long as you maintain your saved games folder with the logbook in it then I think progress should be ok.

Not heard of any performance issues recently. While the campaign is at the the more demanding end due it's complexity, with multi threading most users are in a very good place these days. If you use TACVIEW, then disabling it can be helpful, as the high unit count can be a bottle neck for TACVIEW.

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.