InputSystem Changelog

1.8.2 #

Added

• Documentation to clarify effects of ordering of interactions when a single action has multiple interactions ISXB-221.
• Additional tests for UI Input default actions (Navigate, Submit, Scroll etc.)
• Documented behaviour of InputSystemUIInputModule automatically enabling the UI action map. ISXB-621

Fixed

• Fixed an issue where UI interactions would not function without setting up a project-wide actions asset in Project Settings. Default UI actions are now created on the fly, if no asset for project-wide actions has been set. ISXB-811.
• Physical keyboards used on Android/ChromeOS could have keys "stuck" reporting as pressed after a long press and release ISXB-475.
• NullReferenceException thrown when right-clicking an empty Action Map list in Input Actions Editor windows ISXB-833.
• Fixed an issue where System.ObjectDisposedException would be thrown when deleting the last ActionMap item in the Input Actions Asset editor.
• Fixed DualSense Edge's vibration and light bar not working on Windows
• Fixed Project-wide Actions asset failing to reload properly after deleting project's Library folder.
• Fixed an issue where System.InvalidOperationException is thrown when entering PlayMode after deleting an ActionMap from Project-wide actions and later resetting it.
• Fixed OnPointerClick events not propagating to child objects unless the child also handled OnPointerDown events ISXB-857.
• Fixed Input Actions Editor window resource leak that could result in unexpected exceptions ISXB-865.
• Fixed an issue where UI integration would throw exceptions when Project-wide Input Actions asset did not contain the implicitly required UI action map or was missing any of the required actions. Additionally this fix now also generates warnings in the console for any divergence from expected action configuration or lack of bindings in edit-mode.
• Fixed a minor issue when importing InputAction assets that could result in unexpected logging during internal package validation checks.

Changed

• For Unity 6.0 and above, when an EventSystem GameObject is created in the Editor it will have the InputSystemUIInputModule by default if the Input System package is installed and enabled.