Use TARGET to assign single switches

[Laud]

As promised here's the tutorial how you configure single switches with TARGET while keeping other buttons default mapping in DCS.

 

First use the attached TARGET-Profile as a sample (you can modify it or create a new one according to your needs).

 

SAMPLE PROFILE

 

When you open the profile you can see, only the Throttle is embedded in this profile.

 

 

Then, on the next window, you will see the mapped buttons, while all other buttons are mapped as default DX-butons. Thats quite important! You will also notice that the modified buttons are mapped, using two layers.

 

 

Leave the "Edit configuration" and run the profile! It should then look like the picture below.

 

 

Now start DCS:A-10C! Go to Options->Controls! You should find a column called "Thrustmaster Combined" (see picture below).

 

 

Click into a field within this column. Now the "Load Profile"-Button should be highlighted (see picture below). Click it and then load the deafult TMW-Throttle lua-file (see picture below)!

 

 

Now everything should work like the default Plug&Play configuration, except for the switches you mapped with TARGET.

 

Hope this helps!

Edited December 5, 2010 by Laud

[Raz_Specter]

great thanks

[Druid_]

nice work Jabog

[Galwran]

 

Could you post a blank profile for both the stick and the throttle?

 

And If I make my own profile, do I have to have every button on it mapped, or is there an easy way for force default DX buttons on every button of the controller? (ie. so that they are visible in the side bar, just like in your second picture)

[Laud]

The profile was made by JaBoG32_Woodstock. I'll ask him for a blank stick-profile.

 

If you want to try it yourself, the DX-button-assignment can be found in the small manual that came with your HOTAS.

[Laud]

HERE is a blank profile for the Stick alone.

 

To get a blank Throttle profile, just remap the MicSwitch with DX-Buttons. You'll find the assignment in the printed manual of the HOTAS (p.4+5 (english section)).

 

Remember: This workaround will not work if you want to assign custom keys to both Stick and Throttle. You have to choose one, else you would have to map the whole system in-game or with TARGET manually!

[hassata]

Awesome job. Thanks for taking the time.

[Laud]

No problem mate, it took only 15 minutes.

[Galwran]

No problem mate, it took only 15 minutes.

 

Thanks again :)

 

Btw, have you found out how could one make a custom profile for both the stick and the throttle without running out of DX buttons? I mean, there can be only 32 DX keys in a single controller, but WH has a lot more when the stick and throttle are counted together. So what is the trick to use here?

[Succellus]

:thumbup:Nice work

[Laud]

Btw, have you found out how could one make a custom profile for both the stick and the throttle without running out of DX buttons?

 

That's the main Problem with using TARGET. The only way to go with both devices in a TARGET-Profile is to map the whole thing within TARGET mapping keyboard-presses.

 

Let's hope there will be a future TARGET-Release which makes it possible to handle both devices as individuals.

[Laud]

Looks like we were a bit too early with beeing happy with this solution...

 

Today I figured that if you alt-tab out of the game and then return a handful switches will flip to positions they're not meant to be at.

 

Seems to make no difference wether you chose the sync-option for the TMW or not.

 

This sucks!!!

[Geskes]

Alt-TAB is not working fully currently, I get graphic glitches sometimes when tabbing back in. Sometimes it refuses to reload the game at all, and I will just see a black rectangle top left of my windows desktop.

 

I have solved it personally by using a keyboard emulator. I only needed to add a push-to-talk button so I just had a button emulate the PTT keypress I mapped in TS and I was good.

 

PS my wing uses TS2 which does not support Directx buttons for PTT, I know TS3 does.

[Laud]

Except the described issue with TARGET I NEVER had any issues with alt-tabbing!

 

We also still use TS2 but I don't really get what you did to make it work!??

[Laud]

Cool, looks like I found the problem!

 

It' not caused by any alt-tab issues of DCS. It's because the flip-switches on the throttle-base need to be configured as "pulse" instead of "hold". I'll do a re-work on the profile, test it and then upload it here again.

[Laud]

Argh... For the moment I give up on this...

 

The Flip-Switches which are assigned with only one DX-Button will not survive an alt-tab out and back into the game. Doesn't matter wether they're set up as "Hold"- or "Press/Release"-Buttons.

 

However: As long as you stay in the game everything works fine. Maybe it will change with further builds of the Sim, as it seems like DCS somehow generates a change of state of the switches where it's not meant to do that.

[Laud]

I'm totally confused now!

 

I stepped back to using the Warthog without TARGET, because of the above mentioned Alt-Tab-Issue. I never had any problems with this configuration, but while flying a squadron-training-session last monday I suddenly had some of the switches on the throttle base change their position (ending up with r-engine off) after alt-tab and return to game. This never happened before, without TARGET. So it looks like it's maybe not TARGET causing the problem, but more the fact that some switches are set up as toggles instead of defining conditions in each switch-position.

 

Hopefully BETA4 will bring some further key-assignments, so I can finish my TARGET-Profile without having to screw around with the .lua-files.