Configure a Thrustmaster TWCS throttle and pedals in FlightGear with correct axis mappings, calibration, inversion and duplicate-input fixes.
Connect the Thrustmaster pedals either to the TWCS throttle or through their USB adaptor, then start FlightGear and assign the throttle, rudder and both toe-brake axes. Calibrate each axis, reverse any that moves backwards, add a small rudder dead zone, and remove duplicate yaw or throttle bindings.
Should the pedals connect through the TWCS or USB?
If your pedals have a Thrustmaster RJ12 lead, plug them into the pedal socket on the TWCS before launching FlightGear. They will then appear as additional axes belonging to the throttle rather than as a separate pedal device; that is normal.
Alternatively, connect compatible pedals through their USB adaptor. This is preferable when you want to use the pedals without the TWCS, need to diagnose the devices separately, or have spare USB ports. If the adaptor has a car/flight selector, set it to flight mode. Use one connection method only: never connect the pedals through RJ12 and USB at the same time.
Configure the TWCS axes in FlightGear
- Connect everything before starting FlightGear. Some builds handle hot-plugging inconsistently, so close and reopen the simulator after changing a USB or RJ12 connection.
- Check the controls at operating-system level. Open the available game-controller test or calibration panel and confirm that the throttle, rudder travel and two toe brakes produce four separate axis movements. Move each through its full range.
- Open FlightGear's joystick configuration. The exact menu wording varies between builds, but look for joystick or input-device configuration in the launcher or in-simulator menus. Select the TWCS and, if connected separately, the pedal device.
- Assign one physical control at a time. Select the desired FlightGear action and move only that control. Axis numbers vary by operating system and connection method, so copying another user's axis numbers is unreliable.
- Set direction and response. Reverse an axis only if its indicated movement is backwards. Use a small dead zone around the rudder centre, but keep the throttle response linear unless a particular aircraft requires something different.
- Save and test at low speed. Start with the parking brake released, verify the controls visually where possible, then perform a slow taxi before attempting take-off.
| Physical control | FlightGear assignment | Required behaviour |
|---|---|---|
| TWCS main lever | Throttle or all-engines throttle | Forward gives full power; rearward gives idle |
| Pedal sliding axis | Rudder | Centres when released |
| Left toe brake | Left brake | Zero when released; increases when pressed |
| Right toe brake | Right brake | Zero when released; increases when pressed |
| TWCS paddle | Unassigned when using pedals | Use for rudder only when no pedal axis is available |
Our axis-by-axis control assignment reference explains the difference between centred controls such as rudder and uncentred controls such as throttle and toe brakes.
Why do the throttle or pedals move backwards?
An axis is reversed when pushing the TWCS forward reduces power, pressing a toe brake releases it, or pressing the left pedal commands right rudder. Enable FlightGear's reverse or invert option for that axis, but do not reverse it in both the operating-system tool and FlightGear.
The rudder should settle near its centre without twitching. Add only enough dead zone to suppress sensor noise; a large dead zone makes taxi corrections abrupt. For more detailed pedal tuning, use our guide to rudder calibration, reversal and duplicate-yaw troubleshooting.
Why does the aircraft yaw or brake without input?
Uncommanded yaw usually means two controls are bound to rudder. Clear the rudder assignment from the TWCS paddle, a joystick twist axis or any other controller once the pedals are active. Also disable auto-coordination while checking independent pedal movement, because it can add rudder when the ailerons move.
Dragging brakes usually come from an inverted toe-brake axis, the wrong axis being selected, or FlightGear interpreting an uncentred brake as a centred control. With both feet off the pedals, left and right brake indications must be at zero. Check the parking brake separately.
What if FlightGear does not detect the TWCS or pedals?
- If the operating system cannot see the axes, reseat the RJ12 or USB connection, check the adaptor mode and recalibrate using the installed controller utility.
- If the operating system sees them but FlightGear does not, exit the simulator completely, reconnect the hardware and restart it.
- If pedals connected through the TWCS are absent as a separate device, inspect the TWCS axes before assuming they are missing.
- If one control moves several FlightGear functions, remove duplicate assignments rather than trying to hide the problem with sensitivity or dead-zone settings.
If the lever is detected but still has no effect on engine power, follow our FlightGear throttle input checks for conflicting bindings, keyboard overrides and aircraft-specific control behaviour.
Can one TWCS lever control every engine?
Yes. For twins and other multi-engine aircraft, assign the TWCS lever to the combined or all-engines throttle action where that option is available. Binding it only to engine one produces asymmetric thrust, which can look like a pedal or rudder fault during take-off.
A single TWCS lever cannot independently set different power on each engine without using additional axes, buttons or aircraft-specific control modes. For normal flying, the combined throttle assignment is the correct choice.