TPR Rudders and Target software issue

[Oilman100]

Just purchased the TPR rudder pedals and wanted to use it with Target software to allow customization of curves etc. I’m hopefully not the first person who came across this issue. When you add the script lines (I got these from the GUI script software) for the rudder and brakes and then run the script file, I found the brakes uses the same axis as as the slew control on the throttle (RX & RY) and the rudder uses the same axis as the Throttle (Thrust) Axis RZ ?? So therefore in DCS it won’t allow you to have dual usage of an axis. If I exclude them from the script, then DCS finds them as it’s own controller and it all works fine. Any chance someone found a workaround for Target ?

[Teej]

Short answer: - leave the TPR out of TARGET.  

 

Long answer.

TARGET combines all the things it's managing into a single "controller" as far as Windows is concerned - the Thrustmaster Combined device.  AFAIK, DCS still uses the "DirectInput" API for processing controller inputs. DirectInput can handle a maximum of 8 axes per controller.  By adding 3 axes from the TPR, you're presenting a total of 10.  No can do.  Sorry.

 

[Oilman100]

Thx for the reply and explanation