Ace3: Nightvision script error when changing settings

[klemmchr]

Arma 3 Version: 1.80 (stable)
CBA Version: 3.5.0.171204 (stable)
ACE3 Version: 3.12.0 (stable)

Mods:

- CBA_A3
- ace

Description:

• While being on our server this error appeared every time nightvision server settings changed. Nightvision generation 4 has been used.

Where did the issue occur?

• Dedicated

[PabstMirror]

You should be seeing a warning like this:

[klemmchr]

Yeah, that’s right. However, a mission restart is not required to see changes made to settings. Also this happened on just one machine but it still refreshed the view and applied the settings.

[jonpas]

Yes, as it says, restart required to prevent issues, and this is an issue you reported. :p

[klemmchr]

You're kinda right but I interpret this message more in that way that you should restart the mission if you have issues that settings don't get applied. This shouldn't throw script errors in any situation, should it?

[commy2]

It shouldn't. My opinion.

[PabstMirror]

You will only have problems when changing setting from 0 to non-zero or non-zero to 0.
(e.g. if you want to disable mid-mission, just drop to 0.01)

ACE has a lot of global settings like this that are just not designed to be changed mid mission
We have non-removable XEH or run specific code paths based on settings at mission start.
Making these settings changable on the fly is not trivial.

[KarlMoebius]

ACE has a lot of global settings like this that are just not designed to be changed mid mission

Is it possible to mark, indent, color code, or otherwise differentiate those in the settings to help distinguish them from semi-changeable settings?

[klemmchr]

ACE has a lot of global settings like this that are just not designed to be changed mid mission

Now as CBA settings have been introduced they maybe should be adjusted to be able to change them mid mission.

[jonpas]

Now as CBA settings have been introduced they maybe should be adjusted to be able to change them mid mission.

And you should continue reading after that statement. ;)