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

[GarrettJMorgan]

@slughead Can confirm downloaded the latest version from the github version 1.0.8

[slughead]

6 hours ago, GarrettJMorgan said:

leaving everything unplugged and then starting the script

I re-read your message after having a coffee (or two). The devices must be plugged in before you run any Thrustmaster script. Otherwise, the Thrustmaster code can't find the device, and the script will therefore not be able to communicate with them.

Hence, you see this:

No USB HID devices - device "VID_044F&PID_0404" cannot be found
No USB HID devices - device "VID_044F&PID_0412" cannot be found
No USB HID devices - device "VID_044F&PID_0413" cannot be found
No USB HID devices - device "VID_044F&PID_0416" cannot be found
No USB HID devices - device "VID_044F&PID_0417" cannot be found
No USB HID devices - device "VID_044F&PID_0415" cannot be found
No USB HID devices - device "VID_044F&PID_0414" cannot be found

Going back to my earlier request, try a Thrustmaster script supplied by Thrustmaster for the Viper. I really can't help you further than I have as the problem is a Thrustmaster/Microsoft issue. Other users that have experienced this filter issue have resolved it using the information I provided previously.

[Red Panda]

On 1/18/2025 at 1:27 AM, cptmrcalm said:

Done a step by step tutorial to get the LEDs working. I've credited you and tigershark. Should help promote your work!

Really great stuff. Do you have any further plans for the 2nd column? (for the F16)

 

https://youtu.be/9nKPVTAYC7U?si=uZDqA7VGpX78xalB

 

 

@slughead Hi!  I have tried to replicate the same steps as found in this video by MrCalm.  I have also tried multiple times to replicate success with this script and hook combo using your instructions as outlined in this post and in the GitHub posts.

I have had absolutely zero success; the reason I say I have had no success is because when I start the script, it creates a new virtual controller that has no axis input whatsoever, except from the Viper TQS itself; it eats any kind of input from my AVA stick base and doesn't accept input from the axis on it.

Including the following for you from the Script editor: 

 

Running script: C:\Users\Ameli\Desktop\LED Light Fix\TMHotasLEDSync-main\build\TMHotasLEDSync\TMHotasLEDSync.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** 
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Compile Succeeded.

TMHotasLEDSync v1.0.4

Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200"
2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
USB HID device "Viper TQS"(USB\VID_044F&PID_0412\3665348C3031) 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 "AVA Base"(USB\VID_044F&PID_0415\208F316A4B4B) selected
USB HID device with hardware id "VID_044F&PID_0414" 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

Also attaching my dcs.log file from my most recent attempt at getting it to work.  

I am begging you for help because I have tried, deleted files, tried again, and deleted again so many times that I feel like I'm going crazy.

The funny part?  If I start DCS as normal and everything else, the lights work... I just can't fly my plane.

Please help. T_T

P.S. - MrCalm found a potential issue and linked me to the info from this Reddit post.  I had one brief moment of success where when I ran the script, it kept seeing my AVA base AND created the virtual controller... but after that, I had to restart my computer and I have had no success in replicating the results since then, and I don't really know what I did.

P.P.S - I just did a little experiment and I've found that no axis controls exist at all on the thing after running the script, and using the Virtual controller.  Nothing.  Nada.  Zip.  Zero.
 

dcs.log

Edited February 18 by Red Panda

[slughead]

I’m not sure that I can be of much help with this. The virtual controller is all managed internally by Thrustmaster and I have no control over it.

What version of the Thrustmaster TARGET Script editor are you using? What firmware do you have installed in your Thrustmaster devices? Are the the latest versions?

[Red Panda]

2 hours ago, slughead said:

I’m not sure that I can be of much help with this. The virtual controller is all managed internally by Thrustmaster and I have no control over it.

What version of the Thrustmaster TARGET Script editor are you using? What firmware do you have installed in your Thrustmaster devices? Are the the latest versions?

Re: TARGET software; it is the freshest install available from TM on their proprietary website, I haven’t followed any other download links.

 

Re: devices are new and the latest version of the Firmware was downloaded when I picked up both pieces of kit last week.  I would venture to guess that there hasn’t been a firmware update on the AVA base or the Viper TQS since 11FEB.

 

