top of page

Unresponsive Thrustmaster rudder pedals in TARGET: A workaround


T-Flight Rudder Pedals
T-Flight Rudder Pedals

This is a quick post about Thrustmaster T-Flight Rudder Pedals (TFRP) becoming unresponsive when a Target software profile is run which includes the TFRP.


Warning: Make sure your are comfortable doing this, this is for informational purposes only. I can't take responsibility for any loss or damage incurred. This is working on my particular machine and setup, your experiences may differ.






Setup


You have your TM hotas setup and working. You have TFRP plugged into a usb port using the supplied TFRP adapter. The TFRP adapter is correctly set to the 'flight' setting and the LED on the adapter is green. All the devices can be seen by windows and are calibrated and seem to be working.


You have the latest version of Target installed and Target GUI application works without issue.


Target GUI
Target GUI

TFRP adapter
TFRP adapter, allows selecting flight or racing modes










The problem


Running a Target profile
Running a profile

You create a new Target profile or update an existing Target profile in the Target GUI, adding the TFRP. You run the profile in Target GUI and it starts correctly.








Target Device Analyzer
Target Device Analyzer: The rudder pedal axes (displayed as T-Rudder) in the bottom left of the image remain static despite moving the pedals.

However when you look at the test tools available, both the Device Analyzer and Joystick Control Panel show the TFRP to be unresponsive. Moving the pedals just doesn't change anything within these test tools.


You may have also noticed that the LED is not showing at all on the TFRP adapter.



The TFRP has been disabled, the physical TFRP controller is replaced by the virtual controller created when running the Target profile. This is normal and all the physical TM hotas controllers will be disabled, replaced by the virtual controller. They all come back once the Target profile stops running.


However the other hotas controllers remain powered on, while the TFRP seems to go into a powered off state.


An update and a fix!


The below workaround is not longer recommended, as an actual fix has been found for this issue, take a look at Unresponsive Thrustmaster rudder pedals in TARGET: A fix!


The workaround (not recommended)


  • Run up the profile in the Target GUI.

  • Run the Windows Device Manager application.

  • In the View menu, change the selected option to Devices by container. This makes it easier to find the rudder pedals.

  • Expand the T-Rudder section. You should see a HID-compliant game controller and USB Input Device.

  • Right click on the HID-compliant game controller and select Enable device.




This should make the LED on the TFRP adapter come on and the pedals should be responsive once again. You may have to repeat this each time you run a profile with the TFRP included.


If you look at the Joystick Control Panel test tool you should see the rudder pedals working in the virtual game controller normally.


Some background


This is a quick list of some of the things I tried before discovering the workaround, none of which resolved or reduced the frequency of the issue:


  • Plugging TFRP into a USB 3.0 port in a hub.

  • Plugging TFRP into a USB 3.0 port on the motherboard.

  • Plugging TFRP into a USB 2.0 port on the motherboard.

  • Setting the power management in Windows 10.

  • Disabling USB device powering down in Windows 10  power management.

  • Disabling the 'Allow the computer to turn off this device to save power' option for each USB device, USB controller and Thrustmaster device in the Device Manager.


Notes:


  • If you continually move the pedals as you run the Target profile, the pedals will remain responsive and the green LED remains on in the adapter, as soon as you stop moving the pedals they become unresponsive and the adapter LED goes out.

Comentarios

Obtuvo 0 de 5 estrellas.
Aún no hay calificaciones

Agrega una calificación
bottom of page