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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.