Random device scanned OK by FSUIPC 6 and 7 but no input recognized

[LeCoyote]

Hello,

This is the second time I've had this rather weird incident and it's quite frustrating, so I thought I'd submit it here.

One of my USB controllers stops working in FSUIPC. Windows sees the device, P3D can use it, but even though FSUIPC logs it and lists it as "acquired for use", it will not detect any button press or axis movement.

The first time it happened to me, after 2 hours of trial and error, I eventually removed the device USB entry from the device manager, unplugged and re-plugged it, and that was it.

Today was different however. After I used the technique above to restore that first controller, another USB device failed, in exactly the same fashion; it was working the moment before, and it just stopped, but Windows could still see and use it. I used the same technique again, which worked, but a third device now failed. Lathe, rinse, repeat, and fortunately the series stopped there.

Interestingly, both FSUIPC 6 and 7 failed to recognize the same device at the same time.

I am attaching the logs and ini files here. You'll see yet another weird thing: FSUIPC complains that there are duplicate entries for joystick 0, 3 and 7, but no such duplicates exist in the ini file. The FSUIPC6.ini has been cut before the control definitions as it otherwise exceeds the 20kB limit of the forum. In sequence, the devices that failed where the VPC Left Panel, the Warthog throttle (which is where I grabbed the log), and the warthog joystick.

Any input would be greatly appreciated to try and see clearer in this mess 😅

Cheers

Romain

FSUIPC6_prev.log FSUIPC6_short.ini

[John Dowson]

This is usually caused by the device going to sleep. Check your USB hub device properties and make sure that the allow to sleep option is disabled.

15 hours ago, LeCoyote said:

FSUIPC complains that there are duplicate entries for joystick 0, 3 and 7, but no such duplicates exist in the ini file.

This refers to duplicate registry entries for your devices, probably caused by you unplugging and reconnecting - you shouldn't do this. They are only warnings, but to remove these you would need to clean your registry.

You should change this entry, from No to Yes, in the [JoyNames] section of your FSUIPC6.ini file:

Quote

[JoyNames]
AutoAssignLetters=No

this will prevent issues if your joystick ids change.

Also, you are using version 6.1.6, which us quite old. Please update to 6.2.0 which is the latest and only supported version.

John

 

[LeCoyote]

On 7/24/2023 at 10:05 AM, John Dowson said:

This is usually caused by the device going to sleep. Check your USB hub device properties and make sure that the allow to sleep option is disabled.

IF the device had gone to sleep, would it still be acting in Windows and other applications? Because that's what is happening: while FSUIPC is ignoring the device, it is simultaneously acting normal in Windows Control Panel.

