"Magnum" mission went off the rails

[CH4Pz]

First half of mission was fine, launch the talds and got the SA8 first time round, then as i circled back, we were getting words for the oil pumps etc a windows box came up (with error chime), was too quick to read but i thought i seen the word "script" or "schedule", then vanished. Me being the naval aviator that i am, i continue...

 There was no F10 option to tell wingman to attack the targets either (as he was the only one with bombs). So i tried 'wingman 2>attack my target' nothing, then tried 'flight>engage mission & rejoin' to which he broke off, but instead of attacking targets he just started heading south (i think?!) and just kept flying away. asking for rejoin etc had no effect. Then after some time it came up with "tell devil you are unable with F10" so i went to that but "player" just said "engagement complete" and the dialouge played as if i hit the targets (but they were still fine in tgp), wingman still heading south, but he then also said "another gecko popped up near the city". At this point i conceded something was fubar and quit. 

Tbh, not a fan of the half in built menu for orders and half F10, i just find it confusing and when i use inbuilt orders at the wrong time in earlier missions, it just breaks the wingman, forcing me to quit & restart, i'd suggest going all F10 orders if its not too much work.

Sorry didnt get a better look at the error, so may not be much help but wanted to report

Otherwise, great campaign, i like the simplicity, i did have to learn the simrate function though haha theres some looong transits

[Jakes]

On 5/29/2025 at 2:05 PM, CH4Pz said:

First half of mission was fine, launch the talds and got the SA8 first time round, then as i circled back, we were getting words for the oil pumps etc a windows box came up (with error chime), was too quick to read but i thought i seen the word "script" or "schedule", then vanished. Me being the naval aviator that i am, i continue...

 There was no F10 option to tell wingman to attack the targets either (as he was the only one with bombs). So i tried 'wingman 2>attack my target' nothing, then tried 'flight>engage mission & rejoin' to which he broke off, but instead of attacking targets he just started heading south (i think?!) and just kept flying away. asking for rejoin etc had no effect. Then after some time it came up with "tell devil you are unable with F10" so i went to that but "player" just said "engagement complete" and the dialouge played as if i hit the targets (but they were still fine in tgp), wingman still heading south, but he then also said "another gecko popped up near the city". At this point i conceded something was fubar and quit. 

Tbh, not a fan of the half in built menu for orders and half F10, i just find it confusing and when i use inbuilt orders at the wrong time in earlier missions, it just breaks the wingman, forcing me to quit & restart, i'd suggest going all F10 orders if its not too much work.

Sorry didnt get a better look at the error, so may not be much help but wanted to report

Otherwise, great campaign, i like the simplicity, i did have to learn the simrate function though haha theres some looong transits

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.

[CH4Pz]

14 hours ago, Jakes said:

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.

I only play campaigns, so no mods etc installed. I dont usually have easy comms on, although i know for a while it kept re-enabling itself, but i think that was the launcher, which ive disabled also! Tacview may be on there, i never really use it though, will check that its disabled.

 

Some nice little tips in there though, i will try the mission again, if i still have issues will try this list and report back, thanks Jakes

[CH4Pz]

16 hours ago, Jakes said:

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.

So just updated to the latest hotfix patch (DCS 2.9.16.10973), and while it did play a little different this time, it was similar result, but fortunately i was able to capture the error. So the error comes up, when the SA8 comes online (after talds), or possibly when i fire on it, and as mentioned the error stayed in place this time so i screen capped it, but after i clicked ok, it asked me to report to devil (as i splashed it), but after trying approx. 10 times, the command wouldnt tell devil, it just closes the comm menu, then obviously mission couldnt progress. 

So last time the mission kept going, and told me to take out the oil rigs, but i was able to report destroying the SA8 that time. Anyways heres the error 

Edited yesterday at 05:38 AM by CH4Pz

[CH4Pz]

oh and fwiw, easy comms was off, tacview isnt installed, and "force my options" was also unchecked

[CH4Pz]

So managed to get the mission to work as intended.

Following Jakes advice:

1.deleted fxo & metashader2

2.Ran long repair with "find additional files after" ticked (most likely the solution)

3.Up until now i had released the talds at 30 & didnt turn right till 15-20 out from wp5, then when the 8 came online i turned in left and attacked. This run when 2 said "ready for right turn", basically immediately after releasing TALDs i turned right, and didnt run in until a full circuit, and actually found there was extra dialogue in between, so not sure if this was causing the issue either?

I just realized ive had to run repair after the last probably 3-4 updates, so maybe theres a core issue there, but regardless, heres a solution if anyone else gets this problem 

[Nix Mills]

On 6/1/2025 at 3:28 PM, CH4Pz said:

So just updated to the latest hotfix patch (DCS 2.9.16.10973), and while it did play a little different this time, it was similar result, but fortunately i was able to capture the error. So the error comes up, when the SA8 comes online (after talds), or possibly when i fire on it, and as mentioned the error stayed in place this time so i screen capped it, but after i clicked ok, it asked me to report to devil (as i splashed it), but after trying approx. 10 times, the command wouldnt tell devil, it just closes the comm menu, then obviously mission couldnt progress. 

So last time the mission kept going, and told me to take out the oil rigs, but i was able to report destroying the SA8 that time. Anyways heres the error 

I'd have thought that was an impossible bug to create. The error you got was because it was trying to calculate the bearing to the Gecko the moment it fires at the decoys, so that Shadow can call it out. It appears that you'd have somehow managed to destroy the Gecko at the same time it fired its first missile. 

Anyway, the script error you got should not have had any impact on your ability to complete the mission. I have however created a failsafe for this now.