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

[adirtynurse]

I use this for my Warthog throttle. I get Thrustmaster Combined IN ADDITION to the original Warthog Throttle. How can I have the original disabled when the script is running?

[sedenion]

15 hours ago, adirtynurse said:

I use this for my Warthog throttle. I get Thrustmaster Combined IN ADDITION to the original Warthog Throttle. How can I have the original disabled when the script is running?

As far as I know, this is not related to the script itself, but with TM driver configuration. The fact is that once a TARGET script run (either via Script Editor or GUI editor), the driver automatically "shutdown" the physical devices so they are not visible anymore in games... In your cas, it seem that the Throttle was not properly "shutdown" and still available along the virtual device. I can't remember where, but I believe remembering that there is an option, maybe within TARGET editor, to allow physical device to not be disabled. You may look for that, or, maybe, simply purge then reinstall the drivers.

[adirtynurse]

Thx. I'll look into that

[MadMonty]

Hi!

 

I defenitely need some help here. Have been using Thrustmaster Combined Full DX Mapping for years without a problem. Now I have updated Win11 to 22H2 update and everything is messed up. Couldn´t use it anymore, had compile errors. So I downloaded latest TARGET and V2.7 of Full DX Mapping, but no joy. I always get the following error:

 

Running script: F:\UPDATE\Thrustmaster\TARGET Profiles\TM_Combined_Full_DX_v2.7\TM Combined Full DX\Run_Simple.tmc
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
3: "T-Pendular-Rudder" - "USB\VID_044F&PID_B68F&REV_0110"
Error:(internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404"
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found
USB HID device with hardware id "VID_044F&PID_0438" cannot be found
USB HID device with hardware id "VID_044F&PID_0439" cannot be found
USB HID device with hardware id "VID_044F&PID_0432" cannot be found
USB HID device with hardware id "VID_044F&PID_043A" cannot be found
USB HID device with hardware id "VID_044F&PID_0420" cannot be found
USB HID device with hardware id "VID_044F&PID_0428" cannot be found
USB HID device with hardware id "VID_044F&PID_0421" cannot be found
USB HID device with hardware id "VID_044F&PID_0429" cannot be found
USB HID device with hardware id "VID_044F&PID_0422" cannot be found
USB HID device with hardware id "VID_044F&PID_042A" cannot be found
USB HID device with hardware id "VID_044F&PID_041B" cannot be found
USB HID device with hardware id "VID_044F&PID_041C" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined

main returned 0

 

already tried the following:

1. Open REGEDIT (Windows + R; Type "regedit" and run it).

2. Go to this, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB

3. Then look for the following; VID_044F&PID_0404 

4. You will then use the drop-down menu to open and find Device Parameters. (Clicking on Properties will not work)

5. Off to the right, Every number that you see (#) like that, we are going to change them all to (0). Do not leave any 1's behind.

6. Restart and Enjoy.

 

Also reinstalled drivers and reinstalled TARGET, having switched off TM USB devices. But still I return to the above error message.

 

Any ideas??

[Lange_666]

In the comments on the DCS User files of Thrustmaster Combined Full DX Mapping there is a post with the same error but with no solution.
Digging a bit deeper into the internet cave i came across what you already tried (in white).

But there's a bit more below where I found that "solution":
-----------------------------------------------------
You should explain people what it does. It prevent the pc to turn on/off the device for power saving. It can be a reason for this error message.
But most of the time it's because we install driver and Target in the incorrect order. Driver must be installed first, then we MUST disconnect all Target compatible peripheral before installing Target. Should be ok now.
(It can also be due to the Teamspeak 3 joystick plugin. I had to delete it).

If you read the ThrustMaster TARGET release note, it is said it is a must.

Warning

Unplug all T.A.R.G.E.T-compatible controllers before proceeding with installation. When prompted to reboot after installation, plug each controller again.

If we install TARGET with controller plugged in, it will take a long time to install filter, and controller will not hide when we run a script. Must reinstall properly after having made this error. Many people do it. As we have to plug our controller to install the driver.. And.. We rarely read release note.
-----------------------------------------------------

Another one:

What I did to remedy this.

1. Unplug joystick and uninstall Drivers, then TARGET

2 Deleted all Thrustmaster folders in >Program Files, Program files x86, and Users\UserName\AppData\Roaming

3 Went to Device Manager>View> show hidden devices

4 (make sure at this point al your regular USB devices such as phones, printers and headphones are connected to USB) DO NOT CONNECT your Thrustmaster device

5 Right clicked and uninstalled all greyed out  Universal Serial Bus controllers, Human Interface Devices. ( for a good measure look through other categories to make sure there isn't a greyed out Thrustmaster device somewhere there)

6 Restarted the PC

7 Plugged in my joystick and let Windows install drivers. I did not install drivers from thrustmeter support downloads. What that changed is that now my joystick is displayed as a Thrustmaster Virtual Game Controller (root) : Status OK. Instead of T.16000m FCS : Status OK.  

8 Installed TARGET

---------------------------------------------------------

This one above is different because in step 7 and 8 he's plugging in his joystick before installing Target which should not be done according to the release note.

---------------------------------------------------------

Also,my own encounter with this problem (at that time with the Target Gui which returns the same error):

PS: The solved not 100% points to the device analyzer problem where devices don't show up, nothing to do the internal error.

To remove the "USB HID device with hardware ID cannot be found" message when compiled I edited target.tmh and commented out the Thrustmaster devices i don't have (this was not needed on older target.tmh versions).

If you can't solve it, you can contact TM support through their website. It can take a few days before they respond but I always got an answer and they go through until you have a solution. 



 

Edited yesterday at 09:54 AM by Lange_666

[MadMonty]

14 hours ago, Lange_666 said:

In the comments on the DCS User files of Thrustmaster Combined Full DX Mapping there is a post with the same error but with no solution.
Digging a bit deeper into the internet cave i came across what you already tried (in white).

But there's a bit more below where I found that "solution":
-----------------------------------------------------
You should explain people what it does. It prevent the pc to turn on/off the device for power saving. It can be a reason for this error message.
But most of the time it's because we install driver and Target in the incorrect order. Driver must be installed first, then we MUST disconnect all Target compatible peripheral before installing Target. Should be ok now.
(It can also be due to the Teamspeak 3 joystick plugin. I had to delete it).

If you read the ThrustMaster TARGET release note, it is said it is a must.

Warning

Unplug all T.A.R.G.E.T-compatible controllers before proceeding with installation. When prompted to reboot after installation, plug each controller again.

If we install TARGET with controller plugged in, it will take a long time to install filter, and controller will not hide when we run a script. Must reinstall properly after having made this error. Many people do it. As we have to plug our controller to install the driver.. And.. We rarely read release note.
-----------------------------------------------------

Another one:

What I did to remedy this.

1. Unplug joystick and uninstall Drivers, then TARGET

2 Deleted all Thrustmaster folders in >Program Files, Program files x86, and Users\UserName\AppData\Roaming

3 Went to Device Manager>View> show hidden devices

4 (make sure at this point al your regular USB devices such as phones, printers and headphones are connected to USB) DO NOT CONNECT your Thrustmaster device

5 Right clicked and uninstalled all greyed out  Universal Serial Bus controllers, Human Interface Devices. ( for a good measure look through other categories to make sure there isn't a greyed out Thrustmaster device somewhere there)

6 Restarted the PC

7 Plugged in my joystick and let Windows install drivers. I did not install drivers from thrustmeter support downloads. What that changed is that now my joystick is displayed as a Thrustmaster Virtual Game Controller (root) : Status OK. Instead of T.16000m FCS : Status OK.  

8 Installed TARGET

---------------------------------------------------------

This one above is different because in step 7 and 8 he's plugging in his joystick before installing Target which should not be done according to the release note.

---------------------------------------------------------

Also,my own encounter with this problem (at that time with the Target Gui which returns the same error):

PS: The solved not 100% points to the device analyzer problem where devices don't show up, nothing to do the internal error.

To remove the "USB HID device with hardware ID cannot be found" message when compiled I edited target.tmh and commented out the Thrustmaster devices i don't have (this was not needed on older target.tmh versions).

If you can't solve it, you can contact TM support through their website. It can take a few days before they respond but I always got an answer and they go through until you have a solution. 



 

Thank you very much. Worked all night to solve the problem. At the end I asked ChatGPT and went through all steps, incl. deactivating all other USBs, connecting throttle directly to PC and deactivating MSI afterburner and a couple of other software. Script was moved to TM folder in C:\Programme\TM\Scripts... At the end, I managed to get the driver installed and TM Throttle running als TM combined with DX buttons. Very much relieved now...