Fix: Unity Input System On-Screen Stick Not Tracking

You drop OnScreenStick onto a Canvas, build to mobile, the stick visually moves but the player doesn’t. The Control Path needs to match the action binding exactly, multi-touch may need enabling, and behavior mode picks whether the stick teleports.

The Symptom

OnScreenStick widget moves visually with the touch, but no Move action fires. Or stick produces input but second OnScreenStick (look) doesn’t. Or the stick jumps to wherever you tap, not back to its origin.

What Causes This

OnScreenStick simulates a virtual gamepad device that the new Input System sees as a control. The simulation works only if:

1. The Control Path field is set to a valid path.
2. Your InputAction has a binding to the same path.
3. Multi-touch is enabled when you have multiple sticks.

The Fix

Step 1: Control Path. Select the OnScreenStick GameObject. Inspector → OnScreenStick → Control Path. Click the small selector and pick <Gamepad>/leftStick for the left stick. For the right stick on a different OnScreenStick, pick <Gamepad>/rightStick.

Step 2: Action binding. Open your Input Actions asset. Move action → Add Binding (or 2D Vector Composite) → pick path <Gamepad>/leftStick. Now the action listens to the same virtual stick the on-screen widget drives.

InputActionAsset:
  Player Map:
    Move (Value, Vector2):
      <Gamepad>/leftStick
      [Composite WASD] (optional, for editor testing)

Step 3: Multi-Touch. On both OnScreenStick components: tick “Use Multi-Touch”. Without it, the second touch is captured by the system but assigned to whichever stick’s touchable area happens to win first.

Step 4: Behaviour mode. Relative locks the visual stick to its anchor; finger movement past the radius gets clamped. Exact moves the stick origin to the touch start point — useful for “tap-anywhere-to-move” designs where the player doesn’t need to look.

Touch Simulation

For Editor testing without a touch device, enable EnhancedTouch and use mouse simulation:

using UnityEngine.InputSystem.EnhancedTouch;
EnhancedTouchSupport.Enable();
TouchSimulation.Enable();

Now mouse drags simulate single-touch in the editor for sanity checks before deploying.

Verifying

Window → Analysis → Input Debugger. Run on device or with mouse simulation. Drag the on-screen stick. The Gamepad device should appear in the device list with leftStick / rightStick values changing live.

If the device shows but values don’t change, the Control Path is wrong. If the device doesn’t show, OnScreenStick isn’t enabled or its GameObject is hidden.

Understanding the issue

Input bugs are perceptible to players even when the gameplay code is correct. A 16ms delay that the profiler considers fine is the difference between 'responsive' and 'sluggish'. The fix is often in the input pipeline, not the gameplay.

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

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

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

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

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.

“Path on stick. Path on action. Multi-touch on. Sticks track.”

Related Issues

For Input rebind not persisting, see rebind persistence. For touch screen UI events not firing, see UI button.

Path matches. Multi-touch on. The stick drives.