Besides, although I have now removed the sleep option from all devices, the problem still happens, and is currently happening with the HOTAS Warthog Throttle with FSUIPC7 (it is easier to test with 7 since I don't have to start the simulator). Would you like me to open a separate thread in the appropriate section?

For some reason FSUIPC7 says the Warthog Joystick is missing, but registering events, and assigned the letter J to the Throttle in the FSUIPC7.ini file but showing J as the Joystick in the runtime window... It appears to be very confused and I'm not sure how to "clean my registry", as you suggested.

I can't attach more files because of the max total size, please advise how you  would like to proceed next.

Thanks a lot!

Romain

[LeCoyote]

After having disabled the sleep option on all my FS devices, I have restarted the computer and launched P3D with FSUIPC 6.2.0

The Warthog Throttle is currently working in the Windows control panel, but not causing any events in the FSUIPC GUI.

I cannot attach more files due to the thread size limit.

Relevant section of FSUIPC6.INI:

[JoyNames]
AutoAssignLetters=Yes
4=VPC SharKa-50 Panel
4.GUID={442E8330-E604-11ED-8001-444553540000}
3=RIGHT VPC Panel #1
3.GUID={2651B9D0-6744-11EC-800F-444553540000}
6=VPC Rudder Pedals
6.GUID={C352A460-673A-11EC-8001-444553540000}
7=Joystick (Razer Tartarus V2)
7.GUID={ED824BD0-367B-11ED-8005-444553540000}
5=LEFT VPC Panel #2
5.GUID={DC149FB0-674B-11EC-8018-444553540000}
1=Throttle - HOTAS Warthog
1.GUID={8FE49350-3954-11EB-8001-444553540000}
A=Throttle - HOTAS Warthog
A.GUID={8FE49350-3954-11EB-8001-444553540000}
B=RIGHT VPC Panel #1
B.GUID={2651B9D0-6744-11EC-800F-444553540000}
C=VPC SharKa-50 Panel
C.GUID={442E8330-E604-11ED-8001-444553540000}
D=LEFT VPC Panel #2
D.GUID={DC149FB0-674B-11EC-8018-444553540000}
E=VPC Rudder Pedals
E.GUID={C352A460-673A-11EC-8001-444553540000}
F=Joystick (Razer Tartarus V2)
F.GUID={ED824BD0-367B-11ED-8005-444553540000}

Confusingly, my Warthog joystick is entirely missing from that section, but it works in the GUI and shows up with device letter "A"

Log file:

********* FSUIPC6, Version 6.2.0 (30th June 2023) by Pete & John Dowson *********
Prepar3D.exe version = 4.5.14.34698
Running inside Prepar3D v4
Module base=7FF932600000
Windows 10 Home 64 Bit reported as Build 19045, Release ID: 2009 (OS 10.0)
Reading options from "C:\Users\LeCoyote\Documents\Prepar3D v4 Add-ons\FSUIPC6\FSUIPC6.ini"
Checking the Registrations now ...
User Name="Romain Riviere"
User Addr="mr-smoke@spinning-plates.eu.org"
FSUIPC6 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 25/07/2023 10:29:15
       16 FLT path = "C:\Users\LeCoyote\Documents\Prepar3D v4 Files\"
       16 Using DialogMode
       63 FS path = "E:\Prepar3D v4\"
      172 ---------------------- Joystick Device Scan -----------------------
      172 Product= VPC SharKa-50 Panel
      172    Manufacturer= VIRPIL Controls 20230328
      172    Serial Number= FF
      172    Vendor=3344, Product=025D (Version 1.0)
      250    GUIDs returned for product: VID_3344&PID_025D:
      250       GUID= {442E8330-E604-11ED-8001-444553540000}
      250       Details: Btns=45, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U60000,V60000,X60000,Y60000,Z0
      250 Product= R-VPC Panel #1
      250    Manufacturer= VIRPIL Controls 20230328
      266    Serial Number= FF
      266    Vendor=3344, Product=4259 (Version 1.0)
      266    GUIDs returned for product: VID_3344&PID_4259:
      266       GUID= {2651B9D0-6744-11EC-800F-444553540000}
      266       Details: Btns=41, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z60000
      266 Product= VPC Rudder Pedals
      266    Manufacturer= VIRPIL Controls 20230328
      266    Serial Number= FF
      266    Vendor=3344, Product=01F8 (Version 1.0)
      266    GUIDs returned for product: VID_3344&PID_01F8:
      266       GUID= {C352A460-673A-11EC-8001-444553540000}
      266       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U60000,V0,X0,Y0,Z60000
      266 Product= 
      266    Vendor=1532, Product=022B (Version 1.1)
      266    GUIDs returned for product: VID_1532&PID_022B:
      266       GUID= {ED81AF90-367B-11ED-8003-444553540000}
      266       Details: Btns=1024, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      266       GUID= {ED824BD0-367B-11ED-8005-444553540000}
      266       Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255
      266 Product= Joystick - HOTAS Warthog
      266    Manufacturer= Thustmaster
      266    Vendor=044F, Product=0402 (Version 1.0)
      266    GUIDs returned for product: VID_044F&PID_0402:
      266       GUID= {8FE49350-3954-11EB-8001-444553540000}
      266       Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0
      266 Product= Throttle - HOTAS Warthog
      266    Manufacturer= Thrustmaster
      266    Vendor=044F, Product=0404 (Version 1.0)
      266    GUIDs returned for product: VID_044F&PID_0404:
      266       GUID= {8FE49350-3954-11EB-8005-444553540000}
      266       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y1023,Z16383
      266 Product= IFR1
      266    Manufacturer= Octavi
      266    Serial Number= HIDCF
      266    Vendor=04D8, Product=E6D6 (Version 1.0)
      266 Product= L-VPC Panel #2
      281    Manufacturer= VIRPIL Controls 20230328
      281    Serial Number= FF
      281    Vendor=3344, Product=825B (Version 1.0)
      281    GUIDs returned for product: VID_3344&PID_825B:
      281       GUID= {DC149FB0-674B-11EC-8018-444553540000}
      281       Details: Btns=42, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      281 -------------------------------------------------------------------
      281    WARNING: Joystick ID 3 is duplicated in Registry
      313    WARNING: Joystick ID 0 is duplicated in Registry
      328    WARNING: Joystick ID 7 is duplicated in Registry
      328    WARNING: Joystick ID 0 is duplicated in Registry
      328 Device acquired for use:
      328    Joystick ID = 4 (Registry okay)
      328    4=VPC SharKa-50 Panel
      328    4.GUID={442E8330-E604-11ED-8001-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 3 (Registry okay)
      328    3=RIGHT VPC Panel #1
      328    3.GUID={2651B9D0-6744-11EC-800F-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 6 (Registry okay)
      328    6=VPC Rudder Pedals
      328    6.GUID={C352A460-673A-11EC-8001-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 7 (Registry okay)
      328    7=Joystick (Razer Tartarus V2)
      328    7.GUID={ED824BD0-367B-11ED-8005-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 1 (Registry okay)
      328    1=Throttle - HOTAS Warthog
      328    1.GUID={8FE49350-3954-11EB-8001-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 5 (Registry okay)
      328    5=LEFT VPC Panel #2
      328    5.GUID={DC149FB0-674B-11EC-8018-444553540000}
      328 -------------------------------------------------------------------
      828 Controllers are set to ON, using RawInput within P3D
      828 LogOptions=00000000 00000001
      844 -------------------------------------------------------------------
      844 SimConnect_Open succeeded: waiting to check version okay
      844 Opened separate AI Traffic client okay

FSUIPC is getting the GUIDs wrong between the joystick and the throttle, and I have no idea why.

[John Dowson]

23 minutes ago, LeCoyote said:

Would you like me to open a separate thread in the appropriate section?

No, thats fine. Bit lets stick to one FSUIPC version - if you are testing with FSUIPC7, stick with that and please show me your FSUIPC7 files. not your FSUIPC6 ones.

29 minutes ago, LeCoyote said:

I can't attach more files because of the max total size, please advise how you  would like to proceed next.

You can always zip the, before attaching...

17 minutes ago, LeCoyote said:

I have restarted the computer and launched P3D with FSUIPC 6.2.0

Please do not keep switching between P3F/FSUIPC6 and MSFS/FSUIPC7. Choose one and lets stick to that one please...

Please show me an FSUIPC6.JoyScan.csv file and I can prepare a script to clean your registry.

John

 

[LeCoyote]

Just now, John Dowson said:

Please do not keep switching between P3F/FSUIPC6 and MSFS/FSUIPC7. Choose one and lets stick to that one please...

I was only doing so because the issue was exactly the sale in both which, in my mind, seemed to indicate the issue was with FSUIPC. I now understand it might have to do with Windows' registry of USB devices. So let's use FSUIPC7 for ease of testing, and I'm assuming the solution will apply to both.

I've attached my INI file, the log, and the scan result.

During this testing session, the Warthog Throttle is unresponsive in FSUIPC7, and the Warthog Joystick is showing in the GUI as letter "J", even though the INI file has that letter mapped to the Throttle.

Thanks a bunch for your help, let me know if you need any other information.

FSUIPC7.zip

[John Dowson]

Please first tun regedit and take a back-up of your registry. Then, disconnect all of your devices.

Run the attached regedit script - just save it and then double-click it in windows Explorer to run it: removeDevices.reg

Then reboot and re-connect your devices and try again.

Any issues, please show me all 3 files - log, ini and JoyScan,csv.

[LeCoyote]

Thanks a bunch John, all of the devices now work in FSUIPC7 🙂

However, there are quite a few duplicate entries under JoyNames (for example, the Throttle is listed as 5 and then C, J and S). Is it safe to remove the "oldest" letters for each set? One of these entries is "B=Joystick - HOTAS Warthog << MISSING JOYSTICK >>", I assume it's safe to delete too?

I cannot attach anything anymore since the max total size is now 2.54kB, but if needed I can delete the previous attachments if you need to see the whole files again.

Another question, you mentioned:

On 7/24/2023 at 10:05 AM, John Dowson said:

you unplugging and reconnecting - you shouldn't do this

Did you mean "while FSUIPC is running"? While the OS is running? (it would defeat the whole hotplugging purpose of USB but heh, Windows right…) I'll soon have to relocate my whole setup and unplug/replug everything, possibly with an added hub in the mix for better cable management. Should I expect any issues with FSUIPC after that?

Last but not least, as expected, P3D/FSUIPC6 is now "cured" too, although it is displaying the same sort of duplicates in the INI file. I will obviously have to redo the assignments, but I kept the INI file from before the fix, so I'll just need to search and replace all of the Px/Ux instances of the old IDs with the new ones.

Looking forward to your feedback on the ini file cleanup. Many thanks again!

[John Dowson]

1 hour ago, LeCoyote said:

However, there are quite a few duplicate entries under JoyNames (for example, the Throttle is listed as 5 and then C, J and S). Is it safe to remove the "oldest" letters for each set? One of these entries is "B=Joystick - HOTAS Warthog << MISSING JOYSTICK >>", I assume it's safe to delete too?

No, don't delete anything if you do not know what you are doing. The Missing joystick message is because you have an assignment to that letter. You need to change the letters if the GUIDs to match your assignments. If you show me your files, I  can do this for you.

1 hour ago, LeCoyote said:

Did you mean "while FSUIPC is running"? While the OS is running? (it would defeat the whole hotplugging purpose of USB but heh, Windows right…) I'll soon have to relocate my whole setup and unplug/replug everything, possibly with an added hub in the mix for better cable management. Should I expect any issues with FSUIPC after that?

You shouldn't disconnect and re-connect when FSUIPC is running. Moving devices to a different USB socket/hub can sometimes cause ids to change, but you should be ok with this as you are using joyletters for your assignments, not the ids.

1 hour ago, LeCoyote said:

Last but not least, as expected, P3D/FSUIPC6 is now "cured" too, although it is displaying the same sort of duplicates in the INI file. I will obviously have to redo the assignments, but I kept the INI file from before the fix, so I'll just need to search and replace all of the Px/Ux instances of the old IDs with the new ones.

Best to show me your files for FSYUPC6 as well and I can update for you. You shouldn't need to redo your assignments.

[LeCoyote]

2 hours ago, John Dowson said:

No, don't delete anything if you do not know what you are doing.

Which is why I'm asking you 😉 The duplicate letters refer to GUIDs that were removed by your fix, so I was wondering whether I could clean them up. What happens when I reach "Z" btw? I'm already at "P" with all these changes 😄 I'm not touching the numbers obviously, I know they refer to Windows' joystick ID.

2 hours ago, John Dowson said:

The Missing joystick message is because you have an assignment to that letter. You need to change the letters if the GUIDs to match your assignments. If you show me your files, I  can do this for you.

Indeed, that went away as soon as I fixed the assignments. And thanks for offering but I didn't want to bother you with this, a few regexes made short work of it anyway 🙂

2 hours ago, John Dowson said:

You shouldn't disconnect and re-connect when FSUIPC is running. Moving devices to a different USB socket/hub can sometimes cause ids to change, but you should be ok with this as you are using joyletters for your assignments, not the ids

Duly noted, thanks!

One last oddity (but I blame Windows for this) is that the Razer Tartarus is now known as "USB Input device". It works exactly like before, including the Razer software and profiles, it's just not called by its proper name anymore. I guess I'll just live with it, hopefully Windows won't decide to change it again in the future …

Thanks for your support, and for this nifty piece of software that I couldn't sim properly without!

Cheers

Romain

[John Dowson]

21 minutes ago, LeCoyote said:

The duplicate letters refer to GUIDs that were removed by your fix, so I was wondering whether I could clean them up.

You can remove those. You just need for entries for each device - two (name and GUID) with the letter and two with the id. You can remove everything else, but take a backup first in case you remove the wrong entries...

25 minutes ago, LeCoyote said:

One last oddity (but I blame Windows for this) is that the Razer Tartarus is now known as "USB Input device". It works exactly like before, including the Razer software and profiles, it's just not called by its proper name anymore. I guess I'll just live with it, hopefully Windows won't decide to change it again in the future …

Do you use any additional software for the Razer Tarturus? If so, that may have updated the name in the registry when it was installed, so you could try r-installing that, if applicable.
If you do this, it may also require a manual update of your ini, aa both the name and GUIDs must match between the id and letter entries. The new name will be picked up for the if entry, but you may need to then manully change the name in the letter entry so that they again match.

Cheers,

John

[LeCoyote]

Huh, apparently I forgot to press "Reply" yesterday, sorry about the delay.

On 7/25/2023 at 5:12 PM, John Dowson said:

You can remove those. You just need for entries for each device - two (name and GUID) with the letter and two with the id. You can remove everything else, but take a backup first in case you remove the wrong entries...

Thanks for the info. Yes I always make a backup before attempting anything destructive.

On 7/25/2023 at 5:12 PM, John Dowson said:

Do you use any additional software for the Razer Tarturus? If so, that may have updated the name in the registry when it was installed, so you could try r-installing that, if applicable.

There is a dedicated piece of software to manage device profiles, as it is capable of sending keystrokes and joystick button events.

I'm not sure I want to try reinstalling, as it's still working right now, and the name only appears as such in the Game controllers settings module of the Windows control panel (oddly enough it kept its name in the Device manager) and in the INI file itself. But I'll keep your advice in mind should I decide to go through with it.

Again, thanks a lot for your help with this issue 🙂

Cheers

Romain