Jump to content

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


Recommended Posts

Posted

@slughead

 

I am so sorry for the late response!

 

I’m actually celebrating my birthday today, so this comes as a VERY pleasant surprise!  I’ll be trying this new script out and seeing if it works.

 

Thanks!!

Posted
1 minute ago, Red Panda said:

@slughead

 

I am so sorry for the late response!

 

I’m actually celebrating my birthday today, so this comes as a VERY pleasant surprise!  I’ll be trying this new script out and seeing if it works.

 

Thanks!!

Happy Birthday! Did you get any flight som treats? A WinWing ICP perhaps?

  • Like 1
Posted
Just now, slughead said:

Happy Birthday! Did you get any flight som treats? A WinWing ICP perhaps?

Saving up the Pennies for a seat right now, actually.  
 

(I may also be waiting on a tax return to roll in.. ahem. But I digress.)

 

That WinWing ICP is on my “want” list though. 
 

See, my logic is pretty solid here… if I can ultimately have one of those nice NLR Military edition chairs with the mounts, just get a smaller front mount for the ICPs, I could, in theory, just use the ICP without passthrough because everything will pretty much be in-line enough for me to just reach out with my hand and touch it/use it quicker than I could screwing around with the mouse.

Soon™️.

 

Thanks again for the response; I’ll definitely be checking this script out soon.  

Posted
1 minute ago, Red Panda said:

(I may also be waiting on a tax return to roll in.. ahem. But I digress.)

Sadly, this year, I will be giving the taxman lots! A change of job has pushed my salary beyond the realms of regular tax returns! I'm not complaining.... ok, I am. 😆

3 minutes ago, Red Panda said:

See, my logic is pretty solid here… if I can ultimately have one of those nice NLR Military edition chairs with the mounts, just get a smaller front mount for the ICPs, I could, in theory, just use the ICP without passthrough because everything will pretty much be in-line enough for me to just reach out with my hand and touch it/use it quicker than I could screwing around with the mouse.

I don't have the room for a dedicated "cockpit" setup, which is why I developed the Slugmouse. It allows you to point and click with your hands rather than reach for a mouse. It's the closest thing to actual cockpit interaction without a physical cockpit and passthrough. It's probably a good thing that I don't have the space, or I would be spending a small fortune in gear!

Posted

@slughead That's a great addition for the F-16. Makes a big difference when starting the plane. Thank you!

I also tried the F-18 with the warthog throttle and really like the APU light. This is great. I did notice that the lights no longer turn off when turning off the engines. Can this be changed back? The previous version seemed more immersive when starting cold and dark. 😉

Also, when I used the new script I got the following error: "Runtime Error: Symbol not found: AVA_F16 in main (line 37 in TMHotasLEDSync.tmc)"

After removing the lines with AVA_F16 and AVA_F18, it works again.

 

 

 

Posted
4 minutes ago, CM2024 said:

I also tried the F-18 with the warthog throttle and really like the APU light. This is great. I did notice that the lights no longer turn off when turning off the engines. Can this be changed back? The previous version seemed more immersive when starting cold and dark

See below.

20 hours ago, slughead said:

Note that the Warthog minimum background lighting level will be level 1 instead of off. Otherwise, the column of LEDs will always be off when the console lighting dial is set to off or the generators are not producing power.

 

4 minutes ago, CM2024 said:

Also, when I used the new script I got the following error: "Runtime Error: Symbol not found: AVA_F16 in main (line 37 in TMHotasLEDSync.tmc)"

After removing the lines with AVA_F16 and AVA_F18, it works again.

I will have to see what I can do to make it more universal for those who do not have the AVA base.

Posted
51 minutes ago, slughead said:

Sadly, this year, I will be giving the taxman lots! A change of job has pushed my salary beyond the realms of regular tax returns! I'm not complaining.... ok, I am. 😆

I don't have the room for a dedicated "cockpit" setup, which is why I developed the Slugmouse. It allows you to point and click with your hands rather than reach for a mouse. It's the closest thing to actual cockpit interaction without a physical cockpit and passthrough. It's probably a good thing that I don't have the space, or I would be spending a small fortune in gear!

I’ve looked at those!  They seem pretty cool.

And I’ve gotta clean up the space I wanna put that chair in.  The place I live has a pretty decent little niche spot that can easily hold my junk, plus a decent sized workstation/painting station for my partner.  That’s the plan for our spring cleaning; getting that area better organized and set up the way we wanna use it.  😄

Posted
36 minutes ago, CM2024 said:

Also, when I used the new script I got the following error: "Runtime Error: Symbol not found: AVA_F16 in main (line 37 in TMHotasLEDSync.tmc)"

I expect you are running an old version of the Thrustmaster TARGET software released before the AVA base was available. Hence it doesn't know about the AVA base symbols. Can you update the TARGET software and see if that solves your problem?

Posted

Hi Slughead,

Just tried the new version but it doesn't work, worked with the previous version pretty good. 

