John Dowson

Well, its been around for a while, but has been updated to work with MSFS2020. Note that all previous versions of FSUIPC (for FSX and P3D) were .dll files, and so always started with the FS. It only became an option to start manually with MSFS, as FSUIPC7 is now a separate application, a .exe. As such, it makes more sense defining how you would like to use it when you install. It doesn't make much sense (to me, at least) to have this as an option in FSUIPC7 itself, as it is something that once set you would very rarely want to change. In fact, you will most ptobably be updating FSUIPC7 via the installer more often thn you would want to change this option (as I release updates every 4-5 weeks). I could add this as an option within FSUIPC7 itself, but I think there is far more useful functionality to be added (e.g. some indication of an update being available) at the moment, and I doubt I would ever have time to get around to implementing such a feature. John

How are your axes assigned? If 'Direct to FSUIPC Calibration', you can reverse the axes in the calibration dialog. If you are not calibrating in FSUIPC, you can scale the input axes values - to reverse them, simply add ",*-1" to the end of the axes assignment line in your FSUIPC5.ini file. See the section Additional parameters to scale input axis values in the Advanced User guide. John

Links work just fine here. What are the properties of the link? This is what one of mine looks like (created with the link shell extension): VoiceAttack also starts ok via the [Programs] section for me. However, creating a link to the VoiceAttack.exe doesn't seem to work for some reason. It runs ok according to the FSUIPC7.log file but no window is displayed and no process running when I check in Task Manager. Maybe you can show me your FSUIPC7.log file - there should be errors reporting why the run failed. If the run error indicates a permissions issue, try installing VoiceAttack outside of your Program Files folder, which has some windows restrictions which can cause issues. John

If you install the auto-start component, FSUIPC will be automatically started with MSFS. That is what the auto-start component does! If you don't want FSUIPC to auto-start with MSFS, re-install and de-select/uncheck the auto-start component. You will then need to start FSUIPC7 manually when you want to use it. John

Ok, so VPilot itself is not an FSUIPC client, but when using the later version of FSUIPC, which you need to use FSC 10, this somehow prevents VPilot from working correctly. How strange.... Presume you are doing the in the VPilot UI, with the 'Mode C' button, no? If so, I can't see how FSUIPC can be interfering with this, especially as it doesn't even use FSUIPC. I think you need VPilot support to determine why the Mode C button isn't working when 4.976 is installed. Regards, John

Sorry, but I have no idea what FSC 10 is and cannot support that - does that not have its own support forum? I am still slightly confused though... You said: So is everything working as expected with 4.974? You also said: Is that a vpilot issue? How have you configured FSUIPC to activate Mode C on Vpilot? If you can let me know (and show me your FSUIPC4.ini file), we can try adding some logging to see what the difference is between 4.974 and 4.976. Maybe you could start by activating logging for Buttons & Keys as well as Events, and produce a short log file with each version where you try activating C mode on Vpilot (via FSUIPC). I can then compare the log files. Thanks, John

Ok. I don't think comments are allowed in an auto line, but I am surprised that would crash FSUIPC.... Try just: [Auto] 1=Lua PMCO John

I don't think the file is needed/copied there any more in 5.2 - I do not have one there... No need to do this. Can you show me/attach your FSUIPC6.log and FSUIPC6.ini files and I will take a look. John

@mtjoeng Took a look and seems there was an issue determining the execution folder when passing command-line parameters. Could you try the attached version please. Should work with symbolic links and bat files, although I haven't tried the latter: FSUIPC7.exe John

Updated.

The only update for v4.976 was a change om the build environment, which is worrying... It could be related to the VC++ libraries, as people have had issues with FSUIPC7 on new Windows 10/11 builds. Could you try installing (or re0installing) the VC++ 2015, 2017 & 2019 redistributables from here (both x64 and x86): https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads Please uninstall them first if already installed (individual or combined). Once that's done, could you try 4.976 again to see if the issue remains. Thanks. John

Ok, thanks - that is interesting... Could you test with 4.975 please? I'll see if I can dig out (or build) a copy.. John

I'll will update shortly...

