UnityRef is currently in early development. Some features may be incomplete and/or not functioning.

UNITYREF

Your Pit Stop For Solving ANYTHING in Unity

ui

[Input System] UI Buttons Unresponsive with Simulator Tab Open

Solution

uguieditordevelopment workflow

Unity 6.0.x - Unity 6.3.x

Published 9 days ago

Author Profile Photo

Reviewed by _architect

Chief Editor

80 posts
Issue

 In Unity 6.0 and subsequent versions, UI buttons may fail to respond to input despite being correctly set up as children of a Canvas with an active EventSystem. This behavior occurs when the Input System prioritizes simulation over standard viewports, typically resulting in ignored click events.

Quick-Fix

UI buttons may become unresponsive in Unity 6 because the InputSystemUIInputModule incorrectly prioritizes touch input when the Simulator tab is open alongside the Game View.

Expand Analysis

The InputSystem which is enabled by default in Unity 6 includes pre-defined action maps for various input devices. A potential conflict arises when multiple input sources are perceived as active simultaneously by the InputSystemUIInputModule across different editor viewports.

When the Simulator tab is open concurrently with the GameView tab, the InputSystem may erroneously detect and prioritize touch input, even if a touch-enabled device is not actively being used or is not the intended primary input method. This misprioritization leads to UI buttons failing to register clicks or other interactions from keyboard or mouse input.

To resolve this, ensure that only the necessary viewports are active:

  1. Identify if the Simulator tab is currently open or docked in the Editor.
  2. Close the Simulator tab to ensure the InputSystem correctly processes the intended primary input for the GameView.
  3. Ensure the EventSystem object contains an InputSystemUIInputModule and that the InputActions asset is correctly assigned.

Additional Tips

  • If the issue persists, verify that the Canvas GraphicRaycaster is not blocked by a higher-depth Canvas or Panel with the “Raycast Target” property enabled.
  • Check the Input Debugger (Window > Analysis > Input Debugger) to monitor which virtual device is sending events to the Simulator.
  • Ensure that “Send Navigation Events” is enabled on the InputSystemUIInputModule if using controller or keyboard-based UI navigation.

Related Posts Haven't quite found a solution to your problem? We think these posts might help you.
[Input System] How to Disable Multi-Touch in Unity 6[Canvas System] Duplicated UI Assets: Awake Initialization Skip[Input System] OnMouseDown Fails: Why Your Clicks Aren't Registering

Content inspired by a Unity discussion post.