Jakes

Hi there @CH4Pz I just flew the mission now and had no issues. (This is after updating to the Hotfix version) Do you have any mods installed or 3rd party software? Some things to try if you still get the issue post update: 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. This may not happen on every mission, it may not even happen consistently, but it can and will catch you at some point. Every update can be different, any change in DCS Core, or to a module or any kind of assets that mod may piggyback/overwrite can cause huge issues in campaigns. 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 mine" 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.

Saint is just an A-hole. Have you read the books?

Those are mods... mods can (and probably will) ruin campaigns unfortunately. 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. This may not happen on every mission, it may not even happen consistently, but it can and will catch you at some point. Every update can be different, any change in DCS Core, or to a module or any kind of assets that mod may piggyback/overwrite can cause huge issues in campaigns. 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 mine" 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.

I just flew this mission with no issue at all. Are your tapes on? 3 switches below the IFEI. Normally I set mine to RDDI, LDDU, MAN or AUTO null

Hi @Neqqe, Here is a response from @Nix Mills on this same issue and a link to the post. Hope it helps: "Thanks for reporting this. Had a similar report on Discord. For the update that just came out today, I see that I made a mistake in updating M14 in an attempt to delay start up, taxi and departure of 307 and 309 a bit. Do this (just go with it): When you taxi out to the catapults and facing down the carrier deck (heading between 210 and 220, or so). Pull the hand brake, then release it again. 307 and 309 should now have pilots and be starting up. "

With lights off, no one is going to see you easily anyway. You should also be getting formed up on it ASAP as this is a time sensitive flight, take too long on checking and they get away.

Nice thing with this mission is that your target WP is on your DMPI. When approaching, just hit waypoint designate on the HSI and you can just fine tune the TGP. No need to re-enter it.

Hi @Papa1 Just want to confirm, are you running ANY mods or 3rd party software like Viacom or voice attack?

Did the mission just randomly end after the Marauder started its descent?? Also, are you running ANY mods?

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. This may not happen on every mission, it may not even happen consistently, but it can and will catch you at some point. Every update can be different, any change in DCS Core, or to a module or any kind of assets that mod may piggyback/overwrite can cause huge issues in campaigns. 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 mine" 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. For start ups, these are the steps I always follow and have not had issues. - Battery and APU on - Salute for engine start up (deck crew raises arm) - Finish Starting Up - Wait for the on screen pop up that says I can start taxiing OR As per the mission brief - Designer Notes at the end (Some missions have you waiting on deck a long time before you get to taxi) - Salute Again for taxi clearance - Follow Taxi director orders

Correct, myself and Pete(in this week) have flown it with no issues. @paulw10 are you running ANY mods?

Hi @Ralphk I am unable to reproduce this issue. Here are the steps I followed: - Battery and APU on - Salute for engine start up (deck crew raises arm) - Finish Starting Up - Wait for the on screen pop up that says I can start taxiing OR As per the mission brief - Designer Notes at the end - Salute Again for taxi clearance - Follow Taxi director orders - Took off, flew 240 until I passed 2.5 then flew direct WP1 - Levelled at 20k and got the pop up to check in with Knight and did so - Had to do an orbit for WM to join up and he was pretty much right there already - Mission progressed Some things to 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 mine" 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. null

Are you getting this on all 3 versions or just that RTB one?

@MichTerran Just one more bit of info, were you running the full mission or one of the shortened versions from the F10 menu at the start?

@MichTerran are you running ANY mods or 3rd party programs like Voice Attack?