[Request] Higher granularity in master controls give/takeover

[AndreGeddert]

The concept of giving and taking master-controls does not fit for every plane. On the DC-6 for example, the flight engineer operates the throttles while the pilot flying controls the yoke and rudder. A quick fix for this would be to move the throttles in the aircraft yaml definition to the [shared] section, but this could cause trouble if for some reason the pilot flying touches the throttle axes, overriding the value the flight engineer has set.

A solution to this could be to define more than one [master] section of controls, maybe a [secondary] section. In the GUI there could be buttons for "take master controls" and "take secondary controls". If an aircraft yaml did not define a secondary section, the button could fall back to "take controls" for simplicity.

[KeinDatenvolumen]

+1

[Jannis-D]

+1 That would be great!

[AndreGeddert]

As a workaround for the DC-6 you can you this yaml: https://cloud.geddert.net/s/FqNpnNpM5FX9wWH This makes the throttles shared, so that flight engineer and pilot can use them simultanously.

[Sequal32]

Planned for the next major rewrite, V3, which will be started next year!