John Dowson

I think that's up to them. The problem is that all MF users aren't necessarily FSUIPC users (and vica-versa). I think the best long term solution would be (barring MSFS providing direct access to lvars via SimConnect!) for a single open-source WASM module that provides access to lvars/hvars and also does event processing. Basically a combination of the functionality offered by the MF WASM module and the FSUIPC one.

Yes, shouldn't be a problem to use this with any other WASM module. If any other WASM module is using the same event numbers as the FSUIPC WASM then that will cause problems. However, if that occurs, you can change the event numbers that the FSUIPC WASM uses via the ini files. Not needed for the MF WASM.

Ok. I'll check when I get a chance and report to Asobo. What a/c were you using? And, again, if it was a mod, did you try the vanilla version?

Yes, sorry - I forgot that FSUIPC5 doesn't create an uninstaller. Just delete the folder. You could also edit your DLL.xml file to remove the entry that starts the FSUIPC5.dll - should be under your <User>\ApppData\Roaming\Lockheed Martin\Prepar3D v4 folder.

Have you tried re-installing the P3D client yet? It only takes a few minutes so worth a try, especially as the other user who had this issue said it was fixed by a P3D re-install (although that was complete re-install).

Please download and try again, as I updated the packages this morning, recompiled against the latest version (although I didn't update the version number). I haven't had time to check it works with the latest release yet though, I'll do that now.... If you still have issues, can you tell me what message, if any, was displayed in the main window, and attach the logs from both the WASM module and the client. And let me know if you are using a Steam or MS Store install. Later: just checked and its working ok for me still (steam install), so if its not working for you, please attach your logs.

There is a link on the SimMarket page for the download (and probably in your purchase email...I'm can't remember for sure though...), and also all are products are available from www.fsuipc.com.

Yes, thats normal as it will be receiving both the physical button press and the virtual button presses for buttons < 32. Ok. So that's not recognising them either. You can try that, if you can map you device to a virtual device (using vjoy), and then use vjoy offsets to map the virtual device to the virtual button offsets. I haven't used vjoy in quite a while (over 2 years), so I can't really advise on how to do this (withou looking in detail, which I don't have time for at the moment I'm afraid). I'll also provide you with another lua script for an additional test at some point, which will log the real data when it changes, as opposed to the raw data processed by the Lua. This may show something. However, it may take me a while to get around to this - I'm a bit behind on support at the moment and have a backlog of requests to go though, which will take me a while (this one is near the end of the list, sorry!). John

I do not know where you have installed things. For FSUIPC5, you need to find out where it is installed, and run the uninstaller that should be in the same location as the FSUIPC5.dll. For FSUIPC6, you can uninstall also by using the provided uninstaller (in the same folder as the FSUIPC6.dll), or use the windows app management control panel to uninstall. I cannot advise on the QW787 as I do not have or know that aircraft. Try leaving it installed first.

Go to the Controls page (in MSFS, from OPTIONS), select you device, then click PRESET MANAGER, then + (to create a new profile), then give it a name and click Ok. Thats it. Takes 30 seconds for each controller, and you only need do do this once.

Why post twice, with you second comment being just a copy of the first? The FSUIPC5 installer will not detect FSUIPC6, so it has installed a second copy with your QW787 update. Just uninstall that copy - or, better, when you install the QW787, don't opt to install FSUIPC5, if that is possible. It may be better to uninstall FSUIPC6 as well as FSUIPC5, and then re-install again once everything has been removed.

When you install v6, it will detect your v5 installation and automatically uninstall it. You can install in the same folder, and then re-name your FSUIPC5.ini to FSUIPC6.ini. Of course, you will need a new key/registration for FSUIPC6, available from SimMarket (with a discount applied at checkout for FSUIPC5 license holders). John

Yes, sorry. The initial link was to edit that post for which you don't have permissions. I've corrected this now.

Usually when an axis jumps like that and has two values, its because it is registered incorrectly as a digital axis (on/off) in windows. Your could try clearing the registry entries and letting it re-register. There is a FAQ entry on how to do this for Saitek devices - you need to adjust (vendor and product ids) as needed - see

Yes, I have heard that screws up the exe.xml. Maybe best to make a copy of the EXE.xml before you install the AFC-Bridge, and then if you have issues you could go back to that and then edit to add the AFC-Bridge launch section.

There's also a new SDK with yesterdays release, v0.11.0.0. I'll rebuild FSUIPC7 using this SDK and release later today, so may be worth checking again once thats done.

This topic is for discussion (including bug reports, feature requests, etc) of the FSUIPC WASM module for MSFS and the client API for using this module, available here:

If you haven't already, I think you need to try a P3D re-install, as it seemed to solve this issue reported here:

Yes, that show the device does have the buttons, but I (mistakenly) though the HiDScanner utility also logged button changes, but it doesn't. I'm really not sure why those button changes aren't being recognised. You could try with the full HidDemo.lua script (available in the zip examples archive in your documents folder). The Alpha and Bravo scripts are based upon this. Try temporarily removing your Alpha/Bravo scripts and using the HidDemp.lua - you will need to edit to specify the correct vendor and product Ids.

Ok, yes - forgot about that option (sorry!). That will switch to using the Axis Throttle<n> Set controls using the full range (-16383 idle, +16383 max)

There are AP Wing Leveler On/Off controls (and an AP Wing Leveler Set control) which you can try, but I don't know if they are connected yet (i.e. will have an effect). May also be aircraft (or AP system) dependent. If its not working, it should be reported to Asobo.

That is something for MSFS/Asobo. We provide guides on how to use FSUIPC which gives access to the controls/events exposed by MSFS. There are now two types of profiles - those in MSFS that are attached to your controllers/devices, and those in FSUIPC which are per aircraft (or group of aircraft). They are different. If assigning a controller in FSUIPC (whether using profiles in FSUIPC or not), it is a good idea to start with an empty profile for that controller in MSFS. If you just create a new profile in MSFS, it will be empty by default. You just need to do this once for each of your devices (except keyboard and mouse - its best leave the default MSFS profiles for those, at least initially). If using a renamed previous in (from FSUIPC4/5 or 6), ,make sure you delete the contents of the [General] section and let that get rebuilt. Also clean profile aircraft names (or replace them with the MSFS equivalents), or start again with a clean/fresh one and start from scratch.

Ok, then your log makes sense then, and it shows that FSUIPC isn't interfering and the correct events are being sent when you click on the doors you want to open. I don't know why these aren't working. OK - that was still in the ini file that you posted though. And there are no other assignments anyway - what do you use FSUIPC for? You can remove this now as its not an issue, I just mis-understood your log file. I'm really not sure what to advise, as FSUIPC is not doing anything on your system I cannot see how it can be affecting the door operation within P3D - its only logging the events). Maybe @Pete Dowsonmay know more?

Ok. Strange as the lua script should provide access to those buttons as the alpha one does for the Alpha. I don't know why this isn't working for you. It will be unteresting to know if the HIDScanner utility recognises those buttons.

Ok, but that should work, expect I am wondering why you have this assignment: 35=PC,0,C1005,512 -{: Joy C (2) Button 0}- Do you need that? FSUIPC maintains the button flag - from the Advanced User guide: So you shouldn't also toggle the same flag as assigned to the button (in your assignment) as that will result in it changing back to the same state (i.e. toggles twice).