Search Issue Tracker
Fixed
Fixed in 1.13.1, 7000.0.0
Votes
0
Found in [Package]
1.11.2
7000.0.0
Issue ID
ISXB-1351
Regression
Yes
Action Property Interactions for selected Action do not update on project-wide setting changes, until unselected
Steps to reproduce:
- Open a Unity Project
- Create a new Input Action Asset via GameObject > Create > Input Actions
- Open the Input Action Asset in Input Actions Editor by double clicking on it
- Create an Action Map using the '+'
- Click on the newly created Action
- Under the Interactions Action Property, add a Hold property using + > Hold
- Ensure that Default is checked (should be by default)
- Click on 'Open Input Settings'
- If required to use the menu, create an Input Settings Asset
- Change 'Default Hold Time' from 0.4 to 0.2
- Observe the Interaction in the Input Action Editor
Actual results: The Hold Time does not update straight away when the Default Hold Time is set. You have to click out of the Action and back into it for it to update
Expected results: The Hold Time updates automatically as soon as the Default Hold Time is changed.
Reproducible with versions: 7000, 1.11.2, 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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.