Jump to content
The simFlight Network Forums

My Throttle X55 is no longer detected by FSUIPC 5.157 with P3D v4.5


Recommended Posts

After doing in sequence:

  1. Unplugged the controllers
  2. Run removeX55.reg
  3. Launch P3D/FSUIPC. At this stage, there was a problem with the stick being assigned the throttle command (same as above) and my throttle controller not being detected.
  4. Shutdown P3D and changing AutoAssignLetters to Yes
  5. Relaunched P3D (situation of controllers still the same as above)
  6. Shut down P3D and attached are the 2 files.

FSUIPC5.ini FSUIPC5.log

Link to comment
Share on other sites

41 minutes ago, John Dowson said:

Are you sure you don't have the saitek/logitech drivers installed, or are running any saitek control software

I forgot to answer this... I have no driver installed and no Saitek program installed... The only third-party running with P3D is EZCA v3

44 minutes ago, John Dowson said:

.are you unplugging your devices?

Not since I shut down P3D this morning.

Link to comment
Share on other sites

I don't understand why the registry cleaning seemed to do nothing this time.
And I don't understand why it is again getting two GUIDs for your stick but none for your throttle.

Could you show me your FSUIPC5.JoyScan.csv file please.

Link to comment
Share on other sites

I suspect that there may be other registry entires that need removing....

You could try running the.reg file again with devices unplugged (again, backup first), then reboot. Start regedit, backup again, and then search for 0738 (the VendorID for the X55). All entries you encounter that look related to your devices (i.e. if they also have a Product ID of 2215 or A215) should be removed. Then reboot again, connect you devices, start P3D/FSUIPC and see what is recognised. Show me you .log, .ini and .joyscan.csv files after doing this.

Maybe show me your current JoyScan.csv file first before doing this though....

Edited by John Dowson
Link to comment
Share on other sites

Maybe also try removing the installed drivers for the X55 after you have removed the registry entries (and before you plug in your controllers), and let windows re-install them again when you re-connect. I would do this before manually removing anything else with the same vendor and product ids.

Link to comment
Share on other sites

Sorry, I'm probably posting too many messages and confusing you...
If you have done anything yet, first try this:
 - unplug your devices
 - backup your registry
 - run the .reg file again
 - remove the drivers for your X55 using the windows device manager
 - reboot
 - connect your devices. Let windows install the default drivers
- start P3D/FSUIPC, load an aircraft, then shut down
- show me your 3 files, the .ini, .log and .JoyScan.csv files

If you still don't get the devices recognised as individual devices after doing this, then you can try manually setting/changing the joystick using a program called JoyIds. See 

John

 

Link to comment
Share on other sites

11 hours ago, John Dowson said:

If you have done anything yet, first try this:
 - unplug your devices
 - backup your registry
 - run the .reg file again
 - remove the drivers for your X55 using the windows device manager
 - reboot
 - connect your devices. Let windows install the default drivers
- start P3D/FSUIPC, load an aircraft, then shut down
- show me your 3 files, the .ini, .log and .JoyScan.csv files

Good morning John,

I was asleep when you replied, therefore I did not anything else than the above checklist.

11 hours ago, John Dowson said:

you can try manually setting/changing the joystick using a program called JoyIds.

When I click here, I reach a page from Air Group 52 within which there is no link to download the software... But I could find something with the same name here, expecting that is is the same. 

I ran the program and swapped ID2 to ID1. The result in P3D is that none of the controllers reacts...

JoyIDs_zhELulfiTG.png

FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv

Link to comment
Share on other sites

Are those files from after you changed the ids or before? After I presume....


Can you again do the following:
- unplug your devices
 - backup your registry
 - run the .reg file again
 - remove the drivers for your X55 using the windows device manager
 - reboot

Once done, don't connect your devices, but go into regedit and search for any entries with  a vendor id of 0738  and a product id of 2215 or A215. Do you see anything?
If so, try removing those. You really want  to remove all traces of these devices so that they are detected as new devices. Once those entries have been removed, reboot again and give the registry a last check. Then connect you devices, start P3D/FSUIPC, load an aircraft, shut down, and then show me those 3 files again.

Link to comment
Share on other sites

3 hours ago, John Dowson said:

Are those files from after you changed the ids or before? After I presume....