so.. I dunno, man.  It just decimates my use of the AVA base.  I dunno what else to tell you, other than “this definitely ain’t working with whatever configuration I have” and I can’t begin to tell you how I came to this juncture other than by continuing to dump log files.

[slughead]

For the avoidance of doubt, can you please quote the actual versions of software and firmware that you have installed as reported by Windows, not the website.

Edited February 19 by slughead

[Red Panda]

49 minutes ago, slughead said:

For the avoidance of doubt, can you please quote the actual versions of software and firmware that you have installed as reported by Windows, not the website.

I’ll be glad to once I’m home in a few hours time.  Damn time zones.

 

PS: I know that I probably sound annoyed, and being fair, I righteously am— but not at you.  This is very much a Thrustmaster issue that they won’t admit they overlooked when getting ready to market this product. I’m more peeved at them that an advertised function won’t work unless you do some kind of wild workaround.

Edited February 19 by Red Panda

[slughead]

A few things:

"Running script: C:\Users\Ameli\Desktop\LED Light Fix\TMHotasLEDSync-main\build\TMHotasLEDSync\TMHotasLEDSync.tmc"

Where is says -main\build tells me you have installed the source code and not installed from the zip file. It probably won't make any difference.

You should install only the zip file shown below, not from the source code(zip) or source code(tar.gz).

Second, you say no axis. Is that just in DCS or Windows? Run joy.cpl from the start search bar and you will see get this:

Then select your AVA Base and click on properties and you will see this:

With the script running, do you see axis movement in the window shown above? You may need to start the script before opening the windows above for Windows to recognise the virtual devices and make sure the window above is the active window for movement to be seen.

[Red Panda]

4 hours ago, slughead said:

A few things:

"Running script: C:\Users\Ameli\Desktop\LED Light Fix\TMHotasLEDSync-main\build\TMHotasLEDSync\TMHotasLEDSync.tmc"

Where is says -main\build tells me you have installed the source code and not installed from the zip file. It probably won't make any difference.

You should install only the zip file shown below, not from the source code(zip) or source code(tar.gz).

Second, you say no axis. Is that just in DCS or Windows? Run joy.cpl from the start search bar and you will see get this:

Then select your AVA Base and click on properties and you will see this:

With the script running, do you see axis movement in the window shown above? You may need to start the script before opening the windows above for Windows to recognise the virtual devices and make sure the window above is the active window for movement to be seen.

 

@slughead - Hey again!  As promised:

I am currently running v 3.0.24.618 of the TARGET software.

The directory you reference in the first point here - I did as told with what files were available from the GitHub repositories.  They were unzipped and put into files where I could find them, and then moved per instructions given.

If there is something that I'm apparently missing (I don't really do much with GitHub normally and this is the first time I've ever ran into a problem with getting files from GitHub to work), please provide me a more direct link to the exact file(s) I should be getting.  

When I run the script, this is what screens I see.

First cap: The script editor, pre script start.
Second cap: Game controllers dialogue, Pre-script start
Third Cap: Script editor, Post-Script Start
Fourth Cap: Game Controllers dialogue, post-script start
Fifth Cap: AVA Base controller settings dialogue as above, pre-script run, which allows me to check ROM on the axis - which it is there.  The AVA base completely disappears after I begin running the script, as referenced in Cap 4.
Sixth Cap: The Game Controllers Dialogue settings for the Virtual Device that the script makes, which has NO axis input whatsoever.  This is obviously not the TM dialogue you should be expecting me to get. 


null

null

null

null

nullnull

Edited February 19 by Red Panda

[slughead]

Open the game controller windows after starting the script.

[Red Panda]

48 minutes ago, slughead said:

Open the game controller windows after starting the script.

Will do.  I’ll be back at the computer in roughly 30 minutes, and attempt to replicate/record what I’m doing.

[Red Panda]

@slughead Recorded the process in which I opened things up.

The same process is how I came to screencaps 4, 5 and 6 in the previous response.

P.S. - I did repeat the process and opened the Game Controllers dialogue after I ran the script.  It doesn't matter; the same thing occurs.

Edited February 20 by Red Panda

[slughead]

You’re going to need to talk to Thrustmaster. This is outside my sphere of influence.

