This are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Fixing problems with 50% (or digital on/off) action with axes assignments
This is quite an old post! Saitek now provide some .reg files that will remove /re-calibrate your Saitek device, so before following the details of this post for Saitek devices, please see the following:
https://support.logi.com/hc/en-us/articles/360023194074-Recalibrate-controller-axes-RegEdit
For non-saitek devices, you can follow the general advice here. Basically you need to unplug your device and remove any and all registry entries for that device - you can search the registry on the VID and PID numbers of your device to find the entries.
Please back-up your registry before editing!
====================================
It appears that some users have problems with some controller drivers (e.g. Saitek Quadrant) setting up the Registry incorrectly for one or more of the levers, with the result that either only 50% of the range use used or the values you get are only on (max value, 16383) or off (min value 0 or -16384).
Here is the way to edit the Registry and fix this.
(Thanks to a main forum reply by "goaround"):
====================================
Here is our registry calibration guide:
One way to re-calibrate your device is to reset the raw data values that are held in Windows registry.
To do this:
- Remove the USB plug for your controller from the PC.
- Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box.
- Type regedit and then click ok.
- The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name.
+ HKEY_LOCAL_MACHINE + System + CurrentControlSet + Control + Media Properties + Private Properties + Joystick + OEM
- Delete any folder inside the OEM folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID.
- Then navigate to the DirectInput folder
+ HKEY_CURRENT_USER + SYSTEM + CurrentControlSet + Control + Media Properties + Private Properties + DirectInput
- Delete any folder inside the Direct Input folder that begins VID_06A3 or VID_0738, if you know the specific PID number or your device then you only need to delete the string that matches the VID and PID.
- Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. This will rebuild the data range for all axes.
Hello, I test this and it does not worf for me..
Posted by: @guit32I test this and it does not worf for me..
What is your device? Did you use the correct VID and PID numbers for your device?
Is your issue as described here, i.e. do you get 50% range or just on (max) / off (min) values?
What values do you see for your axis in the windows game controllers calibration?
Hello
I have a saitek throttle quadrant. I delete all the VID_06A3 folder in the registery? I have no full range in fsuipc and in MSFS2024, I am on windows 11, it seems ok in the windows game controleur calibration ? I install also saitek driver (otherwise no detection in windows)
Device HID\VID_06A3&PID_0C2D\a&174fb37&0&0000 was configured.
"Did you use the correct VID and PID": what do you want to say ? where ?
Is your issue as described here, i.e. do you get 50% range or just on (max) / off (min) values?
I have only 50% of range (it jump to -16000 rapidly)
Posted by: @guit32I install also saitek driver (otherwise no detection in windows)
Try uninstalling and deleting the Saitek drivers, and don't use/run any saitek software when using FSUIPC. Windows should install standard default drivers. These should work just fine with FSUIPC.
Already did unfortunately it does nothing, I have also buy a new quadrant throttle but it does the same.. Is it working for other people ?
Posted by: @guit32Already did unfortunately it does nothing,
What do you mean? Doesn't FSUIPC recognise your device with the default windows drivers? Did you check / verify that the saitek drivers didn't get re-installed (which is why its best to delete / remove them from your system)?
Posted by: @guit32I have also buy a new quadrant throttle but it does the same.. Is it working for other people ?
Well, I hope you didn't buy a new one because the old one had the same issue...
Saitek throttle quadrants should work just fine with FSUIPC. I have one somewhere which I used for many years, although I don't use this any more.
To help other:
I found the solution for me: I download the saitek programm to recalibrate axis here and now it wor ks !
https://support.logi.com/hc/en-us/articles/360023194074-Recalibrate-controller-axes-RegEdit
Posted by: @guit32"Did you use the correct VID and PID": what do you want to say ? where ?
I wasn;t sure what device you were using, and wanted to check that you were using the correct VID & PID for yuor device when deleting registry entries.
After you have removed any saitek drivers and disconnected your device, search your registry for all entries using that VID and PID and delte them (take a backup of your registry first). Then reboot before re-connecting your device, and then let windows install default drivers. Then check the drivers installed are not the saitek ones. Then check your device in FSUIPC.
Posted by: @guit32To help other:
I found the solution for me: I download the saitek programm to recalibrate axis here and now it wor ks !
https://support.logi.com/hc/en-us/articles/360023194074-Recalibrate-controller-axes-RegEdit
Ah, ok. Then that would indicate that you didn't remove all the necessary registry entries. But re-reading this post, its not that clear and is in fact confusing. I will update this.
Thanks for the update,
John