Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.0-preview.1
Issue ID
1273033
Regression
No
[Input System] Input Action gets stuck in the "Performed" state after first activation when using Pass Through Vector2 Composite
Reproduction steps:
1. Open the attached project ("case_1273033-PerformedAction.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Press the "W" key and release it
5. Inspect the printed logs in the console
Expected result: Logs are printed only while the key is being held
Actual result: Logs continue to be printed when the key is released (action is stuck in the "Performed" phase)
Reproducible with: 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Couldn't test with 2018.4 (minimal package version needed is not supported)
Reproducible with package versions: 1.0.0-preview.5, 1.1.0-preview.1
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
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when disabling "Allow FSR2" parameter while in Play Mode with Direct3D12 set as graphics API
- Crash on vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
- Stencil buffer is incorrectly cleared across Vulkan render passes during depth-only clear operations when using CommandBuffer API
Resolution Note:
Pass-Through actions go through Started to Perform on the first value change and then remain in that state until the action is disabled. In general, phases are not all that meaningful for pass-through actions. They are mere input collectors. Polling a pass-through action overall is not that useful. It's an input sink.