Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.2f1
Issue ID
UUM-72071
Regression
No
Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
Steps to reproduce:
- Create a 3D URP Project (Or create a Project and Install the Input System Package)
- Navigate to Project Settings > Input System Package
- Create atleast 2 Action Maps
- Select the second Action Map in the list
- Create an Action, open the dropdown for than Action and select "<No Binding>"
- In the Binding Properties on the left click on the dropdown menu for the field "Path"
Actual results: The currently selected Action Map switches to the first one in the list on the left side, the first Action in that Action Map is also automatically selected (This is more relevant when editing the Binding Path of an Action if the first Action Map is already selected)
Expected results: The currently selected Action Map stays selected
Reproducible with versions: 6000.0.2f1 (Input System 1.8.2/1.8.1)
Can’t test with versions: 2021.3.38f1, 2022.3.28f1, 2023.1.20f1, 2023.2.20f1 (No editing of the Input Actions Asset in Project Settings)
Tested on (OS): Windows 11
Notes:
- Performing the same steps and editing the Input Actions Asset outside Project Settings will not reproduce the issue
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
- Incorrect rotations on bones when importing FBX animations with a Humanoid Rig
- Render Graph Viewer “Pass List” section is flickering when resizing vertically and the Render Graph Viewer window is docked
- Render Graph Viewer Capture button plays the click animation but does not do anything when the Capture button is pressed with the “Enter” key on the keyboard
- UI Builder Scrollview is unable to scroll all the way down when the window is downsized vertically
- Celestial bodies order remains unchanged when the Distance setting is modified
Resolution Note:
This bug is known internally and is planned to be fixed in the next release (1.8.3)