Hardware & Technical X52 Pro: Trigger (fire button) does not work in game.

DukeIronHand

D
Have a practically brand new X52 Pro that has been boxed up for years that I couldn't use after I got my new computer - with Intel USB 3.0 which problem everyone is familiar with.

Well, using the instructions found here I got the W10 X52 Pro beta drivers installed (finally) but with one slight issue: the trigger/fire button does not work in the game.

I can select it, and use it in the control configuration in the ED control menu but it just doesn't work in the game itself.

As far as I know the other buttons are working - at least the ones useable while docked that I can test.

Any ideas?
 

Asp Explorer

Asp Explorer
Maybe try backing up your bindings file, selecting the X52 Default in Elite, and see if it works there - then rebinding to your preference.
 

DukeIronHand

D
This stick has been a PITA ever since I got it. And I am not entirely sure where the fault lies: The clunky nature of setting the stick up or too many buttons and I just haven't put the time into figuring it out.

Ready to take a hammer to it and get the T16000M HOTAS. Been using the T16000M for a long while now. Maybe I am just used to it.
 

Gimi

Gimi
Before you take a hammer to it.
A few things that you probably know about, but better double check just in case.
-Move/rename binding files and start game with fresh ones using default settings.
-Check that the button is responding in the Saitek control panel.
-Check that you don't have any odd assignments in Saitek Profile Editor. In fact, remove all profiles.
-For the default profile make sure that the "clutch" tick box in the control panel is unticked (to make boost button work)
-Latest drivers are out of beta. They are available here if you haven't tried them: http://saitek.com/uk/down/drivers.php
-Finally, make sure that you have assigned your weapons and modules in fire groups in the right panel in game.

If all this is done and ok, then I don't know.
 

DukeIronHand

D
Okay just got the new drivers and software from the link you gave.

Since the stick is (apparently) mostly working do you think I can just overwrite the beta drivers with the new ones?
Or should I uninstall everything Saitek and start from scratch?

Just your best SWAG if you will.
 
Last edited:

Gimi

Gimi
DukeIronHand said:
Okay just got the new drivers and software from the link you gave.

Since the stick is (apparently) mostly working do you think I can just overwrite the beta drivers with the new ones?
Or should I uninstall everything Saitek and start from scratch?

Just your best SWAG if you will.
Click to expand...

