Warthog HOTAS conflicts and button names

[imacken]

I have been trying to get the TARGET profile in this thread https://forums.frontier.co.uk/showthread.php/22379-Thrustmaster-Warthog-Configuration-amp-Sheets to work with my Warthog HOTAS.
The profile runs OK, but when I start configuring the joystick/throttle binding from 'Empty', I get conflicts in ED. For example, different buttons on the HOTAS bring up the same joystick button ID and a 'conflict' is flagged.
Also, when assigning certain buttons/switches I get a keyboard command showing when the switch/button is pressed on the HOTAS.
Any help on this?
Thanks a lot.

 

[StiTch]

TARGET does not work well with ED (it isn't a very elegant bit of kit to start with).

You have a couple of options, but your best bet is usually to create a profile in ED where each function is bound to an arbitrary keypress - boost to Q, Landing gear to W, whatever - make sure these are all on record in a document/screenshot etc., and then profile TARGET according to this. If you need to later rearrange your HOTAS keybinds, do it within TARGET and not ED.

I have too many issues with how TARGET works otherwise. Sometimes it will simply not put ANY keypresses into ED while a profile is running, at other times it will stop toggle switches working in both directions, so I have to move the toggle down/up every time I want to deploy landing gear, then again to retract. Using just the profiler to keybind is a longer startup process and inelegant asf, but when implemented is immensely more reliable.

If you want help relating specifically to Mikey's script I'd put a question in that thread and PM him.

EDIT: If you're ever feeling down, go look up what TARGET is supposedly an acronym for...

 

[Andy_Pipkin]

I only use Target to switch the LEDs on my Warthog throttle on or off....everything else is configured in ED.

 

[furrycat]

A DirectX device can only have so many buttons. It might be 32, from memory but maybe it's a few more. When you run TARGET and configure a profile the software creates a virtual device, which Elite sees as ThrustMasterWarthogCombined. The device is "removed" from the system when TARGET stops. Your throttle and stick together have many more than the limit of buttons which can be assigned, so the software assigns a particular button on either the throttle or joystick to a particular virtual button on the "Combined" device. If you run out of buttons you have to reassign some or assign them to keypresses instead. Or, and this is probably what has happened to imacken, you have multiple physical buttons generating the same virtual button.

There is a trick which is not documented in the TARGET manual. Normally when you start your profile, as well as creating the ThrustMasterWarthogCombined device the software also removes the individual throttle and stick devices, respectively ThrustMasterWarthogThrottle and ThrustMasterWarthogJoystick. If you add the following lines to your script (you are using the script editor, right, not the GUI?) the software will not do that; you will have three devices to play with!

Configure(&Joystick, MODE_FILTERED);
Configure(&Throttle, MODE_FILTERED);

Unless you are actually using a script function such as CHAIN() for a particular button you should bind it to a null event like this:

MapKey(&Throttle, MSU, EV_HID_NONE);

Now when you press MSU on the throttle Elite will see an event for that button from ThrustMasterWarthogThrottle rather than whichever virtual button you happened to have configured on ThrustMasterWarthogCombined.

Null out all the buttons you aren't doing anything clever with and make sure that your bindings XML references the "real" device. Then you can use your limited pool of virtual buttons for the funky stuff.

 

[imacken]

Thanks so much guys for your help.
No, I'm not using the script editor, I'm just running the TARGET script from the thread I posted a link to in post #1. I tried to understand what was going on, but I think I'll give up on TARGET and just configure everything in game.
I have no idea how to write the code that TARGET requires, and at the moment, I can only see that it's only use is to switch the LEDs on and off!
I'm sure I am missing something, but I couldn't get over the conflicts that appear in the setup linked to in post#1. For example, the IGN R Normal gives a JOY32 and so does the Speedbrake back, so a conflict occurs.
I know it must be me, but....

 

[Andovar]

...but I think I'll give up on TARGET and just configure everything in game.

That's your best bet.
I fought with TARGET for a while, and eventually gave up. it really is a PoS

On a side note, when doing all the configs in ED, I get some controls with identical labels. So there's a "Joy 1" from the stick, and a "Joy 1" button on the throttle. But they're recognized internally differently, so there is no conflict.

 

[Windscreen Smudge]

I'll be honest. I never even considered using target for bindings and have only ever done it through ED. I use it for tuning S curves and that's it.

 

[imacken]

I'll be honest. I never even considered using target for bindings and have only ever done it through ED. I use it for tuning S curves and that's it.

The thing I don't get (one of the many!) is, why do the controls have to be set in ED and TARGET? Why are they not taken from the TARGET profile?
For example, using the script from the link I posted to in #1, has all sorts of bindings in TARGET, yet, MickeyTT says to load the TARGET profile and then start with the Empty profile in ED and populate it with all the bindings as used in the profile.
Why is that necessary? I honestly can't see the point of the TARGET profile except for switching on a couple of LEDs. I am clearly missing something fundamental here!

 

[Windscreen Smudge]

The thing I don't get (one of the many!) is, why do the controls have to be set in ED and TARGET? Why are they not taken from the TARGET profile?
For example, using the script from the link I posted to in #1, has all sorts of bindings in TARGET, yet, MickeyTT says to load the TARGET profile and then start with the Empty profile in ED and populate it with all the bindings as used in the profile.
Why is that necessary? I honestly can't see the point of the TARGET profile except for switching on a couple of LEDs. I am clearly missing something fundamental here!

Macros, S curves and multiple profiles.

 

[Yaffle]

The thing I don't get (one of the many!) is, why do the controls have to be set in ED and TARGET? Why are they not taken from the TARGET profile?
For example, using the script from the link I posted to in #1, has all sorts of bindings in TARGET, yet, MickeyTT says to load the TARGET profile and then start with the Empty profile in ED and populate it with all the bindings as used in the profile.
Why is that necessary? I honestly can't see the point of the TARGET profile except for switching on a couple of LEDs. I am clearly missing something fundamental here!

It gives you the option to code macros, and allow multiple functions per button as each button has several 'states' a bit like pressing shift on a keyboard.

For really impressive work try here - https://forums.frontier.co.uk/showt...edroid-s-Enhanced-Thrustmaster-Warthog-Script

That uses scripting, which is a bit different from TARGET. It does have a preset ED thingy you can use though.

 

[imacken]

It gives you the option to code macros, and allow multiple functions per button as each button has several 'states' a bit like pressing shift on a keyboard.

For really impressive work try here - https://forums.frontier.co.uk/showt...edroid-s-Enhanced-Thrustmaster-Warthog-Script

That uses scripting, which is a bit different from TARGET. It does have a preset ED thingy you can use though.

Thanks for that.
I tried running that script and got nowhere. It just repeats a loop of disconnecting the devices in TARGET and I have to force close the app. I'll try posting on that thread.

 

[Aussiedroid]

Thanks for that.
I tried running that script and got nowhere. It just repeats a loop of disconnecting the devices in TARGET and I have to force close the app. I'll try posting on that thread.

Hi imacken,

That is a known issue in my profile at the moment. Still working on why, but I seem to have been able to stop it in a test build I have. In the mean time, you can actually load the script through the TARGET GUI and it will work fine.

Pop me a message on my Steam guide or the forum thread if you have any issues and will try to help.

Also regarding the original issue, I think furrycat hit the issue on the head, but to add, I also found that for some things I needed to map directly to a key and not a DX mapping. Sometimes mapping to the DX in Elite and profile would result in no actions taken, when there is a layered response on the button. For my profile this meant setting up some double mappings on the ED side, and then map the keyboard button to the TARGET side. Never really got to the bottom of it, but ended up going with what worked.

I'll have to disagree with the others in the post stating TARGET is a POS. Lack of understanding doesn't make the software crap guys

It is without a doubt the most powerful software package to come with a controller I have ever seen... although without a doubt the hardest to use too! LOL

AD

 

[Windscreen Smudge]

Hi imacken,

That is a known issue in my profile at the moment. Still working on why, but I seem to have been able to stop it in a test build I have. In the mean time, you can actually load the script through the TARGET GUI and it will work fine.

Pop me a message on my Steam guide or the forum thread if you have any issues and will try to help.

Also regarding the original issue, I think furrycat hit the issue on the head, but to add, I also found that for some things I needed to map directly to a key and not a DX mapping. Sometimes mapping to the DX in Elite and profile would result in no actions taken, when there is a layered response on the button. For my profile this meant setting up some double mappings on the ED side, and then map the keyboard button to the TARGET side. Never really got to the bottom of it, but ended up going with what worked.

I'll have to disagree with the others in the post stating TARGET is a POS. Lack of understanding doesn't make the software crap guys

It is without a doubt the most powerful software package to come with a controller I have ever seen... although without a doubt the hardest to use too! LOL

AD

CH is harder, in my opinion, but almost as good. I just haven't had a need to do a bunch of scripting for my Warthog. I've got some S curve profiles for practicing FA OFF but otherwise just binding things through ED has been sufficient.

Still snagged a copy of your setup though. Going to see if I can tinker with it (Read: rip the guts out of it until it's unrecognizable as anything that was once remotely functional. I have a CH throttle) and see if I can get anything that feels better than my current setup out of it. Thanks for the superb steam guide!

 

[Aussiedroid]

CH is harder, in my opinion, but almost as good. I just haven't had a need to do a bunch of scripting for my Warthog. I've got some S curve profiles for practicing FA OFF but otherwise just binding things through ED has been sufficient.

Still snagged a copy of your setup though. Going to see if I can tinker with it (Read: rip the guts out of it until it's unrecognizable as anything that was once remotely functional. I have a CH throttle) and see if I can get anything that feels better than my current setup out of it. Thanks for the superb steam guide!

Tinker away!! Use whatever you need.

Thanks for the kind words.