Search Issue Tracker
By Design
Votes
0
Found in
2019.4.40f1
2020.3.38f1
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a9
Issue ID
UUM-13024
Regression
No
Input values are always 0 when Time.timeScale is set to 0
Reproduction steps:
1. Open the attached "9491Repro.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode
4. Click the "A" button on your keyboard
5. Observe the Console window
Expected result: Input value changes
Actual result: Input value is always 0
Reproducible with: 2019.4.40f1, 2020.3.38f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a9
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
- "Customize handled extensions" part in the External Tools settings tab is not aligned with other properties
- Editor Diagnostics foldouts do not open when clicked on the foldout title
- [UI Builder] Visual Elements are not placed at the mouse cursor position when Absolute Position Placement is enabled
- "Width" and "Height" text is misaligned with slider ends in Screen Match Mode Parameters section of Panel Settings Asset
- Editor does not quit when Editor is not in focus and any floating window is opened
Resolution Note:
Unfortunately this side effect is by design, due to GetAxis computing its value based on deltaTime of the frame, and if timeScale is set to 0 then deltaTime is also 0, meaning GetAxis will be always 0 as well.
To workaround it please use GetAxisRaw or GetKey, hope it helps.