mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 08:15:56 +03:00
[GH-ISSUE #772] [Bug]: All games do not support keyboard input #362
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ZombiejsC on GitHub (Feb 2, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/772
Describe the bug
Computer:Macbook Air M2 chip,16GB memory 256GB Solid State Drive Ventura 13.2
Playcover version:2.0.4. Genshin Impact version:3.4.0
In the setting interface of playcover, I'm sure to open the keyboard mapping and mouse mapping. But in the game, I can't use the option key to switch the mouse mode, and I can't use the shortcut of command+k to open the keyboard mapping editing. But the original keyboard mapping can work. It can create a keyboard mapping, but it can't change the keys (no matter what key is pressed, the computer doesn't respond). Even command+q can't exit the game, You can only force the app to close
Steps to reproduce
no more details, I do hope this bug can be solved
Expected behaviour
The bug can be fixed
Crash log
No response
What version of PlayCover are you using?
2.0.4
What version of macOS are you using?
Ventura (macOS 13)
Issue Language
@FlyMeToTheMoonAndLetMePlayAmongTheStars commented on GitHub (Feb 4, 2023):
Have you tried restarting your computer?
@ZombiejsC commented on GitHub (Feb 5, 2023):
omg, it is quite weird, I have restart my computer several times ago, but this time the bug was fixed!Anyway,thx for ur idea!!XD
@AayushGTM6693 commented on GitHub (Nov 6, 2023):
I have the same issue. how to deal it with ??