Spug

Pete, you are so smart!! Yes, I have the controllers turned off, however, I went back to the controller menu and they were active again!!! I've never seen it reactivate itself like that. I was running out of keys to use with my buttons and removed some from the Normal.xml so there wouldn't be a conflict. I wonder if FSX recognizes that the Normal.xml has changed and reactivates the controllers subsequent to that. Either way, I'm good now. You were correct, the controllers were enabled in FSX. Thank you for your help!!

Using FSX in a Windows 10 system. FSUIPC 4.974, RealityXP GNS530 Pressing button PG,9,C66612,0 -{GPS_PROCEDURE_BUTTON}- results in the procedure showing in the RealityXP window but also actuates the landing gear. The same thing happens when pressing PG,7,C66621,0 -{GPS_CLEAR BUTTON DOWN}-, landing gear actuates. Pressing PG,8,C66623,0 -{GPS_ENTER BUTTON}- changes the view. It's as if I'm pressing the "S" key. FSUIPC4.ini

It appears to be working now. Your suggestion of upgrading to the latest version, 4.974 seems to have corrected the problem. Now, both boards are recognized. Thanks for your help Pete!

I have two model 2238-CONN USB boards(desktop aviators) connected to provide button/switch inputs to FSX using FSUIPC 4.968 in a Windows 10 system. FSUIPC only seems to allow one of the two boards at a time to connect and assigns the buttons specified in the INI file to that board. Is there a way to get both working with their individual ID's and button assignments? FSUIPC4.JoyScan.csv