Enforce key bindings before publishing

There is nothing worse than having a home cockpit and still being forced to use the mouse for a particular input. This really kills immersion when going through checklists. It is very annoying because many keybinds just do not exist. Like TBM/Kodiak: Inertial seperator, CWS…

Also there should be a better quality assurance in regard to how at least basic systems work. Turboprops do not move backwards at immidiate beta range. It needs a lot of beta in order to move backwards. During taxi beta is used to control the taxi speed. Such things should just not happen.

I ask Asobo to only publish an aircraft once Asobo or the developer have published ALL keybinds without any exception and Asobo has tested at least the fundamental behaviour of a specific aircraft.

It´s a great idea to have all control options available in the keybindings, but unfortunately you can´t request too many things at once in this subforum, I recently had this kind of thread closed for that reason. Some of these keybinding requests are already here. You´d need to make separate request for internal separator, another for three way switch support, third for keybindings for Garmin intruments (possibly separated by type) etc. etc…