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 !!!!

Edited June 21, 2025Jun 21 by mykejb

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.

Sorry, but I don't know about a new version. The latest original version from SourceForge was the 2.1.9, but there is no API for that version, so AAO has to make do with the 2.1.8 SDK

I've tried looking at the new(?) vjoy.org site, but that one seems like a scammers landing page to me. I was immediately blocked from going there by my AntiVirus.

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 🙂

15 minutes ago, mykejb said:

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 🙂

Not sure if that will work, but you can try downloading the two library dlls from the SDK off the same site and dropping them into AAOs program folder. It may work - or it might not, depends on how AAO sees them. Not working in this case means that AAO won't even start - so save the old DLLs just in case.

vJoy/SDK/c#/x64 at master · BrunnerInnovation/vJoy · GitHub

vJoyInterface.dll

vJoyInterfaceWrap.dll

C:\Program Files\LorbyAxisAndOhs_MSFS24

Edited June 21, 2025Jun 21 by Lorby_SI

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.