Thrustmaster Combined Full DX Mapping

Home > User Files > Thrustmaster Combined Full DX Mapping
Any version
Other

Thrustmaster Combined Full DX Mapping

Uploaded by - sedenion
Date - 09/11/2021 10:32:10
Script suite for Thrustmaster TARGET Script Editor that map Thrustmaster devices as new virtual device with only DX buttons.  Avoids switching profiles to suite each games or modules, allow to configure one universal device which can be binded like a physical device with up to 120 buttons.

Verion 2.5 (2024-03-18)

Combined Full DX is a script suite for Thrustmaster TARGET Script Editor which maps HID buttons (DX buttons) only. Instead of mapping the devices with emulated key strokes - which are all game or simulation module specific - this script only use HID buttons (DX buttons) to emulate a new virtual device with more of assignable buttons.

With such approach, there is no more need to load a specific mapping script each time you switch to another game or simulation module, you only need to load this one once for all. Since the combined device is seen as normal joystick/HOTAS (but with a lot of buttons), you can assign each button to the desired command within the game, each game will have its specific mapping for the same combied device.

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.

__USAGE_____________________________________________________________________________________________________________________________________________________________________________

* Quick Start

  0) Ensure you installed TARGET Software version 3.0.23 or above
  1) Extract and place the "TM Combined Full DX" folder as your convenience
  2) Launch the TARGET Script Editor software (Not TARGET GUI)
  3) In TARGET Script Editor, click the "Menu" icon then sel ect "Open"
  4) Browse to find the ".tmc" file of your choice within the the "TM Combined Full DX" folder.
  5) Click the "RUN" button.

* Details

The mapping script must be launched using the "TARGET Script Editor" software and cannot be run using "TARGET GUI". The "executables" files are the ".tmc" files, these are the ones to be opened in "TARGET Script Editor" to be runned.

There are three .tmc script files corresponding to three mapping presets, "simple", "hybrid" and "complex" to be used according your preferences. A fourth "custom" .tmc files is avaible to let you create your own custom preset.

See the "CUSTOMIZATION" section below for more information about customization

__FAQ_______________________________________________________________________________________________________________________________________________________________________________

* How is it possible to have more than 32 DX buttons ?

On the paper, Thrustmaster T.A.R.G.E.T allow to emulate only up to 32 DX buttons. This lim it is inherited fr om the old DirectInput API, however it does not reflect a true software or hardware limit anymore. Fortunately Thrustmaster does not took this old convension too seriously and developpers implemented the software to allow to emulate a game device with up to 120 buttons and a 8-positions HAT.
By bypassing the proper initialization function within the script, we are able to create a virtual device with the desired amount of HID buttons (up to 120). Then, by completing the defined DX## macros list with the proper integer values, we can assign an extended list of DX buttons within the mapping functions.

* Is this harmful for devices or system ?

Definitely not. The bigger risk is a BSOD in the case you try to use a virtual device with more than 120 buttons. In this case, due to an hard-coded array size within the driver the script will reach for an out of bound index which instantly crash the driver. Even in this case, the only consequence is a need  for system reboot.

* Is this script can be used with other devices than HOTAS Warthog ?

As long as the devices are recognized by TARGET Script Editor, Yes. Currently only HOTAS Warthog mapping is done, but any other TARGET compatible combination
can be made with the proper mapping functions. See the "Customization" section for more details.

__CUSTOMIZATION_________________________________________________________________________________________________________________________________________________________________

The script is intented to be modular, so people can edit, add or remove the devices mapping of their choice to adapt the basis with their own devices.

* Custom Preset

The file "run_custom.tmc" is intended to be modified to create your own specific preset if the three existing ones does not fit your needs. Each ".tmc" file declares general mapping options to enable or disable features and special behaviors such as buttons long-press, S3 I/O mode, Digital Axes, etc..

The file has comments (in green) that describe each parameter and will help you to edit features as your needs.

* Custom Mapping (Advanced)

You can directly edit the mapping functions, which are located in the mapping folder. You'll find precreated *.tmh file for all TARGET supported Thrustmaster devices. If you write a new mapping function for a new device, you'll have to modify the main run script (*.tmc) to include the file then properly call the mapping function within the main() function. Each run_*.tmc file already have 'placeholders' for mapping includes and function call in the form of commented line: Simply uncomment the desired lines.

__VERSION_HISTORY________________________________________________________________________________________________________________________________________________________________

v2.5 (2024-03-18)
- Fix script to be compatible with TARGET 3.0.23.1205_rev1

v2.4 (2023-10-27)
- New mapping system with per device dynamic DX assignation
- Viper TQS and Viper Panel mapping implementation
- Updated mapping charts

v2.2 (2023-10-19)
- Fix script to be compatible with TARGET 3.0.23

v2.1 (2023-06-27)
- Fix typo for TPR Pendular Rudder mapping call that cause script to crash.

v2.0 (2023-06-19)
- Button numbers assignment changed
- Introduce new Simple, Hybrid and Complex mapping presets
- Digital Axis mapping for Friction Control slider now has middle position
- Fix F-18 Grip Hat1 I/O Mapping working in inverted mode
- FLAPS Switch LED now light up from MVR position instead of DN position

v1.7 (2022-08-06)
- Add Digital Axis mapping in Complete variant for Throttle
   microstick and Friction Control slider.

v1.61 (2022-07-24)
- Add delay for buttons press/release sequences in advanced AP Module.

v1.6 (2021-11-26)
- Add support to exclude Airbus Edition devices.
- Add options to change LEDs intensity and disable Throttle backlight.
- Fix wrong mapping for EACOFF.
- Fix virtual keyboard and mouse not created as usual.
  • License: Freeware - Free version, Unlimited distribution
  • Language: English
  • Size: 1.29 Mb
  • Downloaded: 1337
  • Comments: 16
FOLLOW US