I’m sure there was a similar issue with another of Logitechs products (a wheel?) where they brought out a tool to remove some registry keys to fix.
Glad it’s all sorted.
1 Like
Many thanks for this solution. I spent a few hours trying to troubleshoot but would never have thought it was registry issue. My dual Logitech throttle quadrants work perfect now.
This should be a pinned topic. :^)
1 Like
Brilliant - fixed it for me as well - Thanks
Thank you very much!
Hi, im trying to fix this problem but I cant find this two registry keys. Can anybody help me?
After some days working well, I notice the same issue with right and middle axis on axis cuadrant. I solved this problem:
Configuration, Devices, Devices and Printers, select Flight Yoke System, Configuration, Properties.
I saw the same problem in the Test window.
I Restore fixed values.
The problem was solved.
I hope this may help.
Hello. Today i bought a new Logitech Throttle Quadrant. I did a calibration in the Windows 10 Game Controller Settings… Later i found a Logitech 64bit Driver for the Throttle. But now, i dont have the game controller calibration anymore… I tried everything, but i am still have only the Test and Dead Zones tool. What is wrong with this and how can i get back the standard calibration tool? I need a new calibration of the 3 axis for my MSFS aircraft configurations. Thanks!!
I have the same problem with my Logitech throttle quadrant also, both the X and Y axes behave erratically, and strangely, the Z axis works fine. The calibrate option is also not present in the Control Panel, Devices and Printers configuration, though the device is present in that page.
I’m surprised Microsoft/Asobo did not include the calibrate feature in the simulator, if I remember correctly, it was present in FSX, and it is included in X-Plane 11.
Question, do you delete the registry objects that have the VID_* prefix or do you have to start at say… starting at Joystick?
I also see several instances of the VID objects in both registry folders, are you saying that I should delete all of those instances or one specifically, or the parent objects (DirectInput, and Joystick) ?
Keyboard controls work fine, even the ones you set up. However, the controls that are configured for the Logitech TQ device will take precedence over the ones you set up for the keyboard, which is probably a fault. I found this out when I tried to use the keyboard for throttle and flaps and they weren’t working and I couldn’t find anything in the simulator that would change the priority of devices, but when I disconnected the TQ, they keyboard started working.
This was a really useful post and solution, but in in my case I had to remove more than just those registry entries.
So, I hope this help in case somebody else gets my same issue.
As an example, I found out anothe registry entry at: Computer\HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_XXXX&PID_XXXX
To guarantee nothing was remaining, I did a search for the VID_XXXX and everything that was erasable, I removed, and finally end up with the Quadrant working
1 Like
To anyone who still has this problem… axes working fine in the device manager calibration section, but go whacky in the MSFS control setup page, this registry hack is pointless. If it works OK in windows why reset it?
There is an issue in the in game calibration system.
The only workaround is to disable the axes in-game and use FSIUPC to calibrate the axes.
My Saitek is all working perfectly now.
I have the same issue. Downloaded the Logitech driver and uninstalled cuz of no calibrate feature. But it still opens with that driver test page. Did u find a solution ?
No, i never got it back… I am still have only the test tool like in the screenshots. But my Logitech Throttle Quadrant works fine meanwhile in all axis and buttons.
Didn’t work for me, so I cleard all the throttle inputs in MSFS 2020 and setup the throttles through Spad.Next. Works now.
The heck is Spad?