modifier defined in module is ignored by UI layer until is defined also within UI

[wju]

not sure if it is intention, but as said in title: modifier defined in module is ignored by UI layer until is defined also within UI

an example (see screenshots below)
in module:
custom modifier: VKB_BTN42
buttons binded:
VKB_BTN42+JOY_BTN21
VKB_BTN42+JOY_BTN23
VKB_BTN42+JOY_BTN24
VKB_BTN42+JOY_BTN22

 in ui layer: 
no custom modifier
buttons binded:
JOY_BTN21
JOY_BTN23
JOY_BTN24

then working butons are
JOY_BTN21 - from UI
JOY_BTN23 - from UI
JOY_BTN24 - from UI
VKB_BTN42+JOY_BTN22 - from module

not working:
VKB_BTN42+JOY_BTN21
VKB_BTN42+JOY_BTN23
VKB_BTN42+JOY_BTN24

these last three combos starts to work only when modifier VKB_BTN42 is defined in UI-layer, even though it is not used in UI.
Is it intention?

I use only two modifier DCS-wide,  i.e. it is no problem to add it to UI, but some pilots may need more...
thank you for your attention

 

Edited December 10, 2023 by wju

[Snacko]

I can confirm this, as I just tested it myself.  I have a Modifier button assigned to my Winwing throttle in the FA18.  But when I view the UI Layer, and look at the Modifier window there, my assigned button is not there.  It only shows up in the F-18 Profile.

Perhaps this is by design?  But I see no reason to not make a Modifier Global.  

[Lace]

This has always been the case.  Modifiers need to be set by module, I guess because the modifier button you choose for one aircraft may have a dedicated function in another?

Bit of a pain setting it individually, I agree it should be global by default (which could be said about a lot of assignments).

[wju]

the issue is not global/local but the behavior of UI-layer; i.e. you have to define all modifiers from all modules also in UI-layer to make settings behave correctly

[Snacko]

Yea,it would be nice if there was a checkbox to make a modifier global.  So it's our choice.

I use the same 1 modifier on everything.