Skip to content
Microsoft Flight Simulator 11 min read 413 views

Can I use a VelocityOne Flightstick and yoke together on Xbox in MSFS 2024?

Ian Stephens
In short

Use a VelocityOne Flightstick and yoke together in MSFS 2024 on Xbox, with correct bindings, sensitivity settings and duplicate-axis fixes.

Yes. Microsoft Flight Simulator 2024 on Xbox Series X|S can use an Xbox-compatible Turtle Beach VelocityOne Flightstick and VelocityOne Flight yoke together. Put both in Xbox mode, connect them separately, create a custom preset for each device, and clear duplicate pitch, roll, yaw, throttle and brake assignments from every other active controller profile.

Which Turtle Beach VelocityOne models work on an Xbox console?

Only a VelocityOne model that explicitly lists Xbox compatibility will work on an Xbox Series X|S; an ordinary USB connection does not make PC-only flight hardware console-compatible.

  • VelocityOne Flight Universal Control System: use the Xbox-compatible yoke and throttle-quadrant package, with the quadrant connected as designed.
  • VelocityOne Flightstick: use the Xbox-compatible model and select its Xbox input mode before opening the simulator.
  • Flightstick II or another revision: check the supported platforms for that exact revision. Similar product names do not guarantee identical console support.

Our MSFS 2024 controller compatibility guide for each platform explains why exact hardware support matters. We also maintain a separate guide to yokes that work with Microsoft Flight Simulator on Xbox.

Xbox and PC are not interchangeable here. Xbox users need an explicitly Xbox-compatible VelocityOne model operating in Xbox mode. PC presets, configuration utilities and assumptions about generic USB controller recognition do not automatically transfer to an Xbox installation. This setup also assumes MSFS 2024 is installed locally on Xbox Series X|S, not treated as an Xbox One hardware setup.

How do I connect the Flightstick and yoke to Xbox Series X|S?

Connect the yoke and Flightstick as separate Xbox peripherals, preferably directly to the console while establishing a working baseline.

  1. Select Xbox mode. Set both devices to their Xbox input mode before launching Microsoft Flight Simulator 2024.
  2. Connect the yoke correctly. Attach its throttle quadrant through the connection intended for that package.
  3. Connect the Flightstick separately. Use another console USB port; do not plug it into a pedal, accessory or quadrant socket on the yoke.
  4. Fully quit the simulator. Do not resume a suspended Quick Resume session. Quit MSFS 2024, connect the controls and then relaunch it.
  5. Check the controller tiles. Open the Controls settings and confirm that the Flightstick, yoke and Xbox Wireless Controller each appear as separate devices.

A powered USB hub may work in some arrangements, but it adds another failure point. Configure and test both controls through direct console connections before introducing a hub.

How to assign VelocityOne Flightstick bindings in MSFS 2024

Build a dedicated Flightstick preset, bind each analogue control once, and remove the same flight axes from the active yoke and Xbox controller presets.

  1. Select the Flightstick tile. In MSFS 2024 Controls settings, highlight the VelocityOne Flightstick rather than the yoke or Xbox Wireless Controller.
  2. Create a custom preset. Duplicate an existing usable preset or create a new one, then give it a clear name such as Flightstick aeroplane. Avoid relying on a default preset that may be replaced or reselected.
  3. Search or filter the controls. Use the search field and control-category filters to find flight-control, engine, brake, trim and camera commands. Switch between assigned and unassigned filters when checking for duplicates.
  4. Bind pitch and roll. Assign fore-and-aft stick movement to the analogue pitch or elevator axis and left-and-right movement to the roll or aileron axis.
  5. Bind rudder or yaw. Assign the twist grip to the analogue rudder axis if you are not using pedals. Do not leave another rudder axis active on the yoke, gamepad or pedals in the same profile set.
  6. Bind the throttle. Assign the Flightstick lever to the appropriate analogue throttle axis. Use either a combined throttle axis or aircraft-specific engine axes, not overlapping versions of both.
  7. Add brakes, camera and trim. Use a brake button if you have no analogue toe brakes, a hat or suitable control for cockpit camera movement, and accessible buttons for elevator trim up and down.
  8. Check direction and travel. Move each control through its full range. Invert an axis when its direction is wrong rather than trying to correct it with an extreme sensitivity curve.
  9. Clear the yoke duplicates. Select the VelocityOne yoke tile and its paired preset, then remove pitch, roll, rudder, throttle and brake axes that the Flightstick is intended to control.
  10. Clear the Xbox controller duplicates. Select the Xbox Wireless Controller tile and remove its aircraft pitch, roll, yaw, throttle and brake axes from this profile set. Keep the gamepad’s menu and interface controls.
  11. Save and test. Confirm that moving one physical control produces one on-screen input. If a control surface moves when the intended device is untouched, another binding remains active.

