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

[Desertdawg]

I am using a powered hub. I tested with the AVA base connected directly to the PC, but the outcome was still the same.

[Desertdawg]

I have the lights working now, but still no AVA base with the script running...

I had to edit the file name in the saved games/dcs/scripts/hooks

it was named "dcs2artget.lua"

I renamed it "dcs2target.lua"

I have no idea how the "t" was removed, but now the  lights  work properly

 

[slughead]

Mine looks like this when the script is running: I get the "Thrustmaster Combined," which is created by Thrustmaster when the script is executed, but I also retain the AVA Base. Please speak with Thrustmaster for assistance.

[CM2024]

I just got the Viper TQS Mission pack, booted into DCS, and the script works perfectly. The gear handle is actually cool now. Thank you again for creating it!

Installation was easy, since I had the script already installed. I just disconnected my old warthog throttle, connected the new Viper, and it just worked.

I do miss the console lighting, especially when starting up or shutting down the engine. This was so immersive on the warthog.

Can the console lighting option be added? Or have the script check if the engine is on or off and then turn the lights on or off?

[slughead]

13 hours ago, Desertdawg said:

I have the lights working now, but still no AVA base with the script running...

I had to edit the file name in the saved games/dcs/scripts/hooks

it was named "dcs2artget.lua"

I renamed it "dcs2target.lua"

I have no idea how the "t" was removed, but now the  lights  work properly

 

Is your Windows account an admin account or a normal user account? Have you tried running the Thrustmaster software with admin privileges?

[Desertdawg]

I appreciate you not giving up on me. I

just tried running as admin, still switches ava base to virtual controller.

 

[CM2024]

@Desertdawg Not related to the script here, but I had a similar problem with the Ava base not getting recognized in DCS.

