One TM Warthog profile vs. two sets of Pilot/RIO controls

[hobbes57]

Hi,

I'm using a custom F-14 profile for the TM Warthog that I'm starting and running with the TM Script Editor (or whatever the tool is called). It has all of my pilot controls nicely mapped to my Hotas. I've not changed any default F-14 keybinds in DCS itself. This works lovely - as long as I'm in the pilot seat.

Now I'm starting to dabble with some RIO controls and would  like to use my Hotas as well. However, when I use "2" to switch to the RIO seat, my Hotas of course still sends the pilot keybinds when I press any Hotas button.

Do you know of any way in which I could switch between a "pilot" and "RIO" F-14 TM profile, preferably on the fly, when I press "1" and "2" in the sim? I would like to keep all my Hotas mapping external from DCS, if possible, relying on default keybinds and the TM scripts.

How do other Thrustmaster Warthog Pilots/RIOs solve this "switching" issue?

Thanks! And many thanks to Heatblur for a really high-quality module

 

[_Hoss]

If you are running TARGET GUI you can use the IN/OUT function on the stick, IN = Pilot, OUT = RIO. You can build two distinct profiles. On the throttle you have UP/MIDDLE/DOWN modes, thats two more profiles besides the "Middle" default mode. Plus Sequence and Chain commands. Its all quite easy to do in the GUI function.

[draconus]

19 hours ago, hobbes57 said:

However, when I use "2" to switch to the RIO seat, my Hotas of course still sends the pilot keybinds when I press any Hotas button.

But they don't work then, right? The DCS should prevent any pilot input when you're in a back seat.

[_Hoss]

They should work just fine. 

[hobbes57]

For anybody interested, I looked at https://whitemagic.github.io/JoystickGremlin/ which has something called Modes. They seem to be just what I'm looking for, so I'll try it out sometime:

Mode

In certain situations it can be beneficial to split a profile into several parts, called modes. Each mode can have their own individual set of physical input to action mappings. For example in flight simulators this can be used to have one mode for air combat, one for ground attack, and one for communications. One powerful feature of the mode system is the inheritance capability. A mode can inherit from a single parent which results in the child mode executing whatever action their parent defined for a given input if the child has no actions of their own specified. This allows creating basic modes and then fine tuning them in a child mode for particular usage scenarios without having to duplicate common functionalities.