Search Issue Tracker
By Design
Votes
2
Found in [Package]
1.3.0
Issue ID
ISXB-123
Regression
No
[Input System] Events from non-default Action Maps are invoked when UI Toolkit elements are added to the Scene
Reproduction steps:
1. Open the attached "1388797.zip" project
2. Open the "New Scene" Scene
3. Enter the Play mode
4. Left-click on the Scene view window
5. See that three "player event" messages are displayed in the Console
6. Enable the "UI" GameObject
7. Left-click on the Scene view window
8. Observe the Console
Expected result: Three "player event" messages are displayed
Actual result: Three "player event" messages and three "UI scheme event that should not be sent" warnings are displayed
Reproducible with: 1.2.0, 1.3.0 (2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11)
Could not test with: 1.2.0, 1.3.0 (2019.4.38f1) (UI Toolkit unavailable)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
When UI module is active, relevant actions are also active, which is by design. Correct way is to only have character controls or UI controls active at a same time and never both.