Thanks. Did not know that. Good to know for replacement
Saitek X52 Pro
- Thread starter Piercetech
- Start date
If anyone with an X52 could help me out by filling in a reference sheet and sending me their custom binds file as per https://forums.frontier.co.uk/showthread.php?t=209273 it would be much appreciated.
I'm on my 4th x55 RMA, it went back last week. The next one I get I expect will either be faulty on arrival or develop a fault within 5 months. I would never buy Saitek/MadCatz again unless the community unanimously gave it mega feedback. Recent drivers are abysmal too.
Thanks for the suggestion i will take a look at this one.
I looked long and hard at CH when I replaced my X55 and when I read that the one time family oriented company had been bought by a large corp (06/2013) I got concerned. When I read that their products were no longer made in the U.S. by the people that had made the products that had received such praise for their durability, I got scared. When I then read that they no longer sold the parts for people to fix the products themselves (potentiometers, switches, etc.) and would only offer service for warranty repair, I said no way and moved on.
I guess us hotas gamers just aren't a big enough niche for a company to take serious anymore
Well, my X55 stick broke tonight - the twist / yaw element of it. Was in the middle on taking out an Anaconda in my FDL and "twang", then loose as anything. I got about 18 months use out of it, so it's not horrendous but I'd hoped it would last longer than that.
So, just before Xmas, great timing and even better with 2.0 coming out next week!
Anyway, I've decided to keep the throttle as it's still fine atm. Trouble is, there isn't much else that has the twist function and that's why I stumped for the X55.
Going to order a CH Combat Stick and the CH Pedals. Wife's going to kill me :-(
So, just before Xmas, great timing and even better with 2.0 coming out next week!
Anyway, I've decided to keep the throttle as it's still fine atm. Trouble is, there isn't much else that has the twist function and that's why I stumped for the X55.
Going to order a CH Combat Stick and the CH Pedals. Wife's going to kill me :-(
Last edited:
I have also just sent my X55 back for repair. All the buttons and rotaries on the throttle started to die one after the other. Had to assign bindings back to the keyboard.
I gave up a couple of weeks ago as it was a pain in the proverbial having to take hands off throttle all the time. Not played in a couple of weeks now...getting withdrawals
Its just over 12 months old, luckily had a 2 year warranty. In the mean time I purchased a used X52 Pro from Ebay that arrived Friday, not had the time to use yet.
Judging by this thread that was a wrong move.
Hopefully it will work until the X55 is returned. Fingers crossed.
I gave up a couple of weeks ago as it was a pain in the proverbial having to take hands off throttle all the time. Not played in a couple of weeks now...getting withdrawals
Its just over 12 months old, luckily had a 2 year warranty. In the mean time I purchased a used X52 Pro from Ebay that arrived Friday, not had the time to use yet.
Judging by this thread that was a wrong move.
Hopefully it will work until the X55 is returned. Fingers crossed.
If you are buying used, and get gear that was actually built by Saitek before MadCatz bought them, you'll do fine. MadCatz build quality and QA immediately tanked when they started making 'em. The more recent runs of kit have been more reliable but there's a LOT of the batches with truly dreadful build and QA still in the supply chain.
Those of us like me who say we've had our X5* for years without issues bought original Saitek kit.
Those of us like me who say we've had our X5* for years without issues bought original Saitek kit.
Saitek: I won't buy another after my experiences with the one I got for the IL-2 Sturmovik game years ago.
Thrustmaster t16000: I am about to order my second one. Bought the first when I got ED in April and I've been really happy with it. You may not think that 8 or 9 months is very long but that does represent 2,600 hours of game time - about 30 times the life of my old Saitek. All working fine except the primary fire trigger has started sticking a little and that is getting to be a liability in combat.
Thrustmaster t16000: I am about to order my second one. Bought the first when I got ED in April and I've been really happy with it. You may not think that 8 or 9 months is very long but that does represent 2,600 hours of game time - about 30 times the life of my old Saitek. All working fine except the primary fire trigger has started sticking a little and that is getting to be a liability in combat.
Last edited:
Because you do not need any joystick in something that it appears will never appear as a game perhaps. Or am I just a jaundiced Freelancer Dur, stuck in hangar for over a year going rusty, owner.
I have had my X52 Pro for about 4 years, when it was run by Saitek. and it works fine, since the upgrade to Windows 10 I have had driver issues for it, but use the BETA driver on the Saitek site and when you startup Windows at the login screen do a restart, it has to be a restart and windows will install the drivers correctly allowing it to work properly. but I emphasize it has to be a restart
Had to remove the detent on mine the other day, same reason, it got stuck. Wish I did it a long time ago though. Works/feels better without it. That seems to be the weakest point on the X52pro.
I got my x52 second hand it is five years old. Works great. I had the same issue. I learned my problem wasn't with the joystick but windows 8.1 turning off USB ports. All I had to do to fix it was install the program software. That forces windows 8.1 to keep the damn thing on.
I am sorry you wasted your money when the cause may have been that. Which is actually the main reason why they just turn off randomly. Saitek updated that profiler to force windows to keep it on to fix the issue.
Your stick may also have been legitimately broken, but my experience this year with my old beat up second hand saitek. I learned that issue was caused by windows not the controller.