starred/PlayCover

Fork 0

mirror of https://github.com/PlayCover/PlayCover.git synced 2026-04-26 00:05:52 +03:00

[GH-ISSUE #1493] [Bug]: Wuthering waves - Phantom keymapping #921

New issue

Closed

opened 2026-03-03 19:02:09 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 19:02:09 +03:00

Owner

Originally created by @kryptofaz on GitHub (May 26, 2024).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1493

Describe the bug

I had a keymap i had imported that i was using with WW. When i started to edit the keymap i noticed that pressing a key would click a point on the screen where there was no key mapped to that section. I've tried uninstalling the game, deleting all data, installed a different nightly build, reset the keymap from the settings, yet still even with no keymap imported some of the old keymaps are lingering. I can't use new keymaps because pressing the keys will trigger the same old phantom spots.
I've used nightly builds 623 and 752 and its doing the same thing on both. The only thing i haven't done is uninstalled playcover completely by dragging it to the trashcan

Please help

Steps to reproduce

Expected behaviour

Crash log

No response

What version of PlayCover are you using?

Nightly/beta (please specify build number)

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

Yes my issue is written in English

Originally created by @kryptofaz on GitHub (May 26, 2024). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1493 ### Describe the bug I had a keymap i had imported that i was using with WW. When i started to edit the keymap i noticed that pressing a key would click a point on the screen where there was no key mapped to that section. I've tried uninstalling the game, deleting all data, installed a different nightly build, reset the keymap from the settings, yet still even with no keymap imported some of the old keymaps are lingering. I can't use new keymaps because pressing the keys will trigger the same old phantom spots. I've used nightly builds 623 and 752 and its doing the same thing on both. The only thing i haven't done is uninstalled playcover completely by dragging it to the trashcan Please help ### Steps to reproduce na ### Expected behaviour na ### Crash log _No response_ ### What version of PlayCover are you using? Nightly/beta (please specify build number) ### What version of macOS are you using? Sonoma (macOS 14) ### Issue Language - [X] Yes my issue is written in English

kerem

2026-03-03 19:02:09 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@XuYicong commented on GitHub (May 26, 2024):

WuWa natively processes some keys, including left mouse button for attack, M for map and J for task, and more. You must be triggering an attack by clicking left mouse button.

@XuYicong commented on GitHub (May 26, 2024): WuWa natively processes some keys, including left mouse button for attack, M for map and J for task, and more. You must be triggering an attack by clicking left mouse button.

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@kryptofaz commented on GitHub (May 26, 2024):

I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely

@kryptofaz commented on GitHub (May 26, 2024): I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@XuYicong commented on GitHub (May 26, 2024):

I think the "old keymap" you describe is just the native keyboard support of the game. The game will soon release a Mac port and it would fully support keyboard by then.

Or you can try disable keymap in settings, or remove playtools completely. That would disable the keymapping function of playcover.

@XuYicong commented on GitHub (May 26, 2024): I think the "old keymap" you describe is just the native keyboard support of the game. The game will soon release a Mac port and it would fully support keyboard by then. Or you can try disable keymap in settings, or remove playtools completely. That would disable the keymapping function of playcover.

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@Shaynou commented on GitHub (Jun 21, 2024):

I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely

Hello, I have exactly the same problem here. Did you find a solution to assign Q for another key without tiggers the echo skill? Thank you

@Shaynou commented on GitHub (Jun 21, 2024): > I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely Hello, I have exactly the same problem here. Did you find a solution to assign Q for another key without tiggers the echo skill? Thank you

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@kryptofaz commented on GitHub (Jun 21, 2024):

Unfortunately no :(
Makes it almost impossible to play. Waiting to see if the next version of WuWa fixes it. Lets see
On Jun 21, 2024 at 4:15 AM -0400, Shaynou @.***>, wrote:

I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely
Hello, I have exactly the same problem here. Did you find a solution to assign Q for another key without tiggers the echo skill? Thank you
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@kryptofaz commented on GitHub (Jun 21, 2024): Unfortunately no :( Makes it almost impossible to play. Waiting to see if the next version of WuWa fixes it. Lets see On Jun 21, 2024 at 4:15 AM -0400, Shaynou ***@***.***>, wrote: > > I'm not even using the mouse. Its just that a couple of keys that i had mapped are somehow 'stuck' in the same part of the screen. I had assigned Q for the echo ability, then i moved it to the Ultimate position, but hitting Q still tiggers the echo. Even if theres no mapping there. Its like PlayCover itself has the keymap for a couple keys somewhere in its memory and i'm trying to figure out how to erase the keymap completely > Hello, I have exactly the same problem here. Did you find a solution to assign Q for another key without tiggers the echo skill? Thank you > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you authored the thread.Message ID: ***@***.***>

kerem commented

2026-03-03 19:02:10 +03:00

Author

Owner

@MEMORIEmusic commented on GitHub (Jul 19, 2024):

I think the "old keymap" you describe is just the native keyboard support of the game. The game will soon release a Mac port and it would fully support keyboard by then.

Or you can try disable keymap in settings, or remove playtools completely. That would disable the keymapping function of playcover.

Wuthering Waves has in-built partial keyboard and mouse support separate to PlayCover. This in-game mapping has been done by Kuro Games themselves and can't be changed(as of game ver 1.1)

@MEMORIEmusic commented on GitHub (Jul 19, 2024): > I think the "old keymap" you describe is just the native keyboard support of the game. The game will soon release a Mac port and it would fully support keyboard by then. > > > > Or you can try disable keymap in settings, or remove playtools completely. That would disable the keymapping function of playcover. Wuthering Waves has in-built partial keyboard and mouse support separate to PlayCover. This in-game mapping has been done by Kuro Games themselves and can't be changed(as of game ver 1.1)