Options contolled by livery / MCP option with paddles

[BodoM]

Hello,

1. Options contolled by livery

as you can select several option in the preferences:

- steam gauges
- eye brows
- winglets

they shoul be defined in a "livery.cfg" in the livery folder to provide an automatic preselection when loading the livery. Otherwise you must manually chance them any time when selecting a different livery.

2. Optional MCP with A/P paddles

As you offer optional steam engine gauges it would be nice to also offer an alternate MCP which that the paddles for the A/P engage. This type was used by several airlines like Delta, Lufthansa and Southwest.

Thank you.

[Litjan]

Not a bad idea - maybe it should not even depend on the livery (as for example Lufthansa had both options for autopilot engagement), but a user could set up a combination of preferences including the livery and then save them under a unique name...

[AngelOfAttack]

12 hours ago, Litjan said:

Not a bad idea - maybe it should not even depend on the livery (as for example Lufthansa had both options for autopilot engagement), but a user could set up a combination of preferences including the livery and then save them under a unique name...

As the reg number came with livery, I think link to livery is good enough, if you want different config for same airline, just have different livery for same airline

[BodoM]

I am fine with the reg number and link to a livery.
Felis 747 has a "livery.cfg inside the livery folder and inside the cfg file you store:  "tailnumber=N809MC" for example.

So here it could be = "D-ADIG" for Air Berlin and DBA. 

[rosseloh]

18 hours ago, BodoM said:

I am fine with the reg number and link to a livery.
Felis 747 has a "livery.cfg inside the livery folder and inside the cfg file you store:  "tailnumber=N809MC" for example.

So here it could be = "D-ADIG" for Air Berlin and DBA. 

Notably, the "tailnumber" field doesn't change the painted number on the livery (because that's a texture file; there are dynamic livery reg options but they require more complicated plugins designed to do that in the first place), but what it *does* do is change the tailnumber dataref in the sim, which is useful for external data logging apps or the sim logbook (by default they just show whatever Planemaker is set to, which in this case is D-IXEG which is quite annoying when you fly different registrations!).

So yes, I agree - would be a very nice addition.