Search Issue Tracker
Fixed
Fixed in 2022.2.0f1, 2023.1.0a3
Votes
0
Found in
2022.2.0b9
2023.1.0a16
Issue ID
UUM-18496
Regression
No
[UI Toolkit] Mouse events not triggered in build when Active Input Handling is set to both
*Steps to repro:*
# download the attached project
# Make sure you can build a player (windowsstandalone)
# Hit play in the gameview and click and hover the label ( some logs will appear and clicks events are listed)
# now build a player and once its built, do the same
*Result:*
Events are not registered by clicking on the label.
!label.gif!
*Workarounds:*
- Adding a script with an empty OnGUI method seems to fixes the problem.
- Adding a standaloneinputmethod as a compoent on the UI Document fixes the problem.
*Notes (From Benoit):*
I'm pretty sure the problem comes from some optimization in our Build code that detects there's no GUI active in the game, and seeing that the new Input is also present (because you have "Both" selected) it probably discards the old input events. On the other hand UIToolkit detects that the old input also available and it tries to consume the GUI events, which aren't there.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Dynamic lights still show up in the Profiler consuming time when "Main Light" and "Additional Lights" are disabled in the UniversalRP-HighQuality asset
- Sprite Asset changes are unsaved after updating sprite atlas
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
Resolution Note (fix version 2023.1.0a3):
Was already fixed by https://ono.unity3d.com/unity/unity/pull-request/143646/_/uitoolkit/bugfix/1411711-pointerdeltayinverted-2