Search Issue Tracker
Won't Fix
Won't Fix in 1.6.X
Votes
0
Found in [Package]
1.6.1
Issue ID
ISXB-566
Regression
No
Adding Processors to Value Action Types is misleading when using certain Control Types
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. Set "Action Type" to "Value"
5. Set "Control Type" to "Bone" and try to add a "Processor" with the "" button
Actual result: Hovering over the "" button shows a tooltip to add the "Processor", the button is enabled, and no indication that this action is unavailable is present. The only time the user is informed that this action is not available is when the "Processor" is added with a different "Control Type" and then changed to a type with which the processor is not compatible. The "Control Types" affected: touch, quaternion, pose, integer, eyes, double, digital, bone
Expected result: The action to add a "Processor" is either disabled or other indication of the problem is present and the user is not left thinking that this button just doesn't work
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.
Resolution Note (1.6.X):
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.