BUTTONS AND SWITCHES: VERIFY THE SUPPORTED COMMAND
Fenix publishes a keybind table because its external systems do not respond to every default simulator command. Start with that table and the current V3 changes. Name each profile entry for the actual cockpit action and test press, hold and release. A command appearing in MSFS does not prove the add-on consumes it as expected. [78, Externalised architecture and useful default bindings]
V3 adds autopilot key-event bindings according to its launch changelog. An old blanket statement that autopilot bindings are unsupported therefore cannot be applied wholesale to V3. Equally, this addition does not prove every generic event works. Test the exact event, observe the FCU/FMA result and retain the verified mapping. [77, Added MSFS key-event bindings for autopilot and pedal disc]
For a maintained switch, establish whether the interface sends an explicit state or a toggle. Test a mouse change followed by a hardware change and compare the result. This is a proposed state-agreement test; obtain the supported event or variable for that specific control before scripting it. [79, Switch manipulation using installed cockpit variables; author-proposed test]