baltic_dragon

The typical AI quirk.. thanks!

I confirm all flights now have correct D/L settings set up in the ME. Please check after the last DCS update.

Do you have Easy Comms set to off? Sounds like that may be a culprit here.

Hm.. maybe try to work with the audio settings and volumes. Nobody complained about this issue so far for the Gamblers campaign and when designing it the new radio system was already in place so I took good care to make sure all the transmitters are close enough to the player. Yes, sometimes there is a bit more static, but in my experience it sounds OK and nobody from the testing team nor players picked it up or complained. I dare say the missions are designed properly and there is nothing more I can do as I made sure to not have too big distances between transmitting units.. really don't know what to say here.

thanks. Will check

It is more complicated, as I didn't envisage using the GBUs against the convoy. I'll have to find a good solution for that, as even if the mission progressed, after you dropped the GBU-12s so early you will get stuck later on. This is entirely on me, obviously missed a course of action that players might take.

Correct - I didn't envisage player using bombs on trucks, which creates problems but also will make you fail the later part of the mission. At this stage I'll probably just add a note saying that you should not use the GBUs at that part of the mission, but I'll have a closer look at the triggers and voiceovers that I have and maybe will be able to find a more elegant way out. Working on it & thanks for the report!

I'll see if I can remove that fence. This is one of the unannounced changed Ugra made to the map.. I hate it when the rules are being changed during the match and it is not the first time this happens..

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.