ChillNG

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

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

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

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

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

Campaign Update 04/12/24 Last Out Weasels Over Syria II released! FIWOS - All missions updated with fixes after issues with Syria map update. Persian Freedom - Mission 16, adjusted kill conditions for mortar team in on call tasking.

Yep, and believe me we've been telling ED that as well. Patch announced for tomorrow (3rd December).

Next update is very close (unless it slips again) so hopefully all will be patched very soon. If you really want to have a go at it yourself, you can in the editor, but you won't be able to play the missions from the campaign menu, you will have to edit them and launch from the editor itself due to encryption/copy protection. You will need the mission files, located in your DCS INSTALL\MODS\CAMPAIGNS\WEASELS OVER SYRIA. There should be no static objects with 60 feet of the edge of the H4 runway, this means deleting some of the parking area (helipads) I placed down at the 10 end of the runway, possibly pushing back the aircraft on the ramp and slightly moving back the TACAN beacon (it's hidden so you need to check 'show hidden units' in the View Unit List). Just H4 for this campaign.

You'd still lock up on the HAD to direct your TGP to the SAM and cue your Mavs/JDAMs.

Oh wow I did not realise you could do that now! Top advice

IIRC there are conditions where the HAD won't lock onto a target, having the mark point page up on the DED is one of them so could be the culprit.

Wait for the next update for the fix, it's due soon.

Yes I believe so. Might be worth loading the mission from the mission menu instead to avoid that happening.

Just waiting for ED to release their patch, the fix will be in it. Was hoping the patch would be out by now but testing is still ongoing.

H4 airbase has an issue as of the last update to DCS, preventing the AI from taking off. This is fixed internally and awaiting the next patch from ED, which should be very soon.

That's the MGRS coordinates, an alternative way of doing coordinates. The Viper can use them, but I tend to stock to the lat/long the Viper defaults to. https://en.wikipedia.org/wiki/Military_Grid_Reference_System

Yep, apart from the fake refuelling break between parts 1 and 2, all AAR is for real if you want to use it.

There's some randomisation in the campaign for enemy locations, that's probably what you're seeing.

The fix is on the next update, hasn't landed yet but should be very soon. Cerberus North is not affected.

Not exactly sure what caused the issue, but we've seen an issue with H4 airbase specifically where the AI won't taxi if there are any ground units/statics with 60 feet of the runway. This was introduced with the last update. Thankfully a very easy fix, just required moving a few objects. I don't know if this is the cause or not but H4 itself appears to have moved by a few feet, you can tell as all the statics are now slightly out of position and the player staring position is slightly in the dirt off the taxiway in some missions. No idea if Ugra is fixing or not, they never tend to say a lot publicly, I would recommend making changes in the editor yourself.

Not allowed to say, but hopefully very soon.

It's fixed for the next update, changes to the Syria map caused some issues with H4 airbase.

Join the queue . ED will release the update when it's ready, unfortunately until then we have to wait.

You'll need to roll back earlier, .2406 was a hot fix for the update in question. You will need to go back to 2.9.8.1214 I would think.

Good spot, thanks!