I solved it by installing Joystick Gremlin (https://whitemagic.github.io/JoystickGremlin/) and mapping the Ava base to a virtual controller. Then in DCS, you get a new virtual input device and can map the controls from the Ava base to it.

What I do now is to 1. start Target for light script, 2. start Joystick Gremlin for the Ava base, 3. start DCS.

It's a bit involved but may help. Good luck.

[Desertdawg]

@slughead Could this be the issue?

 

 

[Desertdawg]

@CM2024 I appreciate the info, When I switched from the Warthog base to the AVA base DCS recognized it right away and all I had to do is remap axis and Buttons.

 

 

 

@slughead Been doing some searching and reading , and others also say that target should create a Thurstmaster Combinded controller, but for some reason mine is not doing that.

 

[slughead]

36 minutes ago, Desertdawg said:

@slughead Could this be the issue?

 

 

No. My scripts do nothing with the joystick axis.

31 minutes ago, Desertdawg said:

 

@slughead Been doing some searching and reading , and others also say that target should create a Thurstmaster Combinded controller, but for some reason mine is not doing that

Yes, I mentioned that a couple of replies back. You need to speak to Thrustmaster as the creation of the combined controller is all done internally by Thrustmaster. It’s their bug.

4 hours ago, CM2024 said:

I just got the Viper TQS Mission pack, booted into DCS, and the script works perfectly. The gear handle is actually cool now. Thank you again for creating it!

Installation was easy, since I had the script already installed. I just disconnected my old warthog throttle, connected the new Viper, and it just worked.

I do miss the console lighting, especially when starting up or shutting down the engine. This was so immersive on the warthog.

Can the console lighting option be added? Or have the script check if the engine is on or off and then turn the lights on or off?

Thrustmaster forgot to provide any control over the backlight/console brightness for the Viper. I have asked them if they would add it when I was in contact with the development team. That was a good year ago so I wouldn’t hold your breath.

[slughead]

41 minutes ago, Desertdawg said:

@slughead Could this be the issue?

 

 

Hmm. I have the F-18 and the F-16 stick. I haven’t tried the scripts with the F-18 stick attached. I will give it a go and see if that replicates the problem. What stick are you using on your AVA base?

[Desertdawg]

I'm using the F-16 grip

 

If the issue is in the target software how come yours and other users target software creates the Combined controller , but mine doesn't. That's so weird don't you think..?

I have contacted TM support and they want me to send a video of the issue and the S/N of my AVA base. They said they would get back to me. I'm betting that if they do get back to me they are just going to tell me to not use the script.... lol

I really appreciate your help. I'm still learning all this stuff about DCS and related gear

 

Edited March 8 by Desertdawg

[slughead]

@Desertdawg @Red Panda Can you try this new script please?  Rename your old copy of the file so you don't overwrite it, then copy this file to the same folder and give it a whirl.

TMHotasLEDSync.tmc

Edited March 8 by slughead

[Desertdawg]

@slughead  Good Morning,

First off, thank you for writing the new script. It Works!!
The new script keeps the AVA base and all inputs work. I still don't get the "Thrustmaster Combined" controller in the windows Game controllers application and it still creates the "Thrustmaster Virtual Game controller". I have tested the new script a few times to include a complete system shutdown. Each time the script continues to work. Thank you !!!

[slughead]

That's good news! I will check the change into github. The virtual game controller vs combined controller might just be down to a newer driver; yours potentially being newer than mine. I'd not worry about it.

[Desertdawg]

I hear you on that, if it ain't broke don't fix-it , right!!

It could be exactly that my version of Target is new than yours. I am running v.3.0.24.618

Thanks again for your help...

 

Edited March 9 by Desertdawg

[slughead]

New release! New features!

The following F-16C lamps will be replicated on the second column of LEDS from top to bottom:

1. JFS RUN
2. MAIN GEN
3. STBY GEN
4. FLCS RLY
5. EPU RUN

The following F-18C lamps will be replicated on the first LED, with the lower four LEDs indicating the speed brake position.

1. APU RUN

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.

I will add other indications for the F-18C and the A-10C/A-10C2 soon.

Let me know if you have any suggestions for the F-18C and A-10C LEDs.

[Desertdawg]

Good Morning @slughead
with this update do I have to download both "dcs2target" and TMhotasLEDSYNCE" or just one of them? I'm thinking it's just the dcs2target

 

 

Edited March 10 by Desertdawg

[slughead]

Just now, Desertdawg said:

Good Morning @slughead
with this update do I have to download both "dcs2target" and TMhotasLEDSYNCE" or just one of them?

 

You will need both.

[Desertdawg]

Alright thank you, again thanks for the help getting the ava base working yesterday....I just started using dcs a few months ago and I'm still working on getting my head wrapped around all of this controller stuff and how the game works. Again thank you for your help and patience..

 

 

[slughead]

35 minutes ago, Desertdawg said:

Alright thank you, again thanks for the help getting the ava base working yesterday....I just started using dcs a few months ago and I'm still working on getting my head wrapped around all of this controller stuff and how the game works. Again thank you for your help and patience..

 

 

You’re welcome! Enjoy!

[Desertdawg]

@slughead I updated both files and everything seems to be working properly although I'm not very familiar with the items for the second set of led lights but I did see all lights on at various stages of a cold start. When I update the files in my saved games scripts folder I told my pc to overwrite existing files. The dcs2target file did overwrite to old file, but my hooks file didn't overwrite the .lua files I have 2 .lua file the first one i downloaded and the updated one you just put out. My question is this an issue and should I delete the older .lua file?

[slughead]

2 minutes ago, Desertdawg said:

@slughead I updated both files and everything seems to be working properly although I'm not very familiar with the items for the second set of led lights but I did see all lights on at various stages of a cold start. When I update the files in my saved games scripts folder I told my pc to overwrite existing files. The dcs2target file did overwrite to old file, but my hooks file didn't overwrite the .lua files I have 2 .lua file the first one i downloaded and the updated one you just put out. My question is this an issue and should I delete the older .lua file?

Please make sure you are using all of the files from the zip files. Some have changed and some haven’t. So best to replace all of them.

[Desertdawg]

I believe I did replace all files. can I safely remove the dcs2taget.lua dated 3/7/2025?

 

[slughead]

Yes. The other file is misnamed, although the file's name shouldn't matter. I will correct it.