John Dowson

Can you confirm that your issue is only when you are in the menus please, and not when you have a plane loaded and a flight started. If that is the case, then your issue would be fixed when I correct the start process. Anyway, I'll do this first and then you can check - I'd rather do this first than install VoiceAttack (although its downloaded ready). John

You could also try FSUIPC6 to see if that makes a difference. There are no functional changes in this area, but the load style/order would be different and may make a difference, so maybe worth a try. To do this, please download FSUIPC6 from www.fsuipc.com. Run the installer, and install in some where like 'C:\FSUIPC6\' (i.e. a separate folder outside of Program Files) - it will default to your FSUIPC5 installation folder - change this! This will uninstall FSUIPC5 but leave all your files. You can skip registration, and save the attached key file to your FSUIPC6 installation folder (it is time-limited for you to test). You can then copy across your FSUIPC5.ini, and rename it to FSUIPC6.ini. Also copy across any other files, e.g. *.lua, *.mcro or any *.dll, that you may use. Then test again with that - just report your findings and if any different. Afterwards, you can run the uninstaller (created in the FSUIPC6 installation folder) to remove FSUIPC6, and then re-install FSUIPC5 to get back to your previous configuration. FSUIPC6.key John

Sorry, I was mistaken - I hadn't clicked the 'Ready To Fly' button. After doing that, MSFS receives my key board input and forwards to FSUIPC7 via simconnect as expected. So I am not sure what is going on in your situation.... I'll download Voice Attack now and install the free version and try with that. I cannot test in VR though. P.S. The 'KeyboardFocus=Yes' is used (sometimes) when you have keys assigned to button presses, and it isn't used for key assignments (MSFS or FSUIPC7 must have the focus for any key assignments to work). Sorry if that confused you - I wasn't sure if your 'commands' were via button presses or key assignments.

Ok, I can see the issue (keyboard commands not working when MSFS has the focus and a wnd window is displayed). Such command work when FSUIPC7 has the focus. I also think the lua is being started too early, but that is a separate issue (that I will also look into).

Hi @SparkerInVR. I'm going to look at this now. Just reviewing the issue and this struck me: But the 'Select Departure Airport' is done when in the main menus, not when you have started a flight. Or am I missing something here? Lua scripts can't (or shouldn't) be started until you are 'ready-to-fly', i.e. out of the main menu and with an aircraft loaded. That is when they should be started... Anyway, I am going to try your script now and will report back. John

@Fragtality I have just done various tests with a simple lua assigned to a button press, and can run this lua when any window has the focus, on the FS display or on my second display, and the lua is executed and there is no change to the focus and no focus issues, so I am at a loss why you are having such focus issues. Could you show me your FSUIPC6.ini file please. John

Did you try this yet?

Ok, thanks for the update. I'll take a look when I get time.

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: