Search Issue Tracker
Fixed in 1.0.0-preview.6
Votes
0
Found in [Package]
1.0
Issue ID
1205285
Regression
No
[InputSystem] Problem with button state after deactivating and reactivating an action map
-e: The first time the actions maps are switched everything works fine. But then, the actions are only triggered after pressing the corresponding key 2 times.
-repro:
--press play
--click on the gameobject "state machine". The state variable should have the value 1.
--click on the game window to get focus
--press A. The State variable in StateManagement has now the value 2.
--press B. The State variable in StateManagement has now the value 1.
--press A. NOTICE: Nothing happens.
--press A again. The state variable in StateManagement has now the value 2.
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.0.0-preview.6):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1064