vJoy for IL-2 Sturmovik: Solving the Device Limit by Merging

IL-2 Sturmovik players run into a counting problem. A warbird cockpit wants a stick, a throttle quadrant with several levers, rudder pedals, perhaps a button box — and the simulator’s willingness to juggle many separate controllers becomes the bottleneck long before the pilot runs out of USB ports. The vJoy answer is merging: read the physical devices with a feeder such as Joystick Gremlin or UCR, combine the controls you need into fewer virtual devices, and let IL-2 bind those. One vJoy device can carry up to 8 axes, up to 128 buttons and up to 4 POV hats, and vJoy supports up to 16 virtual devices as a documented limit, so a merged layout has real headroom when it is planned instead of improvised.

Merging also buys consistency. Instead of remembering which quadrant lever landed on which device number after a hardware change, you document one virtual layout and keep it stable while physical gear changes underneath. Gremlin handles curves and button logic on the way through, which suits IL-2 aircraft where a softer pitch centre and carefully placed radiator, mixture and trim controls make long flights calmer.

What you need

• vJoy from our download page — BrunnerInnovation 2.2.2.0 first on Windows 10 and Windows 11, 2.1.9.1 as the fallback if a feeder misbehaves on 2.2.x.
• Joystick Gremlin for merging and curves — see our Joystick Gremlin guide — or UCR for remapping, covered in our UCR (Universal Control Remapper) guide. Choose one feeder for the merge and stay with it.
• All physical devices tested in Windows first, with a written inventory: device, axes, buttons, and the IL-2 function each will own after merging.
• For head tracking, the OpenTrack chain described in our OpenTrack and FreePIE head-tracking chain if you plan to look around the cockpit through a vJoy-linked setup.

Setup, step by step

1. Install vJoy and, in Configure vJoy, create the first virtual device with the axes for your primary flight controls: stick X and Y, throttle, and rudder are the usual starting four. Keep a second device in reserve rather than creating it on day one.
2. In Gremlin or UCR, map the physical stick to vJoy X and Y, the main throttle lever to a vJoy axis, and the pedals to another. Activate the profile and confirm every axis in joy.cpl, full travel, both directions.
3. Add the secondary quadrant levers — propeller pitch, mixture, radiators where your aircraft and your hardware support them — to the remaining vJoy axes. Write the final virtual layout down; this document is now the source of truth for binding.
4. Shape pitch and roll curves in the feeder for a calmer centre. Warbird flying involves long periods of small corrections, and a curve you trust reduces pilot-induced oscillation on approach. Shape in the feeder only, not in both feeder and game.
5. Decide on visibility: if IL-2 also reads the raw physical devices, duplicate inputs can fight the merged ones. Where needed, use the hiding approach described in our HidHide guide so the game binds the virtual layout you documented.
6. In IL-2, bind the vJoy device controls group by group — primary flight controls, engine controls, then buttons for gear, flaps, brakes and weapons systems. Test each group in a quick mission before binding the next.
7. If you hit the practical device ceiling again as the cockpit grows, add the second vJoy device deliberately for a defined group — for example all button-box functions — and document it the same way. Planned devices stay understandable; accidental ones do not.
8. Back up the feeder profile and export or photograph the IL-2 assignments. A merged cockpit represents hours of decisions, and the backup is what makes a Windows reinstall a nuisance instead of a disaster.

Head tracking through the OpenTrack chain

Looking around is half of warbird situational awareness, and community setups commonly run head tracking through an OpenTrack chain in which FreePIE and vJoy can carry the resulting axes. Our OpenTrack and FreePIE head-tracking chain explains that chain link by link, including the honest point that OpenTrack does not require vJoy in every configuration. Treat tracking as a separate subsystem from the HOTAS merge: get the flight controls bound and stable first, then add tracking, so a problem in one system cannot masquerade as a problem in the other.

Limitations

Merging concentrates risk as well as controls. If the feeder profile is not running, IL-2 sees quiet virtual devices and the cockpit appears dead, so build a launch order habit: feeder first, game second. Device numbers also matter — if Windows enumeration changes after a major hardware swap, check the feeder mapping before rebinding the game. And a merged setup cannot extend a device that is physically worn out; test raw hardware in joy.cpl with no feeder active when an axis misbehaves.

Return to the vJoy setup guides by game hub for the full list, and read our vJoy for DCS World setup — the merging discipline transfers directly between the two simulators.