Getting use out of those X52 extras (pic hvy)

OK - wish I hadn't made this post now as I have had hell loads of issues recently.
The B button only responds sometimes and I have an intermittent fault on the thruster buttons that regularly fail to respond when I am at max or min thrust.
Have mailed Saitek - we'll see what happens.

Warthog is no good as an alternative in my view because of the missing Z axis

Stick is being returned to Saitek today.
I have been looking around for a viable alternative as a spare but they all have big problems as far as I can see ...
X52 - known problems mainly with build quality causing faults
X55 - Same as X52 only worse according to reports
Warthog - no Z axis
Thrustmaster T-Flight - Not enough controls
Black Widow - See T-Flight

Are there any others ?
 
Last edited:
Thank you,
I don't know why my previously functioning setup stopped doing so on friday night. But after an entire weekend of faffing about - your post fixed it.

One golden joystick award for you!
 
All of my X52 woes ended just by keeping the control panel open on my desktop. Not had one problem since then and all my buttons/trigger/switches work all the time. It's just part of my "setting up for an ED session" routine.

That was basically what I did for the longest time, but I must admit the OP's suggestions does clean up the driver/profile considerably, allowing for some more button options.

I have one small issue though. I would like to use the mouse scroll wheel that is on the throttle (for radar sensor zoom), but it seems when I have the profile open (so the pinky trigger works correctly), the mouse wheel stops working. But when I close the profile, the mouse scroll wheel works, but then my pinky tends to get stuck a lot (I use hold button option for most things so it is quite annoying when it gets stuck).

Has anyone found a way to have both things working correctly without having the profile open all the time? Maybe some setting in the profile editor that I am missing? Would appreciate it.

EDIT: Think I fixed it. Just had to make sure the pinky didn't have 'Latched' ticked and was unprogrammed, and that I bound the scroll wheel to 'Button = Scroll Down / Up' on both of them. Seems to all work correctly now without having to have the Control Panel open!
 
Last edited:
Well I have more or less given up on my X52 after it went wrong, got replaced by Saitek, replacement turned out to be faulty and I am still awaiting a second replacement.
Just pray you don't have to deal with Saitek for after sales support !
 
I have an x52pro and I had problems setting up profiles (I WANT to use 3 diff profiles for combat, SC, docking/flying around stations), so I searched teh interwebs, and I finally found this:
https://www.reddit.com/r/hotas/comments/38hfq0/having_issues_programming_saitek_x52_pro/

The specific problem I had was that the game would not recognize my setup as keyboard keypresses. For example I would set the B button on the stick to key "B" (that is, when I pressed the B button on the stick, programs in windows should read that as if I pressed the B key on my keyboard). Notepad didn't read any button presses, nor any other program, including of course ED.
I followed the instructions on jakerake's comment, and finally got it to work! The only issue I had later was with the trigger which would become 'stuck' (it'd keep firing for no reason), but I realised it was because I had set it up as a keyboard key. I changed it to "unprogrammed" and that fixed it.
 
Last edited:
Calaban my friend,

After reading this thread I decided to open my wallet and buy the X52 (upgraded from the Thrustmaster Hotas X). In good time I decided to buy it!! It'a amazing, after doing what you did...:D My game is so much better now!!I can fly my Vulture so close to Pythons and 'Condas that some times I ram them:p . The 8 way hat on the thruster :eek: !! Now this is flying close!!!
I only find it bad that in order to reverse we have to press a botton and the it goes in to reverse mode!! I made a compromise.. 50% on the thruster is stopped, if I move it foword to zero it goes to 100% if I move it to 100% it goes reverse, so from 50% to 0% is forward motion, from 50% to 100% is reverse !! Took a bit of getting used to but it's not hard!! It's a on landings:eek: . Thank you for your help.
 
Last edited:
Hi PsYcHo4MuFfInS,

Do you mean the windows control panel?

I assume that you have installed the drivers for the stick?
 
oh, wow, this topic hasn't been moved to tech support yet?
(or um.. if I may presume: ) Or stickyed there yet?
 
Last edited:
Stick is being returned to Saitek today.
I have been looking around for a viable alternative as a spare but they all have big problems as far as I can see ...
X52 - known problems mainly with build quality causing faults
X55 - Same as X52 only worse according to reports
Warthog - no Z axis
Thrustmaster T-Flight - Not enough controls
Black Widow - See T-Flight

Are there any others ?


CH. They have been around for years and they are very reliable. People who use them swear by them.

http://www.amazon.com/CH-Products-200-571-Fighterstick-USB/dp/B00006B84X
 
Hello, im trying this setup thx a lot now all buttons appear to work, but it happened once 5 min ago while playing, my cloche start blinking and controls were not responding anymore... Had to reboot the computer for make it work again...
My sistem is Win 8.1 and I have same your software and drivers and an old first version X52.
 
I have an X52 (not PRO) and I have used your set up, thanks. All was well until a few weeks ago, now when I select Head Look using the E button the head Look goes to the bottom of the cockpit and cannot be moved with my POV hat 1 (it used to work, but now not). Pressing the E button again brings the Head Look back to the front. This is really annoying as I now cannot use Head Look. Any ideas?
 
Last edited:
Nice. Well done for that. The X52 is a good bit of kit.

Mine bloody isn't. It's a disaster of epic proportions.

The software is quite powerful though; if only it would actually run on my machine I'd bea bly to put up with the unstable deadzones, creaky wobble plastic parts and frequent disconnects. If only.
 
Mine bloody isn't. It's a disaster of epic proportions.

The software is quite powerful though; if only it would actually run on my machine I'd bea bly to put up with the unstable deadzones, creaky wobble plastic parts and frequent disconnects. If only.

I'm guessing you have a madcatz pos not a "real" saitek build (before they got bought out)
 
Always thought the pinky switch was the perfect button for shift states. Secondary fire is assigned to the C button (shift state chaff). Works nicely. That pinky button for shift state really negates the need for using different profiles at all.
 
Back
Top Bottom