Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42710
Regression
No
[Input Manager] Held down key presses are not carried over when a Scene is loaded
Reproduction steps:
1. Open the attached "repro_IN-IN-45693.zip" project
2. Open and analyze the "InputPresser" script in the project Assets folder to understand how the script behaves
3. Enter the Play Mode
4. Press and hold the right arrow key
5. Notice that the Console keeps printing the output "holding right" - that means that the right arrow key is being registered
6. While holding the right arrow key, press the "R" key to reload the scene
7. Observe the Console output
Expected result: The Console keeps printing out "holding right", as the right arrow key is still being registered
Actual result: The Console is not printing out "holding right", as the right arrow key is not being registered anymore
Reproduced with: 2021.3.28f1, 2022.3.4f1, 2023.1.4f1, 2023.2.0a23
Reproduced on: Windows 10
Note:
- If you keep holding the right arrow key after reloading the scene, and press "P", the scene will be paused, proving that the right key is not being registered, as the script is written to only execute the pause if the right arrow key is not being pressed when pressing the "P" button
- Reproducible in Player
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.