#Unable to map Thrustmaster Joystick

1 messages · Page 1 of 1 (latest)

sonic plume
#

I am unable to map any joystick controls using Thrustmaster joysticks.

In the F1 menu, I attempt to map controls to my sticks, after clicking the control mapping, I get the popup asking for input. When I give input from my sticks, the popup remains, and no control is mapped. The sticks work fine in a variety of other programs and games. I am not running any third party joystick software that might interfere.

NVIDIA GeForce RTX 2060
Intel(R) Core(TM) i5-10400F 2.90GHz 6-Core CPU
Asus PRIME B460M-A R2.0 Motherboard
2x16 GB T-Force Delta RGB DDR4-3600 RAM
Thrustmaster Dual T.16000M FCS

quiet elbow
#

I had verified that with my T16k and with the info about gltw I found out that gltw disables DirectInput joysticks the moment it detectes XInput support.
T16k FCS do not implement XInput and hence get ignored by gltw.

#

btw there is one workaround for it. A tool to map DirectInput devices on XInput devices. Namely XBox controller emulators

sonic plume
#

I'll look into it

quiet elbow
#

It was an idea with x360ce but yeah if not working then it will be no other choice then having some stuff be done on side of gltw and/or archean

noble ether
#

have you check on Thrustmaster's website for specific drivers?

#

it's likely that a driver/software from Thrustmaster will enable XInput for it

#

@sonic plume @quiet elbow

sonic plume
#

Not as far as I can find

quiet elbow
#

It is a common issue with a lot of joystick manufacturers if they primarily target things like flight simulation they do not have XInput because flight simulation market still relies on DirectInput because XInput has more limitations regarding button count and so on

#

XInput is something that has to be done explicitly. Joystick USBHID device support on the other hand you get without implementing own software.

sonic plume
quiet elbow
#

Worse some games started to consider Target to be blacklisted in their anti cheat detections because macro software capability

sonic plume
#

Didn't know about that, but it makes sense

mighty swan
#

@noble ether hey, did you ever get a good resolution on this? it'd be nice to be able to map extra axes to aux0-9 for things like trim or manual control of tiltrotor tilt

#

out-of-the-box the joystick fails to be recognized by archean, I think with TARGET I can map to XInput (DirectInput?) but at the cost of losing axes:

#

I want to use twin-stick with throttle

mighty swan
#

with this software it's not possible to create multiple virtual devices, rather you select axes from a pool of devices that get composed into a single virtual device. the axis count seems to be limited, so you can only map a subset of your actual controls