baltic_dragon

@alboon2000 thanks, I'll check.

The F-14s won't attack, because their behavior was bugged... I'll have to check if that was fixed by ED before I enable their attack again or I will update the scoring. Thanks!

Yeah, the radios are a huge change that ED implemented which broke many of the campaigns (despite ours - campaign devs - repeated warnings). We are trying to do damage control but it affects so many missions it is a really slow and painstaking process.. thanks for the kind words though!

Hey! Can't help with the crash, in 99.9% of cases this is either on user end or DCS issue, not a campaign fault. The labels may be forced to off or dot in this one, otherwise the ingress part would get too easy as you have to spot the outpost...

OK, we will check this one.

OK, I'll give the tanker unlimited fuel, that should solve it.

They might have. And taxi directors are largely out of my hands, so in many cases there is nothing I can do when people experience problems with them... and usually for some given mission works fine, for others it doesn't. We found out that correct procedure is super important though: Battery and APU on Salute for engine start up (deck crew raises arm) Finish my start up Wait for the on screen pop up that says I can start taxiing (As per the mission brief - Designer Notes at the end) Follow Taxi director orders. Launch while all other aircraft are moving to their spots for launch

@baco30 yep, I didn't expect anyone to use guns on SA-2 so the mission counts your HARM kills, and if you don't shoot a HARM - it counts as Betsy's kill. The downside of scripted campaigns I guess..

The plane directors are out of my hands to large extent, but I haven't fully updated M10 yet so I'll look at it and hope to make it work better for next update. Bear with me a little longer please!

The taxi directors are largely out of my hands and they did work in my latest tests... Have you followed the correct procedure: Battery and APU on Salute for engine start up (deck crew raises arm) Finish my start up Wait for the on screen pop up that says I can start taxiing (As per the mission brief - Designer Notes at the end) Follow Taxi director orders. Launch while all other aircraft are moving to their spots for launch (None got stuck)

OK, I am yet to get to M10 with full update, so will fix that once I'm there (testing M8 now)

Gents, the taxi directors are completely out of my hands unfortunately we will check this one, but there is only so much I can do to fix issues like this one... the correct behavior on deck is also super important: Battery and APU on Salute for engine start up (deck crew raises arm) Finish my start up Wait for the on screen pop up that says I can start taxiing (As per the mission brief - Designer Notes at the end) Follow Taxi director orders. Launch while all other aircraft are moving to their spots for launch (None got stuck) Let me know if this helps

Thanks, I'll see if I can find the issue.

@simon111 there is a prompt telling you not to use the GBU-12s at this stage, as it may cause the mission to stall.. I am thinking how to update the mission to avoid the problem, but for now I need to count on players to follow the on-screen instructions. It is my bad though that I didn't put it in a Voiceover or something, that may be a good way out. In any case, I'd suggest to fly the mission again without using GBUs on the trucks.

@Hyperlynx I don't think I can do anything on my end, everything is set up correctly. I've noticed having issues like that in random missions in several campaigns, but it is a DCS thing I believe (as they all have everything done in the same way in mission editor).

@Rmnsvn that is a good point regarding the hard deck and looks like my oversight. Looking back I really regret adding the option here at all, as it caused a lot of trouble for players (like this one). I might just remove that option and play with the "both planes" attack scenario. I'll think how to tackle this, thanks for the report.

Yeah, I can add a note about that in the briefing, no problem. As for safeguards for triggers, you can't imagine how many there are in this (and all other campaigns), and how much time It takes to add those.. and still quite often things won't work due to DCS bugs, user errors and of course my mistakes

Glad you found out the issue. I am sorry, I know I make things harder sometimes and refuse to guide player by hand, but and the end of the day you learn much more that way (from mistakes) than from a prompt telling you what to do Hope you enjoy the rest of the campaign!

Hey @mariskal101da this looks like something on your side. Fortunately, there are a few things which you can try: The No.1 Rule with DCS Campaigns... If you have ANY mod that is NOT purchased from the DCS Store, it will probably cause issues. SRS and OpenKneeboard(Mostly VR users) seem to be ok, as we test these missions using both. Make sure to remove any and all mods before flying campaigns. (Check out OVGME, I use it daily and it works well) If you have no mods, or if removing all mods still does not fix the issue, take the following steps(Test after each step): 1) Delete fxo and metashaders2 folders in your saved games. Can get gummed up with old files. 2) Rename you DCS Saved Games folder, run DCS and let it create a new one. Close DCS and then just copy the Config folder from the old to the new so you don't lose your bindings and also copy your logbook.lua from saved games mission editor folder, that way you don't lose campaign progress. (Some mods can write to places like your scripts folder in your saved games location as an example. Also seems to help sometimes even if you never run mods at all) 3) Do a full deep repair of DCS to clear up any unwanted stuff in your main game folder. Some settings to check: 1) If you have easy comms enabled, disable it. 2) Under Gameplay options, make sure the tick box on the bottom right for "No force from mission, use min" is NOT ticked. 3) Try disabling TacView under special options. It can cause issues, usually performance, that can lead to bugs if your cores are overloaded/too busy and it misses a trigger point due to that. Let me know how it goes!

DCS 2.9.12.5336.1 (05/02/2025) All missions: fixed the S-3 skins broken with the last update. M03-07: updated mission to new standard with I/R system removing the SPACE BAR presses, seamless frequency changes, datalink etc. Fixed issues with too much radio static. M07: fixed issue with smoke not appearing on the water for target practice

DCS 2.9.12.5336.1 (05/02/2025) M02: fixed problems with Smoke refusing to refuel during the mission M03: fixed problems with wingman not refueling during the mission. M06: fixed issue with script error during the flight M10: updated push time to take into account longer launch process; fixed rare issue with first SAM hitting the player; fixed problem with flight lead flying on afterburner most of the way to the target.

DCS 2.9.12.5336.1 (05/02/2025) Missions 1-5: Updated most subtitles for better consistency; updated manual reference pages.

DCS 2.9.12.5336.1 (05/02/2025) M01: added safeguard to encounter with Backfire; added clearer instructions for the player during intercept phase M02: fixed a bug with mission stalling when Rovaniemi air defences take out enemy missiles; fixed several floating statics at Vuojarvi airstrip; fixed missing tower call. M03: updated placement of some statics at Vuojarvi; fixed Bullseye waypoint number on the kneeboard. M04: fixed placement of some statics at Vuojarvi; removed debug message; updated placement of objects at the hill (last part of mission)

Thank you Sir!

Well, no matter what I set for the AI, it sometimes does things differently than I want it to... there probably was a safety trigger built that the tactical should blow up the moment it gets damaged (as a safeguard in case AI misses or something else goes wrong). You have to learn to live with these small glitches I guess. There are a lot of things built in under the hood that normally players don't notice (as it should be) but which make the missions run much smoother.