Fix FS2004 toe brakes by checking Windows calibration, assigning both brake axes, removing duplicate bindings and reversing incorrect inputs.
In FS2004, toe brakes usually fail because the pedal axes are uncalibrated, assigned to the wrong commands, duplicated on another controller or reversed. Confirm both toe-brake axes in Windows, then assign them separately to FS2004's left and right brake-axis controls, delete competing assignments and reverse any axis that responds backwards.
How do I assign toe brakes in FS2004?
Assign each pedal to its own normal-flight brake axis; do not bind toe brakes to the momentary Brakes button command.
- Check the pedals in Windows. Run
joy.cpl, select the pedal set and open its properties. Press each toe brake slowly. Windows should display two independent brake axes, plus a separate rudder axis. The axis names may be generic rather than labelled left and right. - Open FS2004's axis assignments. Go to
Options > Controls > Assignments, select the pedal device and use the joystick-axis section. If normal and slew assignments are separated, choose the normal-flight axes. - Remove incorrect automatic assignments. Delete any rudder, throttle, aileron or brake assignment that FS2004 has attached to the wrong pedal axis. Check every connected controller, because a joystick or throttle can also carry an unwanted brake binding.
- Assign each brake separately. Map the left pedal to the left brake-axis command and the right pedal to the right brake-axis command. Keep the rudder centred while detecting each toe axis so FS2004 does not capture the main rudder movement instead.
- Set a sensible calibration baseline. Start with high sensitivity and a small null zone for both brake axes. Increase the null zone only if the brakes flicker or drag while the pedals are released. Our FS2004 controller calibration and axis-assignment walkthrough covers these settings in more detail.
- Test with a default aircraft. Release the parking brake, taxi slowly and press one toe at a time. The left brake should slow the left wheel and encourage a left turn; the right brake should do the opposite.
A moving cockpit pedal animation is not proof that the brake axis works, and some aircraft do not animate toe movement accurately. Judge the result by the aircraft's behaviour.
Why are the brakes stuck on or reversed?
Brake pressure at rest means the relevant axis is reversed, miscalibrated or receiving a duplicate input.
- Reverse the affected axis: Use FS2004's reverse option for each brake independently. Many pedal sets report maximum axis value when released, which FS2004 can interpret as full braking until reversed.
- Recalibrate in Windows: Confirm that each axis travels cleanly from one end to the other and returns consistently to its released position.
- Separate the parking brake: Release the parking brake with its own command before assessing the toe brakes. A parking-brake indication is not fixed by reversing the toe axes.
- Remove duplicate bindings: If moving the yoke, throttle or rudder changes brake pressure, another controller axis has been mapped to a brake command. Use our diagnosis for brakes triggered by other flight controls to isolate the competing input.
If an external controller utility or FSUIPC is assigning the brakes, choose one assignment method. Mapping the same axis both there and inside FS2004 can produce dragging, oscillating or apparently reversed brakes.
Why does only one toe brake work?
One working toe brake nearly always means Windows exposes only one axis, both pedals share one assignment, or one side is calibrated outside its usable range.
Return to joy.cpl and verify that each pedal moves a different indicator. Then check the FS2004 assignment screen and confirm that the detected axis names differ. A common mistake is pressing both pedals or twisting the rudder while creating the assignment, causing both brake commands to capture the same axis.
Some pedal software offers combined and separate brake modes. FS2004 needs separate left and right axes for differential braking. If Windows shows only one combined brake axis, switch the pedal software to separate or split axes before assigning the controls.
What if FS2004 cannot detect the pedals?
FS2004 cannot use a pedal axis that Windows does not expose as a game-controller input.
- Close FS2004, connect the pedals directly to the computer where practical, and confirm that they appear in
joy.cpl. - Calibrate them through Windows or the manufacturer's control panel where that option is provided.
- Restart FS2004 after connecting or recalibrating the hardware, then select the correct device in the assignment screen.
- Temporarily disconnect unnecessary controllers if the assignment list is confusing, then add them back after the pedals work.
If the pedals are missing, frozen or erratic in Windows as well, the problem lies outside FS2004. Follow our rudder-pedal and toe-brake detection checklist to distinguish calibration, USB, driver and hardware faults.
When keyboard braking works in a default aircraft but the toe brakes do not, the aircraft's brake system is functioning; concentrate on axis detection, reversal and duplicate assignments. If both keyboard and pedal braking fail only in one add-on aircraft, test a default aircraft before changing the controller configuration.