Can a 15-pin game-port joystick work over USB? Choose the right active adapter, avoid VGA cables, test in joy.cpl and fix Windows 11 faults.
Yes—on a Windows PC, most standard analogue game-port joysticks can be used for flight simulation through an active game-port-to-USB converter that presents itself as a USB HID controller. A passive 15-pin-to-USB cable will not work, and proprietary digital or force-feedback models may need model-specific hardware or remain incompatible.
This advice covers PC flight simulation in general, including Microsoft Flight Simulator, FSX, X-Plane, Prepar3D and FlightGear. The simulator normally sees the converter as a generic USB controller rather than by the joystick’s original make and model.
Do not assume the same converter will work on Xbox or PlayStation. Consoles and individual games restrict which USB controllers they accept, so a generic HID adapter is primarily a Windows PC solution.
Is a 15-pin VGA-to-USB adapter the same as a game-port adapter?
No. VGA and the PC joystick game port both have 15 contacts, but their layouts, signals and purposes are completely different.
- PC game port: a DA-15 connector with two rows of contacts, arranged 8+7. It is often loosely called DB-15. The joystick cable usually has the male plug with exposed pins.
- VGA: a higher-density DE-15 connector with three rows of five contacts. It carries video, not joystick axes or buttons.
A device advertised as a 15-pin VGA-to-USB adapter is video hardware and cannot operate a game-port joystick. Likewise, a product described only as a 15-pin D-sub-to-USB adapter is too ambiguous: the listing must explicitly say that it converts a legacy PC joystick or game controller to USB.
A gender changer or cable that merely makes the plugs fit does not translate the electrical signals. The conversion requires electronics.
What game-port-to-USB adapter do I need?
You need an active converter that reads the joystick’s analogue signals and reports them to Windows as a standard USB HID game controller.
| Connection method | Expected result | Verdict |
|---|---|---|
| Active game-port-to-USB HID converter | Reports supported axes and buttons as a generic Windows controller | Best choice for an ordinary analogue joystick |
| Passive 15-pin-to-USB cable | Provides no signal conversion | Will not work |
| USB-to-VGA display adapter | Transfers video rather than controller input | Wrong connector type and function |
| USB MIDI adapter or game-port MIDI cable | Handles MIDI data rather than joystick positions | Not a joystick converter |
| Model-specific or programmable converter | May decode a proprietary digital protocol | Choose only if the exact joystick is supported |
| Legacy sound card with a native game port | Depends on a suitable expansion slot and compatible Windows drivers | Usually impractical on a modern PC |
Some working converters look like simple cables because the electronics are hidden inside the USB plug or an inline housing. Judge a USB controller adapter by its stated function, not its appearance.
Before buying, check that it:
- connects a legacy joystick to a USB host, rather than operating in the opposite direction;
- uses the standard USB HID game-controller class and does not depend on an abandoned proprietary driver;
- supports the number of axes and buttons you need;
- has an analogue mode or explicitly supports the joystick’s exact digital protocol;
- supplies the game-port power expected by the joystick, where required; and
- provides the correct two-row female socket for the usual male joystick plug.
A mistake we see constantly is buying an adapter solely because both ends fit. A converter intended for two axes and two buttons may detect the joystick yet omit its throttle, rudder or additional controls.
How can I tell whether my old joystick is compatible?
A conventional analogue joystick is the strongest candidate; a digital, highly programmable or force-feedback game-port model is much less certain.
- Identify the exact model: the same game-port connector was used for standard analogue hardware and proprietary digital devices. The plug alone does not prove compatibility.
- Count the controls: the original game-port design provided up to four analogue axes and four button inputs across the interface. Hardware with more controls often used special encoding that a basic converter cannot interpret.
- Check for mode switches: some joysticks could operate in different analogue or digital modes. The converter and joystick must use compatible modes.
- Treat force feedback separately: a generic converter normally exposes only axes and buttons. An external power supply may power the motors, but it does not recreate the proprietary force-feedback command protocol.
- Inspect the hardware: worn potentiometers produce drift, spikes and unstable centring. USB conversion cannot repair noisy sensors.
- Consider attached throttles or pedals: daisy-chained controls may use all four standard axes or a manufacturer-specific wiring arrangement. Confirm that the converter supports the complete layout.
If the joystick has ordinary X and Y movement, no more than four analogue axes and a small number of buttons, an active analogue converter has a reasonable chance of working. If its original documentation describes digital operation, programmability or a proprietary interface, require explicit model support.
Do I need a generic USB joystick driver in Windows 11?
No separate generic USB joystick driver should be required when the converter is HID-compliant; Windows 11 and Windows 10 use their built-in USB game-controller drivers.
The original Windows 95 or Windows 98 software for the game-port joystick is not useful once an adapter handles the conversion. Do not install an unrelated driver package simply because the controller appears under a generic name such as USB Gamepad.
If Windows reports an unknown USB device, concentrate on the converter, its mode and the USB connection. An old joystick driver cannot make a passive cable perform analogue-to-USB conversion. An adapter that requires discontinued vendor software is a poor choice for a modern Windows installation.
How do I connect and configure the joystick?
- Identify the hardware. Record the joystick’s full model name, axes, buttons, operating mode and any external power requirement.
- Set the converter mode. If the adapter has a selector for different joystick layouts, choose the closest match before connecting it to USB. Unplug and reconnect the adapter after changing modes.
- Connect the 15-pin plug first. With the converter unplugged from USB, attach the joystick and secure its thumbscrews. Connect any original power supply the joystick requires, then plug the converter into the PC.
- Open Windows Game Controllers. Press
Win+R, enterjoy.cpland press Enter. A generic device name is normal. If no controller appears here, the flight simulator will not receive its input through the standard Windows controller system. - Test every control. Open the controller’s properties and watch the test display while moving the stick, throttle, twist grip or pedals through their full travel. Press every button and note any missing, stuck or coupled inputs.
- Calibrate where available. Use the Windows calibration option if the converter exposes one. Move every axis through its complete range and leave the controls centred when requested. Our detailed calibration and dead-zone steps cover drift, poor centring and restricted travel.
- Create simulator bindings. Assign the horizontal axis to roll or ailerons, the vertical axis to pitch or elevator, and any throttle or rudder control to the corresponding analogue axis command. Do not map an analogue axis to separate left, right, up or down button commands. Our flight-simulator axis-mapping guidance explains the usual primary control assignments.
Will a generic USB controller work in every flight simulator?
Most Windows PC flight simulators accept standard HID game controllers, but the converted joystick may have no ready-made control profile.
Microsoft Flight Simulator 2024 and 2020, FSX, X-Plane, Prepar3D and FlightGear can use ordinary controller axes and buttons when the software detects them. Expect to bind a generic converted device manually, reverse any axis that moves in the wrong direction and remove duplicate assignments from other controllers.
A blank or incomplete preset does not necessarily mean the joystick is unsupported. For the modern Microsoft simulators, follow our manual controller-profile steps for MSFS 2024 and 2020.
What about RealFlight and other RC flight simulators?
Compatibility with RealFlight depends on the exact edition and the controller interface it expects.
Some older editions were designed around a supplied InterLink interface, so a generic game-port-to-USB converter is not a guaranteed substitute even when Windows detects it. If the specific edition accepts an ordinary Windows joystick or gamepad, test the converted controller in joy.cpl and then map it in the software; otherwise, use the interface required by that edition.
Why is my game-port-to-USB joystick not working?
The decisive test is joy.cpl: no response there indicates a connection or conversion problem, while clean Windows input points to the simulator’s profile and bindings.
| Symptom | Likely cause | What to do |
|---|---|---|
Nothing appears in joy.cpl | Passive, VGA or MIDI cable; failed converter; wrong mode; USB connection problem | Confirm that the adapter explicitly provides HID joystick conversion, set its mode while unplugged and try a direct PC USB port |
| Windows shows an unknown USB device | Converter fault, unsupported converter driver or unreliable USB connection | Reconnect it without a hub and verify its Windows support; the original joystick driver will not fix this |
| The controller appears, but no axes move | Digital joystick on an analogue-only adapter, missing power or incorrect converter mode | Check exact-model compatibility, power requirements and the adapter’s selector setting |
| Only some axes or buttons work | Converter input limit or proprietary button encoding | Try the appropriate converter mode or use hardware that supports the full control layout |
| Axes jump, drift or will not centre | Incorrect calibration, unsuitable converter range or worn potentiometers | Recalibrate and add only enough dead zone to stop residual movement; persistent spikes indicate a hardware fault |
| An axis is reversed or controls the wrong function | Incorrect simulator binding or adapter mode | Assign the correct analogue command, use the simulator’s reverse option or select a more suitable adapter mode |
| It works in Windows but not in the simulator | Blank profile, missing bindings, disabled controller input or duplicate assignments | Create a dedicated profile and temporarily disconnect other controllers while testing |
| Force feedback is absent | The converter exposes ordinary HID input but not the original force-feedback protocol | Expected with a generic adapter; model-specific conversion is required |
Once every required axis moves cleanly in joy.cpl, the game-port-to-USB conversion has succeeded. Reinstalling drivers will not repair missing simulator bindings, and simulator settings cannot recover an axis or button that the converter never reports.
Is converting a game-port joystick worthwhile?
Conversion is sensible when the stick is mechanically sound, uses standard analogue signalling and needs only the axes and buttons supported by an inexpensive active adapter.
- Choose conversion when: you value the joystick’s feel, its sensors are stable, its controls fit within the converter’s limits and Windows can use the adapter without special software.
- Choose replacement when: the joystick uses an unsupported digital protocol, relies on force feedback, has noisy potentiometers, needs a costly custom converter or lacks enough controls for the aircraft you fly.
A converter cannot improve the underlying sensors; high USB resolution claims do not restore a worn potentiometer or add buttons the adapter cannot read. When replacement is the practical option, a modern budget USB flight joystick with dependable Windows support will usually be easier to configure and provide more usable controls.