Search Issue Tracker
Won't Fix
Won't Fix in 1.5.X
Votes
0
Found in [Package]
1.4.4
1.5.0
Issue ID
ISXB-419
Regression
No
Setting InputActionReference doesn't work when it has already been set
Reproduction steps:
1. Open the attached project “InputSystem”
2. Enter Play mode
3. Select the "Test" GameObject in the Hierarchy
4. Click "Set And Log Action 1"
5. Click "Set And Log Action 2"
Expected result: "Test1" and "Test2" is logged in the Console
Actual result: "Test1" is logged twice
Reproducible with: 1.4.4 (2020.3.46f1, 2021.3.20f1), 1.5.0 (2022.2.10f1, 2023.1.0b7, 2023.2.0a5)
Reproducible on: macOS 12.4 (Intel), Win 10
Note from the user report:
"The reason is that the input action cached in the input action reference is not emptied when setting new values.
If it's prohibited to do that, the method should send an error."
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
- [UI Toolkit] Bindings do not work when custom list is used
- VFX warning and simulation error when using a specific Custom Attribute configuration
- Resizing Device Simulator window affects the uGUI Canvas size
- Font Asset Creator does not support Multi Atlas Texture while it is supported by Font Assets
- Dark patches are present when using APV and GI
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.5.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.