Set up and save VelocityOne Flightdeck profiles correctly, with clean bindings, separate device presets and practical fixes for lost settings.
To set up and save Turtle Beach VelocityOne Flightdeck profiles, update and verify both units, configure any device-side settings in Flight Hangar, then create named control presets for the stick and throttle inside your simulator. Remove duplicate auto-bindings, save or apply every preset, restart the sim, and verify that each profile reloads.
This procedure applies to PC flight simulators generally, including Microsoft Flight Simulator, X-Plane, DCS and FlightGear. If by “Fly One” you mean this controller, its official name is VelocityOne Flightdeck; instructions for other VelocityOne products may not match the Flightdeck HOTAS.
What does a VelocityOne Flightdeck profile actually save?
A complete Flightdeck setup has separate device-side and simulator-side layers, and saving one does not save the other.
| Layer | What it contains | Where it is saved |
|---|---|---|
| Flight Hangar or device profile | Settings exposed by the installed firmware and software, such as calibration, lighting, display behaviour, modes or programmable functions | In Flight Hangar and, where supported, on the Flightdeck hardware |
| Stick control preset | Pitch, roll, yaw or twist, trim, view and button assignments | Inside the simulator, against the stick controller entry |
| Throttle control preset | Throttle axes, engine controls, flaps, gear, reversers and throttle-unit buttons | Inside the simulator, against the throttle controller entry |
| Aircraft or module association | Which control preset loads for a particular aircraft or aircraft class | Inside simulators that support aircraft-specific selection |
The Flightdeck stick and throttle normally appear as separate game-controller entries. A mistake we see constantly is configuring both but saving or selecting a preset for only one of them.
How do I set up and save VelocityOne Flightdeck profiles?
The reliable order is to verify the hardware first, build clean presets for both controller units, and test that they survive a complete restart.
Install Flight Hangar and update the firmware. Complete firmware updates before spending time on bindings, and do not disconnect either unit during an update. Firmware changes can affect device behaviour and may require a simulator preset to be selected again.
Use stable USB connections. Connect the stick and throttle directly to the PC while setting them up. Once they work, keep them on the same USB ports where practical; reconnecting through different hubs or ports can occasionally make Windows or the simulator treat a unit as a new device instance.
Test both units in Windows. Press Windows-R, enter
joy.cpl, and inspect each Flightdeck entry. Move every axis through its full travel and test hats, rotaries and buttons. If an input is absent, stuck, noisy or off-centre here, the simulator profile is not the cause.Calibrate through the supported device procedure. Use Flight Hangar or the Flightdeck’s own calibration process when available. Avoid applying Windows calibration merely to mask a fault; competing calibration layers can produce shortened travel or a persistent centre offset.
Create and save the device-side profile. Configure only the Flight Hangar features you need, give the profile a recognisable name, and use the displayed save, apply or synchronise control. The exact wording can vary with the installed software and firmware.
Create separate simulator presets for the stick and throttle. Duplicate a stock preset or create a new one rather than overwriting a known-good default. Use paired names such as
MSFS - GA - StickandMSFS - GA - Throttle.Clear automatic and duplicate assignments. Check the Flightdeck, pedals, gamepad, keyboard and any other connected controller. Microsoft Flight Simulator often assigns pitch, roll, yaw, throttle, brakes and camera controls to several devices; our guide to clearing unwanted MSFS controller bindings provides a clean starting point.
Bind the principal axes using axis commands. Assign controls labelled as an axis, such as aileron, elevator, rudder and throttle axis, rather than digital commands such as increase, decrease, pitch up or pitch down. If you use rudder pedals, clear the Flightdeck twist-axis rudder assignment unless you deliberately want both.
Choose combined or individual engine throttles. Use a combined throttle axis when one lever should control every engine. Use engine-specific axes for independent multi-engine operation, but do not bind the same lever to both the combined throttle and an individual engine axis.
Check direction, range and centre response. Reverse an axis in the simulator if it moves in the wrong direction. Add only enough deadzone to stop genuine centre noise, and avoid applying aggressive response curves in both Flight Hangar and the simulator because the two curves compound.
Map high-use buttons before specialist systems. Start with trim, brakes, parking brake, flaps, gear, view reset, autopilot disconnect and pause. Add propeller, mixture, spoilers, reversers, helicopter controls or combat functions only after the basic profile flies correctly.
Save or apply every simulator preset. Confirm the named preset separately on the stick and throttle controller pages. Some simulators retain edits automatically while others present a save or apply command, so do not assume that closing the controls screen commits unfinished changes.
Restart and verify persistence. Close Flight Hangar and the simulator, reconnect using the normal USB ports, then relaunch everything. Confirm the intended device profile and both simulator presets before loading a straightforward default aircraft.
Back up confirmed profiles where export is supported. Export the stick and throttle presets separately and record which device profile accompanies them. Do not assume an exported profile will transfer cleanly across a different simulator generation or major firmware change.
Does Flight Hangar save my simulator controls?
No. Flight Hangar configures supported Flightdeck hardware features, but it does not replace the control preset stored by Microsoft Flight Simulator, X-Plane, DCS or another simulator.
Keep primary flight axes and aircraft commands in the simulator wherever possible. Device-side modes and shifted buttons are useful for expanding the available controls, but complicated hardware macros make faults harder to trace and can behave differently between simulators.
The profile names do not technically need to match, though matching names make mistakes less likely. For example, pair a Flight Hangar profile called Airliner with simulator presets called Airliner - Stick and Airliner - Throttle.
How do different simulators store Flightdeck presets?
Each simulator organises controller profiles differently, so a Flightdeck setup that works in one simulator is not automatically available in another.
| Simulator | Profile behaviour to check |
|---|---|
| Microsoft Flight Simulator 2020 and 2024 | Each detected controller has its own preset. Menu wording differs between releases, but the stick, throttle, pedals and gamepad must each have the intended preset selected. |
| X-Plane | Joystick profiles can be associated with particular aircraft. Check the aircraft association if the correct bindings appear in the menu but a different profile loads in flight. |
| DCS | Bindings are organised by aircraft module and by controller column. Configuring the Flightdeck for one module does not populate another, and automatic axis assignments should be checked in every module. |
| FlightGear | Recognition and mapping depend on the active joystick configuration. Confirm the raw inputs before assigning simulator functions. |
For the last case, follow our FlightGear control-detection and axis setup procedure rather than trying to import a preset from another simulator.
Why are my VelocityOne Flightdeck profiles not saving or loading?
Most apparently lost profiles are either saved to the wrong controller entry, left unapplied in one layer, or replaced by a different active preset after reconnection.
| Symptom | Likely cause and fix |
|---|---|
| The profile name has disappeared | Check whether Windows or the simulator has created another controller instance after a USB or firmware change. Return to the usual ports and inspect every Flightdeck controller entry. |
| The profile exists but default controls are active | The wrong simulator preset is selected on the stick, throttle or both. Select and confirm each controller separately. |
| An axis moves twice, jitters or fights itself | The same function is assigned to another controller, or the axis is bound to both combined and engine-specific commands. Search all connected devices for duplicates. |
| A throttle or stick moves only part-way | Check Windows input range, calibration, the assigned command and any response curve. This is usually a range or binding problem rather than failed profile saving. |
| Buttons produce different commands after startup | The wrong Flight Hangar profile or mode layer is active. Select the device-side profile before opening the simulator and confirm which input each button sends. |
| Changes work only until reboot | The edit may have been a temporary preview or left unapplied. Save or synchronise the device profile explicitly, then confirm the simulator presets independently. |
| Only one aircraft ignores the controls | The aircraft may use specialised commands, an aircraft-specific preset or custom systems logic. Test the same control in a default aircraft before rebuilding the hardware profile. |
| The simulator cannot see the Flightdeck | Return to joy.cpl. If Windows also cannot see it, check the cables, USB connection, firmware state and both individual units before changing simulator settings. |
What if the Flightdeck works in one simulator but not another?
If Windows detects every input and one simulator responds correctly, the hardware is functioning; rebuild the profile inside the simulator that does not respond.
Do not import assumptions from the working simulator. The second sim may use a different throttle command, invert an axis independently, store controls per aircraft, or interpret a mode-layer button as a different input. Start with one pitch axis and one throttle axis in a default aircraft, then add the remaining controls methodically.
Should I use one Flightdeck profile for every aircraft?
Use one common profile only for aircraft with similar controls; create separate profiles when the required axes or cockpit jobs change substantially.
One general-aviation profile is sensible for similar single-engine piston aircraft using throttle, propeller and mixture controls.
A separate multi-engine profile is better when the throttle levers need individual engine assignments.
Airliners need their own layout when you require spoilers, reversers, autothrottle disconnects and additional autopilot functions.
Helicopters and combat aircraft need specialised profiles because collective, rotor or module-specific controls do not fit a conventional fixed-wing layout cleanly.
Keep essential functions in consistent positions across those profiles: trim on the same hat, brakes on the same control and autopilot disconnect in the same place. A naming pattern such as SIM - AIRCRAFT CLASS - STICK and SIM - AIRCRAFT CLASS - THROTTLE also makes the active pair immediately clear.