John Dowson

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).

You can still use the letters and assign to that flag. Did you try? You can disable joyletters completely but I wouldn't recommend it, especially if you have assignments to those letters. Could you maybe explain in a bit more detail what you are trying to achieve, What are you assigning the button to? Or are you doing something in lua?

Did you try unchecking the 'Exclude THROTTLEn_SET' on page 3 of the calibration page, and then reverse the axis there for Throttle 1 and Throtttle2? You can still calibrate in FSUIPC when sending to the FS, but this may result in multiple values being received by the sim (due to priority levels). I don't have the FSLA320, you you need to check this. You could also try assigning direct to FSUIPC calibration and to Throttle 1 and Throttle 2 and calibrate in FSUIPC. Otherwise, check that you have 'No reverse zone' checked in the individual throttle calibration screen as this would reduce the available range if unchecked. Also maybe try assigning to the Axis Throttle n Set controls (under 'Send to FS as normal axis) instead.

Your log is very strange: This shows: - letter 'A' (65) pressed, followed by - letter 'S' (83), followed by - '2' key (50) There is no log of a ctrl+shift+ e key combination. Could you tell me what you pressed to produce this log? If it wasn't those keys, then something is seriously wrong.... You do have a TOGGLE_AIRCRAFT_EXIT being sent. This must come from P3D (not FSUIPC7) - did you send this from the UI, or do you have an assignment to the 'A' or 'S' key in P3D? Could you produce another log file for me. Change the TimeForSelect back to 4 before you test please. Attach you log and ini files after the test, and also provide a brief description if what you did (i.e. keys pressed). If you did press ctrl+shift+e in your original test, there may be some memory corruption somewhere. This can be caused by a corrupt weather file - you could try adding NoWeatherAtAll=Yes to the [General] section of your ini file to disable weather for the time being. Could you also try a default aircraft (e.g. Lockheed Martin HC-130H), and test the doors in that. Thanks, John

The problem with the Alpha turned out to be a missing cable, but this doesn't apply to the Bravo. Can you see any buttons/switches at all on the Bravo, i.e. those with numbers < 32? If you run the windows game controller panel, can you see any buttons highlighted there? What are the button numbers shown in the MSFS controllers description dialog (where it shows a picture of your device and the button numbers for each switch) - that should show the button numbers for those < 32. Also check that you don't have power management enabled for that device - and maybe try a different USB port.

Ah, found the problem! You need to connect the short curled ethernet cable (included) from the yoke to the base: see https://forums.x-plane.org/index.php?/forums/topic/205495-switches-not-working-on-the-honeycomb-yoke/ After connecting this, everything works as it should. Do you have that cable connected? John

You shouldn't need the Alpha software installed.... I also cannot see those buttons in the Windows game controller panel. They should show as buttons 1-12 but aren't. I am not sure why. I am going to ask on Honeycomb support. John

I've just plugged in my Alpha and get the same. However I don't think this is to do with buttons in the >32 range. I can see the virtual buttons for those when I switch the starter rotary to Left, Both or Start, and get virtual device 64 with buttons 0,1 & 2 respectively. So the script is working for the buttons > 32. The issues seems to be that the buttons/switches on the yoke, with button numbers 1-12 (according to MSFS) aren't recognised. They are also not recognised in the default Alpha profile for MSFS. I didn't install any Alpha drivers or software yet. Did you? I am going to try that now..... John