Jump to content

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


Recommended Posts

Posted

Thank you for your work and sharing it with the community!!!

First it didn't worked after i installed everything as you discripted, then i installed the updated TMS-LED file you posted here in july and now it works everything as it should. 

I like it, all the LEDs shining on my ViperTQS while I fly with the F-16 🙂

Many thanks and all the best for you 👍

My System: i7 7700k @4,2Ghz, MB GigaByte Aorus Z270X, 32GB RAM @3200MHz, ASUS TUF RTX 4070 12Gb OC, Win 10 64bit

HOTAS Warthog Joystik/Throttle, TM Rudder, 2x TM F-16 MFD, WinWing ICP, Track IR5

Modules: Modern: F/A-18C, F-16C, A-10C II, AV-8B,  M-2000C, FC 3; Cold War: F-14, AJS-37, F-5E, MIG-21bis, MIG-15bis, F-86F, L-39; WW II: Bf-109 K-4, FW-109 D9,FW-109 A8, P-47D, P-51D, Spitfire LF Mk. IX

Terrains: Nevada, Normandy 2.0, Persian Gulf, Syria, South Atlantic, Super Carrier

 

Posted

That's the reason I do not use VR... I want to see and touch my hardware-cockpit... 😉 

My System: i7 7700k @4,2Ghz, MB GigaByte Aorus Z270X, 32GB RAM @3200MHz, ASUS TUF RTX 4070 12Gb OC, Win 10 64bit

HOTAS Warthog Joystik/Throttle, TM Rudder, 2x TM F-16 MFD, WinWing ICP, Track IR5

Modules: Modern: F/A-18C, F-16C, A-10C II, AV-8B,  M-2000C, FC 3; Cold War: F-14, AJS-37, F-5E, MIG-21bis, MIG-15bis, F-86F, L-39; WW II: Bf-109 K-4, FW-109 D9,FW-109 A8, P-47D, P-51D, Spitfire LF Mk. IX

Terrains: Nevada, Normandy 2.0, Persian Gulf, Syria, South Atlantic, Super Carrier

 

  • 2 weeks later...
Posted
On 9/6/2024 at 8:39 PM, slughead said:

Any luck with this?

Sorry for the late update I removed DTC and experienced one crash; unfortunately, I forgot to save the log file but then reinstalled DTC and haven't had any crash since

  • Like 1

Signature

  • 4 weeks later...
Posted

DCS2target doesn't work anymore with the newer Target Version (TARGET_v3.0.24.618_rev1).

Is there a solution for this?

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

 

Posted

Thanks for your answer! This is what I get:

 

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

TMHotasLEDSync v1.0.4

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
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
Installing filter driver to VID_044F&PID_0415. Please Wait...Done!
USB HID device "AVA Base"(USB\VID_044F&PID_0415\205732995746) selected
USB HID device with hardware id "VID_044F&PID_0414" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Script stopped!
Done
Device name set to Thrustmaster Combined

Runtime Error: STOP request received while running main on line 63 in "C:\Users\micky\Saved Games\DCS.openbeta\Scripts\dcs2export\TMHotasLEDSync.tmc"
Error: Script run timed out!
 

Have to mention this is with the AVA-Base.

with TARGET_v3.0.23.1205_rev1 everything works fine!

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

 

Posted

I have the same configuration as you do but with the addition of Thrustmaster pendular rudder pedals.

The error occurs on this line:

if(Init(&EventHandle)) return 1;

It's a standard Thrustmaster line that all Thrustmaster scripts must call to initialise the event handler. Have you tried running one of the scripts that Thrustmaster supplies?

Also, take a look at the link below. It doesn't appear to be the same problem you are experiencing, but it might be worth checking.

 

Posted (edited)
On 10/25/2024 at 11:46 PM, slughead said:

I have the same configuration as you do but with the addition of Thrustmaster pendular rudder pedals.

The error occurs on this line:

if(Init(&EventHandle)) return 1;

It's a standard Thrustmaster line that all Thrustmaster scripts must call to initialise the event handler. Have you tried running one of the scripts that Thrustmaster supplies?

Also, take a look at the link below. It doesn't appear to be the same problem you are experiencing, but it might be worth checking.

 

Not yet, but I will. btw the error cannot be related to the winwing stuff I use?

(winwing skywalker pedals, MFD's, ICP, UFC+HUD)

edit: Don't know what happened. I changed nothing but everything works now!

Edited by MickyG

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

 

Posted (edited)

Hello, 

I had to update some items in my VIPER TQS pack. I am now unable to run the program here is the error I seem to be getting. All i did was update my driver on the pack and the Winwing ICP as well.

Thanks,

TMHotasLEDSync v1.0.4

Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
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
USB HID device with hardware id "VID_044F&PID_0415" cannot be found
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
DCS2TARGET v1.0.7
F-16C_50
 

Edited by Rusty88
Posted
13 hours ago, Rusty88 said:

Hello, 

I had to update some items in my VIPER TQS pack. I am now unable to run the program here is the error I seem to be getting. All i did was update my driver on the pack and the Winwing ICP as well.

Thanks,

TMHotasLEDSync v1.0.4

Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
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
USB HID device with hardware id "VID_044F&PID_0415" cannot be found
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
DCS2TARGET v1.0.7
F-16C_50
 

 

This is a problem with the Thrustmaster Target installation/registry settings. You can find the solution here: 

 

  • 1 month later...
Posted

Hey @slughead I gave the files a try today and didn’t have any luck. I unzipped the files as instructed and placed them in the right place within “Saved Games”. 
 

I used the LED file you shared in July. When I initially load and then run script in the script editor the Viper Panel’s LEDs cycle through once. However, when I then load DCS I’m not getting the landing gear status (3 green LEDs), Landing Gear Warning (1 red LED on landing gear level) and the RWR lights. 
 

Please can you help me out? 

Posted (edited)
12 hours ago, slughead said:

I’m going to need something to go on. The Thrustmaster console output and dcs.log would be a start.

But before that. Please get the files from the links in the first post that are on GitHub. I can only support the latest version.

Here you go @slughead - this was done using the files linked to in the original post.

Script Output:

Running script: C:\Users\Darren\Saved Games\DCS\Scripts\Hooks\TMHotasLEDSync-main\source\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[3]:
1: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"
2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200"
3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
USB HID device "Viper TQS"(USB\VID_044F&PID_0412\386433503530) 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_0415" cannot be found
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

dcs.log

Edited by DarthTater
Added log file.
  • Recently Browsing   0 members

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