Common control assignments

[Lace]

I wish DCS would allow common control assignments.  I don't understand why when I allocate a control for 'Airbrake Extend', or 'Trim Nose Down' it can't then apply to all aircraft with that function.  This is especially time consuming for multiple variants of the same aircraft (Why do the A-10C and A-10CII for example require different assignments?). Perhaps there could be an 'Override Common Assignment' next to a control if you want to deliberately allocate something different to a particular aircraft. Or a pop-up asking 'Apply change to all modules?' when you change an assignment.  

Obviously some aircraft have specific requirements, and that is fine, but there is a huge amount of commonality between modules, that it could be a great time saver for new installs, or HOTAS hardware changes.

[Baldrick33]

I use JoyPro for this, it is brilliant!

https://github.com/Holdi601/JoystickProfiler

[Lace]

1 hour ago, Baldrick33 said:

I use JoyPro for this, it is brilliant!

https://github.com/Holdi601/JoystickProfiler

Looks interesting, might give it a try.  How use-friendly is it?

[MAXsenna]

Like you you wrote, some modules are different. But in general I agree.
Add all the kneeboard keybinds to this, with populated keystrokes. Should be in the common category.
Could make things easier for 3rd parties as well.

Cheers!

Sent from my MAR-LX1A using Tapatalk

[Lace]

27 minutes ago, MAXsenna said:

Like you you wrote, some modules are different. But in general I agree.
Add all the kneeboard keybinds to this, with populated keystrokes. Should be in the common category.
Could make things easier for 3rd parties as well.

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

Yep, so many could be in a 'common' category.  Eject, views, axes, basic flight controls, kneeboard, trim, etc.  JoyPro looks good, but it would be nice if we didn't have to keep going to 3rd party solutions and workarounds.

[Baldrick33]

3 hours ago, Lace said:

Looks interesting, might give it a try.  How use-friendly is it?

JoyPro takes a bit of getting into but it has videos explaining each bit. Once you get the hang of it then it is invaluable IMHO.

[SharpeXB]

This is just the way it is… and since many modules are made by third parties this sort of coordination just might not be possible. Also any solution can’t screw up the settings for players who have already assigned controls or make the 3rd party devs go redo things. Likely this will never change much for that reason. 
Honestly the number of shared controls isn’t so great and mapping these doesn’t actually take very long. 

[Lace]

33 minutes ago, SharpeXB said:

This is just the way it is… and since many modules are made by third parties this sort of coordination just might not be possible. Also any solution can’t screw up the settings for players who have already assigned controls or make the 3rd party devs go redo things. Likely this will never change much for that reason. 
Honestly the number of shared controls isn’t so great and mapping these doesn’t actually take very long. 

It might only be 5 or 10 minutes, but for example, the latest Beta installed the new Mirage F1 EE, I already have assigned all the controls for the almost identical F1 CE, but I need to start again from scratch for the EE. There are a lot of modules which have different versions of the same aircraft, and that's even before you consider the commonality between all aircraft.  If I install a new HOTAS, then that's 5-10 minutes for every module, which is easily hours of work.  As suggested above, JoyPro might be the answer.

[upyr1]

I've asked for this as well. At the bare minimum here is all we need to map

1. ptich
2. yaw
3. roll
4. right throttle
5. left throttle
6. trim
7. target cursor
8. guns
9. weapon release
10. toe brakes
11. brake lever
12. air brake/ spiers
13. landing gear
14. flaps

Then helicopters

1. cyclic
2. collective
3. throttle lever

There probably a few other things. I have never seen good argument against doing this (perhaps becuse there isn't one)

We have sharpeX trying to claim that it would break existing modules - that's easy to fix when the generic controls profile gets introduced it won't change the settings for existing modules - unless you tell it to do so. (Apply template or set to default might work) Then we have people bringing up the curves and sensitivity setting claiming that becuse they don't use the same curves for everything therefore we shuld be able to set the basic controls. 

[Baldrick33]

7 hours ago, Lace said:

Yep, so many could be in a 'common' category.  Eject, views, axes, basic flight controls, kneeboard, trim, etc.  JoyPro looks good, but it would be nice if we didn't have to keep going to 3rd party solutions and workarounds.

When you start using JoyPro it demonstrates how uncoordinated the controls aspect has evolved between modules.

Every control has an identifier which looks unique but it isn't and gets used for different operations. 

For example the controls identifier d3017pnilunilcd2vd0vpnilvunil will retract the Yak flaps. It also turns off the Spitfire magnetos and the MiG-15 Transfer Pumps!

Creating a database of common control identifiers correctly assigned for each aircraft is no mean task and would need updating regularly. I just can't see the resource being available as nice as it would be.

In the meantime JoyPro is a very clever bit of software, it is well worth exploring and is an excellent method of handling controls where you have multiple modules.