Hammer, meet nail.
I’ve just started to understand the concept of the different VARS, and am barely scratching the surface in regards to how to find and use them to make my aircraft do what I want, with the peripherals I’ve got.
My comment on Bvars is based on what I’ve learned over at the SPAD discord. It’s been said many times that "If a peripheral switch/button makes an event happen, but you don’t see the corresponding switch/button move in the virtual cockpit, it’s a B-event, or Bvar.)
I think I understand what you’re saying about ‘split logic.’ A recent example would be the starter button in the DCG Spartan 7W. I found the ‘Start_Engine’ command (forgive me, I’m not at the sim, so I don’t recall the exact data name) and when I press the button on my peripheral I’ve bound it to, it opens the cover, depresses the start button, cranks the engine, and disconnects after a short while. Works like a charm.
But when I found that flipping the Primer switch in the virtual cockpit sends an event called ‘Toggle_Engine1_Primer’, I programmed a button on my Bravo to that command. When I press that button, I see the event happen in Event Viewer, but the virtual switch doesn’t move.
To my limited understanding (mostly based on what I’ve been told in the discord) that means the primer switch animation is a Bvar.
Maybe it’s something altogether different, and your ideas will hopefully add to my knowledge of such things. I appreciate them.
My goal is to eliminate cockpit mouse clicks completely. To do that I need to know what commands the virtual buttons/switches are sending, and how to bind them to my peripherals. It’s not easy, for sure.