Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-302
Regression
No
Keyboard InputActions stop working in another Scene when Gamepad is used in the last Scene
How to reproduce:
1. Open the “TidalWaveTom.zip” project
2. Plug the controller into the machine
3. Enter Play mode
4. Press “New Game”
5. Try using the keyboard
6. Complete the level with a controller
7. Try using the keyboard
Expected result: Keyboard input controls the character
Actual result: Keyboard input stops controlling the character
Reproducible on: 1.3.0 (2022.1.0b16)
Could not test on: 1.3.0 (2021.3.9f1), 1.4.2 (2022.1.16f1, 2022.2.0b8, 2023.1.0a10) (Script errors prevent reproduction)
Reproducible with: macOS 11.6.5 (Intel)
Notes: The “ESC” key and pause menu work when the player input stops working. The issue is present in the Editor Play mode and the Build.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
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.