mykejb

I'm having problems showing/hiding the HUD in the iFly 737Max8 in MSFS2024. There's a VC_HUD_MOVE_VAL Lvar that controls the position of the HUD but if I set the position to fully down the information display isn't visible, just the HUD panel. Does anyone have a script that pops the HUD up/down correctly? Thanks!

Not sure where the problem with this is likely to be. I have a StreamDeck profile with Event buttons that send one event on press and a different event on long press. The buttons work fine on a hardware SD-XL but don't work on SD Mobile. I've tried using both the long press down and up events but neither work. Interestingly, if I have a button with just a keydown event the event is sent as soon as I touch the on-screen button. If I have a button with a keydown (event A) and a long-press keydown (event B) the event isn't sent until I take my finger off the button at which point event A is sent. I was expecting event B to be sent if the delay between touching the screen and removing my finger is longer than the long-press timeout of 750ms.

How do I go back to editing the master config with a plane loaded with a different livery? For example, I have a master config for FSLabs A321 and I have a different livery loaded that links back to that master config. How do I add a binding to the A321 config so it will apply to all liveries without going back and loading the basic plane again?

Replacing those DLLs lets AAO work with the latest vJoy drivers which is good as it means I can have AAO and PilotsDeck working at the same time. Still need to do some more testing, but it's looking positive so far.

I got it from GitHub - BrunnerInnovation/vJoy: Virtual Joystick which seems legit. There do seem to be a lot of versions floating around from different forks from the original. Just unfortunate that the interface seems to have been changed so it's not compatible. Anyhow, AAO works fine with the older version so I'm happy 🙂

OK - so it was very basic!!! The version of the vJoy interface embedded in AAO is 2.1.8 which doesn't seem to work with the latest 2.2.2 version. I loaded the 2.1.9 version of the vJoy driver and it now works perfectly. 2.1.8 didn't load in Win11 due to a driver problem but 2.1.9 fixed that.

Hopefully I've just got something very basic wrong here! I have a script that contains simply (VJBD:1|1) (SLEEP:2000) (VJBU:1|1) If I test this script by triggering it from a StreamDeck it shows the commands in the debug window with the delay between down/up, so I know that they're executing. BUT neither MSFS2024 or the vJoy monitor app see the button press occurring. Nothing else is accessing the vJoy interface so there's no conflict there I can see. I have only one vJoy device, the vJoy interface is enabled in AAO and I can see that device in the "Show vJoy devices" dialog. I have a regular button assigned to a vJoy device as in the release notes so it gets initialised. AAO version 4.54 b08, vJoy version 222 Help appreciated !!!!

The one thing the FSL has is state saving - if the Fenix had that I'd jump on it, but sadly it doesn't so I'll probably go with the FSL.

I had freezes every so often when I rebuilt my PC recently. Was working perfectly before, but the rebuild had freezes every minute or two. Turns out it was the Streamdeck software. The latest version caused freezes. Rolling back to the oldest version that worked with PilotsDeck (6.5) stopped all the freezes and I'm now back to a smooth system. Just as a test I updated to the latest Streamdeck and the freezes came back. Rolled back again and everything is good again.