vJoy vs PPJoy: The Replacement, Explained
If you found an old flight-sim or racing guide that tells you to install PPJoy, you are reading history. vJoy was created to replace PPJoy — that is not marketing language added later. The vJoy project description on SourceForge says it was “originally designed to provide an open-source replacement for PPJoy,” creating virtual joystick devices that the system sees as standard joysticks while a feeder application writes the position data. This comparison explains what PPJoy was, why it faded, and why vJoy is the tool to install today.
What PPJoy was
PPJoy — short for Parallel Port Joystick — began in an era when connecting a joystick, a radio-control transmitter, or a homemade controller through the PC parallel port was a practical hobbyist route. It let software present virtual joystick devices to Windows so simulators and games could read inputs that did not come from a normal USB joystick. For its time that solved a real problem: getting custom and radio-control hardware into simulators that only understood joysticks.
The context matters because almost everything around PPJoy has changed. Parallel ports disappeared from mainstream PCs, Windows driver signing became stricter, and 64-bit Windows made the old workarounds fragile. Historically, PPJoy on 64-bit Windows belonged to the test-mode era — the period when unsigned or test-signed drivers needed Windows test signing enabled before they would load. That was tolerable for enthusiasts at the time. It is a poor foundation for a modern Windows 10 or Windows 11 setup.
What vJoy changed
vJoy keeps the useful idea — a virtual joystick the system treats as a standard DirectInput joystick — and rebuilds it for the signed-driver era. Instead of relying on legacy parallel-port thinking, vJoy is a Windows virtual joystick driver whose devices are configured with vJoyConf and fed by a separate feeder application through vJoyInterface.dll. The driver alone does nothing; the feeder writes axes, buttons, and POV data, and the game reads the result as an ordinary joystick.
The documented specification is also far beyond what most PPJoy-era setups offered. Each vJoy device can expose up to 8 axes (X, Y, Z, Rx, Ry, Rz and two sliders), up to 128 buttons, and up to 4 POV hat switches, with up to 16 virtual devices documented in SDK-based tools. That headroom is why dual-stick HOSAS setups, merged HOTAS devices, button boxes, and scripted feeders standardised on vJoy rather than trying to revive PPJoy.
| Point | PPJoy | vJoy (Shaul lineage) |
|---|---|---|
| Status | Legacy and unmaintained | Builds still distributed; newest signed build is BrunnerInnovation 2.2.2.0 (2023) |
| Era | Parallel-port and test-mode era | Signed-driver era: attestation / EV signing on current builds |
| Devices & inputs | Limited legacy virtual joysticks | Up to 16 devices; up to 8 axes, 128 buttons, 4 POVs per device |
| Feeding model | Legacy feeder tools | Any feeder via vJoyInterface.dll — Gremlin, UCR, FreePIE, custom code |
| Windows today | Not a sensible choice on modern 64-bit Windows | Brunner 2.2.2.0 explicitly supports Windows 10 and 11 |
Why there are no PPJoy download links here
You will not find a PPJoy download link on this page, and that is deliberate. PPJoy is unmaintained, no live canonical project page was found for it in our research, and pointing readers at random repackaged installers of an obsolete kernel driver would be irresponsible. Kernel drivers run with deep system access; an old, unverified copy from a file locker is exactly the kind of download this site exists to steer people away from. If a guide links you to one, treat that guide as out of date.
The safe path is the replacement, not the original. Our download page lists the three verified vJoy builds with file sizes and SHA-256 hashes we checked ourselves: BrunnerInnovation 2.2.2.0 for Windows 10/11, the njz3 2.2.1.1 force-feedback fork, and the original-line 2.1.9.1 as the compatibility fallback. If you are unsure which one fits your feeder, read Which vJoy Build Should You Download? before installing anything.
If an old guide sent you here
Most PPJoy instructions appear inside otherwise useful guides for radio-control simulators, DIY controllers, and older flight sims. You can usually translate them directly: where the guide says to create a PPJoy virtual joystick and feed it, create a vJoy device in vJoyConf with the axes and buttons the guide needs, then use a current feeder to write the same data. Joystick Gremlin and UCR are the two feeders most readers end up with — our comparison of Joystick Gremlin vs UCR explains which feeder model fits which job, and neither of them can do its vJoy work without the driver underneath.
One warning when translating old guides: ignore any step that tells you to enable test mode, disable driver signature enforcement, or disable Secure Boot as a routine first step. Those steps belonged to the PPJoy era. Current vJoy builds are signed precisely so you do not need them. Treat any instruction to weaken Windows security for a joystick driver as a last-resort risk to question, not a setup step to follow blindly.
Verdict
Use vJoy. PPJoy is the predecessor, not a competitor. There is no modern use case where seeking out PPJoy beats installing a signed vJoy build: vJoy offers more devices, more buttons, maintained signing, and a live feeder ecosystem. Keep PPJoy in your vocabulary only so you can recognise outdated guides — and translate them. For the full set of head-to-heads, see the Alternatives & Comparisons hub, and for gamepad-style Xbox emulation (a different job entirely) see vJoy vs ViGEmBus vs XOutput.