Fix a URSA Minor 32 throttle that will not bind in MSFS 2024 by checking Windows detection, selecting the right axis and saving its device profile.
A URSA Minor 32 throttle usually fails to bind in Microsoft Flight Simulator 2024 because the wrong device profile is selected, Windows is not seeing the lever as an analogue axis, or a button-style throttle command was chosen. Verify the axis in Windows, then assign it to an analogue Throttle Axis command.
What causes the URSA Minor throttle binding failure?
The first task is to establish whether the problem sits with the hardware, its Windows input, or the MSFS 2024 control profile. Repeatedly changing bindings will accomplish nothing if Windows itself cannot see the lever moving.
- No Windows axis response: the device needs reconnecting, calibration or attention in its manufacturer utility.
- Wrong peripheral selected: MSFS stores bindings separately for every joystick, throttle, keyboard and controller.
- No default preset: an unrecognised or generic device may need a new custom profile; this does not necessarily mean it is incompatible.
- Wrong command type: Increase, Decrease and fixed-percentage throttle commands are digital button controls, not analogue axes.
- Input scanning misses the lever: the binding scanner may not detect an axis already resting at one endpoint.
How do I bind the URSA Minor 32 throttle correctly?
- Check it in Windows. Press Windows key and R, enter
joy.cpl, select the URSA device and open its properties. Move the throttle through its complete travel and confirm that one axis moves smoothly from endpoint to endpoint. If it does not, reconnect the controller directly to another USB port, run its calibration and check the manufacturer's configuration utility. Our Windows-to-MSFS calibration checks cover this isolation process in more detail. - Connect it before starting the simulator. Restart MSFS 2024 after reconnecting the device so that the simulator enumerates it cleanly.
- Select the physical URSA device. Open the Controls settings and choose the URSA controller tile, not the keyboard, Xbox controller or another joystick. If several similarly named devices appear, identify the one receiving the throttle movement.
- Create a custom profile. Duplicate an editable preset or create a new profile for that device. Bindings saved under another peripheral will not control the URSA, even when the profile names look identical. Follow our custom controller mapping and saving procedure if the active-profile controls are unclear.
- Show all aircraft commands. Do not leave the list filtered to assigned controls. Search for
Throttle Axisunder the aeroplane controls. - Scan the full lever movement. Start the assignment scanner, sweep the lever from minimum to maximum and back through the midpoint, then accept the detected analogue axis. Moving it only a few millimetres may not cross the scanner's detection threshold.
- Save and activate the profile. Apply the changes and verify that the new URSA profile remains selected. MSFS 2024 profiles are device-specific, so saving a joystick profile does not also save the throttle's assignments.
- Check direction and range. Open the axis response or sensitivity display. Enable the reverse-axis option only if advancing the physical lever reduces the on-screen input.
Which throttle command should I use?
Use the continuous analogue command that matches the number of physical throttle levers. Command wording can vary slightly between control categories, but the distinction between an axis and a button command is what matters.
| Command type | Use it when | Typical result |
|---|---|---|
| Throttle Axis | One lever should operate all engines | Best starting choice for the URSA lever |
| Throttle 1 Axis, Throttle 2 Axis | You have separate physical levers for individual engines | Controls only the specified engine |
| Throttle Increase or Decrease | You are assigning buttons, keys or a hat switch | Unsuitable for a continuous lever |
| Fixed throttle percentage | You want a button to select a preset power level | Jumps to a fixed position rather than following the axis |
If MSFS lists the URSA Minor as a generic controller without a ready-made preset, manual axis assignment is expected. The fixes for a missing default controller profile explain how to proceed without relying on an automatic preset.
Why does the throttle bind but not control the aircraft?
A successful assignment with a moving input graph means the binding itself works; the remaining fault is usually a conflict, the wrong engine axis or an aircraft system overriding the lever.
- The cockpit throttle snaps back: clear duplicate throttle axes from gamepads, other joysticks and unused controller profiles.
- Only one engine responds: replace an individual-engine axis with the general Throttle Axis command, or assign every engine deliberately.
- The cockpit lever moves backwards: reverse the assigned axis rather than recalibrating an otherwise correct input.
- The lever reaches only part of its range: recalibrate the hardware and inspect the response graph for incomplete endpoints or an excessive dead zone.
- A complex aircraft ignores manual input: disengage autothrottle or automatic power management and test the same profile in a basic default aircraft. This separates a controller problem from aircraft-specific throttle logic.
- The binding disappears after changing aircraft or devices: check that the intended profile is still active on the URSA peripheral, not merely on the joystick beside it.
If the axis is detected and assigned but remains ineffective, work through our throttle-input troubleshooting sequence to find assistance settings, duplicate mappings and profile conflicts.
Can the URSA Minor be bound on Xbox or PlayStation?
Console versions of MSFS 2024 cannot use the Windows joy.cpl or DirectInput workflow. The console must first recognise the URSA Minor as compatible hardware; if no controller tile appears at all, creating an in-simulator profile cannot make an unsupported USB device visible. The procedure above is primarily for the PC version.