Windows 10 & Saitek Drivers
-
Device Specific Installation Notes
-
X52, X52 Pro and X65f - Windows 10, 64 bit – During stage 4 the driver may not over install correctly due to an older signed driver taking priority over the beta version. To resolve this:
- Hold down the shift key on your keyboard, keep it held down.
- Click the Start button, click power and then click restart.
- You can release the Shift key.
- You will be presented with a light blue screen with some options.
- Select Troubleshoot > Advanced Options > Start up Settings, then click restart.
- When the Startup Settings screen appears press F7 on your keyboard.
- Windows will continue to load as normal.
- Rerun the driver installation.
- When prompted, click the install driver anyway option, to get the latest version installed correctly.
-
Note! If you change USB port after carrying out this process, the older driver will again get installed. To resolve this, just rerun the driver installation program.
-
X52 Pro - Windows 10, 32 bit – During stage 4, Direct Output service may not get installed. This is crucial for the MFD to function correctly. To resolve this:
- Go to the Windows folder on the main hard drive.
- Go into Temp\Saitek\Saitek_X52Pro_Flight_Controller_7_0_41_10_x86_Drivers\Msi.
- Double click the DirectOutput installer icon to install the service.
- A successful installation will show DirectOutput 7.0.41.10 in Control Panel > Programs and Features.
-
All Device Software - Windows 10, 32 and 64 bit – If this is the first time you have installed software from Saitek, .Net framework will need to be installed by Windows. This will be asked for either during installation, or the first time you run the Profile Editor application. Once this has installed you may need to rerun the software installation application to get correct functionality.
-
Testing Profiles on all devices and versions – If the profile editor window is open whilst testing profiles in games, this will impede the profiling as it causes an output conflict between the editor and the game. Best practise is to either:
- Test profile commands using the test feature in the profiler editor.
- Activate the profile, close the profile editor application, and then test commands in notepad, or directly in–game.
Known issues with 7.0.41.10 Release
-
X52
- MFD displays Mo instead of Mode 1, 2 or 3 depending on mode switch position.
- MFD brightness display slider has no affect.
-
X55
- After reboot, the throttle input information will not be displayed in Devices and Printers > Game Controllers > Properties test screen. The input and controls will still work though, and can be confirmed on the programming screen of the Profile Editor.
- Profile Editor not opening when system tray icon or desktop icon is clicked. Users have reported this, but we can’t replicate on our test systems. If this happens on your system, go to Program Files > Mad Catz > X55 Rhino, and remove the last ‘.’ (dot) from the H.U.D. application executable. Future releases will remove the dots entirely.
-
X65F
The Devices and Printers > Game Controllers > Properties > Force Settings page for X65F will not read the force settings that have been applied to the device. All sliders will read 100%. Whilst we fix this issue, customers are advised to do all force setting adjustment from the Settings Page of the Profile Editor.
-