Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.2.0f1
2023.3.0a14
6000.0.0b11
Issue ID
UUM-56651
Regression
No
Device Simulator does not register keyboard inputs when in Play Mode
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Focus on the Device Simulator window and press any key on the keyboard
Expected result: Error message “ANY KEY DOWN“ is printed every time the “Esc“ key is pressed
Actual result: Keyboard input is not registered and an Error message “ANY KEY DOWN“ does not get printed
Reproducible with: 2023.2.0f1, 2023.3.0a14
Could not test with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1 (Assets\Scripts\UI\Controls\CustomControl.cs(7,6): error CS0246: The type or namespace name 'UxmlElementAttribute' could not be found)
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: macOS Intel 14.0 (23A344) sonoma
Note:
- Does not reproduce with the Game view window
Comments (1)
-
LMorelPro
Dec 11, 2024 12:40
I know this issue has been tagged as "Won't Fix", but have you found any way to make this work ?
I'm working on a mobile project and we need to use the simulator for testing. The same issue is happening on our Windows machines but not on our macOS ones.
Any answer would be appreciated, even if it's only confirming that there is no way to fix this issue.
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
- Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
Resolution Note:
Thank you for reporting this issue. We’ve investigated and determined that we are unable to address this specific problem at this time. We value your feedback and will consider this issue for potential inclusion in future updates.