I don't know what's wrong, can you advice me please?

This is what I get back in target but the lights won't work.

TMHotasLEDSync v1.0.6

Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "AVA BASE" - "USB\VID_044F&PID_0415&REV_0200"
2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&218EB820&0&1) selected
Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0412"
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
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 2323 

main returned 0
 

 

Gigabyte Aorus Z790 Elite AX, I9 14900, Asus OC RTX 4090, 128GB DDR5

 

Posted
3 minutes ago, MickyG said:

Hi Slughead,

Just tried the new version but it doesn't work, worked with the previous version pretty good. 

I don't know what's wrong, can you advice me please?

This is what I get back in target but the lights won't work.

TMHotasLEDSync v1.0.6

Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "AVA BASE" - "USB\VID_044F&PID_0415&REV_0200"
2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&218EB820&0&1) selected
Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0412"
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
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 2323 

main returned 0
 

 

 

Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0412"

That's your ViperTQS.

Try performing a "Check for Update" in the Viper TQS control panel. Also, make sure you are using the latest version of the Thrustmaster TARGET software.

image.png

Posted (edited)

Thanks for your help! My TQS had an older Firmware (1.23).

Updated the firmware and everything works now!

Had to reinstall the complete package before updating the firmware, check for update replied "you are using the latest version" before!?

 

Edited by MickyG

Gigabyte Aorus Z790 Elite AX, I9 14900, Asus OC RTX 4090, 128GB DDR5

 

Posted
On 3/10/2025 at 5:19 PM, slughead said:

I expect you are running an old version of the Thrustmaster TARGET software released before the AVA base was available. Hence it doesn't know about the AVA base symbols. Can you update the TARGET software and see if that solves your problem?

I just updated the Target software and now it works. Thanks!

I was thinking about options to improve the cold start for the F18 and warthog throttle. Is it possible to use the battery switch for the background lighting level?

Have the background lighting level off when the battery is off. Then when you turn on the battery, turn it to level 1. When shutting down the plane, the last item is to turn off the battery, which could then also turn the background lighting level off.

I really like the new APU option. Using the battery in this way could improve immersion even more for cold starts.

Posted
8 hours ago, CM2024 said:

I just updated the Target software and now it works. Thanks!

I was thinking about options to improve the cold start for the F18 and warthog throttle. Is it possible to use the battery switch for the background lighting level?

Have the background lighting level off when the battery is off. Then when you turn on the battery, turn it to level 1. When shutting down the plane, the last item is to turn off the battery, which could then also turn the background lighting level off.

I really like the new APU option. Using the battery in this way could improve immersion even more for cold starts.

Yes, I think that is achievable. If I get some time this evening, I’ll try to get this added. Perhaps also take a look at adding similar support for APU and backlight level on battery to the A-10 too.

  • Thanks 1
Posted
On 3/13/2025 at 4:11 PM, slughead said:

@CM2024 Your wish has been granted. You need both the new dcs2target and TMHotasLedSync updates.

@slughead This is great. Makes such a difference. Thank you!

  • Thanks 1
Posted

after installing DCS2target 1.10 and TMHotasLEDSync 1.07 DCS crashes after loading a Viper/instant action? when I use DCS2target 1.09 with TMHotasLEDSync 1.06 it works fine, What could be the reason of this?

Gigabyte Aorus Z790 Elite AX, I9 14900, Asus OC RTX 4090, 128GB DDR5

 

Posted
2 hours ago, MickyG said:

after installing DCS2target 1.10 and TMHotasLEDSync 1.07 DCS crashes after loading a Viper/instant action? when I use DCS2target 1.09 with TMHotasLEDSync 1.06 it works fine, What could be the reason of this?

Please follow the troubleshooting section in the first post of this thread.

Posted

never mind, it wasn't related to dcs2target. There seemed to be something wrong with my export.lua file and it made DCS crash.

after removing the file everything worked.

Gigabyte Aorus Z790 Elite AX, I9 14900, Asus OC RTX 4090, 128GB DDR5

 

Posted
6 hours ago, MickyG said:

never mind, it wasn't related to dcs2target. There seemed to be something wrong with my export.lua file and it made DCS crash.

after removing the file everything worked.

What’s in your export.lua file? Post it and I’ll take a look. dcs2target stopped using export.lua a long time ago.

Posted

@slughead

I heard back today from Thrustmaster on the whole naming of the devices. Your Have Thrustmaster combined controller and I have Thrustmaster virtual controller. it iturns out they renamed it like you said might be the case..... Here is a screen shot of the email i got.

Screenshot Thrustmaster answer 2025-03-21 153032.jpg

  • Like 1
Posted (edited)

Another suggestion for the F18 warthog script.

When preparing to land and lowering the landing gear, the gear handle turns red until the landing gear is fully down.

Could this be simulated with one of the LEDs on the warthog throttle?

How about using the bottom LED as a landing gear indicator, then the next 3 for the speed break, and the top for the APU?

Edited by CM2024
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...