I finally managed to fix the Y-axis

Sim Update 5 Beta | MSFS 2024 Hardware
, ,
1

I finally managed to fix the Y-axis deadzone/calibration issue caused by Sim Update 5 without waiting for the SPAD.neXt patch. Here is the step-by-step:

  1. Unplug your X52.

  2. Press Windows + R, type regedit and hit Enter.

  3. Navigate to: HKEY_CURRENT_USER \ System \ CurrentControlSet \ Control \ MediaProperties \ PrivateProperties \ DirectInput

  4. Look for folders starting with VID_06A3 (Saitek/Logitech vendor ID).

  5. Delete those folders (Right-click > Delete). Don’t worry, Windows will recreate them cleanly.

  6. Plug your X52 back in and perform 4 full movements on every axis to recalibrate.

1 Like
4

There’s no need to “roll back,” as Windows automatically resets everything when you plug it in.

The only thing it loses is its Windows calibration (the little red bars in the Windows Control Panel), but since that’s precisely what was off, it’s a good idea to reset it!

1 Like
5

Subject: Fix for Saitek X52 Pro Y-Axis issues after MSFS 2024 Update

Hi everyone,

If you are experiencing calibration issues or “jitter” on your X52 Pro Y-axis following the latest Microsoft Flight Simulator 2024 update, you don’t have to wait for the official patch to start flying again.

I’ve discovered a manual registry fix that solves this issue immediately. I want to reassure you: this is completely safe for your system. It’s a straightforward tweak that simply resets how the sim and Windows interpret the joystick’s calibration data.

Why you shouldn’t worry:

  1. It is 100% reversible: Windows will automatically regenerate default keys if needed.

  2. It only affects the joystick’s calibration settings—nothing else on your PC is touched.

  3. It allows you to fly with perfect precision right now.

Feel free to follow my steps (see my previous post) and get back to the cockpit today!

Blue skies, Revil2000

1 Like
6
1 Like
7

Axe is a bug in the SU5 update

8

If deleting that system registry key fixed the issue, it would suggest the problem was in Windows rather than in MSFS.
You also mentioned SPAD.neXt and said you fixed the Y-axis deadzone/calibration issue without waiting for the SPAD.neXt patch. That actually suggests the problem isn’t directly in MSFS either. As I mentioned before, it points more toward something in Windows or possibly SPAD.neXt itself.

FYI, I’m using SPAD.neXt as well (version 0.9.24.19) and I don’t have any issues with the axes.

9

If you don’t have this bug, good for you, but the bug comes from the latest MSFS24 update which caused a Y-axis malfunction on my X52 Pro that I didn’t have before. Don’t assume that just because you don’t have the problem, others haven’t either.

10

I never said there’s no bug. I was simply pointing out the external factors you yourself mentioned, like SPAD.neXt and Windows registry, that could be influencing the issue.
I mentioned that I don’t have this problem not to brag, but so that the person gathering feedback from us to relay to the dev team knows it’s not a global issue.
You reported a bug, and that’s fine. I’m not looking to discuss it further.

11

If you leave the SU5 beta does the problem persist?

12

I really don’t know

13 
spad has apparently fixed the problem, only a few months ago, beta version for now
Spad has apparently fixed the problem, but only in the beta version for now.
14

I would try leaving the beta before a reg edit. If the problem persists after you leave then maybe.

15 
Modifying the registry does not damage anything.

Modifying the registry does not damage anything.

16

Have a good day

17

Never said it did, just seems like it could be a beta issue that will be resolved before the release

18

Sure, but in the meantime my X52 was doing very badly, impossible to fly.