HOTAS Warthog LED Controls

[Scooternutz]

Hello,

 

Has anyone had any luck with programing the LEDs within TARGET?

[ivanwfr]

Yes, and you're welcome to ask for clarification if necessary at using script attached to this thread: TARGET - Advanced programming.

 

I use them as a feedback to acknowledge some actions like Gear lock and IOUMD shift keys activation... If you have ideas on how to make them useful for something, let us know.

 

And BTW, no luck here, just good old work hours ;)

[Scooternutz]

Yes, and you're welcome to ask for clarification if necessary at using script attached to this thread: TARGET - Advanced programming.

 

I use them as a feedback to acknowledge some actions like Gear lock and IOUMD shift keys activation... If you have ideas on how to make them useful for something, let us know.

 

And BTW, no luck here, just good old work hours ;)

 

 

You are right on the work hours. It does take some time to program a profile but the reward for that time is huge! :thumbup:

[Scooternutz]

I just read through that post and I just can't make sense of it all right now. I was the same way with FOXY and I mastered that. It will just take some time. I am not happy with the plug and play aspect withing DCS only. Don't get me wrong, it is a good thing for those that want a simple solution but I prefer the custom layers along with the real functionality of the first layer. It has made my flying so much better.

 

I am looking to learn about how to make the lights blink when I press certain commands. I would like a light to illuminate when my airbrakes are open. I would also like the entire panel to flash when my Master Caution illuminates.

 

I am still very confused on the friction knob on the right side throttle.

 

I did learn how to custom program the slew axis within TARGET for Black Shark (KU-31). I haven't programmed it for A-10C yet. It is very smooth and accurate in Black Shark. I will program A-10 slew within TARGET and let you know how it works. Right now it is set within the UI.

[Scooternutz]

I programmed the slew control in TARGET and removed the RY/RZ axis settings in the UI. The difference is huge. It is very smooth and accurate. I may be getting more used to it as well.

[hreich]

Is it possible to use some kind of target profile, and at the same time keep default functions inside dcs unchanged?

[bumfire]

A word of warning, if my led's are set to anything but the highest power or off completely, if I set the leds for any power settign inbetween off or full on then the INCR - DCR slider on the throttle suffers spiking.

[ivanwfr]

As far as I know, when you use TARGET, your joystick and throttle is not seen by Windows anymore as their USB drivers are disconnected. They are replaced by a Combined USB virtual device.

• W7 -- Control Panel -- Set up USB game controllers
  

From there, I don't see how it could be possible and those who talked about this did not care to mention how.

 

So, TARGET has to take care of each and every button handling for a single USB virtual device.

 

But it is quite doable, and this is exactly what Thrustmaster is expecting us to use their scripting environment for.

 

Reproducing the default Plug and Play bindings is the ideal exercise leading to mastering this tool. I'm sure Thrustmaster has provided the solution in this particular parallel universe where people think first, shoot later!

[DeepDrummer]

Yes, and you're welcome to ask for clarification if necessary at using script attached to this thread: TARGET - Advanced programming.

 

I use them as a feedback to acknowledge some actions like Gear lock and IOUMD shift keys activation... If you have ideas on how to make them useful for something, let us know.

 

And BTW, no luck here, just good old work hours ;)

 

Thank you so much for the inspiration.

I could find nothing on using the Target GUI to control LEDs other than the manual which is confusing and sparse on this issue but after reading that Scripting manual, I knew what code I wanted to reproduce.

Since my thing is to always try to use a GUI when coding since my eyes are buggy and I hate spending days looking for a missing bracket.

I have got the latest versions of Linux Mint down to never having to go to the command line as well although in the past it was necessary. It's just a me thing.

For DCS I messed with a lot of combinations in the GUI for about a day and a half and then slept on it and then got up and got it done.

I used to scold my staff if they even whispered the word "Can't".

I could be easily to paste the code here but the coders have already got it figured out.

This is for us layman non-coders.

This is so we can just pick button options in the target GUI and have LEDs come on and off

at will.

Well I did some in my youth so it helps when I read it over for sure but this method makes all that unnecessary.

 

I'll try and make a video how to shortly but I am no content creator but I'll post a link hopefully today.

 

Many thanks to all the coders in here that post examples of their code. I'd be lost with out you. Truth.

[Frederf]

Hello,

 

Has anyone had any luck with programing the LEDs within TARGET?

 

What do you need?

      MapKey(&Throttle, PSF, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]43[/color]));    [color=#32cd32]//Backlight Control[/color]
     MapKey(&Throttle, PSM, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]0[/color])); 
   MapKey(&Throttle, PSB, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]86[/color]));

This is the sort of thing I have on nearly all profiles just to turn off the backlight.