For a yoke-controlled aeroplane, reverse the arrangement: activate a yoke preset and clear the Flightstick’s pitch and roll axes. Separate named presets are safer than rebuilding the assignments whenever you change aircraft.

MSFS 2024 binding checklist for stick, yoke and helicopter aircraft

Give every primary function one analogue source and clear that function from the other active device profiles.

Commands containing Axis are intended for proportional hardware movement. Digital commands such as pitch up/down, rudder left/right, throttle increase/decrease and collective increase/decrease move in steps. Do not assign an analogue axis and the corresponding digital increase/decrease commands to the same function in one working setup; the digital command can step the control away from the lever or stick position.

Stick aeroplanes

A stick-controlled aeroplane should use the Flightstick for pitch and roll, with one chosen source for yaw and one for throttle.

  • Flightstick fore/aft: pitch or elevator axis.
  • Flightstick left/right: roll or aileron axis.
  • Twist grip or rudder pedals: rudder axis, but not both.
  • Flightstick lever or separate quadrant: throttle axis, but not overlapping throttle axes.
  • Brake button or analogue toe-brake axes: choose the type supported by the fitted hardware.
  • Hat and buttons: camera view, elevator trim and frequently used cockpit functions.
  • Yoke and Xbox controller profiles: clear the corresponding primary flight axes.

Yoke aeroplanes

A yoke-controlled aeroplane should take pitch and roll from the yoke and engine controls from its throttle quadrant.

  • Yoke fore/aft: pitch or elevator axis.
  • Yoke rotation: roll or aileron axis.
  • Quadrant: combined throttle for a simple setup, or separate engine throttle axes when the aircraft and available levers justify them.
  • Twist grip or pedals: one rudder axis only. If pedals are added, remove the Flightstick twist assignment from that preset.
  • Toe brakes, if available: separate left and right brake axes. Otherwise use a single brake command.
  • Flightstick and Xbox controller profiles: clear duplicate pitch, roll, throttle and brake axes.

Readers expanding the setup can check our guide to supported yoke and rudder-pedal combinations for Xbox Series X|S.

Helicopters

A helicopter should use the Flightstick for cyclic control, one yaw source for anti-torque and a lever assigned specifically to collective.

  • Flightstick fore/aft and left/right: cyclic pitch and roll through the helicopter’s recognised primary axes.
  • Twist grip or pedals: anti-torque yaw through the rudder axis, with the unused yaw source cleared.
  • Suitable lever: collective axis, not an ordinary aeroplane throttle axis.
  • Rotor or engine throttle: assign separately only when the simulated helicopter requires manual control; many models govern rotor speed automatically.
  • Yoke profile: clear pitch, roll and other primary helicopter controls.
  • Xbox controller profile: clear duplicate cyclic, anti-torque and collective assignments.

If raising the physical lever lowers the collective, invert that axis. Do not bind both the collective axis and collective increase/decrease commands as a workaround.

Can both controls remain plugged in, and why do they sometimes fight?

Yes, both controls can remain connected, but only one device should supply each primary analogue function in the active presets.

The controllers appear to fight when MSFS 2024 receives two values for the same axis. A centred but unused stick can still generate a slight signal, while a displaced yoke, quadrant lever or gamepad thumbstick may continuously override the control you intend to use.

  • An aeroplane that twitches in pitch or roll usually has duplicate axes or genuine centre drift.
  • A throttle that moves back after being set usually has a second throttle axis or digital throttle command active.
  • Rudder movement while taxiing may come from both the Flightstick twist and the Xbox controller thumbstick.
  • A helicopter collective that jumps or reverses may have collective and ordinary throttle commands assigned together.

