These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server: https://discord.gg/zjwUTrxmmE
MSFS 2020 not responding to FSUIPC7.5.7 Key Assignments, it's occurring every time.
With the release of GlassOut for multiple monitors I have re-started the migration from P3D to MSFS2020 for my homebuilt B737 cockpit.
When trying to use the FSUIPC7 (Licensed) Key Assignments using Rotor Brake control for the PMDG 737 CDU, the commands totally work as-long-as I leave the FSUIPC7 main page active (see below image & Console Log). The moment I mouse click on any active sim display the commands stop working. Joystick AXIS continues to work.
I have fully uninstalled FSUIPC7 from the PC, cleaned Windows 11 Registry, reinstalled it, applied the license key and the problem persists.
Per the PMDG 737 SDK instructions I’ve confirmed Data Communication Output and Data Broadcasts in the 737_Options.ini
[SDK]
EnableDataBroadcast=1
The CDU Screen Data is enabled for both CDUs:
EnableCDUBroadcast.0=1
EnableCDUBroadca st.1=1
This physical setup worked in P3D with addon iFly737 CBE - Cockpit Builders Edition
Since this occurring on the MSFS side and works immediately after programing FSUIPC7, it seems to be a MSFS issue…I did create a MSFS 2020 Forum Hardware and Peripherals support and they replied with the FSUIPC Forum URL with no other feedback
Any help or suggestions will be appreciated. Thanks in advanced.
[PC Only] Are you using Developer Mode or have you made any changes to it? No
[PC, MSFS 2020 Only] Using DX12
SIOC - Opencockpits USBKeys for the Capt & FO CDU key (button) press capability
If you do not see the key events logged in the console window, then they are not being sent to FSUIPC7. FSUIPC7 will, by default, only see key events when either it or MSFS has the keyboard focus. If MSFS has the focus but FSUIPC7 is not seeing the key events, then it is an issue with MSFS not sending these events on to FSUIPC7.
If FSUIPC7 is not seeing the key events, you can switch to using a keyboard hook (instead of SimConnect) which will enable FSUIPC7 to see all key events regardless of what has the focus. To do this, add the following to the [General] section of your FSUIPC7.ini file:
