SAITEK X52 - Still not working, Months later but still they cant figure it to change a hardware id in a preset

So here we are new patch, nothing changed,

We all know what the issue is, many of us even created tickets pointing out that the hardware id for some people is different depending on the age of their controller, its a simple fix, but microsoft seems to completely ignore any input we give them.

The Microsoft Xbox pass members like me cant change anything because of whatever reasons leaving us out in the cold.

PLEASE let try and get their attention here, PLEASE CHANGE OR DUPLICATE YOUR PRESETS FOR THE SAITEK X52 TO WORK WITH HARDWARE ID’s 0255…

3 Likes

Had similar problems with X52. I know this shouldn’t matter but as soon as I unplugged from a 2.0 USB port and plug into a 3.0 port everything started working fine for me. Not sure this will work for you but give it a try and see what happens.

mac

Thanks for the reply, but it has nothing to do with that, my saitek has a GUID 0255 and apparently they only created support for 075C guids

I have exactly the same problem. What I find strange is that they haven’t even logged it as a known issue despite the fact it has been identified, understood, described, a fix identified and demonstrated and tested as working (for those who have access to files Xbox Pass members don’t)… all the work has been done and its just being ignored. Extremely frustrating.

2 Likes

I associate myself with Cognitivism and Aphec, I do not consider it absolutely justifiable to ignore a problem already reported by users for some time. It should be noted that it has been a while since it was reported and nothing seems to be done to resolve the issue yet. If it’s a hassle to fix, let us fix it ourselves by giving you access to those xml files. I don’t understand this block, the reason then? If you do not want us simple users to solve the problem by putting our hand to the files, tell us what to do since there are few chosen ones that these files can access and why them yes and some not? I believe that if the thing does not go away and there is silence and they ignore the problem, I think I regretfully ask for a refund of the product.

I’ve put in another ticket although I’m not holding my breath.
The only other possibility I can think of is whether its possible to reflash the DeviceID/GUID. I lean towards thinking it probably isn’t as this would undermine the whole concept of unique identifiers. Also I shouldn’t have to.

As far as I know, I don’t think it is unlikely that it is possible to reflash DeviceID / GUID of saitek X52.
Unless you want to keep mfs2020 and buy a Saitek X52 100% compatible with the Saitek_X52_Flight_Control_System.xml file.
As for me I don’t think about buying another Saitek X52 if anything I change simulator.
N.B. Even if we manage to configure the buttons of the Joy manually, some buttons do not work, if you assign keys to 6, it does not work! You can’t give any assignments. Not because the joy is broken, it works great. And because the Saitek_X52_Flight_Control_System.xml file we are talking about was created and edited for the hardware version GUID = “9a117810-f09c-11e7-8002-444553540000” ProductID = “075C” and not the GUID = "745a17a0-74d3-11d0-b 00a0c90f57da “ProductID =” 0255 "

New update still doesnt work, WHO THE â– â– â– â–  watches these forums? Ticketting them does not seem to do ANYTHING

I’m using X-52 joystick and throttle quadrant with Logitech rudder pedes/brakes which work well. Is there a way to use the X-53 Hosta with the CH yoke… It would be nice to use the CH yoke with basic inputs and the Hosta for throttle, mixture and all the other assigned inputs for POV, etc… I would disable Hosta the joy stick flight controls in favor of the CH-yoke. Sure would be nice …john
Ps:
(1) If my x-52 Hosta is working, it’s not my fault - just dumb luck. I wish I could offer recommendations.
(2) I don’t understand the following quote below, and , if someone could direct me to information that could explain this to me, I would greatly appreciate it:
"And because the Saitek_X52_Flight_Control_System.xml file we are talking about was created and edited for the hardware version GUID = “9a117810-f09c-11e7-8002-444553540000” ProductID = “075C” and not the GUID = "745a17a0-74d3-11d0-b 00a0c90f57da “ProductID =” 0255 “”

Mr. JohnWNGrobx. To understand the problem you should follow the various discussions regarding the Saitek X52 on compatibility.
However, to come to your aid and to keep it short without you trying so hard and I hope now that the thing is clear to you, in the list of the various peripherals that they declare, we also read the full compatibility with the Saitek X52. It is not so! There are 2 different Hardware versions, one and the GUID = “9a117810-f09c-11e7-8002-444553540000” ProductID = “075C” and this version is fully compatible since the XML file created by the manufacturers and so if you haven’t had problems is not a matter of luck and because yours has this version. My Saitek X52, like that of many others, has the version GUID = “745a17a0-74d3-11d0-b 00a0c90f57da“ ProductID = ”0255” Therefore not compatible. Now is this easy to understand?
I repeat it is not about luck! It is a question of creating in a time that does not distract from other projects if you want to add the correct and compatible XML file for another version of the Saitek X52 in the simulator. Clear now?

Hi there! Did anyone managed to edit the *.xml files ?

I am trying to edit the xml file for my Thrustmaster T.Flight Stick X Joystick, to match the hardware id in my Control Panel, but nothing seems to work. The files are locked and cannot edit them (I tried taking ownership of the folder in multiple ways, even forced with diferent software, but it doesd not work)

Any hint ?
Thanks

MODERATOR EDIT:
Hello everyone
Newcomer.
I have been a private pilot for years and I have been doing simu since fs98.
I have never seen a simulator so beautiful but so poorly completed in terms of driving precision. My Saitek x52 pro is unreglable. It is perfectly configured under W10 (up to date) and perfectly recognized by the simu and all keys and axes are activated automatically. No matter the aircraft the steering derivative is barred in all directions the nose wheel deactivates hello to keep the runway axis at take-off or landing. The trims are untouchable or the plane takes the roller coaster trims direction non-existent or swerving to the right or left brief unreglable. Decreu tres decu. I have no problem with DCS XPLANE 11 FSX OR ELITE DANGEROUS. The copy is to be reviewed on this side the gentlemen the developers. I will not venture to buy addons for such an approximate simu. In 2 years can be. In the meantime XPLANE11 gives me all satisfactions.
Good flights to all

Bonjour a toutes et a tous
Nouveau venu.
Je suis pilote privé depuis des années et je fais de la simu depuis fs98.
Je n ai jamais vu un simulateur si beau mais si mal abouti en terme de precisions de pilotage. Mon Saitek x52 pro est inreglable.IL est parfaitement paramétré sous W10 (a jour)et parfaitement reconnu par le simu et toutes les touches et axes sont activées automatiquement. Peu importe l avion la derive de direction se barre dans tous les sens la roulette de nez se desactive bonjour pour garder l axe de piste au decollage ou atterissage.Les trims sont intouchables ou l avion prend les montagnes russes trims de direction inexistants ou embardée a droite ou a gauche bref inreglable. Décu tres décu. Je n ai aucun probleme avec DCS XPLANE 11 FSX OU ELITE DANGEROUS. La copie est a revoir de ce coté la messieurs les developpeurs. Je ne me risquerai pas a acheter des addons pour un simu aussi approximatif.Dans 2 ans peut etre. En attendant XPLANE11 me donne toutes satisfactions.
Bons vols a tous