are there plans to unify common settings accross modules?

[aledmb]

there are settings that would be best dealt with if they were unified accross modules and not specific to each module.

 

a simple example of this is the controls indicator (accessible with rctrl + enter)... each module has its own implementation, but the location on screen (corner) and maybe even the color scheme could be unified in the general game settings, as well as the key binding to show or hide it.

 

another example is the kneeboard key bindings... each module seems to have its own bindings and some even have extended functionality... the gazelle lets you set and map shortcuts to specific pages, while most of the other modules barely offer next/previous page binds... in my view, kneeboard functionality should be unified accross all modules... it should be a one time configuration for all existing and future modules.

 

these are the two features i can remember right now, but there are probably a few more that could benefit from such change.

[aledmb]

another thing that is spread accross multiple places is language settings.

 

you can have your ka-50 with an english cockpit and abris in russian without noticing... you need to set another language option in the gameplay tab of the settings screen.

 

these probably don't need to be tied to each other, but they certainly deserve to be shown together.

[Mars Exulte]

The reason they're not unified is mostly as you described here :

"each module seems to have its own bindings and some even have extended functionality"

 

Because they are not unified in any significant sense, each is produced by its own developer and functions according to whatever notions they prioritise or desire. In other words, just because the commands have similar names and/or functions, doesn't mean that the coding behind them is related. End result : Not necessarily as simple as just "unifying them" when it would require a significant rewrite of code.

 

You have to program dozens, if not hundreds of commands per module anyway, the handful you could potentially save by "unification" is negligible.

[aledmb]

The reason they're not unified is mostly as you described here :

"each module seems to have its own bindings and some even have extended functionality"

 

Because they are not unified in any significant sense, each is produced by its own developer and functions according to whatever notions they prioritise or desire. In other words, just because the commands have similar names and/or functions, doesn't mean that the coding behind them is related. End result : Not necessarily as simple as just "unifying them" when it would require a significant rewrite of code.

 

You have to program dozens, if not hundreds of commands per module anyway, the handful you could potentially save by "unification" is negligible.

 

well, ok... but why do we need specific kneeboard implementations for each module?

 

kneeboards only have next/previous and mark/go to key binds.

[Mars Exulte]

You said some of them have extended functionality, and then referenced the Gazelle as having more than just basic commands, which is why I said what I did. So, I'm not sure what you're talking about now...

 

Anyway, I don't know. Like I said, each module is built completely independent of the others, so just because they're doing certain things doesn't necessarily mean they're all the same. I'm not opposed to unifying keys, but there are relatively few places where that is applicable really.

[aledmb]

You said some of them have extended functionality, and then referenced the Gazelle as having more than just basic commands, which is why I said what I did. So, I'm not sure what you're talking about now...

 

Anyway, I don't know. Like I said, each module is built completely independent of the others, so just because they're doing certain things doesn't necessarily mean they're all the same. I'm not opposed to unifying keys, but there are relatively few places where that is applicable really.

 

i mean there should not be multiple implementations and configurable key binds for the kneeboard system.

 

it should be independent of the aircraft you're flying.

 

in my opinion, they should take the gazelle implementation (as it's the most advanced i've seen until now) and make it the only one available to all aircraft.

[PeaceSells]

I wouldn't go as far as asking for unification of the systems, but the basic keybindings at least should be the same (bring up kneeboard, bring up radio menu, etc.). Why not?