Holt

Just getting back to this. I've followed the documentation for vJoyOffsets, but when I try to run it, I get an error message 'The application was unable to start correctly (0xc000007b). Click OK to close the application". I notice that the vJoy installation folder has an x64 folder, but not an x86 folder. Could this be a problem between a 32-bit vJoyOffsets.exe and a 64-bit vJoyInterface.dll? My version of vJoy was installed as part of the Brunner CLS2Sim software. They use it for interfacing to the push-to-talk button on the A320 sidestick. Perhaps I need a different version of vJoy?

The PTT event needs to go to SayIntentionsAI ATC, which is a standalone program, not to the FS. The AI software gets the audio stream from the microphone, but needs help knowing when I’m talking on the intercom so it doesn’t have to feed a continuous audio stream to ChatGPT for speech recognition, which would be prohibitively expensive. For ATC radio transmissions it is triggered by the PTT switch on the Brunner joystick, which then results in a vJoy button press via the Brunner hardware interface software. That vJoy button is finally read in SayIntentionsAI. I was hoping to mimic the same flow using FSUIPC and a Lua script. Pro-Sim will not create the vJoy event for me as does the Brunner software. It will only write to a FSUIPC offset for custom user actions.

I was planning to use the intercom switch on the Airbus Radio Control Panel by Skalarki. Their hardware talks to a proprietary software on the PC which interfaces directly through an SDK into the Pro-Sim software. Pro-Sim allows me to use a software “gate” (intercom switch set) to write into an FSUIPC offset. That part is all working fine. The problem now is how to get from a FSUIPC offset to something that SayIntentionsAI can see. I saw the advantage of a joystick button press being that it wouldn’t require window focus to work, unlike a keyboard press. I guess I need a different plan.

Oh…that would explain everything then.

I seemingly cannot get FSUIPC7 to “press” a button on a vJoy device. I created vJoy device ID 1 using the Configure vJoy tool, and am monitoring it using vJoy monitor. I can use the vJoy feeder demo app and see the button states toogle in the viewer as expected. Then I wrote a LUA script which is running as I can see in the log file. It loops endlessly while writing a ‘1’ to offset 0x3340 as below while true do ipc.writeUD(0x3340, 1) sleep(1000) end However, there is no change in status in vJoy monitor. I would expect to see button 1 set on vJoy ID #1, similarly to using the feeder app. I can confirm that the value 0x01 is being written into the correct offset 0x3340 by putting a watch on that location. FSUIPC is just not delivering that news to vJoy, or so it appears. There are no errors in the log. In debug mode I can see the execution repeating the lines over and over in the while loop continuously. The script has not terminated either with or without errors. What could I be doing wrong? I feel like I must be missing a basic concept here as this appears to be a rather simple task. P.S., My reason for wanting to do this is that the Airbus A320 sidestick has but one trigger on it for radio comms PTT. For SayIntentionsAI ATC app, it would be nice to have a second intercom PTT button somewhere to talk to the AI copilot and/or cabin crew. For this I need vJoy to interface with SayIntentionsAI. Configuration: FSUIPC 7.5.1, Windows 11 24H2, MSFS 2020, Brunner CLS-E Joystick (A320 version), full A320 hardware cockpit from Skalarki, SayIntentionsAI, ActiveSky for MSFS.

Iff uninstalling is what it takes to fix the problem, then that is what I shall do. I won’t have any need to reinstall. Thank you.

I have unselected the menu items 'Open on Start', and 'Auto-Connect to FS', and yet upon launching MSFS 2020, FSUIPC somehow always starts. I find this behavior obnoxious, not least because I have specifically selected it not to. It's like a virus has infected my system. So before I uninstall it along with all the previous crapware that has infected my system, is there a way to prevent it from auto-starting every time MSFS 2020 launches? I hate to come across as impolite, but this really is unacceptable. A program should not force itself on me like some obnoxious ad pop-up that won’t go away. I truly hope there is a reasonable explanation and fix for this. I know FSUIPC is widely used and has a long and well established track record in flight simulation. Nevertheless, my patience is just about ended.