Fix: Unity Rapid Key Press Missed by Input.GetKeyDown

Here is how to fix Unity rapid key presses that get dropped, especially when reading input from FixedUpdate. The legacy Input class samples keys per Update; FixedUpdate ticks at a different rate.

The Symptom

Rhythm games or twitch gameplay miss inputs when the player taps fast. Single press registers; double-tap may register only once.

What Causes This

Read in FixedUpdate. GetKeyDown returns true only the frame after the press; FixedUpdate may not run on that frame.

Variable framerate. Low FPS means longer Update intervals; presses that complete within one Update are seen as one event regardless of taps.

Legacy Input polling. The legacy Input class polls; new Input System events are more reliable for rapid input.

The Fix

Step 1: Read GetKeyDown only in Update.

private bool jumpPending;

void Update()
{
    if (Input.GetKeyDown(KeyCode.Space)) jumpPending = true;
}

void FixedUpdate()
{
    if (jumpPending)
    {
        rb.AddForce(Vector3.up * jumpForce, ForceMode.Impulse);
        jumpPending = false;
    }
}

Step 2: Use new Input System with performed callbacks.

using UnityEngine.InputSystem;

[SerializeField] private InputAction jumpAction;

void OnEnable()
{
    jumpAction.performed += OnJump;
    jumpAction.Enable();
}

void OnJump(InputAction.CallbackContext ctx)
{
    if (ctx.performed) jumpPending = true;
}

Performed callbacks fire on each event regardless of frame timing; rapid taps register reliably.

Step 3: Buffer inputs for forgiveness.

private float jumpBufferUntil;

void Update()
{
    if (Input.GetKeyDown(KeyCode.Space)) jumpBufferUntil = Time.time + 0.15f;
}

void FixedUpdate()
{
    if (Time.time < jumpBufferUntil && isGrounded)
    {
        Jump();
        jumpBufferUntil = 0;
    }
}

150 ms buffer covers physics-Update sync gaps and feels responsive.

Step 4: Test at low framerate. Set Application.targetFrameRate = 30 temporarily. If rapid taps still register, your input handling is robust.

Step 5: For rhythm games, prefer event-driven new Input System. Polling cannot guarantee sub-frame timing accuracy; events do.

Understanding the issue

Input handling sits between hardware and gameplay. Hardware has its own protocol; gameplay has its own model. When these don't agree, the player perceives unresponsiveness even though every layer is technically functional.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. 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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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 Unity-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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Read input in Update. Use new Input System for rapid taps. Buffer for forgiveness. No drops.”

Related Issues

For Touch input, see Touch Not Firing. For control scheme, see Control Scheme.

Update reads. Flags consumed in FixedUpdate. Or new InputSystem callbacks. Inputs land.