Fix PMDG 737 rudder problems in MSFS 2024 with the right axis binding, conflict checks, assistance settings and hydraulic setup.
In the PMDG 737 for Microsoft Flight Simulator 2024, a dead rudder is usually caused by analogue pedals using button commands instead of Rudder Axis, a duplicate binding, the wrong device profile, automated assistance, or unpressurised hydraulics. Correct the axis, clear conflicts, disable assistance, and retest with normal hydraulic pressure available.
Fix the PMDG 737 rudder step by step
- Identify which control is failing. Watch the rudder surface in an external view while moving the pedals. If the rudder moves but the aircraft will not turn sharply during taxi, the problem is nose-wheel steering rather than the rudder.
- Check that the pedals produce an input. Open the MSFS 2024 Controls screen and select the pedal device. The on-screen axis indicator should move smoothly through its full range and return to centre. On PC, also test the device in Windows; our guide to checking and calibrating rudder pedals covers the hardware test and sensible dead-zone adjustment.
- Select the profile actually used by the 737. MSFS 2024 can load different profiles for each device and aircraft. Confirm that the active pedal profile contains your assignment rather than editing a profile that the PMDG 737 is not using.
- Assign the correct command. Bind the combined pedal movement to
Rudder Axis. Do not use Rudder Left and Rudder Right for analogue pedals, and do not substituteNose Wheel Steering Axis. Assign the two toe brakes separately to their left and right brake axes. If the response is backwards, use the axis reversal option rather than swapping unrelated commands. - Remove duplicate inputs. Search every connected yoke, joystick, throttle, gamepad and pedal profile for rudder assignments. Clear unwanted rudder axes from twist grips and controller sticks, especially if they are noisy near the centre. A mistake we see constantly is correcting the pedals while a second device continues to override them. Our MSFS 2024 rudder-pedal checklist explains how to isolate these conflicts.
- Turn off automated rudder assistance. Disable assistance options that steer the rudder or help with take-off control. These can oppose, limit or mask a physical axis. Leave them off while testing, even if you intend to restore them later.
- Pressurise the 737 hydraulics. For a reliable PMDG test, use an aircraft that is already running, or complete the normal hydraulic configuration. The flight-control switches should be in their normal positions, the pumps should be configured correctly and hydraulic pressure should be indicated. A cold-and-dark aircraft without pressure may accept the pedal input while the external rudder surface remains stationary.
Which control binding should PMDG 737 rudder pedals use?
Physical rudder pedals should use one continuous Rudder Axis assignment, with a neutral centre and proportional travel in both directions. Rudder Left and Rudder Right are digital commands intended for keys or buttons; assigning them to analogue pedals produces abrupt movement or no useful response.
Do not hide a broken assignment with a large dead zone. A small dead zone can suppress centre noise, but missing travel, spikes or a permanently offset centre point require calibration or removal of a conflicting axis.
What does each symptom mean?
| Symptom | Likely cause | What to check |
|---|---|---|
| No movement in the Controls screen | Hardware, connection or wrong profile | Test the pedals outside MSFS and select the correct device profile |
| Axis indicator moves, but the powered 737 rudder does not | Assistance, profile conflict or PMDG installation issue | Disable assistance, create a clean profile and update the aircraft through its supplied updater |
| Rudder jumps fully left or right | Digital commands or duplicate axis | Use Rudder Axis and clear assignments from other devices |
| Rudder moves in the wrong direction | Reversed axis | Enable the axis reversal setting |
| Rudder works, but taxi steering is weak | Pedals being mistaken for the tiller | Configure a separate nose-wheel steering control |
| It works with engines running but not cold and dark | No hydraulic pressure | Check flight-control switches, pumps and pressure indications |
Why does the rudder move but the 737 barely turn while taxiing?
The rudder and nose-wheel tiller are different controls. Rudder pedals provide only limited nose-wheel steering in a 737, while the tiller supplies the much larger steering angle needed for tight turns. The PMDG steering option and bindings must also agree; our PMDG 737 tiller troubleshooting explains the correct modes and axis setup.
If the external rudder deflects normally and the aircraft responds in flight, changing rudder sensitivity will not fix a wide taxi turn. Configure the tiller or dedicated nose-wheel steering axis instead.
What if only the PMDG 737 has the problem?
If the same profile operates another aircraft correctly, first test the PMDG 737 with engines running and normal hydraulics. That separates an aircraft-system state from a simulator-wide pedal fault. Then confirm that the installed PMDG package supports MSFS 2024 and has been updated using the updater supplied with the product.
Create a fresh 737-specific control profile before reinstalling the aircraft. If the existing profile appears corrupted or assignments return after being cleared, follow our procedure for resetting or clearing MSFS controller bindings. Reassign only the rudder and toe brakes, test them, and add the remaining controls afterwards.