fennelda

Hi John, just tried that out and it works perfectly! I can see in the log that the phantom controllers are being ignored. Thank you!

I spoke too soon - all three ghost controllers are now showing up again, without any change on my part! And my [JoyNames] section is corrupted again. Of course - I've attached them to this post. MSFSNotRunning: Before MSFS is started StartWithMSFS: FSUIPC starts with MSFS from exe.xml MSFSRunning: Exit FSUIPC from task bar and restart it, without shutting down MSFS FSUIPC7.JoyScan_MSFSRunning.csv FSUIPC7.JoyScan_StartWithMSFS.csv FSUIPC7.JoyScan_MSFSNotRunning.csv

Thanks for the Steam suggestion - I have the same Steam settings as you but after a bit of experimentation I am convinced that it is Steam creating this problem. As well as your suggestions, I also right-clicked on MSFS in the games list, clicked Properties, Controller and then selected "Disable Steam Input". I really felt this was going to work, however I still have the ghost controllers - but I now only have two, not three! I believe the problem is that in the latest versions of Steam client, Steam Controller support can not be disabled completely. Indeed, in the Controller menu mentioned above, it states that Steam Controller and Remote Play are "Enabled, always required", and from a brief search online it seems impossible to change this setting. Interestingly, the positions of the "virtual" controllers in the FSUIPC7.JoyScan.csv file seem to determine whether these controllers cause an issue or not. I still now have two phantom controllers in my list, however since they are the top two entries in the list, they do not mess up my FSUIPC7.ini [JoyNames] section. Thanks for your help John, and no pressure at all - it's not a game-breaking issue, just a slight annoyance!

Hi John, Thanks for your help - I have done as you have suggested but it doesn't help. It would appear that the detection of the controllers is done before the attempts to connect via simconnect, at the moment when FSUIPC is launched by the sim, so delaying the simconnect request makes no difference. I can "solve" this problem by removing FSUIPC from the exe.xml file and launching it separately from the sim, either before or after MSFS has loaded. If there's nothing you can do, I might create a batch file which launches FSUIPC and then MSFS instead of the exe.xml method, but it's not really an ideal solution! Is there any way to encourage HidScanner (or whichever method you use to poll the controllers on the system) to "ignore" these phantom controllers? Or maybe even to delay the controller detection until later in the startup process? Edit: I've attached the relevant files below, in the hope that they reveal something important! This is what happens when I leave FSUIPC to launch with the sim. If I then close FSUIPC from the taskbar and relaunch it, the FSUIPC7.ini will "heal" itself, however the [JoyNames] "A" controller sticks around - doesn't cause an issue though! FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Hi there, I'm struggling with an issue that I see has come up numerous times in the past, and I wonder if there's a solution? If I start FSUIPC before launching MSFS, it detects my 3 controllers perfectly, as seen in the JoyScan.csv file. However, if I let FSUIPC launch with MSFS, I get 3 extra phantom Xbox controllers added, which all seem to copy the GUID of one of my real controllers (see attached file). When this happens, one of my controllers appears missing when MSFS finally launches since the [JoyNames] section is messed up. Curiously, if I then close FSUIPC and launch it again, the JoyScan.csv file confirms that only my three controllers exist again, and the FSUIPC7.ini [JoyNames] section rebuilds itself without issue. Does MSFS somehow "create" artificial controllers during the startup sequence which FSUIPC is detecting? Any advice much appreciated! David. FSUIPC7.JoyScan.csv

Thanks Pete! Great detective work there. Glad I didn't have to start uninstalling things... it's easy enough to work around for the time being.

Thanks Pete! I'm impressed you could reproduce it, I haven't seen it reported anywhere so I figured it was something peculiar to my system. If you need any more data, or tests I can carry out on my side please let me know.

I enabled logging extras in fsuipc and it gave me two entries when I made it happen: 18183875 Deactivated: culprit unknown 18183875 Focus lost: culprit unknown

I've attached the log for the current flight - I've done it multiple times but there doesn't seem to be any record of anything in the file. FSUIPC5.log

Hi Pete, That's interesting, I'm flying now so I tried it out. I assigned a key to arm the spoilers, which worked fine before and after opening the traffic explorer window, however the spoiler axis I assigned to the throttle stopped working until I recycled the FSUIPC window. Maybe reinstalling my joystick drivers might fix it? Interestingly though, the autosave function also disables, which has nothing to do with the Joystick! By time preview I mean World > Time Preview. It allows you to change the time in the sim dynamically without a reload. Thanks!

Hi there, I've just started having a problem with the full registered version of FSUIPC (latest) and P3Dv4.2 - it's been working fine for a long time and I have no idea what has caused it! Every time I open a window within P3D, for example the Traffic Explorer window from TrafficToolbox.dll or the time preview window, FSUIPC stops working. All FSUIPC defined controls suddenly become unresponsive, autosave stops saving etc. There's no error message, and FSUIPC still appears in the menu, but it just stops working in the background. If I go into the FSUIPC menu and click ok, everything suddenly starts working again. Any ideas? I can only imagine it's some sort of simconnect problem, but I really have no idea!