Saitek X52 Pro - Can't bind some buttons in Windows 10 x64 (not clutch button)

[|Bot| ♥♠ - TJChagas - ♣♦]

Ok i've spent 2 days searching and trying different things to try to set up two important functions on my flighstick.
I use windows 10 x64, i've tried pretty much everything to tryu make it work properly but without sucess.
I want to bind that scroll behind the throtle to circle next and previous target subsystem (as i used to do in windows 8.1 x64), and the mouse 1 button (on the throtle too) to toggle flight assist, but i could not find a way to ED recognize those buttons.
In the stick configurations those buttons works great, no problem, but i can't set them on elite dangerous.
I've tried to bind a key to that buttons, but it doesn't work either, nor outside the game.
Someone please explain me the macro system of this flighstick, because i could not figure it out. For example, if i bind a button on the profile configuration to press a keyboard key or a set of keys, wasn't suposed when i press that button for it to type that combination of keys i set up? I have a k90 keyboard with bunch of macro keys, and i press to record, chosse the macro key, type the macro i want, then stop record, so every time i press that macro key it types what i just recorded. Shouldn't that suposed to be in X52 pro macro system?
All i wanted to do with macro was trying to set a simple key to those buttons, like, bind "Z" to the mouse 1 button, so everytime i press the mouse button on the flighstick it would type Z instead of mouse clicking (that would bind to toggle flight assist on ED), once ED doesn't recognize that click. This same way with that back scroll, all i wanted is this.

What i want is simple: the back scroll to circle subsystems, and mouse button to toggle flight assist, only this, nothing else. Everything else is working great.
This is driving me insane...

[Laurreth]

The scrollwheel along with the "mouse button" and the small stick in the back is pretty broken half the time, depending on phase of the moon. It works for some people, but nobody really knows why.

[SeeJay]

Regarding the SST software setup (Profile) for the scrollwheel, I set the scroll wheel to
3 Bands (I think it's called). The center one is used as "DeadZone" and the other 2 (Up/Down)
for 2 different toggles (Buttons). Works like a charm!

I have no idea why the game doesn't recognize it tho. Might work if you set the keys you want
in game and then use the profile created. If not, I guess it's a Win10 problem.

I use Win7/64bit.

[irishfast]

OP, did you ever get it to work? I just picked up an X52 Pro, and I also run windows 10 64 bit. I can get the stick to function, and bind buttons in-game, but the profile software doesn't work when the game starts. For example, I can't use the mode select wheel on the right side of the stick. My mouse also now jumps about an inch straight down from time to time - very annoying. This happens in games, too. Honestly, the stick is beautiful, but Saitek f'ed the software.

I haven't yet had the time to try older versions of the software and remove all Saitek drivers and reinstall. OP, have you tried that yet? That's my project for this weekend if I can't find a solution by then.

I should note that I'm not really interested in answers from people who don't have a solution. It's lovely if yours works, honestly, but it's more important if you know WHY it works and ours don't! Thanks!

[Turd Ferguson]

you have to use the madcatz keymapper to map buttons to keystrokes and then map those keystrokes in the game. DirectX doesn't support as many buttons as the X52 has so if you rely on DirectX to pass the button presses to the game not all buttons will register.

I ended up using the generic "joystick with keyboard" scheme in ED and mapped the keystrokes to buttons using the madcatz utility. If you use the X52 scheme, some buttons will not map. This isn't a limitation of the game, it's a limitation of DirectX.

[natpick]

agree would be great to get these buttons to work on elite but same as you guys i had no luck.not for the want of trying mind.

[Florelit]

Guys, just try to open windows settings - printers and scanners, then scroll down and look for "Devices and printers" link. After that you need to open it and right click the joystick. Select "Game controller settings" and in the next window double click your joystick. Youll see "Saitek x52 blablabla properties" window.
Keeping this particular window opened is fixing all the fucntions of you joystick.

BTW i'm not sure about profiles switcher.

Another problem with x52 is that it doesn't support some usb3.0 drivers. So in this case you'll need to either uninstall them or switch one option in your BIOS (dont remember the exact name but will look for it later)

[irishfast]

Ya know, I remembered seeing something about keeping the control panel open, and I just assumed it was the Saitek control panel, not the windows one... alright, let's add that the list of potential fixes! Thanks for correcting my memory on that, I couldn't find the post where I originally read that info, so I was just going with my best recollection. I'll give it a try later!

Originally posted by Florelit:

Guys, just try to open windows settings - printers and scanners, then scroll down and look for "Devices and printers" link. After that you need to open it and right click the joystick. Select "Game controller settings" and in the next window double click your joystick. Youll see "Saitek x52 blablabla properties" window.
Keeping this particular window opened is fixing all the fucntions of you joystick.

BTW i'm not sure about profiles switcher.

Another problem with x52 is that it doesn't support some usb3.0 drivers. So in this case you'll need to either uninstall them or switch one option in your BIOS (dont remember the exact name but will look for it later)

[Turd Ferguson]

also in Windows 10 disable eHCI in your bios. enable xHCI.

[CMDR.FREEZER]

I had difficulties with the pinkie button on the joystick of my X52. keeping the Windows settings of my stick open while playing enabled the pinkie button....just like that for some odd magical reasons :P

[Florelit]

It's because while the properties window is opened the joystick is kind of in "debug" mode... That's why pinkie button is working... I'm sure i'ts not the only way to fix it, but still it works )

[irishfast]

I looked at the Madcatz page briefly, but it seemed to me (based on a VERY quick read-through) like they weren't handling Saitek issues anymore, so I looked at other fixes first. If it worked for you, I'll give it a shot, too! Thank you!

Originally posted by Turd Ferguson:

you have to use the madcatz keymapper to map buttons to keystrokes and then map those keystrokes in the game. DirectX doesn't support as many buttons as the X52 has so if you rely on DirectX to pass the button presses to the game not all buttons will register.

I ended up using the generic "joystick with keyboard" scheme in ED and mapped the keystrokes to buttons using the madcatz utility. If you use the X52 scheme, some buttons will not map. This isn't a limitation of the game, it's a limitation of DirectX.

[Mu77ley]

Make sure you have clutch mode disabled in the controller.

[Turd Ferguson]

Originally posted by irishfast:

I looked at the Madcatz page briefly, but it seemed to me (based on a VERY quick read-through) like they weren't handling Saitek issues anymore, so I looked at other fixes first. If it worked for you, I'll give it a shot, too! Thank you!

Originally posted by Turd Ferguson:

you have to use the madcatz keymapper to map buttons to keystrokes and then map those keystrokes in the game. DirectX doesn't support as many buttons as the X52 has so if you rely on DirectX to pass the button presses to the game not all buttons will register.

I ended up using the generic "joystick with keyboard" scheme in ED and mapped the keystrokes to buttons using the madcatz utility. If you use the X52 scheme, some buttons will not map. This isn't a limitation of the game, it's a limitation of DirectX.

madcatz amd saitek has been purchased by Logotech. I think if you go to the saitek web site it will habe the software you need...when you install it theres a huge madcatz splash screen. hopefully logitech will tale better care of this product. were hoping for good thi gs from this purchase....maybe a redesign with better materials and a more practical x56

[Turd Ferguson]

Originally posted by Mu77ley:

Make sure you have clutch mode disabled in the controller.

yes. good point. disable clutch mode in the MS control panel. you can program your own clutch button through the madcatz application.