Thrustmaster Combined Full DX Mapping (extending the 32 DX buttons limit)

[Lipfert]

Been using v2.4 Complex for months now and today I got this error message modules/MOdDXExt.tmh at line 60 Compile error. Very odd.

[sedenion]

4 hours ago, Lipfert said:

Been using v2.4 Complex for months now and today I got this error message modules/MOdDXExt.tmh at line 60 Compile error. Very odd.

Di you updates drivers or something ? Except you modified the source file by mistake, there no reason an error "emerge" from nowhere...

[Lipfert]

3 hours ago, sedenion said:

Di you updates drivers or something ? Except you modified the source file by mistake, there no reason an error "emerge" from nowhere...

Sedenion,

100% agree

Besides Windows 10 updates, nothing has been changed in TARGET or the Full DX profile. It's very bizarre, the whole reason I went to your profile was to keep this from happening.

Version is v.3.0.23.1205 for TARGET Script Editor.

Full DX Mapping Script Version is 2.4 (2023-10-24)

Compile Error:

Compiling script: Run_Complex.tmc

Compile Error:Identifier name expected in modules/ModDXExt.tmh at line 60

Line 60 in ModDXExt.thm is: define DX65.........3064

I'll remove TARGET and reinstall, other profiles that I've built are still working ok.

Edited March 17, 2024 by Lipfert
More detail

[sedenion]

1 hour ago, Lipfert said:

Sedenion,

100% agree

Besides Windows 10 updates, nothing has been changed in TARGET or the Full DX profile. It's very bizarre, the whole reason I went to your profile was to keep this from happening.

Version is v.3.0.23.1205 for TARGET Script Editor.

Full DX Mapping Script Version is 2.4 (2023-10-24)

Compile Error:

Compiling script: Run_Complex.tmc

Compile Error:Identifier name expected in modules/ModDXExt.tmh at line 60

Line 60 in ModDXExt.thm is: define DX65.........3064

I'll remove TARGET and reinstall, other profiles that I've built are still working ok.

Try to re-download script and re-try... I don't see the problem...

[Lange_666]

