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
- Build error on Android when using Patch And Run paired with Play Asset Delivery
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
- Copying and pasting Animator Transitions leads to unexpected behaviour
- "ShaderGraph" misses a space in the "Project Settings" section
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.