baltic_dragon

DCS 2.9.8.1107 Fixes in missions: Mission 02 - Increased tanker speed and pushed Menace to right side of the tanker after AAR Mission 03 - Addressed rare issue where mission would not progressed after destroying the convoy and contacting Ghost Mission 04 - Mission should nor register properly when player hits the mortars with the CBU Mission 08 - Updated briefing to instruct player to take off before his wingman Mission 09 - Fixed problem with central SA-6 not activating

And this is fixed for the upcoming patch.

Good point about EXXON. Will do. Yep! The mission should be fixed & fully working with the upcoming patch!

Hey. Mission 2 should be (finally) working as intended as of the coming patch, it is internally fixed. Though it was for the last 2 patches and both broke something new in the mission, so you never know. Let's see. As for the comms... you should be on tanker on left and 1 (element) on right radio. I don't change the comms in the mission, maybe you changed the channel by mistake? I was testing a new Kola mission yesterday for the Hornet and wrote down lots of bugs about the missing radio only to learn that by accident I switched the channel on primary....

Hm, what were they doing on the bridge? There seems to be a lot of stuff happening with the super carrier, I checked it in COB and all looked OK, hopefully it will be fine after the upcoming patch. If not - let me know!

Thanks. I'll check but most likely won't be able to fix for this update.

Haha I have a workaround plugged in for the next patch and if it is delayed I will submit a fixed version of the mission.

Both should be fixed for next update, submitted them to ED already.

Glad you like it! Not sure if at this point late spawning the flight lead wouldn't cause problems later on (you have to be very careful with DCS and AI), but I could make the FL follow tanker longer until you are ready to move on.. would that work?

Guys, there was a bug in this mission where one of the SA-16s did not activate so it was not possible to get full score. Fixed for next update & apologies for trouble.

Hey! I have no control over such issues as a mission maker, I just input the waypoints, so any problems of this kind are likely connected to DCS itself... sorry, can't help you there.

Both M2 and M3 should work fine as of next patch, unless the patch itself breaks something new (which happened a few times already). Fingers crossed it does not though!

@Kleist some of the missions were updated, but I am waiting for taxi directors to make a general overhaul of the whole campaign. Otherwise I am sure I'll have to do the whole work twice as taxi directors will surely mess up almost all of the missions initially. I will also add I/R thingie (to avoid using F-10 and SPACE BAR) to every mission plus will make sure everything else works as intended.

I've spent a few hours trying to fix it, but had no luck - the damn AI would just do some weird things and then refuse to land. For next patch I simply swapped Marauder with a brand new aircraft just before the approach (I know, not very elegant) which seems to work until I find a proper solution (or ED changes something, as this part of the mission used to work without any issues until 2 patches ago). Will keep you posted and let me know if my workaround works once it is out.

That is because there are limits to what I can do in a story-driven campaign. My bad with the scenario where player engages is I didn't put in a warning NOT to use GBU-12s. I'll do that for the next update (too late for this one). If you choose to engage together, then your character clearly states what weapons will be used. So you have a valid point there, I'll update it.

If you are on discord, please hit me up, happy to send you the updated version of the mission to check.

Thanks for the report. Honestly, I have no idea why it happens to some people (for majority it works fine). Do you have any unofficial mods installed (aircraft, VAICOMM, voice attack etc.)? Also, try to run a repair. I had a few reports like that but majority of players didn't encounter this bug and I cannot reproduce it on my end (works fine every time). Let's start troubleshooting with mods, as these may have huge impact on DLC campaigns. Let me know. EDIT: @Dsaniel I just saw that I updated this mission already but it didn't make it for the last patch. I added additional safeguards and as of next patch it should be working fine.

@Ostach @mattj96 @dimanizer thank you guys, you were right. There was a wrong trigger set, fixed for next update. Appreciate the report!

The good news @bojote is that we have M2 and M3 internally fixed and working for next update (should be next week, but who knows). I just hope it doesn't break them again.

I confirm that both should be fixed for the next patch unless it introduces some new bugs. That is becoming a vicious circle with M02 and M03: I fix it, and the patch releasing the fix introduces a new bug, so I have to fix it again with the team. Happened 3 times already...

I checked and he lands normally on my end. Did some tweaks and waiting for confirmation if it helped.

Hey @Chrispazz. I will check if the code for the bombs is set correctly, the new fuzes were added long after the campaign was released and since you cannot change them from the pit anymore, this may be a problem. A polite request for the future though - if you can add these things as separate threads in the bugs section it make it much easier for me to address / follow the issues. Will report back!

Yup, but it's a matter of preference. I think it is more realistic (and cooler) to be able to ask for the coordinates to be repeated so you can note them down. And Weasels over Syria is a great campaign!

Cool. I've built in some additional safeguards for the next patch, hope they solve the issue once and for all. Waiting for report from people testing it. Can you create a separate thread for M6? I'll note it down and check, but I haven't touched anything in the mission and it worked well before, so possibly just a glitch. EDIT: @Gilligan just checked the mission and the script. Laser is firing and can be detected, all looks good on my end, must have been a user error.

Thanks. I'll have another look at it and see if I can replicate / fix this issue. Will keep you posted.