Set up a Winwing Orion joystick and throttle correctly with firmware, calibration, axis bindings, detents, profiles and fixes for input conflicts.
Configure the Winwing Orion as two separate Windows USB controllers: install Winwing’s SimAppPro utility, update and calibrate each unit, then create a clean simulator profile and bind only the required axes. Map the stick to pitch and roll, the two throttle levers per engine, and remove every duplicate automatic assignment.
For general PC flight simulation, the Orion is best treated as a modular HOTAS rather than one combined controller. The stick base, throttle base and any pedals normally appear separately. Orion hardware should not be assumed to work on Xbox or PlayStation simply because the console has USB ports; unless a particular model is explicitly console-licensed, configure it on a Windows PC.
Winwing Orion setup, step by step
- Assemble the controls with USB disconnected. Seat each grip and secure its collar as directed for that Orion model. Avoid twisting or trapping the grip connector while tightening it.
- Connect the stick and throttle separately. Start with direct motherboard USB ports rather than an unpowered hub. Keep them in the same ports after configuration because changing ports or device modes can cause some simulators to treat them as new controllers.
- Install SimAppPro. Let the official Winwing utility detect every base, grip and attached panel. Apply firmware updates over a stable USB connection, following any instruction to disconnect other Winwing units; never unplug a device during its update.
- Calibrate every analogue control. In SimAppPro, move the stick through its full range, let it settle precisely at centre, and sweep each throttle lever from its lowest to highest usable position. Include any rotary axes, brake levers or ministicks that the calibration routine requests.
- Verify the raw Windows input. Open the Windows game-controller panel with
joy.cpl. Check that pitch and roll centre cleanly, each throttle travels independently, and no axis moves without being touched. Use this panel primarily for testing; vendor calibration should normally be done in SimAppPro. - Create a profile for each aircraft or aircraft family. Begin with an empty simulator profile rather than a downloaded community preset. Our general HOTAS connection and profile workflow explains how to keep separate controllers organised.
- Clear automatic assignments before binding. Simulators often assign pitch, roll, throttle or camera movement to several devices at once. Inspect the Orion stick, throttle, pedals, gamepad and any other controller, then remove every unwanted duplicate.
- Bind and test the essential controls first. Add pitch, roll, yaw and throttle, test them in a simple aircraft, and only then assign trim, views, autopilot, weapons or cockpit functions. This makes a bad axis or conflicting binding much easier to identify.
Which axes and buttons should I assign?
Use analogue axis commands for continuous controls and button commands for discrete actions. A common mistake is assigning the stick to digital commands such as “aileron left” and “aileron right”, which produces full deflection instead of proportional movement.
| Orion control | Recommended assignment | Key check |
|---|---|---|
| Stick X axis | Ailerons or roll axis | Moving right must command right roll. |
| Stick Y axis | Elevator or pitch axis | Pulling back must raise the virtual control column. |
| Twist axis, if fitted | Rudder or yaw axis | Leave it unbound when using separate pedals. |
| Left throttle lever | Throttle 1 axis | Check the full idle-to-maximum range. |
| Right throttle lever | Throttle 2 axis | Keep it independent for twin-engine aircraft. |
| Ministick | View slew, radar cursor or cockpit cursor | Do not let its axes become pitch, roll or throttle. |
| Hat switches and buttons | Trim, views, brakes and aircraft functions | Use commands appropriate to the aircraft profile. |
For a single-engine aircraft, use one throttle lever or a supported combined-axis arrangement. Binding two slightly misaligned levers to the same generic throttle command can make the virtual throttle jump between their values. For more detail on choosing analogue and digital commands, see our practical guide to flight-control axis and button mapping.
Start with little or no dead zone. Add only enough to stop genuine centre noise, then use a modest response curve if the aircraft feels too sensitive around neutral. A large dead zone hides calibration faults and creates an abrupt response as the stick leaves centre.
How do I make the Orion throttle detents line up?
Physical detents and simulator detents are separate systems, so both must be calibrated. First give SimAppPro the throttle’s complete physical travel; then align idle, reverse, military power, afterburner or airliner thrust gates within the simulator or aircraft add-on.
- Twin-engine aircraft: bind the left and right levers to Throttle 1 and Throttle 2. Do not also bind both to a generic all-engines throttle axis.
- Airliner detents: use the aircraft’s own calibration page, EFB or cockpit configuration tool when one is provided. The simulator’s global sensitivity page alone may not align idle, climb and maximum-continuous positions.
- Reverse thrust: determine whether the aircraft expects a reverse range on the axis or a separate reverse-toggle button. Do not configure both methods unless the aircraft documentation specifically calls for it.
- Military afterburner: adjust the aircraft-specific curve, saturation or afterburner setting so the virtual afterburner begins as the lever crosses the physical gate.
In Microsoft Flight Simulator 2024 and 2020, axis names and reverse behaviour can vary by aircraft. Our MSFS throttle-axis and detent instructions cover per-engine bindings, inversion and conflicting assignments.
What changes between MSFS, DCS, X-Plane and older sims?
The hardware calibration stays the same, but each simulator stores and interprets the Orion bindings differently.
| Simulator | Recommended approach | Common problem |
|---|---|---|
| MSFS 2024 or 2020 | Create separate profiles for the Orion stick and throttle, then bind per-engine throttle axes where appropriate. | Default bindings on another controller move the same axis, or the throttle direction needs inversion. |
| DCS World | Configure each aircraft in its Controls screen and use the Axis Commands category for pitch, roll, rudder and throttle. | DCS may automatically assign an axis from every connected device to pitch, roll or view control. |
| X-Plane | Run X-Plane’s joystick calibration after the Winwing calibration, then identify and assign each displayed axis. | An unassigned rotary or ministick can be mistaken for a primary flight control. |
| FSX or Prepar3D | Use either the simulator’s control system or FSUIPC for an axis, not both. | Older input handling may expose fewer buttons or create duplicate processing. |
If FSUIPC manages your controls, disable the equivalent simulator assignments and calibrate the Orion axes through FSUIPC. Two calibration layers acting on one axis can produce an uneven range or conflicting reversal.
Do I need SimAppPro running while I fly?
Ordinary DirectInput axes and buttons usually remain available to the simulator without SimAppPro running. Keep it available for firmware, hardware calibration, device modes and Winwing-specific functions; lighting, telemetry synchronisation or virtual mappings may depend on the utility remaining open.
Establish a working direct-input profile before enabling community profiles or compatibility modes. If an older simulator cannot read buttons above its input limit, a multi-device or 32-button compatibility mode may help when offered for that hardware, but changing mode can alter the device identity and require fresh bindings.
Why is the Orion detected but not working properly?
- Visible in SimAppPro but absent from the simulator: confirm it appears in
joy.cpl, connect it before launching the simulator, and restart the simulator after any USB or device-mode change. - Aircraft moves without input: search every connected controller for duplicate pitch, roll, rudder, throttle and camera assignments. Throttle ministicks and rotary knobs are frequent offenders.
- Axis moves backwards: invert it in one place only. Reversing it in SimAppPro and again in the simulator returns it to the wrong direction.
- Throttle cannot reach idle or full power: repeat the Winwing calibration, restore a neutral simulator response curve, and then perform any aircraft-specific detent calibration.
- Stick jitters around centre: recalibrate before adding a dead zone. If the raw input still spikes, try a direct USB port or powered hub and check for a loose grip connection.
- Some buttons are missing: an older simulator may have a button-count limit. Use a Winwing compatibility mode only if the device offers one, then rebuild the simulator profile for the resulting virtual controllers.
- Bindings disappear after firmware or mode changes: the simulator may see a different hardware identifier. Back up profiles where the simulator permits it and keep the controls connected to consistent USB ports.