Search Issue Tracker
Fixed in 1.2.0
Votes
1
Found in [Package]
1.1.0-pre.6
Issue ID
1367556
Regression
Yes
Input Action ReadValue<float> always returns zero when called from FixedUpdate()
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Press the Play button and click into the Game view to focus
4. Press the Spacebar key
5. Observe the Console
6. In the Hierarchy window, select the GameObject "Cube"
7. In the Inspector view, under the component "Controller (Script)", uncheck the "Read In Update" checkbox
8. Repeat steps 3-5
Expected result: after pressing Spacebar, "value 1" is logged to the Console in both instances
Actual result: after pressing Spacebar, "value 1" is not logged to the Console when Read In Update is disabled, despite the correct "Action performed" log
Reproducible with: 1.1.0-pre.6, 1.1.1 (2019.4.31f1, 2020.3.21f1, 2021.1.26f1, 2021.2.0b16, 2022.1.0a12)
Not reproducible with: 1.1.0-pre.5 (2019.4.31f1, 2020.3.21f1, 2021.1.26f1, 2021.2.0b16, 2022.1.0a12)
Comments (1)
-
pitchblende
Oct 14, 2021 20:39
Watching.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.2.0):
Fixed in Input System 1.2.0