Fix: Pygame Joystick Not Detected on Startup

Here is how to fix pygame joystick not detected on startup. You plug in your gamepad, run your pygame game, and pygame.joystick.get_count() returns 0. The controller works in other applications. You call pygame.joystick.init() explicitly and it still returns 0. The joystick is physically connected but pygame cannot see it. This is almost always an initialization timing issue.

The Symptom

pygame.joystick.get_count() returns 0 despite a gamepad being physically connected and recognized by the operating system. Creating a pygame.joystick.Joystick(0) object raises an IndexError or pygame.error. The controller works in other games and shows up in the OS device manager.

What Causes This

Checking count before event pump. Pygame’s joystick subsystem relies on SDL’s event system to detect devices. Until events are pumped at least once after initialization, the device list may be empty. Calling get_count() immediately after init() without pumping returns stale (empty) data.

joystick.init() not called. While pygame.init() initializes the joystick subsystem, if you use selective initialization (e.g., only pygame.display.init()), the joystick subsystem remains uninitialized.

Joystick subsystem quit and not restarted. Some code patterns from older tutorials call pygame.joystick.quit() and pygame.joystick.init() every frame to detect hot-plugged devices. If quit is called without a matching init, the subsystem stays dead.

Platform permissions (Linux). On Linux, joystick devices are at /dev/input/js*. The user running the game needs read access. Without permissions, SDL cannot open the device and reports 0 joysticks.

Controller not supported by SDL. Very old or exotic controllers without SDL Game Controller DB mappings may not be recognized. They exist as raw HID devices but SDL does not enumerate them as joysticks.

The Fix

Step 1: Initialize and pump before checking.

import pygame

pygame.init()
pygame.event.pump()  # Process initial device events

joystick_count = pygame.joystick.get_count()
print(f"Joysticks found: {joystick_count}")

if joystick_count > 0:
    joy = pygame.joystick.Joystick(0)
    joy.init()
    print(f"Controller: {joy.get_name()}")

The pygame.event.pump() call processes pending SDL events including device enumeration. Without it, get_count() may return 0 on the first frame.

Step 2: Handle hot-plug with JOYDEVICEADDED.

import pygame

pygame.init()
joysticks = {}

def game_loop():
    running = True
    while running:
        for event in pygame.event.get():
            if event.type == pygame.QUIT:
                running = False

            elif event.type == pygame.JOYDEVICEADDED:
                joy = pygame.joystick.Joystick(event.device_index)
                joy.init()
                joysticks[joy.get_instance_id()] = joy
                print(f"Connected: {joy.get_name()}")

            elif event.type == pygame.JOYDEVICEREMOVED:
                if event.instance_id in joysticks:
                    del joysticks[event.instance_id]
                    print("Controller disconnected")

            elif event.type == pygame.JOYBUTTONDOWN:
                print(f"Button {event.button} pressed")

game_loop()

JOYDEVICEADDED fires both at startup (for already-connected devices) and when new devices are plugged in. This pattern handles both cases without polling get_count().

Step 3: Avoid the quit/init anti-pattern.

# WRONG: Old hot-plug pattern (causes detection issues)
def update():
    pygame.joystick.quit()    # Kills all joystick state
    pygame.joystick.init()    # Re-enumerates (unreliable)
    count = pygame.joystick.get_count()

# CORRECT: Use events for hot-plug (see Step 2 above)

The quit/init pattern was a workaround for SDL 1.x. Modern pygame (SDL 2.x) uses events for hot-plug. The old pattern can actually cause detection failures.

Step 4: Check Linux permissions. On Linux, joystick devices at /dev/input/js* require read access. Add your user to the input group: sudo usermod -a -G input $USER, then log out and back in.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Pygame, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Pygame. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Pygame-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Pygame, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Pygame joystick detection is event-driven. Pump events first, then query. For hot-plug, listen for JOYDEVICEADDED instead of polling get_count every frame.”

Related Issues

For audio initialization issues in pygame, see general pygame initialization patterns. For game loop timing issues that can affect event processing, ensure your loop calls pygame.event.get() or pygame.event.pump() every frame.

Init, pump events, then check count. Use JOYDEVICEADDED for hot-plug. Never quit/init per frame.