Default control profiles

[h3pilot]

I love that DCS allows you to customize control profiles/button mapping for each aircraft, but I hate to have to start from scratch with each new aircraft.

 

Most aircraft share a large number of similar systems. A core set of control terms could be established for all add-on aircraft. For instance: Landing Gear Extend, Landing Gear Retract, Flaps Extend, Flaps Retract, Pitch trim, Speed Brake Extend, Canopy Open, Flare Dispense, Starter Engage, Zoom View In, Zoom View Out, Pause Game, etc .....

 

The user could then map these "core" game and aircraft functions to create a "default" control profile that would work with every aircraft. Or at least each class of aircraft, such as default jet, default prop, default helicopter.

 

When you purchased a new add-on aircraft, you could load your saved "default jet" profile into your new F-5E and all the core controls would be set. You would then only need to map the additional F-5 specific functions.

 

I have a HOTAS Warthog and use many of the same buttons to perform the same function on multiple aircraft. I use the trim hat for pitch and roll trim on EVERY aircraft. I use the speed brake switch for the speed brakes on every aircraft that has them, I use the same button on the joystick to zoom my view in and out on virtually every aircraft, etc ...

 

It is annoying to have to re-map the same function to the same button, over and over again.

[cichlidfan]

An example of what is wrong with your premise.

 

If you are using the trim hat to trim the P-51, then you are doing it wrong. It is an axis and should be mapped as one.

[Art-J]

Hell no. I prefer the current system and have to agree with cichlidfan here. There's always a question of whether one wants to unify basic assignments across different aircraft, or tries to replicate the layout of buttons and their functions, as on the actual plane - for example, a trigger under your pointing finger might work as a guns trigger in some planes, but works as a radio button in Mi-8. Button on top of the stick might work as a weapons release in many fighters, but works as an airbrake activator in the MiG-15. And that's how I set up my Warthog in every plane, so that my buttons layout matches the DCS (or real) manual for said aircraft. Makes learning the module easier. Belsimtek seems to be providing basic Warthog assignments thought in the same manner.

 

And even If I later forget what the button does, pressing it on my WH directly corresponds to animation on the virtual stick on the screen, with tooltips and all. Wouldn't be possible with proposed "default" setup.

 

Not to mention, that even within a single category - DCS warbirds as a most blatant example, the functional differences between cockpits of Dora and Mustang are so big, that apart from roll/pitch/yaw controls, differential brakes, elevator trim, guns trigger and gunsight range adjustment, you can't really set them up in any similar fashion - any kind of "default prop" profile would literally have to contain a handful of functions - and this is what DCS already does nowadays.

[Kozmyk]

The common commands can be transferred from dissimilar planes by exporting and then importing the controller profiles.

Where the command has the same name it will be used, where the command name is different it will be discarded.

It has worked for me so far.