Just out of curiosity I gave it a go also (but i don't use it normally)

I'm having exact the same problem as Lipfert

Compile Error:Identifier name expected in modules/ModDX++.tmh at line 60

Line 60 reads: define DX65         3064

Edited March 18, 2024 by Lange_666

[sedenion]

Ok, solved the mystery an released a new 2.5 version. Here is what happen:

Since TARGET 3.0.23.1205_rev1 Thrustmaster finally implemented its "Thustmaster Combined" virtual device with 120 HID buttons (DX buttons) out of the box, making the "Extend DX Module" of this script set de facto obselet on its historical core intent. This is also why the "Extend DX Module" header file throw an error at "line 60" : the DX65 to DX128 are now already defined in the core TARGET's header files.

The good news is that you can now Assign up to 120 DX buttons natively from TARGET Script Editor but also TARGET GUI, you are free to create your own custom mapping with 120 buttons and you can get rid of my script set If you still love my mapping setup you can download and use the fixed version for TARGET 3.0.23.1205_rev1 here:

https://www.digitalcombatsimulator.com/fr/files/3318341/

Edited March 18, 2024 by sedenion

[Lipfert]

5 hours ago, sedenion said:

Ok, solved the mystery an released a new 2.5 version. Here is what happen:

Since TARGET 3.0.23.1205_rev1 Thrustmaster finally implemented its "Thustmaster Combined" virtual device with 120 HID buttons (DX buttons) out of the box, making the "Extend DX Module" of this script set de facto obselet on its historical core intent. This is also why the "Extend DX Module" header file throw an error at "line 60" : the DX65 to DX128 are now already defined in the core TARGET's header files.

The good news is that you can now Assign up to 120 DX buttons natively from TARGET Script Editor but also TARGET GUI, you are free to create your own custom mapping with 120 buttons and you can get rid of my script set If you still love my mapping setup you can download and use the fixed version for TARGET 3.0.23.1205_rev1 here:

https://www.digitalcombatsimulator.com/fr/files/3318341/

 

sedenion,

Fantastic and thank you for the amazing work. I think my issue is related to my attempt to get the toe brakes working with my VKB Mk.IV pedals, I didn't even notice the _rev1 release.

S!

Edited March 18, 2024 by Lipfert
Additional Information

[Lange_666]

7 hours ago, sedenion said:

Ok, solved the mystery an released a new 2.5 version. 

Works fine now.

[jonsky7]

On 3/18/2024 at 10:24 AM, sedenion said:

Ok, solved the mystery an released a new 2.5 version. Here is what happen:

Since TARGET 3.0.23.1205_rev1 Thrustmaster finally implemented its "Thustmaster Combined" virtual device with 120 HID buttons (DX buttons) out of the box, making the "Extend DX Module" of this script set de facto obselet on its historical core intent. This is also why the "Extend DX Module" header file throw an error at "line 60" : the DX65 to DX128 are now already defined in the core TARGET's header files.

The good news is that you can now Assign up to 120 DX buttons natively from TARGET Script Editor but also TARGET GUI, you are free to create your own custom mapping with 120 buttons and you can get rid of my script set If you still love my mapping setup you can download and use the fixed version for TARGET 3.0.23.1205_rev1 here:

https://www.digitalcombatsimulator.com/fr/files/3318341/

 

Again, thanks for your work with this.

I was having a problem with DCS with a couple of switches, it seems to add LCtrl as a modifier for some of the switches and this is where it goes wrong. It seems DCS doesn't always "press" LCtrl when the switch is actioned, so the input doesn't go through.

Looking in the event viewer, all the switches seem to work instantaneously, so I don't think it is Target or your script. 

Any ideas please?

 

Edit: Well this is weird, thought I would do some testing and I found out that only buttons 16. 17. and 18 get the modifier added.
If I remap those switches to some other number, no modifier is added. WTF

Edited September 11, 2024 by jonsky7

[sedenion]

6 hours ago, jonsky7 said:

I was having a problem with DCS with a couple of switches, it seems to add LCtrl as a modifier for some of the switches and this is where it goes wrong. It seems DCS doesn't always "press" LCtrl when the switch is actioned, so the input doesn't go through.

What problem ? Adding LCtrl, where, how ? What are you talking about ?

6 hours ago, jonsky7 said:

Any ideas please?

Unfortunately, no, because I understand nothing. What did you want to Achieve ? What was the encountered problem ? What did you trying and why ? What are you doing with "LCtrl", what the point ?

[jonsky7]

37 minutes ago, sedenion said:

What problem ? Adding LCtrl, where, how ? What are you talking about ?

Unfortunately, no, because I understand nothing. What did you want to Achieve ? What was the encountered problem ? What did you trying and why ? What are you doing with "LCtrl", what the point ?

When I was binding certain switches to functions in DCS, after clicking on the box I wanted to assign. When I pressed the switch to assign it, sometimes a modifier would pop in all by itself. This was namely LCtrl.

So for example, when I tried to set the TMW Pinkie switch, instead of it just coming up with BTN17, it would say it was bound to LCtrl+BTN17.
I hadn't pressed LCtrl at all.

It was only doing it with 3 "Buttons", the ones that were BTN16, BTN17, and BTN18.

So I tried the latest version of your .tmc, and it was still doing it. But BTN16/17/18 were on different switches!!

So I used the latest Target GUI and configured all the switches myself, AND DCS WAS STILL ADDING LCtrl to buttons 16/17/18 even though again, I had assigned those numbers to completely different switch presses.

So I used your files, altered the mapping file so it didn't have BTN16/17/18 in it and problem solved.

I don't know what was going on with those numbers???? 

[sedenion]

14 minutes ago, jonsky7 said:

I don't know what was going on with those numbers???? 

My first guess is that you have some conflicting software (such as JoyToKey) running in background that is generating keystrokes when buttons 16, 17 and 18 are pressed.

[jonsky7]

3 hours ago, sedenion said:

My first guess is that you have some conflicting software (such as JoyToKey) running in background that is generating keystrokes when buttons 16, 17 and 18 are pressed.

Correct, I'm an idiot lol

[jonsky7]

@sedenion

May I ask what is the intended purpose of the Advanced AP/LASTE Switch Logic is please?

I see that when you press Autopilot Engage, 2 "buttons" are pressed and held. Which 2 are you binding in game?

[sedenion]

3 hours ago, jonsky7 said:

@sedenion

May I ask what is the intended purpose of the Advanced AP/LASTE Switch Logic is please?

I see that when you press Autopilot Engage, 2 "buttons" are pressed and held. Which 2 are you binding in game?

First, the AP Button act as toggle, then an internal variable follow that toggle, that enable and disable the LASTE switch. This is intended to reproduce what could be the real behavior of the AP and LASTE swtch. You see two button pressed because there is AP On and LASTE Switch position that is also "acted" when it is enabled.

[sedenion]

Script updated to version 2.6 :

 - Added support for AVA Base with F-16 and F-18 Grip
 - New Option to keep Hardware LED setup (ignore custom settings)
 - New Advanced AP Module that allow short-Long press behavior
 - Added some script output

EDIT: New hotfix version 2.7 :

 - Fix Advanded AP module enable status itself at mapping load
 - Refactored Advanced AP module to avoid duplicate code

About the new Advanced AP Module behavior:

The Advanced AP Module has been modified to allow two possible behaviors for AP Toggle so it is now possible to toggle AP status using long/short press. A short press on AP ENGAGE will enable AP Logical Status while long press disable it. Complex and Simple Mapping presets are configured to keep the behavior of the previous versions. If you want to set the AP Toggle behavior to Short/Long press mode, you need to set the AP_LATCHING macro to 0.

https://www.digitalcombatsimulator.com/fr/files/3318341/

Merry Christmas

Edited December 27, 2024 by sedenion
version 2.7 changes log