How to use thrustmaster warthog on other modules?

[WelshZeCorgi]

I'm trying to figure out how to use the warthog hotas on modules that are not the a10c, but can't get the 2 way switches to behave just right. Instead of forward for on, aft for off, it's forward for on, then cycle aft + forward to turn it back off.

 

I tried using the target program but it has this annoying fault where on the A10c, there is no programmable mvr flap settings, so the 3 way flap switch can only be set to flaps down or flaps up.

 

Is there another way to use the warthog on other modules like the harrier while also having 2-way switches working properly?

[Dunx]

I use RS Mapper to achieve this...

 

https://forums.eagle.ru/showthread.php?t=205492

 

You can assign a keypress to each toggle-switch position.

[WelshZeCorgi]

It seems like it works like the target software. If so, I would still have the issue of having the mvr flap setting working on the A10C

[Dunx]

Sorry, I'm not familiar with the A10C and MVR, I assumed you needed to trigger a key press for each position of the physical switch.

 

The physical three-position "Flap" switch on the Warthog Throttle is mapped to two separate buttons in RS Mapper. Each button can trigger a key when pressed and another key when released...

 

Flap Up = Button 22 Press

Flap Center = Button 22 Release / Button 23 Release

Flap Down = Button 23 Press

 

I know this can be done in TARGET but I had horrible problems with it due to device combining.

[LeCuvier]

If you are willing to edit .lua files, there are lots of posts with examples in the thread "How to set up toggle switches (a tutorial)". Post #214 (page 47 right now) has a tutorial document on the subject.

If you are not willing to edit .lua files, I guess TARGET is the best solution. I used it for some time before starting to modify .lua files. If TARGET has a bug when using the A-10C, just don't start TARGET before launching DCS.

PS: I don't understand the problem you are having with MVR and I don't even know what MVR stands for. But there must be a way around it. Maybe wioth a little .lua edit :).

[Bob_Bushman]

I believe you can setup target to simply have the switches work as impulse swithces, that also triggers on both movements, but it's been a while since I have used my warthog.

[VpR81]

I believe you can setup target to simply have the switches work as impulse swithces, that also triggers on both movements, but it's been a while since I have used my warthog.

 

That is correct. If you want to have all switch positions beeing mapped functional, target is the best way to achieve this without having to mod any .lua files. For example you can map the China Hat forward, backward and middle position as 3 separate inputs.

[JUICE-AWG]

I Edit the Lua files, but I am still at the stage where I get a friend to guide me through it...but it is wonderful when the switches work like you want them. Find a friend to help you and I think I have a couple of videos on the basic overview of Lua edits. See if any of your friends are able to assist in that! The top video is an overview and the next one is a little more in depth. Good luck and send me a PM if I can help.

[Bob_Bushman]

I Edit the Lua files, but I am still at the stage where I get a friend to guide me through it...but it is wonderful when the switches work like you want them. Find a friend to help you and I think I have a couple of videos on the basic overview of Lua edits. See if any of your friends are able to assist in that! The top video is an overview and the next one is a little more in depth. Good luck and send me a PM if I can help.

 

It's probably the method with the most satisfactory and more correct result.

Problem is everytime DCS updates you will have to manually edit every file for every module all over again.

 

Granted you will be likely able to just copy paste your lines in, but it can quickly become a long process for every hotfix ED deployed, if you have a 5-6 modules that you hope to use with some regularity it becomes old fairly quickly.

[paeagle]

I tried using the target program but it has this annoying fault where on the A10c, there is no programmable mvr flap settings, so the 3 way flap switch can only be set to flaps down or flaps up.

My settings for the flaps on A-10C is shown in the pictures below (no key command is set for FLAPM switch position) ...

 

 

 

 

This way I get adequate switch position for each separate flaps position (up, maneuver - takeoff, down). It is only needed to check and if necesarry to synchronize the switch and the flaps position during the startup procedure. Than it works correctly until I leave the plane.

[Lange_666]

T.A.R.G.E.T. solution:

 

// Flaps Lever

// Since the A-10C has a 3 position flapsswitch, things need to go in sequence

MapKey(&Throttle, FLAPU, CHAIN(PULSE+Flaps_Up, D(), PULSE+Flaps_Up));

MapKeyR(&Throttle, FLAPU, DX23); // Flaps_Down

 

MapKey(&Throttle, FLAPD, CHAIN(PULSE+Flaps_Down, D(), PULSE+Flaps_Down));

MapKeyR(&Throttle, FLAPD, DX22); // Flaps_Up

PS: credit goes not to me, picked this up somewhere but can't remember where...:book:

[WelshZeCorgi]

It's probably the method with the most satisfactory and more correct result.

Problem is everytime DCS updates you will have to manually edit every file for every module all over again.

 

Granted you will be likely able to just copy paste your lines in, but it can quickly become a long process for every hotfix ED deployed, if you have a 5-6 modules that you hope to use with some regularity it becomes old fairly quickly.

 

Is it not possible to save the .lua file, make a duplicate copy and replace the .lua file after update?

[Bob_Bushman]

Is it not possible to save the .lua file, make a duplicate copy and replace the .lua file after update?

 

Yes but doing so would remove any tweak or improvements done from ED's part. Or potentially if any of the action ID's change it could worst case break the bindings enterily, although that is very unlikely.

[LeCuvier]

It's probably the method with the most satisfactory and more correct result.

Problem is everytime DCS updates you will have to manually edit every file for every module all over again.

Not if you use a program like JvGME or OvGME. I just run "disable all mods" before, and "enable all mods" after the update.

[LeCuvier]

Yes but doing so would remove any tweak or improvements done from ED's part. Or potentially if any of the action ID's change it could worst case break the bindings enterily, although that is very unlikely.

I've managed mods with OvGME for years, and the problem you describe only exists with relatively "young" modules, especially in the early months of early access. But with Notepad++ it's very easy to compare the modified file with the new stock file, and update the additions into the modded file.

 

That makes it a non-problem in my experience.