Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-763
Regression
Yes
Scheme Name in Add Control Scheme menu gets reset after a device is added to the Scheme
Reproduction steps:
1. Open the attached “BugRepro“ project
2. In the Project window, open “Assets/New Controls” Asset
3. In the New Controls (Input Actions) window, open “No Control Schemes“ dropdown menu and select “Add Control Scheme…“
4. In the Add control scheme popup window, enter any Scheme Name
5. Add any device and its usage to the list
6. Observe the Scheme Name
Expected result: The Scheme Name does not change
Actual result: The Scheme Name resets to default
Reproducible with: 1.8.0-pre.2 (2022.3.0f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4)
Not reproducible with: 1.7.0, 1.8.0-pre.1 (2022.3.18f1, 2023.2.7f1, 2023.3.0a14), 1.8.0-pre.2 (2021.3.34f1, 2022.2.21f1)
Reproducible on: Windows 11, macOS 13.6.3 (Intel) (by user)
Not reproducible on: No other environment tested
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note (fix version 1.9.0):
Fixed in upcoming Input System version 1.8.3