Set up Winwing URSA Minor bindings in MSFS 2020, map the correct axes and buttons, remove conflicts, and fix reversed or missing inputs.
Connect the Winwing URSA Minor before launching Microsoft Flight Simulator 2020, select it in Options > Controls Options, create a dedicated preset, then bind the stick to the aileron and elevator axis commands—not the left/right or up/down commands. Map buttons, clear duplicate assignments, test full travel, and save the preset.
How do I create the URSA Minor control profile?
A clean, device-specific preset is the safest starting point because an automatic or inherited profile can contain camera, flight-control and throttle conflicts.
- Check the controller in Windows. Press Windows key + R, enter
joy.cpl, select the URSA Minor and open its properties. Confirm that each axis moves through its full range and every button registers. If it fails here, correct the USB, firmware or hardware calibration problem before opening MSFS. - Launch MSFS 2020 with the controller connected. Open Options > Controls Options and select the URSA Minor device tile. Depending on the model and configuration, Windows may expose more than one Winwing device, so inspect every relevant tile.
- Create a dedicated preset. Use Preset Manager to duplicate a usable default profile, or begin with the blank preset shown for an unrecognised controller. Give it a clear name such as
URSA Minor GA. - Change the filter to All. The Assigned filter hides commands that have not yet been mapped, which is a common reason people think the required axis command is missing.
- Bind one axis at a time. Search for the command, select its assignment field, start input scanning and move only the intended control. Validate the detected input before continuing.
- Map essential buttons. Add trim, brakes, flaps, landing gear, view controls and autopilot disconnect according to the aircraft you normally fly.
- Remove duplicate assignments. Search by input and check the profiles for any connected gamepad, throttle, pedals or virtual controller. Two devices commanding the same axis can make the controls jump or return towards centre.
- Save and test. Choose Apply & Save, load a simple aircraft and verify the cockpit yoke or stick, rudder and throttle before flying.
MSFS binds the physical controller directly, so keyboard emulation is normally unnecessary. Use Winwing's configuration software for firmware, hardware calibration or intentional mode changes, not as an extra layer of keyboard macros unless a particular aircraft requires them. Our complete MSFS controller-profile workflow covers the wider Controls Options interface if the URSA is your first flight-sim joystick.
Which MSFS 2020 commands should I bind?
For normal aircraft control, bind analogue inputs to commands containing Axis; directional commands behave like keyboard keys and produce abrupt or full control deflection.
| URSA Minor input | MSFS 2020 assignment | Selection advice |
|---|---|---|
| Stick X axis | Ailerons Axis | Do not use Aileron Left or Aileron Right. |
| Stick Y axis | Elevator Axis | Reverse the axis if pulling back moves the cockpit control forwards. |
| Twist axis, if used | Rudder Axis | Leave this unassigned when separate rudder pedals provide yaw. |
| Integrated throttle control | Throttle Axis (0 to 100%) | Usually the best choice when the control runs from idle to full power without a reverse range. |
| Hat switch | Cockpit view look or pan commands | Remove any automatic flight-control assignment from the same hat directions. |
| Grip buttons | Elevator trim, brakes, flaps, gear or autopilot disconnect | Prioritise commands needed during take-off, approach and landing. |
Choose engine-specific throttle commands only when you have separate physical levers and want independent engine control. The full-range throttle axis is appropriate when you deliberately need a below-idle or reverse region and the aircraft supports suitable calibration. For incomplete travel, jumping power or an unwanted reverse range, use our throttle-axis configuration and troubleshooting steps.
Why does the URSA Minor move at full deflection?
The stick usually snaps to full deflection because its analogue axis has been assigned to a digital direction command.
Delete assignments such as Aileron Left, Aileron Right, Elevator Up and Elevator Down from the stick axes. Bind the physical X and Y inputs only to Ailerons Axis and Elevator Axis. A button can use a digital command; a stick axis should not.
If the cockpit control still jumps, search by input for that physical axis. An unnoticed camera, trim or secondary flight-control binding may be responding to the same movement.
How do I fix reversed, drifting or over-sensitive axes?
Use the MSFS sensitivity panel only after Windows reports smooth, complete movement from the URSA Minor.
- Reversed movement: enable Reverse Axis for that assignment rather than swapping unrelated commands.
- Small centre drift: add only enough dead zone to stop the input moving when the stick is released.
- Twitchy pitch or roll: soften the sensitivity curve gradually; do not use a large dead zone to disguise excessive response.
- Restricted travel: check Windows or Winwing calibration first, then inspect the MSFS extremity and neutral settings.
- Uneven response: restore a simple baseline before adjusting several sensitivity controls at once.
There is no universal sensitivity percentage for every URSA Minor, aircraft and grip configuration. Start near the default response and tune against the on-screen input trace; our joystick sensitivity guide for MSFS 2020 explains what each curve and dead-zone setting changes.
Why are my bindings missing or fighting another controller?
Missing or unstable bindings are usually caused by the wrong active preset, a second device controlling the same function, or MSFS being started before the URSA Minor was detected.
Return to Controls Options and confirm both the selected device tile and preset name. Then inspect any Xbox controller, pedals, throttle quadrant and virtual device for duplicate aileron, elevator, rudder or throttle axes. Automatic profiles often assign several devices to the same primary controls.
If the profile has become too tangled to audit reliably, clear the affected device and rebuild only the essential axes and buttons. Our controller-binding reset procedure shows how to do that without needlessly wiping every control profile.