Fail to recognize one controller then another after reconnect

[C2615]

Hi, after start my P3Dv5 today with FSUIPCv6 I noticed my main joystick (VKB-Sim Space Gunfighter) while recognized by P3D itself (as main pitch roll control), not with FSUIPC's fuction,

I find it's not in the FSUIPC6.ini, [JoyNames], try to manually add it from a known good back-up file and reload (Reload all buttons) doesn't work

Then I disconnect and reconnected it's USB plug while in the game. then reload FSUIPC.

The VKB stick back online fully, however now my G27 wheel is not recognized (I use it's shifter as landing gear lever).

FSUIPC6.ini, [JoyNames] now have the VKB although mislabeled as 4=Flight Throttle Quadrant, but all buttons and axis works fine, no G27 in it

[JoyNames]
AutoAssignLetters=No
0=MJ162
0.GUID={58B61650-0350-11EF-8004-444553540000}
1=Flight Throttle Quadrant
1.GUID={8E5FFEE0-C03C-11ED-8007-444553540000}
4=Flight Throttle Quadrant
4.GUID={09BCBC70-C03F-11ED-8016-444553540000}
5=MJOY32
5.GUID={8E618580-C03C-11ED-8009-444553540000}
6=TCA Q-Eng 1&2
6.GUID={8E5E0310-C03C-11ED-8003-444553540000}
2=vJoy Device
2.GUID={E07B7D30-C041-11ED-8006-444553540000}

I tried delete all [JoyNames], delete full FSUIPC6.ini and let it rebuild, unplug and replug G27, all without luck, the G27 works fine in control panel, with P3D's own controller menu and with other apps(joytokey for eg, not yet try other games.

It used to be all working fine.

Somehow even LINDA can still read and use it

Have restarted P3D and the issue is still there, and now LINDA also nolonger could relay it. Not rebooted yet.

FSUIPC6.JoyScan.csv

[John Dowson]

1 hour ago, C2615 said:

I find it's not in the FSUIPC6.ini, [JoyNames], try to manually add it from a known good back-up file and reload (Reload all buttons) doesn't work

There is no point doing this...the entries associated to a JoyId number will be completely re-written by FSUIPC. You should also use/enable JoyLetters to prevent issues when the JoyIds changer.

Its also not a good idea to disconnect and reconnect devices when P3D/FSUIPC is running, especially if you have issues and are not using JoyLetters.

Do you still have your original FSUIPC6.ini? If so, please use that, otherwise use the latest one which has all your assignments. Start P3D/FSUIPC, let it load and then exit. Then show me / attach the files FSUIPC6.log, FSUIPC6.ini and FSUIPC6.JoyScan.csv files - I need to see all 3 from the same session.

The JoyScan file you attached shows that your registry is a bit of a mess and will need cleaning. I can provide a script to do this once I have seem those files.
From that file, it looks like you have the following devices:
    1 vJoy devoce
    1 TCA Q-Eng 1&2
    2 MJ162
    2 MJOY32
    1 Logitech G27 Racing Wheel
    1 VKB-Sim Space Gunfighter
    1 Flight Throttle Quadrant

Is that correct?

 

[John Dowson]

...and one thing I don't understand is that 3 of your devices have been assigned the same GUID:

Quote

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?
,,,,,,,,,,,,
,,, HIDscanning completed,,,,,,,,,
,,,,,,,,,,,,
N, x00, x1234, xBEAD, ,-1,-1,0, {NULL}, {NULL}, {E07B7D30-C041-11ED-8006-444553540000}, Y, N
...
N, x00, x231D, x0127, ,-1,-1,0, {NULL}, {NULL}, {E07B7D30-C041-11ED-8006-444553540000}, Y, N
N, x00, x06A3, x0C2D, ,-1,-1,0, {NULL}, {NULL}, {E07B7D30-C041-11ED-8006-444553540000}, Y, N

GUIDs should be unique....I don't understand why these aren't.
Please reboot before providing me the files.

[C2615]

38 minutes ago, John Dowson said:

From that file, it looks like you have the following devices:
    1 vJoy devoce
    1 TCA Q-Eng 1&2
    2 MJ162
    2 MJOY32
    1 Logitech G27 Racing Wheel
    1 VKB-Sim Space Gunfighter
    1 Flight Throttle Quadrant

Is that correct?

 

Thanks for the support.

Only 1 for each, so I'm not sure why you would read 2 MJ162 and 2 MJOY32...

So after my flight (which I almost forget to lower the gear by mouse), I made a test flight in X-Plane make sure all my hardware works (they did), and restart computer. load to P3Dv5, and now the missing roulette is TCA Q-Eng 1&2

My FSUIPC.ini have heritage from an old P3Dv4 install on a win7 system, but all system/driver/application have been freshly installed when I switch to this one,

Another issue I have was the id for joystick used to change a lot back then, so I use JoyIDs to swap them, and I also use it to make the ID align to my old win7 install so I don't need to change the assignment in FSUIPC6 when I got the new system,  not sure if that would be the problem, it seems FSUIPC is the only software that still recognize this ID system now.

Maybe I should switch to joyletter system? not very familiar with it. do I need to reconfig all my working configs?

FSUIPC6joystkmissing.zip

[John Dowson]

2 hours ago, C2615 said:

Only 1 for each, so I'm not sure why you would read 2 MJ162 and 2 MJOY32...

Some devices do report multiple GUIDs - I wouldn't worry about this.

2 hours ago, C2615 said:

Maybe I should switch to joyletter system? not very familiar with it. do I need to reconfig all my working configs?

Yes you should, and you should not have to reconfigure anything. It would be a lot easier to fix your current issue if you had done this, but probably not a good idea to do this at the moment - we can do this later.

Can you do the following please:
   - run the windows registry editor and take a back-up of your registry
   -  disconnect the following devices:
            MJ162, MJOY32, VKB-Sim Space Gunfighter L, Flight Throttle Quadrant
    - download and run (i.e. double-click it) the attached .reg file: removeDevices.reg 
    - reboot your system
    - reconnect the devices you disconnected
    - run P3D/FSUIPC, and once loaded just exit
    - show me / attach those 3 files again (ini. log and JoyScan.csv). Do NOT change anything or assign/re-assign until we have corrected this.
    - if you can, let me know which device ids have changed from those used for your assignments, i.e. if you previously assigned to the device when it had a different id,
      let me know the current id and the id that was previously used for assignments on this device

Note also that your ini file is a bit of a mess. The '//' characters are NOT the comment string for ini files, although such lines will be ignored. Best to remove these or replace with the comment character ';' (a semi-colon). You should also consider using substrings for your profile aircraft names, e.g. for the FSL320 profile, change

Quote

[Profile.FSL320]
1=FSLabs A320X IAE - FSLabs
2=FSLabs A320X CFM - FSLabs
3=FSLabs A319X IAE - FSLabs
4=FSLabs A319X IAE - UNDEFINED CES B-6439
5=FSLabs A320X CFM - UNDEFINED CCA B-9918
6=FSLabs A320X CFM - UNDEFINED CES B-6756
7=FSLabs A319X CFM - UNDEFINED CSN B-6209
8=FSLabs A320X IAE - UNDEFINED CSN B-6627
9=FSLabs A320X IAE - Shenzhen Airlines (B-6571)
10=FSLabs A320X IAE - China Southern Airlines (B-6627)
11=FSLabs A320X CFM - Lufthansa (D-AIPA)
12=FSLabs A319X CFM - Lufthansa (D-AIBI)
13=FSLabs A319X IAE - China Eastern Airlines (B-6439)
14=FSLabs A320X CFM - All Nippon (JA8400)
15=FSLabs A319X IAE - Air China (B-6235)
16=FSLabs A319X CFM - Air France (F-GRXM)
17=FSLabs A320X CFM - China Eastern Airlines (B-6756)
18=FSLabs A320X CFM - Air China (B-9918)
19=FSLabs A319X CFM - China Southern Airlines (B-6209)
20=FSLabs A320X IAE - Jetstar Japan (JA09JJ)
21=FSLabs A320X CFM - Aer Lingus (EI-DEB)
22=FSLabs A321X CFM - China Eastern Airlines (B-6367)
23=FSLabs A321X IAE - China Southern Airlines (B-6687)
24=FSLabs A321X CFM - China Eastern B-6345
25=FSLabs A320X CFM - AIR PEACH (JA816P)é—肩櫢绠撳▓娓僶llection
26=FSLabs A320X CFM - Lufthansa (D-AIZG)
27=FSLabs A321X IAE - SAS Scandinavian Airline System (OY-KBF)
28=FSLabs A319X IAE - British Airways (G-EUOE)
29=FSLabs A319X IAE - Airbus Industrie (F-WWDB)
30=FSLabs A319X CFM - PLAAF ACJ
31=FSLabs A320X IAE - SICHUAN AIRLINES B-2340
32=FSLabs A319X CFM - CHINA EASTERN(B-6439)
33=FSLabs A320X CFM - China Eastern (B-6001)
34=FSLabs A320-214 - FSL (SX-FSL)
35=FSLabs A319-131 - FSL (SX-FSL)
36=FSLabs A320-232 - CSN (B-6627)
37=FSLabs A321-231 - FSL (SL-FSL)
38=FSLabs A321-211 - NH (JA111A)
39=FSLabs A320-214 - CCA (B-9918)
40=FSLabs A320-214 - CES (B-6756)
41=FSLabs A320-232 - HKE (B-LCH)
42=FSLabs A320-214 - AIB (F-WWBA)
43=FSLabs A320-232 - CYP (5B-DBB)
44=FSLabs A320-214 - EZY (G-EZTA)
45=FSLabs A320-214 - APJ (JA822P)
46=FSLabs A320-232 - JSA (9V-JSL)
47=FSLabs A320-232 - CSC (B-6621)

to

Quote

[Profile.FSL320]
1=FSLabs A320
2=FSLabs A319
3=FSLabs A321

You should do similar changes (i.e. use substrings to match all variants) to all your profiles.

Please also update to the latest and only supported version of FSUIPC6, v6,2,1.

John

[C2615]

18 hours ago, John Dowson said:

Can you do the following please:
   - run the windows registry editor and take a back-up of your registry
   -  disconnect the following devices:
            MJ162, MJOY32, VKB-Sim Space Gunfighter L, Flight Throttle Quadrant
    - download and run (i.e. double-click it) the attached .reg file: removeDevices.reg 
    - reboot your system
    - reconnect the devices you disconnected

Things go south very quickly, After applying this and restart, I lost many of my device, and after restore the backup they still don't work.

Searching for a while, now I confirm all 4 USB3.x port on the back of MB (MSI MAG B650M Mortar WiFi (MS-7D76)  stopped working (still power but no data), by switch up some ports I get mouse and keyboard back online, by moving my 10 port hub to usb-c port now I got most but still not all joysticks working, that typeC port works, all 4 usb2 ports works, also one usb3.0 and 2 usb2.0 port on my computer's front panel still works.

Still I can't get normal working without that 4 USB3.x ports, and after system restoring, restarting, and some basic clean up I still can't get them working.

Not sure if it's still within your warranty, I now got one unknown USB Device in device manager with (Code 43)A request for the USB configuration descriptor failed. and following information:

Device USB\VID_0000&PID_0003\8&1fe228af&0&10 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x0
Problem Status: 0xC00000E5

 

[John Dowson]

21 minutes ago, C2615 said:

Things go south very quickly, After applying this and restart, I lost many of my device,

What do you mean by 'lost many of my device'? You should not try and do anything with any device yet. As O said, just run and exit and show me the files.

23 minutes ago, C2615 said:

and after restore the backup they still don't work.

Restore what from backup? Restoring the registry dump from back-up should put your system/registry in exactly the same state as it was before you ran the .reg script, This is the whole point of taking a back-up...

26 minutes ago, C2615 said:

Searching for a while, now I confirm all 4 USB3.x port on the back of MB (MSI MAG B650M Mortar WiFi (MS-7D76)  stopped working (still power but no data), by switch up some ports I get mouse and keyboard back online, by moving my 10 port hub to usb-c port now I got most but still not all joysticks working, that typeC port works, all 4 usb2 ports works, also one usb3.0 and 2 usb2.0 port on my computer's front panel still works.

Still I can't get normal working without that 4 USB3.x ports, and after system restoring, restarting, and some basic clean up I still can't get them working.

That script only removes the registry entries for 4 devices and in no way should affect your USB ports/hubs,

Sorry but I have no idea what you did or why this is happening. You obviously have not followed my instructions, or I would have expected to see your files after you had ran P3D/FSUIPC for the first time after cleaning the registry and reconnecting, and before doing anything else.

Sorry, but I cannot help if you are now having issues with USB controllers - this is nothing to do with FSUIPC.

[C2615]

15 minutes ago, John Dowson said:

Sorry, but I cannot help if you are now having issues with USB controllers - this is nothing to do with FSUIPC.

Sorry for the inconvenience, I was kinda in a panic mode.

After reset CMOS (short JBAT1 port) I was able to restore hardware function.

Maybe it's just a coincidence, or maybe some static interface when trying to unplug the usbs (although I did the normal protocol for preventing static).. anyway it's now fully functioning

And without apply the fix again, FSUIPC now seems working fine. Not sure if the files you still interested but here they are. I tried fly around to see if  things works so technically not "once loaded just exit")

I would be happy to go ahead and update the FSUIPC, then apply the suggested tweaking for ini file,  but what's your thought?

FSUIPC6joystickrecovered.zip

[John Dowson]

5 minutes ago, C2615 said:

And without apply the fix again, FSUIPC now seems working fine.

That is surprising as your log shows two devices assigned the same id and have the same GUID:

Quote

      625 Device acquired for use (as alternative possibility):
      625    Joystick ID = 1 (Registry okay)
      625    1=MJOY32
      625    1.GUID={8E5FFEE0-C03C-11ED-8007-444553540000}
      625 Device acquired for use:
      625    Joystick ID = 1 (Registry okay)
      625    1=Flight Throttle Quadrant
      625    1.GUID={8E5FFEE0-C03C-11ED-8007-444553540000}

Are these two devices working ok?

8 minutes ago, C2615 said:

I would be happy to go ahead and update the FSUIPC, then apply the suggested tweaking for ini file,  but what's your thought?

I would do this as your registry is still a mess.
Maybe also check that you have USB3 devices plugged into USB3 ports, and USB2 devices connected to USB2 ports.

[John Dowson]

By the way, you are now getting two devices reported with the same GUID (previously was 3):

Quote

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x1234, xBEAD, , -1, -1, 0, {NULL}, {NULL}, {E07B7D30-C041-11ED-8006-444553540000}, Y, N
N, x00, x044F, x0407, , -1, -1, 0, {NULL}, {NULL}, {8E5E0310-C03C-11ED-8003-444553540000}, Y, N
N, x00, x8889, x8889, , -1, -1, 0, {NULL}, {NULL}, {58B5EF40-0350-11EF-8003-444553540000}, N, N
N, x00, x8888, x8888, , -1, -1, 0, {NULL}, {NULL}, {8E5FFEE0-C03C-11ED-8008-444553540000}, N, N
N, x00, x8888, x8888, , -1, -1, 0, {NULL}, {NULL}, {8E618580-C03C-11ED-8009-444553540000}, Y, N
N, x00, x06A3, x0C2D, , -1, -1, 0, {NULL}, {NULL}, {E07B7D30-C041-11ED-8006-444553540000}, Y, N
N, x00, x231D, x0127, , -1, -1, 0, {NULL}, {NULL}, {09BCBC70-C03F-11ED-8016-444553540000}, Y, N
N, x00, x046D, xC29B, , -1, -1, 0, {NULL}, {NULL}, {3DB31D00-C03D-11ED-8010-444553540000}, Y, N
 

Maybe make sure those two devices (vJoy Device and Flight Throttle Quadrant) are connected to ports on different USB hubs. GUIDs should be unique for each device - I don't understand why these are being reported as the same. You should really be getting unique GUIDs from HID scanning. Cleaning the registry won't correct this.

[C2615]

38 minutes ago, John Dowson said:

That is surprising as your log shows two devices assigned the same id and have the same GUID:

Are these two devices working ok?

Just checked again and they working fine. in the ini they are on proper ID just as before when I assign things

40 minutes ago, John Dowson said:

Maybe also check that you have USB3 devices plugged into USB3 ports, and USB2 devices connected to USB2 ports.

I can't as there is too little USB2 port, so some USB2 stuff are on USB3 port.

18 minutes ago, John Dowson said:

Maybe make sure those two devices (vJoy Device and Flight Throttle Quadrant) are connected to ports on different USB hubs.

vJoy as name suggests, is a virtual device...I don't really use it in P3D but in some old game only support 2 or 3 controller I might need it for combine physical input, it haven't cause major problem so far, and it's not easy to connect and disconnect as it'll require reboot to do so.

44 minutes ago, John Dowson said:

I would do this as your registry is still a mess.

I suppose you mean, won't? 😅

[John Dowson]

If things are working, then you can just leave everything as it is. However, please update to use JoyLetters - just set
    AutoAssignLetters=Yes
in the [JoyNames] section of your ini.

If you want to try cleaning the registry, follow the instructions previously posted. But switched to JoyLetters first, and run P3D/FSUIPC at least once after doing this, to get your files updated to use the letters.

[C2615]

27 minutes ago, John Dowson said:

If things are working, then you can just leave everything as it is. However, please update to use JoyLetters - just set
    AutoAssignLetters=Yes
in the [JoyNames] section of your ini.

If you want to try cleaning the registry, follow the instructions previously posted. But switched to JoyLetters first, and run P3D/FSUIPC at least once after doing this, to get your files updated to use the letters.

Thanks, I have updated, applied AutoAssignLetters, changed the comment string and profile assignment, few test in and all working good so far.

The MJOY32 (ID1) still in the log, but seems in ini it picked the other one with ID5 and different GUID, and works great, so far,

Appreciate for your patiently support, I believe the case is closed for now.

[John Dowson]

Ok, thanks for the update.