Assigning a modifier takes a button?

[Gloom Demon]

Assigning a modifier apparently does not allow to use the assigned button as a button. I have assigned a button on my joystick to act as a modifier to the HAT to slew the target box seeker of the Shkval on S-25T, however assigning the same button as a standalone button is now impossible. Is there a reason for that, or is it a feature and not a bug?

[Nate--IRL--]

How else would it work? How would the sim know if the button press is a command or a modifier?

 

Nate

[Gloom Demon]

If the button is released without any other button pressed, than it is a command. If another one is pressed, while the first one is still on - it's a modifier :-)

[MTFDarkEagle]

If the button is released without any other button pressed, than it is a command. If another one is pressed, while the first one is still on - it's a modifier :-)

 

Does the shift key on your keyboard have any other function (apart from sticky key $%(@$*)?

[cichlidfan]

If the button is released without any other button pressed, than it is a command. If another one is pressed, while the first one is still on - it's a modifier :-)

 

How long should it wait for the release? If, for example, you are using a button on the joystick in combination with all of the main keyboard keys as CDU buttons, you might hold the joystick button while you peck out your entry on the CDU. At what point does the sim decide what you are trying to do.

 

EDIT: Also, DCS executes functions based on button presses, not releases. You don't want it to work the other way.

[Gloom Demon]

Oh, ok - just a thought I had :-)

[cichlidfan]

Btw, you can do what you want with Target and the TM Warthog! :)

 

EDIT: Though I think there still might be an issue the more I think about it.

Edited December 5, 2013 by cichlidfan

[Flagrum]

EDIT: Also, DCS executes functions based on button presses, not releases. You don't want it to work the other way.

That is not true. The config file for the mappings allows to assign a function to be performed either at button-down, button-up or just button-pressed events.

 

Think for example about the Ka-50 trimmer: the trimming occurs at button-up / button release. :o)

[cichlidfan]

That is not true. The config file for the mappings allows to assign a function to be performed either at button-down, button-up or just button-pressed events.

 

Think for example about the Ka-50 trimmer: the trimming occurs at button-up / button release. :o)

 

I should have said 'most' and 'by default'.