DCS2TARGET: DCS to Thrustmaster HOTAS LED Controller (Viper Mission Pack, Viper Panel and Warthog)

[slughead]

3 hours ago, Freakmeister51 said:

Could you suggest a good quality hub please?
 

I currently use this one. It works for me. I won't guarantee it would work for you. Who knows how well they are built from unit to unit or how they will react with different appliances connected? You'll just have to try it out for yourself. But first, have you connected directly to your PC to make sure the hub is the problem?

https://amzn.eu/d/7SQ8Zf6

[Freakmeister51]

On 4/10/2025 at 7:30 PM, slughead said:

Always connect directly to the pc when fault finding. Not all usb hubs are equal and many cheap ones are poorly constructed and are electrically noisy. Connect direct to the pc then see. If it works, get a better hub or usb pci card.

 

7 hours ago, slughead said:

I currently use this one. It works for me. I won't guarantee it would work for you. Who knows how well they are built from unit to unit or how they will react with different appliances connected? You'll just have to try it out for yourself. But first, have you connected directly to your PC to make sure the hub is the problem?

https://amzn.eu/d/7SQ8Zf6

Thank you for the info.

[slughead]

23 hours ago, CM2024 said:

@slughead I'm starting to learn the A-10C2. Would it be possible to update the script for the warthog throttle?

It would be great to have similar functionality like the F18. Especially to have the lights turn on and off with the battery switch. The gear handle lamp would also be a great addition.

I don't think there is a separate APU light like in the F18, but the "Canopy unlocked" indicator could be a good option for the top LED.

Really enjoying the script. Thank you!

Please test this alpha build. If everything is okay, I will formally release it.

dcs2target.zip

TMHotasLEDSync.zip

[CM2024]

4 hours ago, slughead said:

Please test this alpha build. If everything is okay, I will formally release it.

@slughead This is perfect. I tested on the A-10C2 to turn on and off the battery, changing the light settings, the speed break, canopy open and close, and the gear handle lamp for gear up, down, and stalls. Also tested it when instantly restarting the mission and loading the mission a second time after starting DCS. Checked the F18 too and everything still works.

The updated script makes a huge difference when learning the new plane. Thank you!

Edited April 14 by CM2024

[slughead]

Formal release

Added A-10C/A-10C_2 gear handle lamp and mapped to flash Warthog user LED1.
Added A-10C/A-10C_2 cockpit unlocked lamp and mapped to flash Warthog user LED5.
A-10C/A-10C_2 speed brake remains on Warthog user LEDs 1 through 4, with LED1 shared with gear handle lamp.

DCS2Target is now at version: 1.0.12

TMHotasLEDSync is now at version: 1.0.9

Other versions of dcs2target/tmhotasledsync are not compatible with this release. You must only use the versions listed above.

For support issues, read the first post thoroughly, then follow the "Need Help" section before requesting support.

Edited April 14 by slughead

[MickyG]

Hi Slug,

Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off?

I would like such an option.

BTW: I get an error when using TARGET Ver. v3.0.25.127_rev1? When using TARGET v3.0.24.618_rev1 everything works just fine. Any Idea why this happens?

Thanks in advance for your help.

 

Edited April 26 by MickyG

[slughead]

11 hours ago, MickyG said:

Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off?

I'd have to give that some thought.

11 hours ago, MickyG said:

BTW: I get an error when using TARGET Ver. v3.0.25.127_rev1? When using TARGET v3.0.24.618_rev1 everything works just fine. Any Idea why this happens?

Could you share the console output of the TARGET script? I am not experiencing any faults with the revision of Thrustmaster software.

Edited April 26 by slughead

[MickyG]

yes, of course! Here it is:

it seems to work now but the console output is a lot larger now and I don't know if it is ok like this? (because of all those "cannot be found" issues)

 

 

Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"

TMHotasLEDSync v1.0.9

Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "AVA [R] Viper" - "USB\VID_044F&PID_0430&REV_0200&MI_00"
2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
Installing filter driver to VID_044F&PID_0404. Please Wait...Done!
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&218EB820&0&1) selected
Installing filter driver to VID_044F&PID_0412. Please Wait...Done!
USB HID device "Viper TQS"(USB\VID_044F&PID_0412\2055385B4633) selected
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
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
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
Server socket listening on TCP port 29914 

main returned 0

[slughead]

It’s normal. The script includes other Thrustmaster devices to “ignore” and pass through to the simulator just in case someone has one attached. For example the Thrustmaster TPR rudder.

[MickyG]

"Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off?

I would like such an option."

is there any progress with this?

 

[slughead]

51 minutes ago, MickyG said:

"Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off?

I would like such an option."

is there any progress with this?

 

No progress. I’ve not had the time recently.

[MickyG]

thanks for your answer.

[slughead]

New Release:

Release v1.0.10: Warthog backlight illuminated for unsupported airframes · iknowkungfutoo/TMHotasLEDSync

This release will illuminate the Warthog backlight for unsupported aircraft.

[MickyG]

thanks so much!