Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.0-pre.2
1.11.2
1.12.0
7000.0.0
Issue ID
ISXB-1326
Regression
Yes
After deleting all Control Schemes in Input Actions Editor, dropdown title will still show last deleted Control Scheme as selected one
Steps to reproduce:
- Open a Unity Project
- Create a new Input Action Asset via Assets > Create > Input Actions
- Open the new Input Action Asset in Input Actions Editor by double clicking on it
- Observe that the Control Scheme dropdown says 'No Control Schemes' as none have been created
- Click on the dropdown and add a new Control Scheme. Name it 'TestControlScheme'
- Open the dropdown again and click 'Delete Control Scheme' to delete the TestControlScheme
Actual results: Even though the last Control Scheme was deleted, the dropdown still says 'TestControlScheme' until you either re-open the window or add a new control scheme.
Expected results: The dropdown should say 'No Control Schemes' after the last Control Scheme is deleted. This is how it was before the FAV.
Reproducible with versions: 7000, 1.11.2, 1.12.0, 1.8.0-pre.2
Not reproducible with versions: 1.8.0-pre.1
Can't test with versions: -
Tested on (OS): Windows 11
Notes: -
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.