I just installed over the old drivers, but then again I never had any problems with getting mine to work (problems that weren't my own fault that is) . To be on the safe side I would uninstall all and do a clean install.

Out of curiosity, have you managed to check if the fire trigger works in the Saitek control panel or if the stick shows up in the Windows devices and printers (Control Panel-All Control Panel Items-Devices and Printers).

You did mention that you ware able to assign the fire trigger when setting up the stick in the game, so my suspicion is something to do with your fire groups.
And one more thing, the main fire trigger has a double trigger function. Push it inn half way for fire / all the way inn for auto fire type of thing. Normally not used for ED, but could this be the culprit?
Just brainstorming now.
 

DukeIronHand

D
I was not overly specific in my description.
I was not able to see if it worked for weapons (not that I have any) while docked.

The exact issue was the menus.
When in dock you use the main fire button to select a highlighted choice in the menus. This was not working.
All other X52 buttons (useable for features while docked) appeared fine.

However when in the ED controller set-up screen in Options it recognized it there when I used the "click" the main trigger to assign it as the fire button. It was already there when using FD's X52 profile it just wouldn't work in the menus. Of course I tried to assign it again (and apparently successful) it just doesn't work in the menus.

Not remembering the clean-out of Saitek stuff with any fond memories (with the old drivers) I will try to "install over" first to see if that works. If not I'll clean out and start from scratch.

Thanks again!

EDIT: Yes the stick appeared fine to Windows (finally after two years!) but I did not have the Saitek helper software installed. Tried just the drivers the first time since ED had a X52 profile in-game.

Additional EDIT: Just noticed your "brainstorm" and I was wondering why sometimes when I clicked it in the ED controller assignment page it would show twice -a graphic for two triggers. I was not aware (or forgot) of the "duel trigger" function so now I am not sure if I was actually doing it right in the game!
Hmmm...you may have "stormed" your way into the issue! More research needed.
Thanks again!
 
Last edited:

Gimi

Gimi
DukeIronHand said:
I was not overly specific in my description.
I was not able to see if it worked for weapons (not that I have any) while docked.

The exact issue was the menus.
When in dock you use the main fire button to select a highlighted choice in the menus. This was not working.
Click to expand...
No you don't.
Unless you have changed it, to select in the menus you by default use the (B) button on the stick, (Space) on the keyboard.
 

DukeIronHand

D
For me it is the fire button on my (current) T16000M. This is the default ED setting on, I think, the generic Joystick profile. I have added to it of course but did not change this.

Obviously I did not change it (or even look) on the X52 profile assuming that the fire button was the standard default for menu selection.

With that said I tried all buttons (even the B unless I am having an Alzheimers attack) on the X52 and nothing seemed to work.

Now I am not sure of anything anymore and perhaps I am just being stupid. Will check later again today. Thanks.

EDIT: Since I am being a pest here is there a clear print out or graphic of the ED's X52 button assignments somewhere?

EDIT #2: okay I found at least 2 versions, maybe 3, of the "official" template. Perhaps it has changed over time? Anyway got them all and I'll see which one is current.
 
Last edited:

DukeIronHand

D
Not entirely...in the game anyway.

Works fine in the X52 control panel so I suspect the fault will be with me not knowing what the heck I was doing. Have not had a real chance to test in game. Wanted to finish a CG (Fed exploration one) yesterday and figured it was a bad time to be stick testing. However when I was done...

Got the new drivers loaded up and the stick hooked up. Printed out the (reportedly) default button assignments and even printed off some blank templates. Took my ship and parked it in deep space for testing.

To sum up I am ready to rock later today.
Thanks again for your assistance!
 

DukeIronHand

D
Well Gimi you were absolutely correct.
"B" is now the select.
Just fired up ED with the X52 to check out the key configs, etc.

One thing I have noticed (and IIRC this is an old issue) the buttons on the throttle are not illuminated. Nor was the MFD panel till I went to the Windows Game Controller and turned it down then back up. Buttons are still out though...weird.
And they were fine yesterday. Oh well something to figure out.
 

Gimi

Gimi
DukeIronHand said:
One thing I have noticed (and IIRC this is an old issue) the buttons on the throttle are not illuminated. Nor was the MFD panel till I went to the Windows Game Controller and turned it down then back up. Buttons are still out though...weird.
And they were fine yesterday. Oh well something to figure out.
Click to expand...

This is a known issue and I have yet to find a good solution, and I have looked long and hard. On my system, if I do a reboot right after the initial boot all the lights come on.
Some say that it's a power saving issue in windows. As in Windows is trying to save power going out through the USB port. A powered USB HUB supposedly solves it for some, but I haven't tried that myself.
Another issue I have had is that the stick does not play well at all with USB 3 ports.

Now my x52pro is broken (detents in throttle and the spring that centres the joystick twist broke), I got a refund as the reseller has stopped selling them. I have ordered the new t.16000m HOTAS FCS. Will see how that goes.

While the x52pro is an excellent stick with great feel and functionality, I have had too many quality issues with it and I'm not risking buying another one. I hope you have better luck.
 

DukeIronHand

D
So far so good.
This is an "older" stick when quality was somewhat better (according to the always correct internet) and it seems fine so far but when this give up the ghost I will be joining you on the T16000M HOTAS. Since it sounds like it's release has been delayed that gives me some time with the X52.

After I was all done in ED, in a empty system setting the stick up, I collected my CG money, exited, and went to the Game Controller again. Turned the brightness up and down and the throttle button lights came on - we will see next boot up.

Now it's just a question of getting used to the new stick and settings. I had months on the T16000M so I defintely took my first landing very carefully!

The default profile (which I modified pretty heavily except the various hat(s)) seems combat oriented which, in this career, I have gotten away from. So I will put some final touches on it next boot-up - mainly swapping the thrust control hat for the targeting hat. Besides that, and a better "center TrackIR" button and I'll be good.
Thanks again for the assist.
 
You must log in or register to reply here.
Back
Top Bottom