[Lvar/ variable list of twin otter for AAO - external hardware]

vor 20 Minuten, Mathijs Kok sagte:

Believe me, that is incredibly hard.

 

Thank you for your reply.

 

Yeah I understand. But other devs just put out their own LVars for those that do not respond to default bindings. As you do with some DHC6_ ones. When these also move the switches then assignments with the proper tools (Lorby's, spad.next) would be way easier and this would go way further then what is possible now for integrating into a mouseless environment or homepit. You can then check the state of the switches in the cockpit, hear the associated sounds and assign it to ample hardware (be it stream decks, midi boards, alphas, bravos, joysticks and button boards of many makings). At the moment not many switches actually move when pressed, even with the default bindings (like the generators) or that are accessed by LVar change. Many more are not easily accessible (icing and pumps among others) being not default and having no Lvar.

[Lvar/ variable list of twin otter for AAO - external hardware]

So Aerosoft will you make the switches interactable by hardware buttons and include the missing ones? It should be fairly easily doable to expose the BVars as LVars to the outside user with control over the model, no? That would be way easier than any BVar hacks. And it was kind of said this would be done in the pre release thread.