I have been using Axis and Ohs to map controls to MSFS 2024. Until beta 4 I have not had any issues. With beta 4, most of these mappings do not work. An example is ‘AS1000_PFD_COM_Large_DEC’. This used to change the com channel but now does nothing. I can see that the knob rotation is registered in the Windows game controllers and in Axis and Ohs. It just seems to not be communicating with the sim. This happens on multiple aircraft.
Could it be the same as this issue?
https://devsupport.flightsimulator.com/t/su4-beta-1-6-3-environment-variables-e-are-broken/16633
“Bug-logged” status on the dev forum if it is the same (and the likely cause of WASM issues).
It’s possible. I don’t know enough about these things to know for sure.
My bespoke SimConnect application that uses a MobiFlight style WASM module to set and get custom sim events and vars works perfectly with SU4 beta 1.6.5.0 including your quoted example - AS1000_PFD_COM_Large_DEC
Strange. Rolling back to SU3 fixed my issues. Think I will stay there for now.
I’ve had the same issue:
https://forums.flightsimulator.com/t/some-as3000-xx-variables-dont-work
Have the same problem with Spad.neXt.
As soon as I use a B:Var, the game crashes.
same here, as3000 checklist push using Spad. Sim CTD or lockup.
would this also be why some native key binds are no longer working?
For example, “set starter 1” is no longer working to engage the starter on Taog’s 500C
same here - some of them randomly crash, some of them surefire crash (like toconfig with ini a350)
Same with me using a homemade G1000 and Axis and Ohs. I had to revert back to SU 3 as 4 is unplayable if I want to use my setup.
Anyone knows if this is solved in beta 1.6.11?
I came into SU4 with the 1.6.11. builds. I’ve had two CTD’s when running external mapping software and starting a flight, but mostly no problems.