Module specific options: default settings don't work

[Flagrum]

I've seen this now at least a dozent times, but never saw a proper bug report about it. So, here it is:

 

When installing a new module, the tab Options -> Special -> <module> shows several parameters. Depending on the module, some of them are "set" (i.e. check boxes) or have a value not equal to "initial" or "empty".

 

These default values for those parameters are not taken into account by the respective module.

 

The typcal work-around for this problem is as follows:

1. set one of the parameters to something different than the default value (i.e. uncheck a checkbox that was checked initially)

2. leave the "Special" tab

3. go back to the "Special" tab of the module

4. change the altered value back to what it was initially (i.e. check the checkbx again)

 

Seemingly the default values that come with a freshly installed module are not correctly saved on the disk and therefore are not "seen" by the module. Only after changing something, they get properly saved to disk and can be used by the module.

 

I have seen this (i.e. reported by several communitiy members) for about every module that is out there atm. This makes me believe that this is a general DCS:W problem and not a problem of a specific module.

[uboats]

Since all the customized/tuned configurations under special tab will be saved into Saved Games/DCS/Config/options.lua. So generally, script files in Cockpit/Script or Cockpit/ folder can load the table content to get those parameters. If those parameters left as default, you may not see them in options.lua, then the content == null if forcely loaded by module which may cause problem (e.g. mig-21 cockpit no response due to 'custom livery'). But this can be avoided by simply adding an if-else condition that once the content == null, manually set the default value in the program (module script or dll) not using the one from options.lua (e.g. see livery part in latest mig-21bis/cockpit/mainpanel_init.lua).

 

TBO, I haven't meet the issue you mentioned above except one caused by mig-21 custom livery script which now has been fixed. Could you tell us which module has such problem?

Edited January 14, 2015 by uboats

[Flagrum]

Since all the customized/tuned configurations under special tab will be saved into Saved Games/DCS/Config/options.lua. So generally, script files in Cockpit/Script or Cockpit/ folder can load the table content to get those parameters. If those parameters left as default, you may not see them in options.lua, then the content == null if forcely loaded by module which may cause problem (e.g. mig-21 cockpit no response due to 'custom livery'). But this can be avoided by simply adding an if-else condition that once the content == null, manually set the default value in the program (module script or dll) not using the one from options.lua (e.g. see livery part in latest mig-21bis/cockpit/mainpanel_init.lua).

 

TBO, I haven't meet the issue you mentioned above except one caused by mig-21 custom livery script which now has been fixed. Could you tell us which module has such problem?

Thanks uboats!

 

I would probably not bet my live on it that really every single modules is affected, but my subjective experience led me to that conclusion.

 

Other cases/examples:

UH-1H:

http://forums.eagle.ru/showpost.php?p=2275949&postcount=5

http://forums.eagle.ru/showpost.php?p=2171820&postcount=5

http://forums.eagle.ru/showthread.php?p=2207912

http://forums.eagle.ru/showthread.php?p=2187327&highlight=back#post2187327

 

 

Hrm... strange. So far I could find only related issues with the Huey. Maaaaybe I was wrong and it is in fact really a (more) isolated case. I'll report back if I find other examples of other modules. :o)

[uboats]

Thanks uboats!

 

I would probably not bet my live on it that really every single modules is affected, but my subjective experience led me to that conclusion.

 

Other cases/examples:

UH-1H:

http://forums.eagle.ru/showpost.php?p=2275949&postcount=5

http://forums.eagle.ru/showpost.php?p=2171820&postcount=5

http://forums.eagle.ru/showthread.php?p=2207912

http://forums.eagle.ru/showthread.php?p=2187327&highlight=back#post2187327

 

 

Hrm... strange. So far I could find only related issues with the Huey. Maaaaybe I was wrong and it is in fact really a (more) isolated case. I'll report back if I find other examples of other modules. :o)

 

For Huey, you can have a try:

open options.lua under saved games/dcs/config/options.lua

find and delete

["UH-1H"] = {

["UHTrackIRAiming"] = false,

["weapTooltips"] = false,

},

 

then start the dcs and directly enter the mission and try the feature.