Jump to content
The simFlight Network Forums

FSUIPC 6 not detecting some controllers


Recommended Posts

Hi 

 

My FSUIPC 6 is unable to detect my GF-Pro Yoke and my VPC joystick. It is however able to detect all of my other controllers such as my Saitek TQ. 

I have been using FSUIPC since v4 and this is the first time I encountered something like this.

Also worth mentioning maybe, I am running FSUIPC 7 on another disk with MSFS 2020.

 

Log files attached.

 

Thanks in advance for the assistance.

 

FSUIPC6_prev.log FSUIPC6.log

FSUIPC6.JoyScan.csv

Edited by VERTSPD
Link to comment
Share on other sites

Your log shows there are issues with duplicate ids in your registry, as well as a missing device:

Quote

      188 Product= <not readable at this time: maybe device disconnected?>
      188    Vendor=1532, Product=0208 (Version 1.1)
      188    GUIDs returned for product: VID_1532&PID_0208:
      188       GUID= {3B622070-5FA2-11EC-8001-444553540000}
      188       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      188       GUID= {3B622070-5FA2-11EC-8002-444553540000}
      188       Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255
...
      203    WARNING: Joystick ID 2 is duplicated in Registry
      219    WARNING: Joystick ID 4 is duplicated in Registry
      219    WARNING: Joystick ID 0 is duplicated in Registry
 

But your yoke and VPC joystick are detected, and the latter acquired for use, but with the same id as your Razer Tartarus Chroma:

Quote

      188 Product= GoFlight YOKE
      188    Manufacturer= GoFlight Technology Inc.
      188    Vendor=09F3, Product=0029 (Version 0.1)
      188    GUIDs returned for product: VID_09F3&PID_0029:
      188       GUID= {97185C40-98C8-11EC-8001-444553540000}
      188       Details: Btns=13, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      188 Product= L-VPC Stick WarBRD
      188    Manufacturer= VIRPIL Controls 20220304
      188    Serial Number= FF
      188    Vendor=3344, Product=80CB (Version 1.0)
...
      219 Device acquired for use:
      219    Joystick ID = 6 (Registry okay)
      219    6=Razer Tartarus Chroma
      219    6.GUID={3B622070-5FA2-11EC-8002-444553540000}
      235 Device acquired for use:
      235    Joystick ID = 6 (Registry okay)
      235    6=LEFT VPC Stick WarBRD
      235    6.GUID={3B622070-5FA2-11EC-8002-444553540000}
 

That is very strange,,, Could you also show me your FSUIPC6.ini file please - we can try using that to change/reset the ids.

On 9/15/2022 at 9:47 AM, VERTSPD said:

Also worth mentioning maybe, I am running FSUIPC 7 on another disk with MSFS 2020.

With the same devices? And all is ok there? If that is the case, maybe also show me your FSUIPC7.ini and an FSUIPC7.log file for comparison.

John

Link to comment
Share on other sites

Hi,

 

Very strange indeed. However, all easily fixed by unplugging and plugging my GF-Pro yoke. Once I do that all the controllers get "magically" detected. First time I see this actually. I believe it must be related to the high amount of controllers I have connected to my PC.

Everything working a-ok with FSUIPC 7.

Link to comment
Share on other sites

Sounds like it might be an issue with your USB hubs. Try switching hubs for the GF-Pro yoke if possible, and check that you have power management disabled on all USB hubs. Windows has a tendency to revert this setting on some windows updates.

8 minutes ago, VERTSPD said:

Everything working a-ok with FSUIPC 7.

Good to know, thanks!

John

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.