Saitek X52 is TRASH!!!
-
Thank you, I’ll give it a try!
My only issue with the latest drivers was when moving hard the stick to the right, the display goes for a second off and the throttle starts to recaliber again… -
I was also ready and willing to give up on the X52 and its calibration/configuration issues until I stumbled upon this guide:
https://www.reddit.com/r/EliteDangerous/comments/2qjsw4/psa_saitek_x52_install_problem_solved/
I haven’t had a single hitch ever since (even with the SST programming utility that seems to be the root cause of several of the problems associated with the X52).
Results may vary, but I’d recommend you give this guide a shot and report back before getting rid of your X52.
That is the what I did, followed up with some config copy/pasting……and it worked.
-
Thank you, I’ll give it a try!
My only issue with the latest drivers was when moving hard the stick to the right, the display goes for a second off and the throttle starts to recaliber again…To avoid the loss of calibration, consider too that the hotas works best when you plug it in a self-powered usb hub (that is, one that you plug into a power surge on its own). When it loses calibration, you should in fact notice that the leds blink, as if it loses power for a fraction of second
-
To avoid the loss of calibration, consider too that the hotas works best when you plug it in a self-powered usb hub (that is, one that you plug into a power surge on its own). When it loses calibration, you should in fact notice that the leds blink, as if it loses power for a fraction of second
Yeah, Saruman, I use a self-powered usb-hub. Few minutes ago I’ve finished the procedure described here:
https://www.reddit.com/r/EliteDangerous/comments/2qjsw4/psa_saitek_x52_install_problem_solved/
but no joy.
I start to think that there’s some hardware problem inside the stick, tomorrow I’ll dismount it -
Give a try to that driver/sst combo before using the screwdriver, if you use Win 10
-
well…
X52 works very well with Windows 8.1.
now does not work with Windows 10And you blame X52 ?
Strange reasoning
I blame saitek.Microsoft can’t configure windows for all products. Hardware manufacturers should provide support for new OS.
-
Very true….
Companies like Saitek need to remain relevant, Windows makes OS’s…thats it. Saitek have been behind the eight ball with Win 10. I read somewhere it was because of a company issue(restructure or something) -
For the record, I have had no issue with Windows 10 and my x-52. However, it never leaves it’s usb port and remains plugged in all the time.
-
Yes. Use DX commands and use SimHotasPinkyShift command. I recommend ditching the SST software to the extent possible. Almost completely unnecessary.
See my X52 Pro profile to use as an example. https://www.benchmarksims.org/forum/showthread.php?23661-Flounder-s-X52-Pro-Keyfile-DX-Profile-for-BMS-4-33
A_B, Your post made me remember something I read in the DX Facility manual…
Mapping the Shift Button
The callback name for the DX button that should act as shift button is: SimHotasPinkyShift When shifting is active, this callback replaces the former “SimPinkySwitch” callback. It still fulfills the same EXPAND functionality if it is only tapped and released. When it is pressed and held down, it acts as shift button. Obviously, it is meant to be mapped to the pinky switch on the HOTAS. In order to make shift work properly, the shift callback has to be mapped twice in the keyfile. Once for the pinky button, and once for the pinky button plus shift offset. Example: The pinky switch on the HOTAS uses DX button #3 and the configured shift offset is 256. Hence the keyfile needs to contain the following lines: SimHotasPinkyShift 2 -1 -2 0 0x0 0 SimHotasPinkyShift 258 -1 -2 0 0x0 0 Note: If the 2nd callback mapping is missing, the shift button can not be released correctly again once pressed.
I was wondering if anyone had done is on a Saitek x-65? -
I can´t understand all this comments about X52 and windows 10, the last beta drivers from Mad Catz for Windows 10, works fine without issues, the last are from 18/11/2015, and before since 18/09/2015, this shows us that the devs are involved and working, try out and not sink in a glass of water Falconeers!!!
-
I can´t understand all this comments about X52 and windows 10, the last beta drivers from Mad Catz for Windows 10, works fine without issues, the last are from 18/11/2015, and before since 18/09/2015, this shows us that the devs are involved and working, try out and not sink in a glass of water Falconeers!!!
Probably because those drivers doesn’t work correctly for many users?
I did a clean installation with new and old drivers, but actually I still have a relevant issue that I hadn’t when I had Windows 7 installed… -
To AMOP1970:
I had the same problem (windows 10 BMS 4.33), fighting since two or three days trying to fix the cursor problem.
I tried the solution from Saruman, but it didn’t work for the cursor problem.
Finally I download the latest version of driver and software from Saitek : ftp://ftp.saitek.com/pub/software/beta/Windows10/X52/
It still didn’t work properly for the cursorSo I decided to change the command in BMS 4.33 for the cursor.
Originally, it is a combination of shift and arrow.
I changed for a key F9,F10,F11,F12 : and no more problems with the cursor!!!Of course, it means I also changed in the Ministick command in the SST profile with bands, and F9 to F12.
I think the SST software do not work well with combiantion keys like Shift and arrows.
I hope it will help…
-
Here the video that shows my problem:
I hope somebody can help me to solve this issue! -
Revert back to Windows 7…problem cured
-
This stuff doesn’t work properly with windows 10 and Falcon BMS 4.33!!! It’ better to throw it to the TRASH!!!
There is little difference between beauty and trash, our brains make the picture how we see it
-
Here the video that shows my problem:
I hope somebody can help me to solve this issue!Like you mentioned before, that looks more like a hardware problem. What happens to the windows gamecontroller callibration when this occurs?
I used the X45 before but i totally skipped the SST software, edited the keyfile to map DX commands to the buttons. The cursor can be assigned to the throttle-mouse on the avionics tab in the setup/controller/advanced section. Never had any issues with the cursor……
Greetz,
Terminator -
A_B, Your post made me remember something I read in the DX Facility manual…
Mapping the Shift Button
The callback name for the DX button that should act as shift button is: SimHotasPinkyShift When shifting is active, this callback replaces the former “SimPinkySwitch” callback. It still fulfills the same EXPAND functionality if it is only tapped and released. When it is pressed and held down, it acts as shift button. Obviously, it is meant to be mapped to the pinky switch on the HOTAS. In order to make shift work properly, the shift callback has to be mapped twice in the keyfile. Once for the pinky button, and once for the pinky button plus shift offset. Example: The pinky switch on the HOTAS uses DX button #3 and the configured shift offset is 256. Hence the keyfile needs to contain the following lines: SimHotasPinkyShift 2 -1 -2 0 0x0 0 SimHotasPinkyShift 258 -1 -2 0 0x0 0 Note: If the 2nd callback mapping is missing, the shift button can not be released correctly again once pressed.
I was wondering if anyone had done is on a Saitek x-65?Yes. It works as intended with zero issues. I have nearly every input on the hotas mapped as shifted.
Cheers!
/Jaws
-
Here the video that shows my problem:
I hope somebody can help me to solve this issue!I´m using same drivers and have not the problem, looks like hardware problem, maybe some cable is bitten when you move the stick
-
I´m using same drivers and have not the problem, looks like hardware problem, maybe some cable is bitten when you move the stick
No, I don’t think so. When I had similar issues, I had the same kind of symptom (lights flashing/changing colors). When I reverted drivers and an older Teamspeak version, everything was fine. And has been since.
IMHO, it’s drivers or a conflict with another program …. or both.
https://www.benchmarksims.org/forum/showthread.php?23773-Saitek-X52PRO-radar-cursor-issues&p=343273
-
if you’re using TEAMSPEAK MAKE SURE at the HOTKEYS tab the right down bottom scroll menu selected"mouse and keyboard only"…SST software conflicts and causes pitch problems and other issues when teamspeak hotkeys are set to “default”…Hope this helps