X56 throttle not connecting

[Carlos Alvarez]

Hi. For some reason the X56 throttle stop been recognized by only FSUIPC 7. all other software including 3rd party software are still working. What can i do?

FSUIPC7.log

[John Dowson]

Your throttle has the same joystick id as your rudder pedals for some reason.
Can you please attach your FSUIPC7.ini and FSUIPC7.JoyScan.csv files. We can possibly resolve this by changing your ini file to get the Joy Ids updated, but if that doesn't work me may need to correct/edit your registry.

John

[Carlos Alvarez]

12 hours ago, John Dowson said:

Your throttle has the same joystick id as your rudder pedals for some reason.
Can you please attach your FSUIPC7.ini and FSUIPC7.JoyScan.csv files. We can possibly resolve this by changing your ini file to get the Joy Ids updated, but if that doesn't work me may need to correct/edit your registry.

John

I have no idea why that change. Sure I attach it. Happy new year,

FSUIPC7.ini FSUIPC7.JoyScan.csv

[John Dowson]

Did you install any saitek drivers or software? Your X-56 throttle and stick have the same PID, which is usually caused by installing saitek software and/or drivers.
If so, can you disconnect your devices, uninstall any saitek drivers or software, reboot then reconnect and let windows install the default windows drivers.
Then show me your updated FSUIPC7.log, .ini and .JoyScan.csv files.
If they are still showing with the same PID after that, we will need to clean your registry.

[Carlos Alvarez]

9 hours ago, John Dowson said:

Did you install any saitek drivers or software? Your X-56 throttle and stick have the same PID, which is usually caused by installing saitek software and/or drivers.
If so, can you disconnect your devices, uninstall any saitek drivers or software, reboot then reconnect and let windows install the default windows drivers.
Then show me your updated FSUIPC7.log, .ini and .JoyScan.csv files.
If they are still showing with the same PID after that, we will need to clean your registry.

Hi. No luck still same problem and same log and svc file. Can we go ahead and remove the reg? Can u tell me how.

[John Dowson]

15 hours ago, Carlos Alvarez said:

No luck

No luck with what? What did you try?

15 hours ago, Carlos Alvarez said:

Can we go ahead and remove the reg? Can u tell me how.

Yes, but before we do that can you let me know if you did have any saitek software or drivers installed or not. And if you did and removed them, I need to see your updated files.

[Carlos Alvarez]

3 hours ago, John Dowson said:

No luck with what? What did you try?

Yes, but before we do that can you let me know if you did have any saitek software or drivers installed or not. And if you did and removed them, I need to see your updated files.

Hi John. Yes I had it install before and after the last post I uninstalled the drivers, I have disconnected the joystick and plug back in then. I haven’t see that windows have install any default driver on the joystick so I wanted to give Saitek a second try with the X56 drivers that I had before and was working btw so I reinstalled the drivers and try it again but still no respond on the Throttle so now I have uninstalled the X56 drives again and rebooted my pc but still the reg files are still on the system. I can give u the log again but look the same for me, Tho I have to finish my shift in the airport before u can have access to that. 
 

have a nice day.

[John Dowson]

I need to see all 3 files again (FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv) after the changes you have made and when using the default windows drivers.
Once I have seen them, I can advise on cleaning your registry.

[Carlos Alvarez]

57 minutes ago, John Dowson said:

I need to see all 3 files again (FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv) after the changes you have made and when using the default windows drivers.
Once I have seen them, I can advise on cleaning your registry.

John btw The Windows driver is something I have to get my sel, or is something I can see in the screen when they are installing?  I ask to get more like a visual reference. 

[John Dowson]

8 minutes ago, Carlos Alvarez said:

John btw The Windows driver is something I have to get my sel, or is something I can see in the screen when they are installing?  I ask to get more like a visual reference. 

You usually get a notification of some sort - a message that is displayed then disappears, but I think this depends on your windows settings. I wouldn't worry about it. You can always check which drivers are in use via the Windows Device manager, if needed.

John

[Carlos Alvarez]

Ok John here are thge files with Hotas Driver install

FSUIPC7.JoyScan - With Drivers.csv FSUIPC7 - With Drivers.log FSUIPC7 - With Drivers.ini

[Carlos Alvarez]

and here are the files without any driver. 

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

[John Dowson]

Do not install any Saitek drivers. Disconnect your saitek devices and then take a back-up of your registry (using the Windows Registry Editor, File -> Export).
Then create a file called removeDevices.reg (name doesn't matter but extension must be .reg)) with the following content:

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221]

