Hello,
After a long time without using MSFS 2024, due to a nervous breakdown regarding control management, I decided to come back following the various updates.
But I’m still annoyed because it still doesn’t work.
I use Honeycomb Alpha and Bravo, as well as SpadNext, to manage my controls.
I don’t have any problems with MSFS 2020, but it’s a completely different story with MSFS 2024.
I created a blank profile for my Alpha in “Aircraft Controls.”
For example, I assign the landing lights control to SpadNext, but nothing happens in the cockpit. However, when I switch to Devmode view, the lights control activates correctly because I can clearly see the state change.
So I tried assigning this control not in SpadNext but directly in MSFS 2024, and it still doesn’t work. I’ve watched numerous videos explaining command assignments and read quite a few articles, but nothing works.
I don’t know what’s wrong with my MSFS or my assignments.
And I can’t find a solution. Is there a complete tutorial on these assignments ?
Even my direction commands aren’t working.
Or does anyone use SpadNext and can tell me how to do it ?
Thank you.
See here
Also would help if you would show us what you are assigning via Spad.
Yes, I followed this video. I regularly check out his channel for tips.
I’m not on my MSFS PC right now, and you’ll see my setup when I log in.
Can you screenshot the binding in SPAD please, showing both the on, and off bindings?
I would also suggest that you create an empty control profile in-game. That way there are no conflicts.
I use SPAD, and I find the inconsistency in how different developers expose and use variables to be pretty frustrating at times.
Sometimes a Bvar will animate a switch AND trigger an event. Sometimes a Bvar will only trigger an animation. And sometimes devs use custom variables unique to a specific aircraft.
I’ve found it’s best if I can find a Simconnect event that works, or use a custom variable specific to the aircraft. Failing that it’s just a lot of trial and error finding Bvars, Lvars, etc. that will trigger an event that moves a switch and also executes the desired control.
For example:
- In my Bonanza it’s ‘SIMCONNECT: LIGHT LANDING’ (animates switch and controls the light.)
- In my FSR500 it’s ‘LVAR: LANDING_LIGHT_1’ (animates switch and controls the light.)
- In my Pilatus PC-6 it’s
‘SIMCONNECT:LANDING_LIGHTS_ON’ (only controls the light.)
‘LVAR:Landing_Light_Switch_Position’ (only controls the switch animation.)
It’s entirely possible that there’s a better way for the PC-6, but that’s the frustrating part.
Another thing I’ve found is that it’s good practice to go into Data Monitor, click on ‘Update LVARS’ and wait up to 10 minutes for all the data variables to be retrieved. I don’t know why it sometimes takes that long, and haven’t gotten a good answer to that question. What’s worse is that there’s no progress indication. But if I don’t wait long enough SPAD won’t be able to access variables I might need.
Definitely! My Alpha and Bravo in-sim profiles are both mostly empty. I keep some camera controls active. I also make sure to delete keyboard controls for anything I’m controlling with my Alpha/Bravo or my Streamdecks.
For me its never taken more than a minute, and usually much less than that. It depends on which plane is loaded at that time. For one plane I’ve got ~500 LVARS, and for another its nearer 1100.
Regarding the inconsistencies I guess that’s the nature of providing someone with a tool, as each user will find the best way of using it. I use B-events where possible, but if not I back off to LVAR or even Simconnect events. Whatever works really.
When asked why it was so difficult to program things in SPAD, Les replied, “Nobody ever said it would be easy.”
I don’t find it particulary difficult, especially now that I’m beginning to understand how to use variables and scripting. But it’s still frustrating from time to time, mostly due to the fact that I have so many planes, from different developers, all of whom do things differently. I’m not saying they’re wrong to do so - just that I find it frustrating at times.
How do you know when all the data variables have been imported?
The only way I know is to add data to the list, look at the count, clear the list, rinse and repeat until the list doesn’t get any bigger. I’d love to know a better way.
I don’t think its difficult either, but like anything it gets better as you get used to it.
I think one of the biggest hurdles for new users are the concepts at work, and finding out what you want to set, and the varying methods by which you can find out what to use.
Some like to look at the internal model config files. I prefer a combination of using the "Behaviours " window to highlight a control, and dig through the code it references. Unless its partocularly fiddly I’m usually done with a new plane in 30 minutes or so. The bit that usually takes the most time for me is the starter key on my Logitech Switch Panel. Going from OFF/R/L/BOTH/START for a piston plane is simple, but for a turbine I might want R/L to refer to which fuel tank is active, both to be ignition, and starter being the starter. Then some logic to determine how those get switched off. The logic bit, and order of events, is what can take time, rather than determining what needs to be set.
For example, in the L35, I had some scripts that would disable the yaw damper when it was detected that the main gear was down, and the plane was about 50ft AGL. Then another that enabled nose wheel steering when the nose gear was down, and ground speed was below a certain speed. I could do all that by cockpit switches, but I was happy to apply a little automation to those tasks via SPAD.
It used to take me a long time to do the basics. 
Now it takes me a long time to program my Streamdecks with gauges and controls.
But that’s a whole lot of fun! 