Hello,

Yes, files after id changes.

3 hours ago, John Dowson said:

- unplug your devices
 - backup your registry
 - run the .reg file again
 - remove the drivers for your X55 using the windows device manager
 - reboot

Done as I get used to 🙂

3 hours ago, John Dowson said:

Once done, don't connect your devices, but go into regedit and search for any entries with  a vendor id of 0738  and a product id of 2215 or A215. Do you see anything?

Yes I found some entries after typing SAITEK. See attached file {Entries SAITEK.png}. Entries deleted.

 

3 hours ago, John Dowson said:

Once those entries have been removed, reboot again and give the registry a last check.

Rebbot done and new search in Registry... but with search criteria VID_0738. I used this criteria because I saw the format during the first search. And then I found some other entries {Entries VID_0738.png}. But I CANNOT delete these entries. {Message Entries.png}

 

3 hours ago, John Dowson said:

Then connect you devices, start P3D/FSUIPC, load an aircraft, shut down, and then show me those 3 files again.

Done in sequence. Noticed that my Stick is not detected and the throttle controller is linked to the aircraft joystick axis.

 

3 hours ago, John Dowson said:

Are you connecting your devices to usb3 or usb2 ports? If using usb3, maybe try switching to usb2 ports instead

I was using USB 3 but this time files are related to controllers connected to USB2

Entries SAITEK.png

Entries VID_0738.png

Message Entries.png

FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv

Link to comment
Share on other sites

Ok. But now everything is detected ok:

Quote

      172 Product= Saitek Pro Flight X-55 Rhino Stick
      172    Manufacturer= Madcatz
      172    Serial Number= G0001739
      172    Vendor=0738, Product=2215 (Version 0.87)
      313    GUIDs returned for product: VID_0738&PID_2215:
      313       GUID= {E942D3A0-E721-11EB-8002-444553540000}
      313       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0
      313 Product= Saitek Pro Flight X-55 Rhino Throttle
      313    Manufacturer= Madcatz
      313    Serial Number= PP000503
      313    Vendor=0738, Product=A215 (Version 0.119)
      313    GUIDs returned for product: VID_0738&PID_A215:
      313       GUID= {E94396F0-E721-11EB-8004-444553540000}
      313       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255
      313 -------------------------------------------------------------------
      328 Device acquired for use:
      328    Joystick ID = 0 (Registry okay)
      328    0=Saitek Pro Flight X-55 Rhino Stick
      328    0.GUID={E942D3A0-E721-11EB-8002-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 1 (Registry okay)
      328    1=Saitek Pro Flight X-55 Rhino Throttle
      328    1.GUID={E94396F0-E721-11EB-8004-444553540000}
 

This is good!

Now you just need to change the [JoyNames] section in your FSUIPC5.ini. Change it to this (with P3S/FSUIPC not running):

Quote

[JoyNames]
AutoAssignLetters=Yes
0=Saitek Pro Flight X-55 Rhino Stick
0.GUID={E942D3A0-E721-11EB-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Throttle
1.GUID={E94396F0-E721-11EB-8004-444553540000}
A=Saitek Pro Flight X-55 Rhino Throttle 
A.GUID={E94396F0-E721-11EB-8004-444553540000}
E=Saitek Pro Flight X-55 Rhino Stick
E.GUID={E942D3A0-E721-11EB-8002-444553540000}

Then try starting P3D/FSUIPC, and hopefully things should be ok.....

John

Link to comment
Share on other sites

Hello John,

I think that you made my day 🙂

After editing the .log file with your proposed text, all seems to be fine now. Event the calibration through W10 is now possible, both calibration panels are available...

I just mad a quick flight to validate m settings and everything is good.

I will keep the system under observation for some time.  I will shut down computer and wake it up this afternoon to see if everything is solid. Will keep you advised.

Thanks again for your assistance

Best regards

Bruno

Link to comment
Share on other sites

Glad its all now working. Hope the GUIDs don't change again! You should be ok if the joystick IDs change, as you are now using JoyLetters.

9 hours ago, Braudoux said:

Event the calibration through W10 is now possible, both calibration panels are available...

Ok. This makes me thing it was a driver/registry issue. Hopefully you should be ok now...

Regards,

John

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.