HOTAS recommendation?

[de Carabas]

Do you guys have any issues running X52 on Windows 10? I'm going to pick up one of these tonight, found one on Gumtree for £60 barely used, so bargain for me

I use the X52 on Win10 and I've got it to a place that's 'OK'. You might want a scant through the discussion here

[MrGuarnere]

Do you guys have any issues running X52 on Windows 10? I'm going to pick up one of these tonight, found one on Gumtree for £60 barely used, so bargain for me

I use the X52 on Win10 and I've got it to a place that's 'OK'. You might want a scant through the discussion here

Cheers and thanks everyone for your help. I found this official page by MadCatz talking about the drivers and followed the instructions and its working fine now, except for the lower trigger button (the one for you pinky) doesn't want to work. I keep enabling and disabling clutch mode for the controller and it works for a while but then stops.

Regardless, its an awesome HOTAS and it's made such a difference already flying my ship!

[de Carabas]

Cheers and thanks everyone for your help. I found this official page by MadCatz talking about the drivers and followed the instructions and its working fine now, except for the lower trigger button (the one for you pinky) doesn't want to work. I keep enabling and disabling clutch mode for the controller and it works for a while but then stops.

Regardless, its an awesome HOTAS and it's made such a difference already flying my ship!

Exactly my point about my setup being 'OK'. For me, that issue was sorted by having a profile for the X52 loaded that has all buttons set to 'unassigned' as per the instructions here. I then added back in button mappings for scroll wheel up/down to numpad 5/numpad 2 that I then use in game for cycling through target subsystems.

[MrGuarnere]

Exactly my point about my setup being 'OK'. For me, that issue was sorted by having a profile for the X52 loaded that has all buttons set to 'unassigned' as per the instructions here. I then added back in button mappings for scroll wheel up/down to numpad 5/numpad 2 that I then use in game for cycling through target subsystems.

Ye I found that thread also, gonna go through it tonight. That's my only annoyance with it right now so 1 out of the 32-odd buttons is not bad

I think I will keep Digga's recommendation to keep that pinky button as Target in Front as you dont want to accidentally hit boost when docking or sneaking around

Once I do the fix in that thread I hope the button will work as normal and all will be fine. Oh and I need to find some BlueTac to keep the bloddy sticks on the table, the suction pads come off after like 10 seconds which is quite annoying.

[de Carabas]

I think I will keep Digga's recommendation to keep that pinky button as Target in Front as you dont want to accidentally hit boost when docking or sneaking around

I've found that I've switched to using it as a 'shift' modifier to get even more controls on to the X52. It's definitely each to their own though when it comes to the set-up!

Once I do the fix in that thread I hope the button will work as normal and all will be fine. Oh and I need to find some BlueTac to keep the bloddy sticks on the table, the suction pads come off after like 10 seconds which is quite annoying.

There's a post somewhere where someone (can't remember who) showed how they had used nuts and bolts through the holes in the HOTAS bases to secure them to the desk. Might be something to look at. If I can find the post I'll add the link.

[MrGuarnere]

Thanks, though not sure I want to be drilling my desk just for this. I found some anti-slip mats on Amazon and I'm going to Tesco tonight so will have a look out for some.

I also have one of those antislip mats you put in the car and it's supposed to hold your phone, though it never stuck to my car so that's knocking about somewhere. I think the main joystick is fine with just the normal rubber, it has a big base so doesn't move. It's just the throttle, because of those 3 mid way points you get when accelerating (that bit of resistance) and Im trying to accelerate quick, the whole thing just lifts a little.

[JohnLuke]

Drivers
I had some issues with the Win7 drivers in windows 10 (mouse slowness and devices lock up when hotas unpluged)
The Win10 beta drivers seem to fix this and had no issues with my X52 Pro on Windows 10.

Software
The win10 beta software still comes with unsigned drivers (same as older versions) and this causes the same issues in Windows 10 as with previous windows versions.

Latest Win 10 drivers
Frontier forum post that lead me to the win10 beta drivers

Thanks for posting this, Digga.

I installed the beta drivers for Windows 10, and my X-52 Pro is (still) working fine. The advantage for me was that it resolved an issue in Device Manager with the Programmable Root Enumerator showing a driver error.

[Jeffers2112]

I didn't bother fitting the suckers, I just used 4 or 5 blobs of bluetack in the corners of the bases and that works fine.

[MrGuarnere]

Ye I'm gonna try that first, then if thats no good will get creative. Just need to figure out a "routine" of where to keep the sticks when I am just using the PC normally. They are not exactly compact

Though I do have a massive desk muahahahahah http://www.ikea.com/gb/en/catalog/products/50219044/

[Digga]

Drivers
I had some issues with the Win7 drivers in windows 10 (mouse slowness and devices lock up when hotas unpluged)
The Win10 beta drivers seem to fix this and had no issues with my X52 Pro on Windows 10.

Software
The win10 beta software still comes with unsigned drivers (same as older versions) and this causes the same issues in Windows 10 as with previous windows versions.

Latest Win 10 drivers
Frontier forum post that lead me to the win10 beta drivers

Thanks for posting this, Digga.

I installed the beta drivers for Windows 10, and my X-52 Pro is (still) working fine. The advantage for me was that it resolved an issue in Device Manager with the Programmable Root Enumerator showing a driver error.

The issue in Device Manager with the Programmable Root Enumerator showing a driver error was due to the unsigned drivers that come with the software, I thought this issue persisted with Win10 beta software but actually I just needed to uninstalled the old version first.

This is now working for me as well

So an update on my original comments about the software: It fixes the issue with unsigned drivers.