Buttons can remain assigned on both devices when they perform useful functions such as camera changes or cockpit interaction. The serious conflicts come from continuously active axes, not from having two peripherals connected.

VelocityOne Flightstick sensitivity settings for MSFS 2024 on Xbox

There is no single best sensitivity setting for every aircraft, so begin with the default curves, verify the raw inputs and adjust one axis at a time.

ControlStarting pointChange only when
PitchDefault or near-linear responseSmall movements make rotation, flare or trimming consistently too abrupt
RollDefault or near-linear responseThe aircraft banks too sharply around the centre despite correct bindings
Twist yawDefault curve with no added dead zoneThe rudder flickers at centre or taxi and hover corrections are excessively sharp
ThrottleLinear response with full endpoint travelThe lever does not reach idle or full power, or the direction needs inversion
  1. Remove duplicate bindings first. Sensitivity cannot cure another device continuously driving the same axis.
  2. Select the Flightstick tile. Open its sensitivity or input-response panel from the Controls settings on Xbox.
  3. Test the centred axes. Release the stick and twist grip. The pitch, roll and yaw indicators should settle near centre without persistent flickering or offset.
  4. Test full travel. Move pitch, roll, twist and throttle individually to their limits. Check direction and make sure the input reaches both endpoints.
  5. Use a small dead zone only for genuine drift. Add the minimum needed to stop a centred pitch, roll or twist axis from flickering. A large dead zone creates a numb area around the centre and can hide a hardware or calibration problem.
  6. Adjust pitch and roll separately. If one feels too sharp, make the response around centre slightly gentler, save it and test the same aircraft again before changing the other axis.
  7. Tune twist yaw cautiously. A modestly gentler centre response can help with taxiing and helicopter anti-torque control, but retain full rudder authority at the ends.
  8. Keep throttle simple. A throttle lever is not normally spring-centred, so it does not need a centre dead zone. Correct its direction with inversion and investigate endpoint problems rather than applying an aggressive curve.

On Xbox, make one small adjustment, apply or save it, then test it in flight. Changing pitch, roll, yaw and throttle together makes it difficult to identify which change helped. If the on-screen input still moves while the Flightstick is untouched, return to the bindings before adding more dead zone.

What if it doesn’t detect my VelocityOne Flightstick or the bindings are wrong?

Work through mode, session state, individual-device testing, USB connection, firmware and presets in that order.

  1. Confirm Xbox compatibility and Xbox mode. Check the exact model rather than the VelocityOne brand alone. A PC-only model will not become Xbox-compatible through a hub, adaptor or custom binding, and an Xbox-compatible model may not be recognised while left in PC mode.
  2. Fully quit Quick Resume. Returning to the Xbox Home screen is not enough. Quit MSFS 2024 completely, connect the controls and relaunch it so the simulator enumerates the hardware again. Restart the console if a full quit does not refresh the devices.
  3. Test each device alone. Disconnect the yoke and launch with only the Flightstick, then repeat with only the yoke. A controller that fails by itself must be fixed before diagnosing the combined setup.
  4. Reconnect directly without a hub. Use separate console USB ports while troubleshooting. If both controls work directly but fail through a hub, the hub, its power delivery or another attached peripheral is the likely cause.
  5. Verify firmware. Follow the firmware procedure intended for the exact VelocityOne model. Do not install utilities or firmware packages meant for another product revision, and reconnect in Xbox mode afterwards.
  6. Inspect the active preset and duplicate assignments. If the device tile appears and its input indicators move, Xbox has detected it. Select the intended custom preset, check that the required controls are actually assigned, and inspect the yoke, Flightstick and Xbox controller profiles for duplicate axes.

A missing device tile usually indicates mode, compatibility, USB or firmware trouble. A visible tile with moving input indicators but no aircraft response usually points to an empty, unsuitable or inactive preset. Twitching controls and values that move back by themselves nearly always justify another duplicate-binding check before changing sensitivity.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members