In lieu of streamlining the entire control binding system (choose ONE variable type and stick with it, not L and K and B vars, etc.), we need access to set LVARs in the default in-game control settings window. It’s incredibly frustrating to try to use the in-game settings to bind controls to peripherals when even default aircraft use LVARs that the system won’t hook up. Having to use SPAD, AAO, HangarControl, MobiFlight just for basics like turning on lights or avionics is getting out of hand. Those programs do wonders for cockpit builders and seriously advanced simmers, and in that case they’re 100% appropriate. But I just want my landing light switch on my Alpha to bind to the landing light switch in the NXCub, and I can’t do it without modifying an LVAR.
If I had to guess, I’d say there’s literally 0% chance they’re going to do this.
The reason why I’ve unassigned pretty much everything from in-game controls in both MSFS2020 and 2024 and I don’t touch these in-game things with a flight level 500 pole. SPAD is the way (at least for me, though obviously others are having the same success using other equally great apps).
Even if they somehow added simconnect event and bvar/lvar in-game support for PC users, it’d still have very basic mapping functionality compared to specialized apps that have been around for years and with people running 100% of their flight sim hardware off them. Even if Asobo did add lvar support, I wouldn’t care to use it as everything is already running fine off spad.
It’s not as simple as just adding a binding. Custom variables and events often need other parameters to make them function so you would also need some way of applying these different parameters.
I also can’t ever see this happening. When the sim comes up short like it does in many areas you have to look for alternatives. We are lucky that in this case there are very good alternatives. We can’t always say that for all the other issues.