Set up and map the Turtle Beach VelocityOne Flightstick in MSFS 2024 on PC, with correct axes, sensitivity settings and missing-input fixes.
To set up the Turtle Beach VelocityOne Flightstick in Microsoft Flight Simulator 2024 on PC, put the stick in PC mode, update its firmware, verify every axis in Windows, then create a custom MSFS 2024 control preset. Bind analogue axis commands, remove duplicate assignments, tune dead zones, and save the preset.
Set up the VelocityOne Flightstick on PC
A clean setup starts with Windows detecting the Flightstick correctly before Microsoft Flight Simulator 2024 opens.
- Connect the Flightstick directly. Plug it into a PC USB port rather than an unpowered hub. Disconnect other sticks or gamepads temporarily if you want to make input identification easier.
- Select PC input mode. Use the Flightstick's on-device mode control to select PC mode. If it remains in its console-oriented mode, Windows or MSFS may treat it as a generic gamepad.
- Update its firmware. Open the supported Turtle Beach control software and install any offered firmware update. Restart the device and MSFS afterwards, because an update can cause Windows to re-enumerate the controller.
- Check the raw inputs in Windows. Press
Win + R, enterjoy.cpl, select the Flightstick and open its properties. Move the stick, twist grip and levers through their full travel. Use Windows mainly as a diagnostic tool; if the centre or endpoints are wrong, follow the device's supported calibration process before compensating inside the simulator. Our raw-axis and calibration checks for MSFS 2024 cover this in more detail. - Open the MSFS 2024 Controls screen. Select the VelocityOne Flightstick device tile rather than Keyboard, Mouse or Gamepad. Make sure you are editing aircraft controls, not only camera or general controls.
- Create a custom preset. Duplicate the supplied preset if one is available, or create a new profile. Give it an identifiable name and confirm that it is the active preset. The profile, input-scanning and save procedure explains the revised MSFS 2024 binding workflow.
- Map and test the main axes. Assign one control at a time, apply the changes, then test in a simple aircraft on the ground. Watch the cockpit yoke, pedals and throttle to confirm direction and full travel.
Which VelocityOne controls should I map?
The essential assignments are the aileron, elevator, rudder and throttle axes; everything else can be arranged around the aircraft you fly.
| Flightstick input | MSFS 2024 command | Mapping advice |
|---|---|---|
| Stick left and right | Ailerons Axis | Use the analogue axis command, not Aileron Left and Aileron Right. |
| Stick forward and back | Elevator Axis | Pulling back should command nose-up elevator. Reverse the axis if it operates backwards. |
| Twist grip | Rudder Axis | Clear digital Rudder Left and Rudder Right assignments from the same input. |
| Main throttle lever | Throttle Axis or Throttle Axis 0 to 100% | The 0 to 100% form suits a lever without a dedicated reverse range. Put reverse thrust on a button if needed. |
| Two throttle levers | Throttle 1 Axis and Throttle 2 Axis | Use these for independent twin-engine control. Do not bind the same levers to both combined and per-engine throttle commands. |
| Second analogue lever | Propeller Axis, Mixture Axis or Spoilers Axis | Choose according to the aircraft and store the assignment in an aircraft-specific preset. |
| Hat switch | Cockpit look or pan directions | Keep these as directional button commands rather than axes. |
| Buttons and triggers | Trim, brakes, flaps, gear or reverse thrust | After assigning each button, search by input and remove any unwanted default action. |
A common mistake is binding a physical axis to a pair of digital commands. That makes the control jump towards full deflection instead of moving progressively. Clear the assignment and bind the command whose name explicitly contains Axis.
Some complex aircraft also provide throttle calibration through their cockpit tablet or electronic flight bag. Complete the basic MSFS mapping first, then calibrate detents inside that aircraft if its documentation requires it.
What sensitivity and dead-zone settings should I use?
Use a nearly linear curve with the smallest dead zone that gives a stable centred input.
- Aileron and elevator: start with a linear response and a dead zone around 1 to 3% if the raw input is steady. Add a modest negative sensitivity curve only if the aircraft feels too sharp around the centre.
- Twist rudder: use enough dead zone to stop unintended yaw, typically a little more than pitch and roll. A gentle centre curve can make taxiing less abrupt.
- Throttle: keep the response linear with little or no dead zone. Change the extremity setting only after confirming that the physical lever cannot reach idle or full power after calibration.
There is no single ideal curve for every aircraft. A light aerobatic aircraft, an airliner and a helicopter need different control feel, so duplicate the preset before making large sensitivity changes.
Why is the Flightstick detected but not working properly?
If Windows sees the Flightstick but MSFS does not respond correctly, the cause is usually the active profile, an incorrect command type or a second device sending the same input.
| Symptom | Likely fix |
|---|---|
| The Flightstick is absent from MSFS | Close the simulator, reconnect the stick in PC mode, try a direct USB port and confirm that it appears in joy.cpl. If Windows cannot see it, the fault is outside MSFS. |
| The device appears as a gamepad or produces duplicate movement | Recheck its input mode. On the Steam edition, disable Steam Input for MSFS only if it is creating an emulated controller or duplicate commands. Close other remapping software while testing. |
| An axis moves straight to full deflection | Remove the digital left, right, up or down commands and assign the corresponding analogue axis. |
| An axis works backwards | Use the MSFS reverse-axis option rather than remapping the physical direction. |
| The throttle cannot reach idle or full power | Check its complete travel in Windows, select the correct throttle-axis variant and remove conflicting combined or per-engine assignments. |
| One button activates two functions | Search by that physical input and clear the unwanted binding from the Flightstick, gamepad or another connected controller. |
| The profile works in menus but not in the aircraft | Confirm that the custom preset is active in the aircraft-control scope, apply the changes and check whether that aircraft has its own profile or calibration page. |
Autopilot, assisted rudder and other piloting assistance can also mask correct hardware input. Test with the autopilot disconnected and relevant control assists disabled before changing the bindings again.
Can I use separate pedals or a throttle with the Flightstick?
Yes. MSFS 2024 can use the VelocityOne Flightstick alongside separate pedals, a throttle quadrant or other USB controllers.
Give each device its own custom profile and remove overlapping axes. For example, when pedals provide rudder input, clear the Flightstick twist assignment rather than leaving both rudder axes active. The same rule applies when replacing its built-in lever with a separate throttle; our multi-device HOTAS setup method explains how to keep those profiles and conflicts under control.