Search Issue Tracker
Won't Fix
Won't Fix in 1.7.X
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-621
Regression
No
UI Action Map's events are triggered when the it is not enabled
Reproduction steps:
1. Open the attached “ASDQWE” project”
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Press “W” key on your keyboard
5. Observe the message in the Console Window
6. Press “Esc” on your keyboard and repeat the 5th step
Expected result: No message is displayed
Actual result: “Cancel performed“ message is displayed
Reproducible with: 1.5.1 (2021.3.26f1), 1.6.1 (2021.3.26f1), 1.6.3 (2021.3.29f1, 2022.3.6f1), 1.7.0 (2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4)
Reproducible on: Intel macOS 13.5
Not reproducible on: No other environment tested
Note: If Default Map is set to UI, Player Action Map does not trigger
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
This issue is actually caused when the ** InputSystem UI Input Module component also enables all of it's actions on startup. This causes the default action map and any other action maps referenced by this component to become enabled. You can work around the issue by making setting only the map you to enabled explicitly.
Resolution Note (1.7.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
This issue is actually caused when the ** InputSystem UI Input Module component also enables all of it's actions on startup. This causes the default action map and any other action maps referenced by this component to become enabled. You can work around the issue by making setting only the map you to enabled explicitly.