Forced modifier input despite not being pressed in T16000M HOTAS

[Polonsky]

For HT16000M HOTAS scenarios (stick and throttle), modifier button was ALWAYS applied once used.

Pic 1

Pic 2:

Pic 3:

Prerequesites:

1. assign JOY_BTN2 from the throttle the as MODIFIER (pic 1)

2. assign hat on the stick (without modifier) for trim (pic 2,  just like the default DCS profile)

3. assign modifier from throttle + hat on the stick for sensor control switch (pic3)

Test Cases:

1 The control adjustment page (Expected behavior)

√ 1.1 hat on stick - jumped to the correct row for trimming

√ 1.2 modifier from throttle + hat on stick (simultaneously) - jumped to the correct row for sensor control switch

√ 1.3 hat on the stick again - jumped to the correct row for trimming

 

2 Inherent Resolve Campaign+The Syria Map, in game (Bugged, modifier is forced after single use)

√ 2.1 hat on stick - responded as trimming

√ 2.2 modifier from throttle + hat on stick (simultaneously) - responded as sensor control switch

× 2.3 hat on the stick again in all all operations - always responds sensor control switch from now on, like modifier is always pressed

 

3 Stock F-18C Campaign, in game (Bugged, modifier works in toggle manner instead of holding manner)

√ 3.1 hat on stick - responded as trimming

× 3.2 modifier from throttle, then release, then hat on the stick again - Responded as sensor control switch, as if modifier is toggled on

√ 3.3 modifier from throttle again, then release, then hat on the stick - Responded as trim again, as if the modifier is toggled off

 

 

Exported Profile: My_F18C_T16k_thr_example.diff.lua

 

PS: I've also tested JOY_BTN2 as modifier plus the hat on stick operation in A-10C II, modifier works like case I (applies if and only if pressed and hold)

Edited yesterday at 07:30 AM by Polonsky

[Lace]

There are two Modifier modes - one is hold, one is toggle.  Are you sure you haven't selected it as a 'toggle' modifier?

[Polonsky]

14 minutes ago, Lace said:

There are two Modifier modes - one is hold, one is toggle.  Are you sure you haven't selected it as a 'toggle' modifier?

Thanks for the heads up. I've checked again yet didn't find where to select toggle or hold.ption for selecting

  

[Lace]

You've selected the modifier JOY_BTN2 as a switch, so it will operate as a toggle.  Press once to switch on, press a second time to switch off.

Remove that one and add it again under the 'Modifiers' list on the left and you should be good.

[Polonsky]

17 minutes ago, Lace said:

You've selected the modifier JOY_BTN2 as a switch, so it will operate as a toggle.  Press once to switch on, press a second time to switch off.

Remove that one and add it again under the 'Modifiers' list on the left and you should be good.

Thanks for the heads up. I may report the issue to the DLC campaign designer instead to see why modifier can't be toggled off in toggle mode.

[rob10]

13 hours ago, Polonsky said:

Thanks for the heads up. I may report the issue to the DLC campaign designer instead to see why modifier can't be toggled off in toggle mode.

Honestly, from your description in the post, it's all working as expected when you have that button assigned as a SWITCH.  In the binding menus it won't hold the switch on so you don't lose your mind trying to assign it so it's only working when you have it pressed.

In your case 2, you're pressing the modifier switch which is turning it ON.  It's staying on when you release the modifier button so it's still acting as Sensor Control Switch.  You're never pressing the modifier button again so it's staying in the ON state (whereas in the next one you do press it again which is turning it OFF).

In your case 3, you're press the modifier switch which is turn it ON.  As in Case 2, when you RELEASE the button that doesn't change it's state because it's a switch and therefore it is staying ON.  So yes, it's responding as if the modifier is on because it is.  Then in your 3rd line of that one pressing the modifier button which is turning the switch OFF, so it's acting as unmodified trimmer switch.

If you bind JoyBtn2 as a MODIFIER (add it with the LEFT ADD button) it will act like you're expecting it to.  Make sure you remove it from the SWITCH column

Edited 22 hours ago by rob10

[Polonsky]

2 hours ago, rob10 said:

Honestly, from your description in the post, it's all working as expected when you have that button assigned as a SWITCH.  In the binding menus it won't hold the switch on so you don't lose your mind trying to assign it so it's only working when you have it pressed.

In your case 2, you're pressing the modifier switch which is turning it ON.  It's staying on when you release the modifier button so it's still acting as Sensor Control Switch.  You're never pressing the modifier button again so it's staying in the ON state (whereas in the next one you do press it again which is turning it OFF).

In your case 3, you're press the modifier switch which is turn it ON.  As in Case 2, when you RELEASE the button that doesn't change it's state because it's a switch and therefore it is staying ON.  So yes, it's responding as if the modifier is on because it is.  Then in your 3rd line of that one pressing the modifier button which is turning the switch OFF, so it's acting as unmodified trimmer switch.

If you bind JoyBtn2 as a MODIFIER (add it with the LEFT ADD button) it will act like you're expecting it to.  Make sure you remove it from the SWITCH column

I did press the modifier multiple times after step 3 in case 2 by repeating step 2 and step 3 in an attempt to bring back the trimming control. If it should work like a switch, it would probably work as trimming  the second time I press (or even press and hold, assuming switch is triggered upon key down stage) the modifier. It didn’t happen as far as I’ve remember. 
 

Anyway, correcting the modifier type solves my problem.