FBW A320 Incompatible keybindings?

[monkiesandtools]

Trying to match the Honeycomb alpha toggles with the FBW A320 I’m running into a whacky sitution with the models toggle switch behavior;

1. Attempting to sync the Landing switch
   
   
   
   logic I’m trying to work towards; if landing light is off, then landing light should fully retract. Sadly the model doesn’t appear to have retract enabled, so the off state would be ok the time being)

I get the whacky sitution that the Nose light ends up toggling opposite of the landing light state

(when landing lights are off)

(when landing lights are on)

In addition, trying to map the nav toogle, there doesn’t apper to be an eqvienlent within the model (it’s denoted as Nav and Logo, the Nav switch control option doesn’t work, while the Logo is a toggle, and not a state)

How the heck can the honeycomb switches be mapped?

[NonstopOyster0]

If you look at the FBW documentation under development you’ll see a section describing the simevents and simvars and lvars. There is a section on landing lights which basically says mapping these to external switches is nearly impossible. I know this doesn’t help but I gave up trying the same thing and just use the yoke for flying (I know should be a stick but don’t have the desire to change things around.)

[Sunday748]

You can or better have to use Mobiflight to add events to your controller. You will find all relevant bindings for the FBW. E.g., engine start is bind to a switch of my TM warthog throttle.