Thrustmaster TARGET and keybindings...

[MikeMikeJuliet]

Hello everybody!

 

I have been making my own TARGET script profiles for some time now. Those of you who have dipped into the skripting should know that the skript outputs the keys you tell it to output. Now the problem arises when you cannot use keyboard unputs, such as the new UI layer commands for VR use, where you can bind mous keyes to your controllers.

 

As we know as well, TARGET combines the controllers you set as one virtual DX-device.

 

Now the question is, is there a way to use a blank, non-skripted button or switch on my controllers, while the skript is running to make a keybind within a software?

 

That probably made no effin' sense, so let me expand a little. If I make a skript in which a particular button is left unmapped and I go to dcs, is there a way for me to bind said button within dcs?

 

This would also help with Simple Radio Standalone, since the program doesn't apparently register keyboard inputs while DCS is the active window... again meaning that I cannot skript a certain key to a button, because it doesn't work.

 

 

Without the skripting I lack a lot of features on my controllers, and I would need to revert to way clunkier control setups with major limitations... or else I need a third hand to press buttons on a separate controller...

 

 

Regards,

MikeMikeJuliet

[Svend_Dellepude]

Can't you just map them as DX buttons?

TG1, DX1);

TG2, DX2);

etc...

[cichlidfan]

Can't you just map them as DX buttons?

TG1, DX1);

TG2, DX2);

etc...

 

Agreed. That is what I would do. Once the Warthog button is told to output DX? then you just have to map it in game.

[og_wolf]

You cannot map ingame unmapped button (in target). Unmapped means unused. In fact you should never leave any unmapped button even if you for some reason don't plan to use it as target sometimes assigns random DX buttons to unmapped ones what can lead to confusion and/or collision. Such buttons should be mapped to 0 (not "0" just 0, null).

 

Like guys above said if you want to map some buttons ingame, not in target you need to assign to them any keystroke with DX buttons being the best choice in this case. Warthog should send regular DX inputs to the system and it might help you with Simple Radio.

[MikeMikeJuliet]

Thanks for the input. For some reason I was unaware I could just simply do that. Now that you mentioned it, it's very obvious.

 

I'm at work and got a busy weekend, but I'll come back if it doesn't work for some reason.

[MikeMikeJuliet]

Well, I sure was a dumbdumb not figuring that out. Now I can do all sorts of key combos. I don't know if it's bugged on SimpleRadio Standalone's end or what, but the DX outputs via the skript don't seem to work in it... they do work on DCS though, so I'm kind of half way there. Need to do some more testing.