[Red Panda]

20 minutes ago, slughead said:

You’re going to need to talk to Thrustmaster. This is outside my sphere of influence.

@slughead This was my worst fear.

Honestly, this doesn't change my opinion on the TQS that much; the unit itself is still a solid piece of kit and I've enjoyed it so far.  

I just wanted to get the cool lights to work. 

I kinda wish TM had the fore-withal to actually consider that users may want the functionality that your script provides and actually provide proprietary, written code for it in their software packages that's supported... Maybe if enough people pitch a fit about it, they'll actually look into it more.

Thank you for trying to help, Slug, and I do appreciate you taking the time to try and help a weary internet wanderer.  Have a cookie for your troubles. 

P.S. - If anyone runs into a similar issue, please give me a ping, especially if you have found an actual fix.  This almost drove me mad.

Edited February 20 by Red Panda

[CM2024]

I just installed this for the F18 with the warthog throttle. The directions are perfect. It just works. Thank you!

It makes quite a difference when starting up and shutting down the plane. I really like that the lights come on or off depending on the right engine.

Is there an option to show the APU light during start-up? For example use the top LED for it (and only 4 LEDs for the speed break).

Showing the APU light, both to turn on and go off, would improve the immersion even more.

Edited February 21 by CM2024

[slughead]

4 hours ago, CM2024 said:

I just installed this for the F18 with the warthog throttle. The directions are perfect. It just works. Thank you!

It makes quite a difference when starting up and shutting down the plane. I really like that the lights come on or off depending on the right engine.

Is there an option to show the APU light during start-up? For example use the top LED for it (and only 4 LEDs for the speed break).

Showing the APU light, both to turn on and go off, would improve the immersion even more.

That's a good idea! I'll give it some thought and see what I can do.

[slughead]

On 2/20/2025 at 12:09 AM, Red Panda said:

@slughead This was my worst fear.

Honestly, this doesn't change my opinion on the TQS that much; the unit itself is still a solid piece of kit and I've enjoyed it so far.  

I just wanted to get the cool lights to work. 

I kinda wish TM had the fore-withal to actually consider that users may want the functionality that your script provides and actually provide proprietary, written code for it in their software packages that's supported... Maybe if enough people pitch a fit about it, they'll actually look into it more.

Thank you for trying to help, Slug, and I do appreciate you taking the time to try and help a weary internet wanderer.  Have a cookie for your troubles. 

P.S. - If anyone runs into a similar issue, please give me a ping, especially if you have found an actual fix.  This almost drove me mad.

Just a thought. Are you connecting your Viper via a USB hub? If you are, try connecting it directly to your PC instead.

[Red Panda]

21 hours ago, slughead said:

Just a thought. Are you connecting your Viper via a USB hub? If you are, try connecting it directly to your PC instead.

I’ll see how that improves things this evening.  Why would that affect it though?  I’m legit curious.

[slughead]

Who can say? However, I have had a report of a hub causing problems with the Viper although I don’t have such problems with mine. Always best to strip back to bare minimum when trying to fault find.

Edited March 4 by slughead

[Desertdawg]

Good Morning, My Saved games folder doesn't have a scripts folder. My saved games DCS folder is on my C:/ drive and the game is on my E:/ Drive. The Eagle dynamics/DCS world file contains a scripts folder and within that folder is a hooks folder. Do I just need to create a Scripts folder in my saved games folder?

Respectfully
Tim B. aka Desertdawg

 

PS I am running DCS Multithread

Edited March 7 by Desertdawg

[slughead]

Yes. Create it in the saved games folder.

[Desertdawg]

35 minutes ago, slughead said:

Yes. Create it in the saved games folder.

Cool thanks

 

[Desertdawg]

Thank you for the help and thank you for all your hard work. I am unfortunately have the very same issue as "red Panda". I will continue to follow the thread here and see what happens. I cant get the lights working and running the script causes my system to stop recognizing my AVA base and substitutes a "Thrustmaster Virtual game controller (root)". when I turn the script off it goes back to seeing my AVA base 

[slughead]

Can you share a screenshot of what you see as the virtual controller?

[Desertdawg]

1st image windows game controller, 2nd image TM target script editor

When I turn off script editor is see this.