Set up the Winwing URSA Minor in MSFS 2024: calibrate it in SimAppPro, bind the correct axes, remove conflicts and fix detection problems.
To set up the Winwing URSA Minor in Microsoft Flight Simulator 2024, connect it directly to the PC, use SimAppPro to check its firmware and calibrate every axis, then create a dedicated MSFS control profile. Bind pitch, roll and any twist or throttle axes manually, remove duplicate assignments, and test them before flying.
Prepare the URSA Minor before opening MSFS 2024
Complete the hardware calibration before opening Microsoft Flight Simulator 2024. This workflow applies to Windows PC; the URSA Minor operates as a USB flight controller, while SimAppPro handles its device configuration and calibration.
- Connect the controller directly: plug it into a motherboard USB port while MSFS is closed. Avoid an unpowered hub during initial setup, because it adds another possible cause if Windows does not recognise the device.
- Open SimAppPro: confirm that it identifies the correct URSA Minor variant. Install a firmware update only when the software offers one for that exact device, and do not disconnect the controller during the process.
- Calibrate every analogue input: move the stick slowly through its full pitch and roll travel. Calibrate the twist rudder and small throttle control as well if your variant includes them, then release the stick so it can settle naturally at centre.
- Check the Windows input: run
joy.cpl, open the URSA Minor properties and confirm that the stick reaches both endpoints, returns to centre and does not activate unrelated axes.
Use SimAppPro as the primary calibration tool rather than stacking a second Windows calibration over it. Our guide to calibrating analogue flight controls before binding them covers endpoint, centre and throttle-range checks in more detail.
If you have several Winwing panels or controls, our broader Winwing profile and SimAppPro guidance explains how to keep their device presets separate.
How do I bind the URSA Minor controls in MSFS 2024?
Create a clean device preset and bind the analogue axes manually rather than trusting MSFS 2024's automatic assignments.
- Open the controls screen: start MSFS 2024 after Windows has recognised the controller, open
Settings > Controlsand select the URSA Minor device tile rather than the keyboard, mouse or another controller. - Create a dedicated preset: use a new or blank preset where possible. Give it an identifiable name so an automatically generated or aircraft-specific profile is not selected accidentally.
- Display all available controls: change the filter from assigned controls to all controls, then search for the required axis. If the interface offers input scanning, move only the control being assigned.
- Choose analogue axis commands: bind the stick to
Ailerons AxisandElevator Axis. Do not use digital commands such as aileron left/right or elevator up/down; those produce full deflection instead of proportional movement. - Add rudder and throttle only when needed: bind the twist grip to
Rudder Axisif you are not using pedals. Bind the built-in throttle control only if a separate throttle is not already assigned. - Remove conflicts: inspect the assigned-control list for duplicate pitch, roll, rudder and throttle bindings on every connected device. A gamepad, throttle quadrant or second joystick can move the same aircraft control without being obvious.
- Test in the cockpit: verify that right stick produces right roll, forward stick commands nose-down pitch and the throttle travels from idle to full power. Save or confirm the preset before changing aircraft.
Recommended URSA Minor assignments
The correct assignment depends on the URSA Minor variant and the other flight controls connected to the PC.
| Physical input | MSFS assignment | When to use it |
|---|---|---|
| Stick left/right | Ailerons Axis | Always; reverse the axis in MSFS only if right stick commands left roll. |
| Stick forward/back | Elevator Axis | Always; pushing forward should command nose-down pitch. |
| Twist grip, if fitted | Rudder Axis | Use without rudder pedals. Leave it unassigned when pedals provide yaw control. |
| Built-in throttle or slider, if fitted | Throttle Axis | Use the 0–100% form for a conventional idle-to-full control. Leave it clear when using a separate throttle. |
| Hat switch | Cockpit or external view movement | Assign by direction; it is normally a set of buttons rather than an analogue axis. |
| Buttons | Trim, brakes, flaps, landing gear or autopilot disconnect | Choose functions appropriate to the aircraft rather than importing a crowded generic preset. |
What sensitivity and dead zone should I use?
Start with the default response curve and no added dead zone, then change only what the input display shows is necessary. Add a small dead zone if the centred stick jitters or causes control drift; excessive dead zone makes fine corrections around centre harder.
If the aircraft feels too lively, flatten the central part of the pitch and roll response rather than reducing the available control range. Keep enough extremity to reach full control deflection. Our dead-zone and response-curve guidance explains how sensitivity, reactivity and extremity affect the aircraft.
Why is the URSA Minor not detected or binding correctly?
Most URSA Minor setup failures come from USB detection, an incorrect control type or duplicate assignments rather than a faulty stick.
- No URSA Minor device tile: close MSFS, reconnect the controller directly, confirm that it appears in SimAppPro and
joy.cpl, then restart the simulator. MSFS may not populate a newly connected device reliably while already running. - The axis does not appear: switch the controls filter to all controls and use input scanning. Move the axis through most of its travel, not just a few millimetres.
- The aircraft jumps to full deflection: a digital left/right or up/down command has been assigned instead of the corresponding axis command.
- The controls move by themselves: inspect all connected device presets for duplicate axes. Temporarily unplug other controllers if necessary to identify which one is sending the second input.
- An axis works backwards: use the reverse-axis option in MSFS. Do not recalibrate the hardware backwards merely to correct one simulator assignment.
- The throttle uses only part of its travel: recalibrate its endpoints and check which throttle-axis form is assigned. A simple idle-to-full slider generally needs the 0–100% control rather than a centred or reverse-inclusive axis.
- Bindings disappear after changing aircraft: verify that the same URSA Minor preset remains active. MSFS can select a different control preset or aircraft-specific assignment set.
If the imported preset is full of unwanted assignments, it is often faster to clear or reset the controller bindings and rebuild the main axes on a clean profile.
Does SimAppPro need to remain open?
SimAppPro does not normally need to remain open for standard URSA Minor axes and buttons, because MSFS reads those through the Windows USB controller interface. Software-mediated mappings or advanced device features may still depend on it.
If inputs disappear when SimAppPro closes, check whether a virtual mapping or software profile is active. Avoid binding both the physical controller and its virtual output, as that creates doubled inputs.
Console support: this procedure is for PC. SimAppPro is not available on Xbox Series X|S or PlayStation 5, and connecting an ordinary PC USB controller does not make it console-compatible. Use the URSA Minor on a console only if Winwing explicitly identifies that exact variant as supported by the platform.