AppUI: unresponsive UI caused by EventSystem [IN-96493]

Unity Engine
, , ,
1

When using the AppUI package, import the Navigation sample, open the respective scene, attach an EventSystem to the UIDocument, and press play: Sample broken, UI is not responding to anything. Disabling the event system fixes the issue. Reported under IN-96493

2

Hello @Fribur !

Have you tried to add an input module along with the EventSystem component?

In the EventSystem component there is a Add Default Input Modules button. It should automatically add either a InputSystemUIInputModule (if you are using the new Input System) or a Standalone Input Module (if you are using the old InputManager) component on the same GameObject.

Without this Input Module, Input events wont be converted into UI-Toolkit input events and no interaction is possible with a UIDocument.

image
image554Ă—154 11.4 KB

With the New Input System

image
image1100Ă—886 105 KB

With the Old InputManager

image
image558Ă—214 14.5 KB

3

„Yes“…In the project where I ran into the issue I do have the input module added. For IN-96493 I may have forgotten this (cannot check right now), but please do not dismiss IN-96493 because of that. The issue remains valid: enabling/disabling the Event System triggers/resolves the issue in my main project. In all projects, I only use the new Input System (Not „old“ or „both“). I should maybe add that in the project where I ran into this, AppUI navigation works just fine with EventSystem added, until I open a Modal popup. After that Game UI is broken and can only be fixed by domain reload or Unity restart. No such issue when using „Tray“ popup instead of „Modal“

4

I indeed forgot in IN-96493 the Input Module…sorry about that (was in a rush to get the repro out), however the reported bug still persists after adding it: You can click the “Test Me” button once: a modal popup opens…and after dismissing it that’s it: “Test Me” button / UI is not responding anymore to any input. It starts responding again when EventSystem is deactivated (or domain reload, restarting Unity)

5

Hello, sorry for the delay.

Can you confirm this issue has been fixed in recent patch version of Unity?

It should be fixed in:

  • 6000.0.42f1
  • 6000.1.0b10
  • 6000.2.0a6
1 Like
6

Indeed, confirmed to work now in 6000.0.43f1. Thanks for addressing this so swiftly!

1 Like