Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.1.1f1
2021.2
Issue ID
1326491
Regression
No
All except last of the inputs that are being held are lost when another scene is loaded
Reproduction steps:
1. Open attached project "New Unity Project.zip"
2. Open "Scene1" scene
3. Enter Play Mode
4. Press and hold the space bar
5. Press and hold the right arrow key
6. Wait until the next level loads
Expected result: "JumpButton" is not 0
Actual result: "JumpButton" is 0
Reproducible with: 2018.4.33f1, 2019.4.25f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Resolution Note:
This issue is By Design in most cases. The fact that it is inconsistent, but has a workaround in specific situations will not be fixed. The possible fix is risky and could cause further regressions.