Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.6.1
Issue ID
ISXB-567
Regression
No
Processor values do not move along with the Processors in the list when using the up and down arrow buttons and the value is selected to edit
How to reproduce:
1. Open any project with Input System Installed
2. Create an "Input Actions" Asset
3. Open it and create an "Action Map" on the left-hand side
4. Create a "Processor" for it that has an input value for example "Scale"
5. Change the value to something different and set it
6. Select the said value and use the arrows on the right to move the "Processor" up or down
Actual result: "Processors" are moved up and down, but the field of the other "Processor" is now the same as the other one. This can be true of different "Processors" are also used. If enter is then pressed, value returns to normal
Expected result: When the "Processors" are moved up or down, the values do not show up in other "Processors" in the list, but the selected value also moves up along with the original "Processor" it actually edits
Reproducible with: 1.6.1 (2021.3.28f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a22)
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
- Rich Text color tag does not apply when color is set by name
- The caret (text cursor) symbol does not move one word when the "Option" key and arrow keys are used to move the caret
- Vertical mapping of most characters is incorrect when using a Texture on each character
- Crash on Animator_CUSTOM_SetFloatString when a Float parameter for an Animator is set in Play Mode after changing the RuntimeAnimatorController
- Particle System Force Field behaves differently when in Play Mode than it does in Edit Mode
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.