Fix: Unity Input Actions Asset Saved But Not Reloading

Here is how to fix Unity New Input System where you edit a .inputactions asset, change a binding, but the game continues using the old binding. The asset window seems to accept the change, the inspector shows it, yet input behaves as if nothing happened. Two distinct stages have to complete: saving the asset, and refreshing whatever holds a reference to it.

The Symptom

You add a new action or rebind an existing one in the Input Actions editor window. Press Play. The new binding does nothing; the old one still works. The asset file modification timestamp on disk is unchanged. Or, if you use a generated C# wrapper, the new action does not show up in autocomplete.

What Causes This

Save Asset not pressed. Edits in the Input Actions editor window stay in memory until you click Save Asset (or enable Auto Save). Standard Ctrl-S in the rest of Unity does not trigger this.

Generate C# Class not enabled. Without it, code-side wrappers are stale. References resolve to old method signatures.

PlayerInput holds old reference. A PlayerInput component caches a reference to the action map at start. Hot edits do not propagate.

Asset re-import skipped. If you copied a .inputactions file in via the file system without restarting Unity, the editor may not pick up the new bindings until reimport.

The Fix

Step 1: Save the asset. In the Input Actions editor window, click Save Asset (top-right). Or check Auto Save next to it so future edits save automatically.

Step 2: Enable Generate C# Class. Select the .inputactions asset in the Project window. In the inspector, check Generate C# Class. Set the file name (e.g., PlayerControls) and namespace, then click Apply. A C# file is generated alongside the asset.

// Generated wrapper usage
using UnityEngine;
using UnityEngine.InputSystem;

public class PlayerController : MonoBehaviour
{
    private PlayerControls controls;

    void Awake()
    {
        controls = new PlayerControls();
        controls.Player.Jump.performed += ctx => OnJump();
    }

    void OnEnable()  { controls.Player.Enable(); }
    void OnDisable() { controls.Player.Disable(); }

    void OnJump() { Debug.Log("Jumped"); }
}

Step 3: Refresh PlayerInput at runtime if needed.

playerInput.actions.Disable();
playerInput.actions.Enable();

This forces a re-resolution of bindings. Useful when you allow runtime rebinding and want the new binding to take effect immediately.

Step 4: Re-import the asset. If you copied the .inputactions file in externally, right-click in the Project window and choose Reimport. The editor reads the new content and regenerates the C# wrapper.

Step 5: Use Auto Save while iterating. Top-right of the Input Actions window, enable Auto Save. Every edit is committed to disk immediately. Tradeoff is no “cancel” option; if you do not want this, save manually.

Runtime Rebinding Persistence

If you let players rebind keys at runtime, persist the bindings via SaveBindingOverridesAsJson and reload via LoadBindingOverridesFromJson:

// Save
string json = playerInput.actions.SaveBindingOverridesAsJson();
PlayerPrefs.SetString("bindings", json);

// Load on next session
var json = PlayerPrefs.GetString("bindings", "");
if (!string.IsNullOrEmpty(json))
    playerInput.actions.LoadBindingOverridesFromJson(json);

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Save Asset is its own button. Generate C# Class regenerates on save. PlayerInput re-resolves on Disable/Enable. Three handles for one workflow.”

Related Issues

For control scheme switching, see Input System Control Scheme Switching. For inputs not arriving at all, see New Input System Actions Not Updating.

Click Save Asset. Generate C# Class. Disable/Enable to refresh. Bindings update.