Problems with Steam recognising my X52 Professional HOTAS as a Xbox contoller. Help Needed.

Hello all. I'm having trouble with steam recognising my X52 professional HOTAS as a xbox controller. I've tried every solution on the internet including uninstalling my controller. I've tried contacting steam, and have heard nothing from them. Even the suggestions here on Steam don't seem to work. Even Logitech couldn't find a work around. I've been unable to play since the beginning of June 2022, and am still waiting from a arepoly from FDEV and STEAM, can anyone help please. TIA Cmdr Knightstslker299
 
not sure I fully understand the question when you say its not recognizing it as an xbox controller so I can only say that's because it is not an x box controller obviously
its an x52 but of course you knew that already so something is getting lost in translation there
after reading my binding guide on how to rename your binding file and back it up (ie your controls file)
I suggest you use one of the x52 profiles you can download here as a start which will also generate a handy reference image https://edrefcard.info/
other than that the device should work as long as windows see's it first in control panel options devices and printers and can be tested there and possibly controller settings in steam big picture mode disabled pending config just rem if windows don't see it the game def wont)
 
Last edited:
yea like I say that may be to do with controler settings in steam big pic mode for now maybe try with that disabled
good luck fa now happy trails
 
Saw this one a while ago and tried doing thtis, unfortunately it still does not show up. Here's what I get.
 

Attachments

  • controller.PNG
    controller.PNG
    814.2 KB · Views: 125
hmm you should get an option in there for an x 52 or at least a controller of some type ie x box pad for eg
lets try to figure whats going on here am I correct in saying you have picked a downloadable x 52 binding file and it is in the correct location do that first and possibly rename it as mentioned in the binding guide
other than that you could try grabing the binding folder put it on your desktop for now so its no longer in the correct directory
restart the game and then see what is available in the controller presets after a effective reset
before hand run the game though a file checker in the launcher options or on steam
(else rinse and repeat with anti virus disabled)
 
Last edited:
Bro, i'm back in the cockpit. Your are Awesome. Looks like playing around with the bindins file in conjunction with a new generic pad jump started it. Thank you so much for all the time you put in. o7
 
np got there in the end, you have too many bind files in there btw store any back up bind files elsewhere as mentioned in the guide
not in the frontier folders as can be problematic
other than your current bindfile as determined by what your startpreset.start file reads
and of course in the future you must launch with all current devices x box pad inc plugged in if you forget dont visit the controls section just quit plug in and restart
and all will be good. (the profile you selected also had an x box or generic type pad connected so is a part of your config or is bound in some way in bindings and therefore the game wont work correctly without it I am presuming your original file was also setup whilst the x box pad was plugged in hence that too would also require all devices present(plugged in) to work correctly)
so I am sorry to say all you had to do since june was plug your controller in also it seems, and on top of that it was trying to tell you so...…..
lessons learned and:poop:happens
 
Last edited:
Back
Top Bottom