You need to (manually) change the profile entry to a substring match for the aircraft fir which you want to use the profie, so something like: Please see the User manual. You do not need to change profiles, let alone quickly. Profiles are loaded automatically, based on the loaded aircraft, once configured for that aircraft. You only need to create or assign an aircraft to an existing profile once. You will need to select the check box for profile assignment when assigning for buttons or keys, as all aircraft also use the general assignments for these (unless overridden by a profile assignment) so you have the choice of where to save such assignments, but if you have selected axes to be profile specific, all axes will be profile specific for that aircraft and no general axes profile is used. This is why you have the option of importing current general axes assignments into your profile specific axes assignments when you create a new profile. .John

Maybe this is helpful: http://thegeekforge.com/2017/11/10/arduino-lua-fsuipc-tutorial-001_a/ John

The events should be queued. I don't think this is quite true... I think some events will be queued but for others only the last event may be available. Best to experiment/test for this. John

Ok, thanks for the info. Note that for those experiencing the Windows 11 issue with MSFS not being detected and FSUIPC7 closing soon after start-up, even thought MSFS i still running, there is a new version of FSUIPC7 available in the following post which allows for an additional FSUIPC ini parameter to disable the MSFS window monitor which will keep FSUIPC7 running: This additional functionality will be released in the next official release, v7.2.12 (in the next few days). John

IPC reads/writes logs reading and writing of offsets from external 3rd party FSUIPC clients, so you certainly don't need those activated. Try logging of Events. If you can assign it in the sim, you can assign it to a keypress (or keypress combination) in MSFS, and then assign your ignition switch/button to the keypress in FSUIPC. Did you have an aircraft loaded and ready-to-fly? The options are only available in this state, not when in the MSFS menu. You can send any control via offset 0x3110. To send keystrokes to the FS, you can use offset 0x3200. To use the arduino directly with FSUIPC (i.e. to get it recognised so that you can assign to its buttons/switches in the FSUIPC assignments panel), it needs to be recognised ass a HID joystick type device, or over connected via COM ports and programmed using lua. I can't really help you with this, but google should help you get started, ot maybe look/ask on https://www.cockpitbuilders.com/. John

From the Download Links -> Updated Modules section of this forum, or over at www.fsuipc.com. Yes - just run the installer and it will replace the dll. John

Yes, but isn't that to manage the Community folder / MSFS add-ons? Loaded (and killed) by what? Not sure what you are asking here... Then sounds like something else is going on. I'll take a look at these issues sometime next week and report back afterwards. John

If you are already using links, as opposed to shortcuts, then no, it won't help. I would have expected Windows to handle the link, but sounds like its not doing that. I'll take a look sometime next week. Maybe try Run2=KILL,"k:\Program Files\VoiceAttack\VoiceAttack.exe -nofocus -profile /"MSFS 2020 VR/"" Ok, then the command with arguments also isn't going to work....What does the FSUIPC7.log file show for this? If the BAT file is starting a separate (detached) thread, then FSUIPC will have no knowledge of that thread and won't able to kill it. John

Yes, sorry - missed a d.p.! The crash will be related to the closing down of the lua threads when using the COM interface, and is most probably a timing issue somewhere, and I doubt very much its an issue that can cause problems elsewhere. The events should be queued. Cheers, John

Hi Trevor, that looks like FS Real Time is unregistered. You need FS Real Time support, sorry - I can't help with that. To check if FSUIPC is registered or no, open FSUIPC or check your FSUIPC4.log file. However, I suspect FS Real Time only uses the unregistered facilities of FSUIPC, so if just using FSUIPC for FS Real Time, you probably don't require an FSUIPC license. Cheers, John P.S. You are using quite an old version of FSUIPC4 - you should update to the latest version, v4.976. Only the latest version is supported.

Just download it from the original post.... John

Well, your [Auto] section was fine in the ini you posted: Your issue was certainly in the button assignments, which were assigned to LuaDebug and Lua, and not LuaSet and LuaClear, as specified in the instructions and as I have been trying to tell you... But nevermind. Glad you finally got it working, although you still don't seem to understand what your issue was... It helps to try and understand how the lua file is working! Enjoy your weekend. Cheers, John