[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221]

Run that file by double-clicking it in Windows Explorer. This will remove those registry entries. Then reboot and re-attach your devices.
Then run FSUIPC7, exit and show me those 3 files again.

John

[Carlos Alvarez]

13 hours ago, John Dowson said:

Do not install any Saitek drivers. Disconnect your saitek devices and then take a back-up of your registry (using the Windows Registry Editor, File -> Export).
Then create a file called removeDevices.reg (name doesn't matter but extension must be .reg)) with the following content:

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaResources\Joystick\DINPUT.DLL\JoystickSettings\VID_0738&PID_A221]

[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaResources\Joystick\DINPUT.DLL\JoystickSettings\VID_0738&PID_2221]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221]
[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0738&PID_A221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0738&PID_A221]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221]
[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0738&PID_2221]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0738&PID_2221]

Run that file by double-clicking it in Windows Explorer. This will remove those registry entries. Then reboot and re-attach your devices.
Then run FSUIPC7, exit and show me those 3 files again.

John

Hi John i think the thouttle has been recognize after the reset but the log still is telling me that is wrong. 

FSUIPC7.JoyScan.csv FSUIPC7.log FSUIPC7.ini

[John Dowson]

Please always exit FSUIPC7 before attaching  files as it helps to see the full files after FSUIPC7 has closed down, not when still running.

Seems to be an issue with your rudder pedals now. Disconnect them, run the below again as a .reg script, reboot then reconnect:

Quote

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763]
[-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763]

I don't know  if you noticed, but I also corrected the first .reg file contents I posted an hour or two after the initial post (due to a typo).
If you ran than before my update, please also run that again (with devices disconnected).

If you still get an issue after that, disconnect those three devices and re-run those scripts and reboot. DONT reconnect your devices, just run FSUIPC7 then exit, and show me the FSUIPC7.Joyscan.csv file, as this will then show what is in your registry with those devices removed and disconnected. They shouldn't appear at all, but if they do there may be some other registry entries that need removing that I am unaware if.

John

[Carlos Alvarez]

Hi again. I dont know if the problem is because W11 that im running on my pc,  for a minute ago i had trouble now with my joystick that didnt want to be recognice, this time i run the reg file again and now is working. Here are the files again. I have no idea what's going on

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

[John Dowson]

48 minutes ago, Carlos Alvarez said:

I dont know if the problem is because W11 that im running on my pc,

That should be fine - as long as your PC meets the minimum requirements. I, and many others, are runnning MSFS with FSUIPC7 on windows 11 without issues.
Note, however, that if running on Windows 11 you may need to add the following to the [General] section of you ini file:
    DisableMSFSMonitor=Enum
This is needed if FSUIPC7 closes because it thinks MSFS has stopped running (cannot be detected) although it still is.

53 minutes ago, Carlos Alvarez said:

this time i run the reg file again and now is working. Here are the files again. I have no idea what's going on

Could you please provide more details on what you have actually done...when I give you several things to try, you need to be explicit in your response so that I know what you have actually done - did you run the first reg file again? Did you run the second reg file?

Maybe we should take this one step at a time...

Disconnect your X56 and your rudder pedals. Run both registry scripts (or combine them into one script and run that). Reboot. Rename or delete your FSUIPC7.ini - you will lose your assignments but you do not have that many, and they are duplicated, you can redo them once we have your devices recognised correctly.
Then run FSUIPC7 - still with your X56 and rudder devices disconnected. This should just leave your Logitech G13 Joystick connected.

Lets see if it recognises that as a single device. Then PLEASE exit FSUIPC7 - as I said, I need to see these files AFTER FSUIPC7 has exited- you keep attaching them when FSUIPC7 is still running (unless it has crashed...).
That should tell us if we also need to clean the registry of your Logitech G13 joystick.

Also, if you have installed Logitech drivers (or software) for that joystick, best to remove them and let windows install the default drivers, as you did with the Saitek devices.

[Carlos Alvarez]

On 1/5/2022 at 5:07 PM, John Dowson said:

That should be fine - as long as your PC meets the minimum requirements. I, and many others, are runnning MSFS with FSUIPC7 on windows 11 without issues.
Note, however, that if running on Windows 11 you may need to add the following to the [General] section of you ini file:
    DisableMSFSMonitor=Enum
This is needed if FSUIPC7 closes because it thinks MSFS has stopped running (cannot be detected) although it still is.

