Well, since it's confirmed that it is in as an option, everyone will be able to choose their preferred method.
What i would do is map all the combat-related and critical controls to keyboard/stick: Radiators, throttle/prop pitch/mixture, weapons, flaps, gear, carburator heaters, generally things that i need to get to fast.
Then, i would use the mouse for the non-critical controls, or the controls that are used sparingly (eg, only during start-up and shutdown, or once-twice per mission): fuel tank selectors, magnetos, etc.
This way i will have a fast way to interact with the critical controls that exist on 99% of the aircraft, are similar and will be easy to remember, but at the same time i won't have to map an absurd amount of commands that i won't be able to remember for aicraft specific controls that change between different flyables.
For example, some aircraft might have an all-in-one de-icing system and some might have a separate one (wing de-ice, prop de-ice, canopy heater and so on).
Some people with good HOTAS setups might be able to map everything, but i sure wouldn't want to have to remember that ctrl+H is the wing de-ice,alt+H is the prop de-ice, shift+H is the canopy heater and that only applies to 3 flyables, because when i fly something else it has an all-in-one system that i toggle with ctrl+alt+shift+H. Much in the same way, even if i had a programmable HOTAS i wouldn't waste my time mapping things like that, cluttering up my interface and having to remember to use shift-buttons and mode selector switches.
Much easier to know the place of the switch in the cockpit and click it, because all i'll ever need to do is turn it on once on the climb-out and turn it off once before landing.
The clickpit might be slow and not practical for critical controls, but it is very useful for the non-critical or support aircraft systems because it cuts down enormously on the amount of shortcuts i have to remember.
|