Set up Virpil controls in MSFS 2020: calibrate the hardware, map every axis, tune sensitivity and fix missing or duplicate inputs.
On PC, set up Virpil controls in MSFS 2020 by first using the VPC Configuration Tool to identify and calibrate each device, then creating a separate simulator profile for every Virpil USB unit. Bind analogue movement to Axis commands, remove duplicate assignments, tune dead zones, and test each control in the cockpit.
This is a PC setup. Microsoft Flight Simulator 2020 on Xbox does not natively support Virpil's PC DirectInput hardware.
Configure the Virpil hardware before opening MSFS
The VPC software should handle hardware calibration; MSFS should receive clean, full-range DirectInput axes. Do not compensate for an incorrectly configured device with extreme sensitivity or dead-zone settings in the simulator.
- Assemble with USB disconnected. Attach the grip to its base carefully and avoid twisting or straining the internal connector. Connect the base, throttle and pedals as separate USB devices unless your particular Virpil hardware is designed differently.
- Install the VPC Configuration Tool. Select the exact base, grip and device combination. Choosing the wrong hardware profile can produce missing buttons, incorrect axes or an apparently dead grip.
- Complete firmware changes before binding. If an update is required, use the firmware supplied with the matching configuration-tool package and do not disconnect the device during the update. A firmware or hardware-profile change made later can cause Windows and MSFS to treat it as a new controller.
- Calibrate every analogue control. Move the stick, throttle levers, rotary axes, ministicks, rudder pedals and toe brakes through their full usable travel. Allow spring-centred controls to return naturally to centre.
- Save the configuration to the device. Check that every physical movement and button produces the expected logical input in the VPC utility.
- Verify rather than recalibrate in Windows. The Windows game-controller panel is useful for checking movement, but do not apply a second Windows calibration over the VPC calibration.
Connect directly to the PC while diagnosing a problem. An unpowered hub, marginal extension cable or overloaded hub can cause intermittent disconnects that look like an MSFS binding fault.
How should Virpil axes be mapped in MSFS 2020?
Map each physical analogue control to an MSFS Axis command, not to similarly named increase/decrease or left/right commands.
- Open Options, then Controls Options.
- Select the Virpil device tile. A generic icon or unfamiliar device name does not necessarily indicate a fault.
- Create or duplicate a preset and give it a clear name, such as
VPC Stick - GAorVPC Throttle - Twin. - Set the filter to show all commands, select the search-by-input function, and move only the control being assigned. Put maintained switches in their off positions first so a permanently held button does not capture the search.
- Assign the axis, validate it, and move the control while watching the on-screen response.
| Physical Virpil control | Typical MSFS assignment | Common issue |
|---|---|---|
| Stick X axis | Ailerons Axis | Do not bind the digital left and right commands |
| Stick Y axis | Elevator Axis | Enable reverse only if pulling back commands nose-down |
| Twist grip or rudder pedals | Rudder Axis | Clear any duplicate rudder assignment on the stick or gamepad |
| Left and right toe brakes | Left Brake Axis and Right Brake Axis | Virpil toe brakes often need the Reverse Axis option in MSFS |
| Single throttle lever | Throttle Axis or its 0–100% variant | Choose according to how reverse thrust will be handled |
| Split throttle levers | Throttle 1 Axis and Throttle 2 Axis | Check that each lever operates the matching engine |
| Propeller or mixture lever | Matching propeller or mixture axis | Some aircraft ignore these because their systems work differently |
Use a 0–100% throttle assignment when the physical lever covers idle to maximum and reverse is activated separately. Use the full-range assignment only when the aircraft and its calibration method expect reverse within the same axis. Complex airliners may also require detent calibration in their own cockpit tablet or configuration panel; our throttle-axis and reverse-thrust setup explains the choice in more detail.
Reverse an axis in either MSFS or the VPC configuration, not both. We normally leave the hardware output conventional and apply aircraft-specific reversal in the relevant MSFS profile.
Which Virpil buttons and switches should I bind?
Bind flight-critical buttons first and use explicit on/off events for maintained switches when MSFS provides them.
- Pitch and rudder trim
- Wheel brakes or parking brake
- Flaps and landing gear
- Autopilot disconnect
- Push-to-talk or simulator communication control, if required
- Cockpit view, external view and view reset
A maintained two-position switch is not the same as a momentary push-button. Binding a maintained switch to a generic Toggle command can leave the physical switch and virtual cockpit out of sync after loading a flight or operating the cockpit control with the mouse. Bind separate on/off commands where available.
A Virpil mode selector does not automatically change the active MSFS control profile. It can provide extra logical button numbers if configured that way in the VPC utility, but each resulting button must still be assigned in MSFS.
Should I use one profile for every aircraft?
Use one MSFS profile per Virpil device, then duplicate those profiles for aircraft categories that need different mappings.
A practical starting set is a general-aviation stick profile, a twin-engine throttle profile and a separate airliner throttle profile. MSFS 2020 profiles are attached to individual controller devices rather than to the whole cockpit, so the stick, throttle and pedals each need the correct preset selected.
Changing a VPC hardware profile, virtual-device arrangement or firmware configuration after completing the bindings may make MSFS create a fresh controller entry. Save a copy of the VPC configuration and finish hardware-level changes before building detailed simulator presets.
Why are my Virpil controls reversed, jittery or missing?
Most Virpil faults in MSFS 2020 come from incomplete calibration, duplicate bindings, held switches or a changed hardware profile.
- The aircraft moves without input: search all connected controllers for the affected axis and remove duplicates. Gamepads, throttles and unused twist grips are common sources.
- An axis moves backwards: use the MSFS Reverse Axis option. Avoid reversing the same signal in both configuration layers.
- The centre jitters: recalibrate in the VPC utility first. Add only enough MSFS dead zone to stop genuine sensor noise; Virpil hardware should not require a large dead zone when configured correctly.
- Travel stops early: repeat the VPC calibration through the full physical range and confirm that the Windows indicator reaches both endpoints.
- A button cannot be detected: verify its logical output in the VPC utility, save the device configuration, and release any maintained switches before using search by input.
- MSFS shows two inputs at once: clear the unwanted default assignment rather than trying to overpower it with sensitivity settings.
- The device is absent: close MSFS, reconnect the controller directly to the PC, confirm Windows detection, and then restart the simulator. Our Windows recognition and duplicate-input checklist covers the wider device checks.
Begin with a straight response curve and a minimal dead zone. Once every axis reaches its endpoints and centres correctly, adjust response around the centre to suit the aircraft; our MSFS joystick sensitivity guide explains how sensitivity, dead zone and reactivity affect the result.
How should I test the finished setup?
Test the controls with a default aircraft before troubleshooting them in a complex add-on.
Load on the ground with the cockpit visible. Confirm that the yoke or stick, rudder pedals, toe brakes and throttle move in the correct direction and through their full range. Test one engine lever at a time, then check trim, flaps, gear and maintained switches; only after that should you add secondary bindings or aircraft-specific detents.