Jump to content
The simFlight Network Forums

Device Number Issue

Recommended Posts

I upgraded to P3Dv5.1 & FSUIPC6 after uninstalling all previous P3Dv4 versions & addons. After clean install I tried to assign controls in FSUIPC, but my throttle device number was different than P3D and would not accept commands (device 1 in P3D & device 3 in FSUIPC). I noticed the same behavior in the Maddogx Load Manager (LM) with it's custom control options. In the LM if I manually changed the device number to match P3D it would work in the sim, however I can't see where I can do that in FSUIPC6. I've tried unplugging all controllers, restarting, and removing in the device manager. I noticed the device numbers in the registry matched the INI file so I manually changed the device numbers in the registry to match P3D: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput. I tried removing the joynames from the INI file and even changing those numbers. No matter what I do the FSUIPC INI & LOG files always assign the wrong numbers. I tried autoassign letters, but it assigned "D" to the throttle, which would correspond to 3 and it didn't work. 


Where is FSUIPC getting the device number from in the registry? Is there a way to force FSUIPC to use a specific device number?


Just prior to upgrading I had one of my TM MFDs go bad. Not sure if this is contributing to the issue. To be sure I unplugged and removed both MFD from device manager and deleted the associated registry entries in directinput & OEM. 


0=Joystick - HOTAS Warthog
2=TPR T.Pendular Rudder
3=Throttle - HOTAS Warthog


      156 Product= Joystick - HOTAS Warthog
      156    Manufacturer= Thustmaster
      156    Vendor=044F, Product=0402 (Version 1.0)
      171    GUIDs returned for product: VID_044F&PID_0402:
      171       GUID= {01BF0F90-487A-11EA-8001-444553540000}
      171       Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0
      171 Product= Throttle - HOTAS Warthog
      171    Manufacturer= Thrustmaster
      171    Vendor=044F, Product=0404 (Version 1.0)
      171    GUIDs returned for product: VID_044F&PID_0404:
      171       GUID= {01C88570-487A-11EA-800B-444553540000}
      171       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y1023,Z16383
      171 Product= T-Pendular-Rudder
      171    Manufacturer= Thrustmaster
      171    Vendor=044F, Product=B68F (Version 1.16)
      171    GUIDs returned for product: VID_044F&PID_B68F:
      171       GUID= {1E9270D0-4901-11EA-8001-444553540000}
      171       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z65535
      171 -------------------------------------------------------------------
      171 Device acquired for use:
      171    Joystick ID = 0 (Registry okay)
      171    0=Joystick - HOTAS Warthog
      171    0.GUID={01BF0F90-487A-11EA-8001-444553540000}
      171 Device acquired for use:
      171    Joystick ID = 3 (Registry okay)
      171    3=Throttle - HOTAS Warthog
      171    3.GUID={01C88570-487A-11EA-800B-444553540000}
      171 Device acquired for use:
      171    Joystick ID = 2 (Registry okay)
      171    2=TPR T.Pendular Rudder
      171    2.GUID={1E9270D0-4901-11EA-8001-444553540000}



Edited by Chris Kelley
Removed screenshots
Link to comment
Share on other sites

You should really be using the JoyLetters facility, as this was designed to prevent problems arising from when your joystick IDs change.
Please activate this facility by setting AutoAssignLetters=Yes  in your FSUIPC6.ini [JoyNames] section, start P3D, load an aircraft and then close, and show me both you FSUIPC6.ini and FSUIPC6.log files please. Attach them, do not post extracts - I need to see the full files.

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.