Rudder pedals not working in your flight simulator? Fix USB detection, axis bindings, toe brakes, calibration, assists and Mac compatibility.
Rudder pedals usually stop working in a flight simulator because the computer cannot see the device, the analogue rudder axis is unassigned or duplicated, the wrong controller profile is active, or an assist is overriding input. Verify raw hardware movement first, then correct the rudder and toe-brake bindings and test a default aircraft.
This answer applies to flight simulators in general, including Microsoft Flight Simulator 2024 and 2020, FSX, Prepar3D and X-Plane. Their menus differ, but the troubleshooting order is the same: hardware detection, controller profile, axis assignment, calibration, assists and aircraft-specific behaviour.
How to fix rudder pedals that are not working
Start outside the simulator and change one thing at a time; sensitivity adjustments cannot repair an undetected device or an incorrect binding.
Check whether the computer detects the pedals. On Windows, open
joy.cpl, select the controller and inspect its test display while moving the rudder and pressing each toe brake. The axes should move smoothly through their ranges without disappearing, jumping or sticking.If nothing responds, reconnect the pedals before starting the simulator, try a direct USB port and temporarily remove unpowered hubs or extension leads. Pedals connected through a yoke, throttle or proprietary adaptor may appear under that parent controller rather than under their own name.
Select the correct device and profile. Many simulators keep separate presets for each controller, and some can load different assignments with another aircraft or control scheme. Confirm that you are editing the pedals or their parent controller, not the keyboard, joystick or an inactive preset.
Microsoft Flight Simulator users should also check the active filter and profile before assuming that a command is missing. Our MSFS 2024 and 2020 controller setup procedure covers device detection, profiles, dead zones and assistance settings.
Bind the analogue rudder axis. Search for Rudder Axis, Yaw Axis or the equivalent command, then move the pedals to identify the input. Do not use button-style commands such as rudder left and rudder right; those produce on-or-off movement rather than proportional control.
If the controls screen is unfamiliar, follow our explanation of binding the correct analogue rudder or yaw axis.
Remove duplicate yaw assignments. Inspect the joystick, twist grip, yoke, throttle, gamepad and keyboard profile as well as the pedals. A second rudder axis can fight the pedals even when that controller appears centred, particularly if its sensor jitters around neutral.
Assign toe brakes separately. A typical pedal set exposes three axes: rudder, left toe brake and right toe brake. Move one control at a time and bind each brake to its corresponding analogue brake axis.
Both brakes must read released when your feet are off them. If the aircraft remains braked at rest and releases when you press a pedal, reverse the affected brake axis. Do not bind analogue toe brakes only to a digital brakes command.
Verify every axis direction. Pressing the left pedal should command left rudder and yaw the nose left. Reverse or invert the rudder axis if it moves the wrong way, but check the two brake axes independently; it is common for the rudder direction to be correct while one or both brakes require reversal.
Calibrate before adjusting sensitivity. Confirm a stable centre and full travel in both directions. Use the manufacturer’s utility where one is required, otherwise use the operating system or simulator calibration facility. Owners of that hardware can follow our Windows calibration process for Saitek pedals and toe brakes.
Add only enough dead zone to suppress real centre jitter. A large dead zone makes taxi corrections vague, while reduced saturation or a large extremity dead zone can prevent full rudder travel. Avoid applying strong response curves in both driver software and the simulator.
Disable assists for the test. Turn off auto-rudder, assisted take-off, assisted landing and simplified steering while diagnosing the pedals. A yaw damper is an aircraft system rather than a controller assist, but it can oppose or smooth yaw and make pedal response less obvious.
Test a simple default aircraft. Use calm weather, no active failures and a basic trainer with conventional controls. Watch the simulator’s input indicator and rudder surface before judging the aircraft’s path; wind, engine torque, asymmetric thrust and braking can make it turn despite a correct rudder input.
Rudder pedals not working: symptoms and likely causes
The symptom usually identifies the failed layer faster than changing settings at random. “It’s not working” can mean no detected input, reversed movement, locked brakes or simply ineffective low-speed steering.
| Symptom | Likely cause | Check first |
|---|---|---|
| No response outside or inside the simulator | USB connection, parent controller, driver or hardware fault | Operating-system detection and a direct USB connection |
| Works in the operating system but not the simulator | Wrong profile, input filter or missing axis binding | Active device preset and analogue rudder assignment |
| Left pedal produces right rudder | Reversed rudder axis | Reverse or invert option |
| Aircraft will not accelerate or feels permanently braked | Reversed, crossed or partly applied toe-brake axes | Left and right brake input indicators |
| Rudder jitters or drifts near centre | Duplicate binding, noisy sensor, calibration or USB fault | Other controllers and raw centre position |
| Full pedal movement gives partial rudder | Incomplete calibration, reduced saturation or extremity dead zone | Raw range and axis tuning |
| Works in flight but not during taxi | Separate tiller, limited nosewheel steering or free-castoring wheel | Aircraft steering design and differential brakes |
| Fails in one aircraft only | Aircraft profile, custom steering logic or unavailable hydraulic power | A known-good default aircraft |
Why are my rudder pedals not working on Mac?
On Mac, rudder pedals fail when macOS or the simulator cannot receive their USB axes, or when a Windows-only simulator is being run through a layer that does not pass the controller through.
Open macOS System Information and inspect the USB hardware list. Seeing the pedal device there confirms that it has enumerated, but it does not prove that its axes are moving. In a native Mac simulator such as X-Plane, use the joystick calibration screen to test the yaw, left toe-brake and right toe-brake inputs directly.
- If X-Plane sees the axes: calibrate them, assign yaw and the two toe brakes, then verify their direction.
- If macOS lists the device but the simulator does not: check whether the pedals require a parent yoke, throttle, adaptor or manufacturer utility. Older hardware may rely on Windows-only configuration software.
- If macOS does not list the device: reconnect it, try another port or adaptor and remove hubs for the test. This is a connection or compatibility problem, not an aircraft setting.
- If using virtualisation, remote play or streaming: the session must explicitly pass through or forward the controller axes. A simulator cannot bind pedals that exist only on the host Mac.
Microsoft Flight Simulator 2020, Microsoft Flight Simulator 2024 and FSX do not have native macOS releases. Windows-specific instructions such as joy.cpl therefore apply only inside a Windows environment that has received the USB device correctly.
Why do the pedals work in flight but not while taxiing?
Working airborne rudder does not guarantee effective ground steering because the rudder, nosewheel, tiller and differential brakes can be separate controls.
A light trainer may link the pedals directly to the nosewheel. Larger aircraft often permit only a limited steering angle through the pedals and require a tiller for tight turns. Aircraft with a free-castoring nosewheel rely on differential braking, while some taildraggers use a steerable or lockable tailwheel.
Check the tiller or nosewheel-steering assignment, tailwheel lock, parking brake and both toe-brake indicators. At walking speed, the aerodynamic rudder may have too little airflow to turn the aircraft by itself.
What if the pedals fail in only one aircraft?
If the pedals work in a default trainer, the hardware and basic rudder binding are probably correct. The affected aircraft may use a different controller profile, custom tiller logic, a control lock, a simulated failure or steering that requires electrical or hydraulic power.
Test airborne rudder and ground steering separately. On a large aircraft, a stationary rudder surface may also require hydraulic pressure before it moves, so an external view with the aircraft unpowered is not always a valid pedal test.
Why does the rudder move but feel weak, erratic or too sensitive?
Once the axis responds, poor rudder feel is usually caused by calibration, response curves, duplicate inputs or normal aircraft systems rather than a missing assignment.
Begin with a nearly linear response. Use a small dead zone only if the raw centre jitters, and soften the curve around neutral if small pedal movements are too abrupt. If full physical travel does not produce full input, correct calibration, saturation or extremity-dead-zone settings instead of adding sensitivity.
Rudder authority also changes with airspeed and aircraft type. High-speed aircraft may limit rudder travel, and an active yaw damper may oppose sudden yaw. For a broader fault-isolation process, see our guide to diagnosing jitter, duplicate axes, calibration errors and USB faults.
What should I do if it is still not working?
If it is still not working after the normal checks, isolate the pedals with a clean profile and prove each layer separately before deleting any configuration files.
Save the existing bindings. Export them where the simulator supports it, or record the important assignments before resetting a profile.
Disconnect other controllers. Leave only the pedals or their required parent controller connected. This removes hidden joystick, gamepad and twist-grip conflicts.
Repeat the raw-input test. If the axes do not move smoothly outside the simulator, no in-simulator setting will fix the underlying USB, adaptor or hardware problem.
Create a clean controller preset. Bind only the rudder axis and, if fitted, the two toe-brake axes. Do not add curves, assists or secondary commands yet.
Load a default trainer. Verify the simulator’s input bars first, then rudder movement, then taxi behaviour. This separates controller input from aircraft-specific steering systems.
Try another USB port or computer if available. Failure on a second system strongly suggests a pedal, cable or parent-controller fault. Smooth axes on another system point back to the original simulator profile or software layer.
Reconnect other devices one at a time. Retest after each one. If the fault returns after reconnecting a joystick or gamepad, inspect that device for a duplicate rudder or brake binding.
The pedals are probably faulty if their raw axes spike while held still, never settle at centre, cannot reach one end after calibration, disconnect when the cable moves or fail on more than one computer. If all axes remain smooth outside the simulator, the cause is almost certainly a profile, binding, assist or aircraft-system setting.