X-52 pro help please

I've been searching forums and google but haven't found anything related to my problem so I was hoping someone here might know. The Trigger button on my x-52 is constantly sticking causing whatever I put on 1 to constantly fire until I hit trigger again. I know its a hardware issue because if I press lightly at the very top of the trigger it can depress and not stick down. On the MFD it will show the trigger being pressed and staying down but it does not do this when I press further activating the secondary trigger.

I think my options are to:
  1. open up the x-52 can clean it which I don't really want to do because I don't know how / don't fully trust myself
  2. assign the main trigger to the secondary trigger turning it into a single stage instead of duel stage.

I'm not sure how to do either of these things and I'm sure I can look them up somewhere but before I do anything has anyone had a similar problem like this and are these the only ways to fix it?

(less than 2 months old by the way and kind of disappointed in saitek....)
 
I thought about that too but wasn't sure if its worth the hassle of not having my controller to play elite with if its just a simple fix. Thank you for replying :)
 
very good site but I seem to be getting a system 500 error every time I search for things relating to the trigger. Looking into reprogramming it myself through the programmer right now but I'm afraid I'm just going to have to send it back and have it replaced. Thanks for the help though!
 
I was having an issue earlier with trigger and other buttons sticking. I re-installed the drivers and it cleared up. Then I had an issue with random button presses. Turns out my USB extension I used was kinked and shorting. Since that was replaced I am a happy camper.
 
Call support. have a digital copy of your receipt, you will have to pay for shipping one way.
had to do that for my throttle, my primary fire button is now starting to not always work..
i still think the X52 is the best stick for the money but it would be nice if they figured out how to make them..
 
I've been searching forums and google but haven't found anything related to my problem so I was hoping someone here might know. The Trigger button on my x-52 is constantly sticking causing whatever I put on 1 to constantly fire until I hit trigger again. I know its a hardware issue because if I press lightly at the very top of the trigger it can depress and not stick down. On the MFD it will show the trigger being pressed and staying down but it does not do this when I press further activating the secondary trigger.

I think my options are to:
  1. open up the x-52 can clean it which I don't really want to do because I don't know how / don't fully trust myself
  2. assign the main trigger to the secondary trigger turning it into a single stage instead of duel stage.

I'm not sure how to do either of these things and I'm sure I can look them up somewhere but before I do anything has anyone had a similar problem like this and are these the only ways to fix it?

(less than 2 months old by the way and kind of disappointed in saitek....)

Set nothing to the trigger button, the first part (as it is a dual trigger)
Set fire to the 2nd part (I have) :)
 
so is this the feature of the dual stage trigger or is it an actual problem...im waiting to "pull the trigger" on either the x52 pro or the x55.

if there are quality control issues on x52 pro then , cause madcatz certainly doesnt have a great rep and they built the x55....

thoughts?
 
so is this the feature of the dual stage trigger or is it an actual problem...im waiting to "pull the trigger" on either the x52 pro or the x55.

if there are quality control issues on x52 pro then , cause madcatz certainly doesnt have a great rep and they built the x55....

thoughts?

My X52-pro trigger sticks a little, I have had it 10 years though ! They both have quality control issues on some of their joysticks. The 2 reasons I didn't get a Wartrhog was price and no twist, if that is not an issue then try it.
Though I have both the X52-pro and the X55, I use the X52 as I prefer the button layout, but then a friend of mine who had both prefers the X55 button layout.
Research before buying anything !!!
 
Set nothing to the trigger button, the first part (as it is a dual trigger)
Set fire to the 2nd part (I have) :)

Thats the simple fix I was trying to do but I'm having a little trouble with the programming. Did you do it in the profile editor? I really need to learn the program better so that I can custom map some things I would like.
 
My X52-pro trigger sticks a little, I have had it 10 years though ! They both have quality control issues on some of their joysticks. The 2 reasons I didn't get a Wartrhog was price and no twist,
Research before buying anything !!!

So the 52 has twist but the 55 does not? that is deal breaker for me.

i am not willing to get pedals for a stick that doesnt have twist.

edit* the 55 and 52 both have twist supposedly, im confusing the x55 with a warthog i think?
 
Last edited:
Thats the simple fix I was trying to do but I'm having a little trouble with the programming. Did you do it in the profile editor? I really need to learn the program better so that I can custom map some things I would like.

I don't use any of the software, I just assign the 2nd fire as my 1st fire button.
Go to the controller page in-game, find the main fire option, do not highlight it yet. First hold trigger in half way till you go past 1st fire trigger, with mouse highlight fire key bind, then squeeze trigger further.
 
or go to :
C:\USERS\user_name\appdata\local\Frontier Developments\Elite Dangerous\options\bindings (or similar)
and find the custom.binds file, look for Joy_1 and replace it with Joy_15

edit :
actually mine looks like this :

<PrimaryFire>
<Primary Device="SaitekX52Pro" Key="Joy_15">
<Modifier Device="SaitekX52Pro" Key="Joy_1" />
</Primary>
<Secondary Device="{NoDevice}" Key="" />
</PrimaryFire>
 
Last edited:
Are you using a USB hub of any sort? IE: plugged into a keyboard, etc...

If you are, it could be a power issue. It's generally recommended to use a powered hub if you're not plugging it directly into the PC.

Saitek's build quality and control software generally sucks. There are some issues with the X-52 they've known about for over 4 years and still failed to correct. Getting a good unit from them is a lottery, so if all else fails, you should just RMA it and hope the replacement wasn't built by a blind monkey missing most of it's fingers.
 
Last edited:
I don't use any of the software, I just assign the 2nd fire as my 1st fire button.
Go to the controller page in-game, find the main fire option, do not highlight it yet. First hold trigger in half way till you go past 1st fire trigger, with mouse highlight fire key bind, then squeeze trigger further.


This worked like a pro, took me 3 times to do it right but I'm not having an issue at all now. It still displays the trigger being depressed on the MFD but requires the second trigger to set off what ever is in fire 1. Thank you again, I would have never thought to change the setting in-game. It may be a quality issue I could send back for but I don't really have a need for a duel stage trigger in any of my games, especially a duel stage with no resistance before hitting stage two so I'm good with this fix.
 
Iv'e also been having a few issues with a new X52 Pro

1. The throttle low detent started giving problems, as expected from other threads here. Easy remove. Undo all the base screws (2 are hidden under foot rubbers) and then just prise out the rectangular thingy. Prefer it without
2. Whilst doing 1. I eased the wiring loom coming down from the throttle grip. I was finding that various button on the grip were 'misbehaving' occasionally. By tugging on the loom and routing it fractionally better I no longer find my mouse wandering over the screen dependant on throttle position
3. As with dognosh above I found problems with key assignments no longer binding properly. Copied and pasted a saved version of custom.binds to the folder mentioned and all is good again. Except a binding went missing this morning. Hmm. Wonder if thats anything to do with the massive memory lead only I seem to have

Item 3 is most appropriate to the OP problem - probably
 
Last edited:
Back
Top Bottom