Could you please provide more details on what you have actually done...when I give you several things to try, you need to be explicit in your response so that I know what you have actually done - did you run the first reg file again? Did you run the second reg file?

Maybe we should take this one step at a time...

Disconnect your X56 and your rudder pedals. Run both registry scripts (or combine them into one script and run that). Reboot. Rename or delete your FSUIPC7.ini - you will lose your assignments but you do not have that many, and they are duplicated, you can redo them once we have your devices recognised correctly.
Then run FSUIPC7 - still with your X56 and rudder devices disconnected. This should just leave your Logitech G13 Joystick connected.

Lets see if it recognises that as a single device. Then PLEASE exit FSUIPC7 - as I said, I need to see these files AFTER FSUIPC7 has exited- you keep attaching them when FSUIPC7 is still running (unless it has crashed...).
That should tell us if we also need to clean the registry of your Logitech G13 joystick.

Also, if you have installed Logitech drivers (or software) for that joystick, best to remove them and let windows install the default drivers, as you did with the Saitek devices.

Im getting an insane amount of CTD after the reg deleted. Should I remove MSFS and reinstalled?

[John Dowson]

Why are you not doing as I asked? 

On 1/5/2022 at 5:07 PM, John Dowson said:

Disconnect your X56 and your rudder pedals. Run both registry scripts (or combine them into one script and run that). Reboot. Rename or delete your FSUIPC7.ini - you will lose your assignments but you do not have that many, and they are duplicated, you can redo them once we have your devices recognised correctly.
Then run FSUIPC7 - still with your X56 and rudder devices disconnected. This should just leave your Logitech G13 Joystick connected.

What have you actually done? Can you please tell me exactly what you have done, as you don't seem to be following my advice - and why are you running MSFS - I only asked you to run FSUIPC7....
I cannot really help you if you are not willing to follow my advice....
I hope that you at least took a back-up of your registry...

[Carlos Alvarez]

On 1/6/2022 at 8:50 PM, John Dowson said:

Why are you not doing as I asked? 

What have you actually done? Can you please tell me exactly what you have done, as you don't seem to be following my advice - and why are you running MSFS - I only asked you to run FSUIPC7....
I cannot really help you if you are not willing to follow my advice....
I hope that you at least took a back-up of your registry...

Hi John i was out of home for a few days. im gonna try to fix the problem now 1 step at the time. So far i just have diosconect from my pc the joystick, throttle and the rudder.

now you meantion to run both reg files? which 1 are they? I only have the 1 you gave me (removeDevices). Should I run this 1 and reboot?

[John Dowson]

Unfortunately I am on holiday now, back on support on the 18th. I am not going to review this support request until then.
Please review what I have already advised. and also please remember that i do need details on what you have actually done, especially when I am suggesting multiple or different options. And I need to see your files each time you have changed things and require further support.

In summary, review what I have already advised, provide the new files and I will get back to you on the 17th or 18th.

Sorry for the delay.

John

 

[Carlos Alvarez]

Well John lets start over.

This is what i hade done so far.

**1** Disconnected the whole set of X56 + rudder. Run the file (remove Devices.reg) which u gave me, reboot my pc after the reg wipeout.

**2** Connecting 1 by 1 (no pop window or sound after reconnection) no software instalation (drivers) and windows didn't do anything either

Resault

The joystick are now back and running but the whole MSFS got damage after the 1st time I run the (removeDevices.reg) I experience CTD within 2 min after i press (fly). Looks like there's nothing left to do them wipeout MSFS. 

PD there was nothnig left on my community folder, so no failty addon is causing the CTD in so short time. I'll provide the both files before I run the (removeDevices.reg) and after.

[Carlos Alvarez]

this're before the remove Devices.reg

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7_prev.log

[Carlos Alvarez]

here's after

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

[John Dowson]

Hi Carlos,

sorry for the delay - I am back now...

Question: did you run the second .reg script I provided (on the 5th January)? There is still a conflict between your Logitech G13 Joystick and your rudder pedals that this should (hopefully) solve.

The registry changes are to clean-up your devices and in no way would this cause any changes to MSFS (so re-installing won't help), and they should also not cause MSFS to CTD. Are you still getting these? Are you using empty profiles for your devices in MSFS (recommended if assigning in FSUIPC), or do you have assignments to your devices in MSFS? 

And did you take a back-up of your registry before making the suggested changes? If so, try restoring that back-up and see if you still get the CTDs with your original registry and we can go form there. Otherwise, try creating new (empty) profiles for your devices in MSFS.