I’ve been using both the Bravo and the Alpha with Spad.next since I got them.
It’s a great piece of software and highly customizable, perhaps a bit too much for my requirements sometimes.
So today I thought leaving Spad.next off and configure the Bravo only within the sim.
The basics work fine, but I quickly found myself in a ditch, when trying to map things like, (for complex twin) Reverse thrust, Prop Feather, Fuel cut off, Fuel Selectors, Hold HDG sets the but to actual heading, a few other more.
So I went back to Spad that that’s that.
However, I’m quite stubborn, and I think it should work, right? So anyone here could copy and paste configurations for those pesky bindings, I’m sure other people are having issues with?
I am a happy Spad user myself but I never used it with my Bravo. Always did the Bravo in MSFS and it works just fine. Even moreso, all the autopilot buttons and dials I never ever touched even within MSFS, they just worked out of the box.
Cool!
That’s what I wanted to hear.
So why do you think it’s not working on my side?
Specifically, thrust Reversers, Prop Feather, Fuel Cutoff, Fuel valve selection, Heading bug to actual heading.
Any ideas?
Cheers!
I got spad specifically for the Bravo, so I could have per-aircraft configurations. I don’t plan to go back to MSFS core configs until 2024 drops with the per-aircraft config support they claim will be available in it.
I’m a little confused by your statement, because we do have the ability to have per aircraft configs in 2020. Granted, it doesn’t switch configs automatically, but I use @Sonicviz’s brilliant Aircraft Manager to switch the controller configs when selecting an aircraft.
So far I’ve been happy with mapping the Bravo using the built-in available assignments. I don’t mind using the mouse in VR.
Another thing to bear in mind is that the game’s native controller implementation causes, like, 50 Hz sim events for every control that you bind natively to the Bravo. With all the Bravo’s switches and knobs, that adds up to servicing sim events at ~1000 Hz. That’s a lot of unnecessary load on the system.
Spad.next just sends a single sim event any time a button or switch’s state changes. That’s orders of magnitude less.