FSUIPC joystick ID always changes

[Nikolaj.Delaney]

FSUIPC7.JoyScan.csvFSUIPC7.ini

Hello,

 

I have a strange issue where the JoyName of my TCA Airbus stick keeps changing because it is "missing". I didn't do anything to the joystick and don't know how to solve it. The joystick GUID just keeps multiplying in the config - ini and log attached.

The "Autoassignletters=no" does nothing, it always shows up with a different ID. It is extremely frustrating because it started when I meticulously set up my PMDG controls for the buttons on the joystick.

Any help on how to make this issue go away would be appreciated.

Best,

Vojta

FSUIPC7.log

[Andre92]

No solution, but just would like to add that i have the same problem with the Winwing Airbus stick.

Regards,

André

[John Dowson]

The issue seems to be that the name of the device (T.A320 Pilot) is now missing. Not sure why this is...do yo have any specific drivers installed or any additional software for this controller?
If so, you could try uninstalling and using the windows default drivers to see if that makes a difference.

On 9/12/2022 at 8:29 AM, Nikolaj.Delaney said:

The "Autoassignletters=no" does nothing, it always shows up with a different ID.

This controls automatic assignment of joyletters, not ids. If you can't get FSUIPC to read the name of the device from the registry correctly, then you could try without using the joyletters facility. To do this, try the attached ini where I have reverted your assignments to use the joy ids rather than the letters.,

John

FSUIPC7.ini

[Nikolaj.Delaney]

On 9/18/2022 at 2:02 PM, John Dowson said:

The issue seems to be that the name of the device (T.A320 Pilot) is now missing. Not sure why this is...do yo have any specific drivers installed or any additional software for this controller?
If so, you could try uninstalling and using the windows default drivers to see if that makes a difference.

This controls automatic assignment of joyletters, not ids. If you can't get FSUIPC to read the name of the device from the registry correctly, then you could try without using the joyletters facility. To do this, try the attached ini where I have reverted your assignments to use the joy ids rather than the letters.,

John

FSUIPC7.ini 6.3 kB · 2 downloads

Hello John,

 

I will try the included ini and reinstalling the drivers. I had an issue recently where for some reason the system did not pick up the joystick and I had to plug it out and back in while MSFS and FSUIPC were active, which prompted a window in MSFS "new control device recognized". I think that that is when the issue started because before it was working correctly.

 

Meanwhile, I did some more troubleshooting and found out that if I run FSUIPC before running the simulator, it reads the name of the device correctly and everything works as normal. But if I run MSFS (not by the .bat from FSUIPC but normal desktop shortcut) and wait until FSUIPC starts automatically, it doesn't read the device name and the issue appears. Then it can be fixed by pressing "reload assignments" in FSUIPC Axes page, closing FSUIPC and starting it manually.

 

I also switched to MSFS SU10 Beta but I  don't think that is the culprit.

Thank you for your time, will keep this updated.

Vojta

[John Dowson]

6 hours ago, Nikolaj.Delaney said:

But if I run MSFS (not by the .bat from FSUIPC but normal desktop shortcut) and wait until FSUIPC starts automatically, it doesn't read the device name and the issue appears.

This sounds strange: the MSFS.bat (and desktop icon link) starts MSFS in the same way as the MSFS icon and menu entries - all that .bat file does is display a splash screen for the first 30-45 seconds or so while MSFS is loading. With FSYUPC7 auto-start, it should makes no difference whatsoever if you use the FSUIPC MSFS.bat file or the MSFS-provided start options.

6 hours ago, Nikolaj.Delaney said:

Then it can be fixed by pressing "reload assignments" in FSUIPC Axes page, closing FSUIPC and starting it manually.

I would like to see a log file (+ .ini) for when this occurs - and exit FSUIPC before reloading the assignments,  I vaguely remember a similar issue from another user a few years which I believe I added a new ini for to resolve, but I need to check, But I cannot help if you do not show me the relevant files...

6 hours ago, Nikolaj.Delaney said:

I also switched to MSFS SU10 Beta but I  don't think that is the culprit.

 Hopefully not...SU10 should be released tomorrow or in the next few days (unless there is yet another delay...) and I will update and release 7.3.9 once I have updated to the new SDK, but for the time being there is a beta available of this release in the announcements sub-forum if you would like to try that.

John

[John Dowson]

The SU10 beta has been updated with several improvements, although there are still issues with some axes controls. See the announcements for the latest betam and the following thread for SU10 axis issues:

 

John