Mapping my controls

[Ice-]

I remember trying out the RoF demo and getting frustrated because a lot of my TM WH controls were already mapped and re-mapping some buttons caused it to do two commands with one button press or something confusing like that.

 

Trying to map my TM WH in BoS seems to have the same confusing effect.  I've just figured out that the two orange boxes icon on the upper right meant the joystick button was mapped to another command as well.

 

So, a few questions:

1.  Is it possible to save "profiles" in BoS?  It seems like there's only the "default" button, there isn't anything to save my settings except the Accept button.

 

2.  How do I quickly check what the "other command" is when a button is mapped to something already?  In BMS, when I am in the controls setup screen and press a joystick button, the list will scroll down to where the button/command is listed.

 

3.  Is it better just to clear everything in terms of mapped joystick/throttle/rudder controls?  Is there a quick way to clear these controls?  I do NOT want to change the keyboard controls as people will invariably use these for instruction purposes, but I want to map my own controls to my HOTAS.

 

Thanks for any help!

[Endy]

No 2 IIRC there's the little red box, that if you hover your mouse over it, it tells you what it's already mapped to.

 

               The first mapping is the worse,  .

[GregP]

One thing worth noting is that the GUI does not seem to support use of a second layer on a HOTAS, thus if you want to use two layers on the Warthog you need to use something like Target. After much frustration with this fact I gave up on the GUI and went back to Target after having not used it for a long time. Even using Target there are other limitations that are often frustrating, such as use of the 3 position switches (letting them stay in the fore or aft position will continue to send the command to the game) and those alone needed to be mapped in game.

 

Thus I've now got a hybrid of Target and in game assignments on my WH, and it's working fairly well.

[Sokol1]

No "Quick Clear" available. And if you are able to do this will have hard times in set all after, some command names need Champollion to interpret.  

 

Just clear (X) the functions that you need put on HOTAS buttons/hat/axis. For example why you need that keyboard arrow keys steer the plane like in default commands? Just erase the and set your HOTAS axis in place, etc.

For each command function the game allow assign three different set of keys, buttons, key/buttons, axis. One key can do two different commands, e.g. the key that reset camera for center view can do this with specific FOV if you set that key for this second function too.

 

A axis can do two different things if used a modifier (limited to Alt, Ctrl, Shift, Win - left and right) for the axis behavior in the second function (E.g. the axis used for wheel brakes can be set with a modifier to act as "park brakes" (function actually not activated in game) - when the modifier is pressed the first function is ignored. 

[vonPilsner]

Your settings are saved in the input folder.

 

The files are:

current.actions

current.devices

current.map

current.responses

 

You can just copy them somewhere.

[Bearcat]

No "Quick Clear" available. And if you are able to do this will have hard times in set all after, some command names need Champollion to interpret.  

 

Just clear (X) the functions that you need put on HOTAS buttons/hat/axis. For example why you need that keyboard arrow keys steer the plane like in default commands? Just erase the and set your HOTAS axis in place, etc.

For each command function the game allow assign three different set of keys, buttons, key/buttons, axis. One key can do two different commands, e.g. the key that reset camera for center view can do this with specific FOV if you set that key for this second function too.

 

A axis can do two different things if used a modifier (limited to Alt, Ctrl, Shift, Win - left and right) for the axis behavior in the second function (E.g. the axis used for wheel brakes can be set with a modifier to act as "park brakes" (function actually not activated in game) - when the modifier is pressed the first function is ignored. 

 

That is fantastic to know.. You just solved a big problem of mine with this post. So it can only do two things.. in other words I could set a command say for AXIS X and then CTRL + AXIS X but not and WIN + AXIS X ... it can only be two commands....