How Do I Disable 'Mission Script Error' Pop-ups?

[Rex]

For the last month, I had a very productive script-writing stretch.  I was using Witchcraft and some other tools to debug my sessions while they were running, and I was monitoring errors via a tail via the DCS log.

Well, I updated to the latest version, and now DCS is back to stopping the sim every time and error is encountered, and popping up the box with the big red "X".    To say that it's beyond obnoxious would be an understatement, not to mention, terribly counter-prroductive.  It also renders witchcraft basically useless, and command from witchcraft will not run when a box is popped up. 

Can someone please tell me how to turn these things back off?

Thank you.

Edited October 28, 2023 by Rex

[Rex]

21 minutes ago, Rex said:

For the last month, I had a very productive script-writing stretch.  I was using Witchcraft and some other tools to debug my sessions while they were running, and I was monitoring errors via a tail via the DCS log.

Well, I updated to the latest version, and now DCS is back to stopping the sim every time and error is encountered, and popping up the box with the big red "X".    To say that it's beyond obnoxious would be an understatement, not to mention, terribly counter-prroductive.  It also renders witchcraft basically useless, and command from witchcraft will not run when a box is popped up. 

Can someone please tell me how to turn these things back off?

Thank you.

 

 

nvm I got it

 

function disableErrorBox()
    env.setErrorMessageBoxEnabled(false)
end

 

[cfrag]

Just be advised that turning the error screen off IMHO is akin to juggling with live grenades. That error screen is there for a (bad) reason: there is next to no real IDE integration with DCS, so having that annoying error screen pop up is pretty much the best (only) thing there is to defend against scripting errors. I wish there was a (much, much) better tool available for mission designers.

Btw, you may be interested in looking at this information from ED - it lists that and many more interesting tidbits. The 'turn off error' is among the first 

 

[Rex]

13 hours ago, cfrag said:

Just be advised that turning the error screen off IMHO is akin to juggling with live grenades. That error screen is there for a (bad) reason: there is next to no real IDE integration with DCS, so having that annoying error screen pop up is pretty much the best (only) thing there is to defend against scripting errors. I wish there was a (much, much) better tool available for mission designers.

Btw, you may be interested in looking at this information from ED - it lists that and many more interesting tidbits. The 'turn off error' is among the first 

 

Cool, thanks!

Oh, and BTW, I monitor the errors very closely.   I mount my DCS drive from a Mac and run a `tail -f $DCS_ERROR_LOG` either straight or with `| grep 'error'` (or whatever) as it's running.  I see the exact same errors that the popups show, only with color-coding and way better formatting.  Getting them from the log also doesn't stop witchcraft command execution, allowing me to retrieve real-time state via Witchcraft, and even test corrections in realtime.  I also have all of my script directories loaded up in IntellIJ with the Lua plugin.  I add things like Mist in as external libraries, allowing me to get code completion while being able to following codepaths through the various libs.  I'm not saying it was simple or intuitive, but over the last several months I've created a DCS development environment that functions more or less like a dev environment for any other language.  The main difference, of course, being that the code can't be run from the IDE, you actually need to fire up a simulator on a different os, on a different machine to see it. 

[Rex]

One other thing, on some missions, I have the ME call an update() function on every cycle (roughly every second), so if an error occurs in that function, or from a function called by update, it results in "box lock", where you press "Okay", only to have the next box appear almost immediately thereafter.  You have to switch back and press 'Esc' in under a second, which can be a little easier said than done, and not very conducive to debugging.

So I'm very happy that they allow us to turn it off.

Edited October 29, 2023 by Rex

[Actium]

On 10/28/2023 at 12:56 PM, cfrag said:

Just be advised that turning the error screen off IMHO is akin to juggling with live grenades. That error screen is there for a (bad) reason: there is next to no real IDE integration with DCS, so having that annoying error screen pop up is pretty much the best (only) thing there is to defend against scripting errors. I wish there was a (much, much) better tool available for mission designers.

Myself annoyed by the error popups (which will also happily freeze a dedicated server), I've written a hook script that will automatically disable the popups. However, to aid in debugging, it will send the logged error message to global chat, so errors are less likely to go unnoticed.