[GH-ISSUE #1483] [Game Support]: Wuthering Waves: mouse randomly fails to pan then zooms in and out instead. #910

Closed
opened 2026-03-03 19:02:03 +03:00 by kerem · 23 comments
Owner

Originally created by @bxb6668 on GitHub (May 23, 2024).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1483

https://apps.apple.com/us/app/wuthering-waves/id6475033368

Current issues

  • App fails to install
  • App fails to open
  • App crashes randomly during usage
  • App experiences graphical issues or broken UI
  • App fails to connect to servers
  • Other

More details

After playing WuWa for a few minutes, the mouse panning fails. I will have pressed option a few times and back to use cursors by then. I have attached my keymap below.
WutheringWavesKeymap.playmap.zip

Mouse zooms in and out instead of panning. Only restart has fixed my problem.
Playcover Nightly: Version 3.0.0 (751)

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 @bxb6668 on GitHub (May 23, 2024). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1483 ### App Store link https://apps.apple.com/us/app/wuthering-waves/id6475033368 ### Current issues - [ ] App fails to install - [ ] App fails to open - [ ] App crashes randomly during usage - [ ] App experiences graphical issues or broken UI - [ ] App fails to connect to servers - [X] Other ### More details After playing WuWa for a few minutes, the mouse panning fails. I will have pressed option a few times and back to use cursors by then. I have attached my keymap below. [WutheringWavesKeymap.playmap.zip](https://github.com/PlayCover/PlayCover/files/15422312/WutheringWavesKeymap.playmap.zip) Mouse zooms in and out instead of panning. Only restart has fixed my problem. Playcover Nightly: Version 3.0.0 (751) ### 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:03 +03:00
Author
Owner

@kang49 commented on GitHub (May 23, 2024):

I confirm this issue is true.

<!-- gh-comment-id:2128022986 --> @kang49 commented on GitHub (May 23, 2024): I confirm this issue is true.
Author
Owner

@LeeeSe commented on GitHub (May 24, 2024):

The temporary solution is to press M to open the map and return to normal after shaking the mouse.

<!-- gh-comment-id:2128790405 --> @LeeeSe commented on GitHub (May 24, 2024): The temporary solution is to press M to open the map and return to normal after shaking the mouse.
Author
Owner

@kang49 commented on GitHub (May 24, 2024):

The temporary solution is to press M to open the map and return to normal after shaking the mouse.

Do you think this's PlayCover's issue or at the game? But i never seen this issue on iOS platform.

<!-- gh-comment-id:2128912179 --> @kang49 commented on GitHub (May 24, 2024): > The temporary solution is to press M to open the map and return to normal after shaking the mouse. Do you think this's PlayCover's issue or at the game? But i never seen this issue on iOS platform.
Author
Owner

@Kxcnw commented on GitHub (May 24, 2024):

The temporary solution is to press M to open the map and return to normal after shaking the mouse.

Do you think this's PlayCover's issue or at the game? But i never seen this issue on iOS platform.

probably playcover, i remember this happening to me a while back on genshin

<!-- gh-comment-id:2129025988 --> @Kxcnw commented on GitHub (May 24, 2024): > > The temporary solution is to press M to open the map and return to normal after shaking the mouse. > > Do you think this's PlayCover's issue or at the game? But i never seen this issue on iOS platform. probably playcover, i remember this happening to me a while back on genshin
Author
Owner

@kang49 commented on GitHub (May 25, 2024):

I found a temporary solution. Just press "CMD+R" to rotate screen and it's work.

<!-- gh-comment-id:2131163152 --> @kang49 commented on GitHub (May 25, 2024): I found a temporary solution. Just press "CMD+R" to rotate screen and it's work.
Author
Owner

@ngocsok commented on GitHub (May 25, 2024):

I found a temporary solution. Just press "CMD+R" to rotate screen and it's work.

Same problem here. I know where the problem lies:

  1. The problem occurs because the user sets the attack key as the left mouse button. During combat, the player will continuously press the left mouse button to attack. Meanwhile, moving the screen means the left mouse button is always held in the middle of the screen, this causes the same left mouse button to have 2 active functions, this conflict causes Playcover to fail and it will Overwriting one more time means it will be like swiping two fingers on the touch screen, which causes the screen to zoom in and out without moving the camera.
  2. You just need to set the attack key to another button, for example, attack will usually be the E button and never left click the mouse without releasing the mouse. This will make it harder for errors to appear.
  3. As for developer WuWa, it looks like they are going to support mouse and keyboard for mobile devices so you can see that even if you don't map or install any buttons for the game, still there but keyboard operation can be used. For example, buttons 1,2,3 switch characters, T button to launch an air hook, M button to open the map... And similarly with the Option or Alt button used to release the mouse, but the problem is Both Playcover and WuWa use this button, this makes it so that when you press it to release the mouse both Wuwa and Playcover will release the mouse at the same time, mostly Playcover will release but sometimes the game recognizes the mouse release key, immediately This means you will not be able to move the mouse pointer anymore.
    Those are 2 issues that I think are happening at the same time causing the game to only work for a few minutes then the mouse won't work.
    I will try your method, hope it helps me temporarily.
    Hope there is a radical solution to this.
<!-- gh-comment-id:2131258204 --> @ngocsok commented on GitHub (May 25, 2024): > I found a temporary solution. Just press "CMD+R" to rotate screen and it's work. Same problem here. I know where the problem lies: 1. The problem occurs because the user sets the attack key as the left mouse button. During combat, the player will continuously press the left mouse button to attack. Meanwhile, moving the screen means the left mouse button is always held in the middle of the screen, this causes the same left mouse button to have 2 active functions, this conflict causes Playcover to fail and it will Overwriting one more time means it will be like swiping two fingers on the touch screen, which causes the screen to zoom in and out without moving the camera. 2. You just need to set the attack key to another button, for example, attack will usually be the E button and never left click the mouse without releasing the mouse. This will make it harder for errors to appear. 3. As for developer WuWa, it looks like they are going to support mouse and keyboard for mobile devices so you can see that even if you don't map or install any buttons for the game, still there but keyboard operation can be used. For example, buttons 1,2,3 switch characters, T button to launch an air hook, M button to open the map... And similarly with the Option or Alt button used to release the mouse, but the problem is Both Playcover and WuWa use this button, this makes it so that when you press it to release the mouse both Wuwa and Playcover will release the mouse at the same time, mostly Playcover will release but sometimes the game recognizes the mouse release key, immediately This means you will not be able to move the mouse pointer anymore. Those are 2 issues that I think are happening at the same time causing the game to only work for a few minutes then the mouse won't work. I will try your method, hope it helps me temporarily. Hope there is a radical solution to this.
Author
Owner

@kang49 commented on GitHub (May 25, 2024):

Summary of the issue:

Steps to reproduce the bug:

  1. Assign the attack action to the Left Mouse Button (LMB).
  2. Press and hold LMB to charge the attack.
  3. Press and hold the Option key (while still holding LMB).
  4. Release the LMB to stop charging the attack.
  5. Press and hold the Option key again, and move the mouse to change the view while the pointer is visible.
  6. Press the Option key to hide the pointer; the bug will occur immediately.

Steps to fix the issue:

  1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves).
  2. Click anywhere once.
  3. Press the Option key again to hide the pointer, and everything should return to normal.

What I believe needs to be fixed in PlayCover is that when the Option key is pressed, all previously held keys should be reset. No command should remain active after pressing the Option key to show or hide the pointer.

Video demonstration:

https://youtu.be/6bSCDkJ41BU

<!-- gh-comment-id:2131284182 --> @kang49 commented on GitHub (May 25, 2024): # Summary of the issue: ### Steps to reproduce the bug: 1. Assign the attack action to the Left Mouse Button (LMB). 2. Press and hold LMB to charge the attack. 3. Press and hold the Option key (while still holding LMB). 4. Release the LMB to stop charging the attack. 5. Press and hold the Option key again, and move the mouse to change the view while the pointer is visible. 6. Press the Option key to hide the pointer; the bug will occur immediately. ### Steps to fix the issue: 1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves). 2. Click anywhere once. 3. Press the Option key again to hide the pointer, and everything should return to normal. What I believe needs to be fixed in PlayCover is that when the Option key is pressed, all previously held keys should be reset. No command should remain active after pressing the Option key to show or hide the pointer. ### Video demonstration: [https://youtu.be/6bSCDkJ41BU](https://youtu.be/6bSCDkJ41BU)
Author
Owner

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

Since it has native mouse button support you don't have to map attack key right? Just remove mapping of left mouse button and issue should be resolved?

<!-- gh-comment-id:2131300767 --> @XuYicong commented on GitHub (May 25, 2024): Since it has native mouse button support you don't have to map attack key right? Just remove mapping of left mouse button and issue should be resolved?
Author
Owner

@kang49 commented on GitHub (May 25, 2024):

Since it has native mouse button support you don't have to map attack key right? Just remove mapping of left mouse button and issue should be resolved?

Yes, i did it right now.

<!-- gh-comment-id:2131301411 --> @kang49 commented on GitHub (May 25, 2024): > Since it has native mouse button support you don't have to map attack key right? Just remove mapping of left mouse button and issue should be resolved? Yes, i did it right now.
Author
Owner

@bxb6668 commented on GitHub (May 25, 2024):

Steps to fix the issue:

  1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves).
  2. Click anywhere once.
  3. Press the Option key again to hide the pointer, and everything should return to normal.

This didn't fix mine.
When I press the Option key, the view doesn't move if i don't press the moust button.

Also, I dunno if something changed;
attack button without mapping works fine with touchpad but not with bluetooth mouse.

<!-- gh-comment-id:2131371338 --> @bxb6668 commented on GitHub (May 25, 2024): > ### Steps to fix the issue: > 1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves). > 2. Click anywhere once. > 3. Press the Option key again to hide the pointer, and everything should return to normal. This didn't fix mine. When I press the Option key, the view doesn't move if i don't press the moust button. Also, I dunno if something changed; attack button without mapping works fine with touchpad but not with bluetooth mouse.
Author
Owner

@kang49 commented on GitHub (May 25, 2024):

Steps to fix the issue:

  1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves).
  2. Click anywhere once.
  3. Press the Option key again to hide the pointer, and everything should return to normal.

This didn't fix mine. When I press the Option key, the view doesn't move if i don't press the moust button.

Also, I dunno if something changed; attack button without mapping works fine with touchpad but not with bluetooth mouse.

Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by XuYicong.

<!-- gh-comment-id:2131373079 --> @kang49 commented on GitHub (May 25, 2024): > > ### Steps to fix the issue: > > > > 1. Press the Option key (you'll notice that even though the mouse button isn't pressed, the view still moves). > > 2. Click anywhere once. > > 3. Press the Option key again to hide the pointer, and everything should return to normal. > > This didn't fix mine. When I press the Option key, the view doesn't move if i don't press the moust button. > > Also, I dunno if something changed; attack button without mapping works fine with touchpad but not with bluetooth mouse. Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by [XuYicong](https://github.com/XuYicong).
Author
Owner

@ngocsok commented on GitHub (May 25, 2024):

When it was first launched, Wuwa integrated mouse operations with the right mouse button for surfing and the left mouse button for attack. But in the latest update they removed the mouse action, which means you will be forced to assign attacks to the mouse, causing the camera movement error to appear more often. Also I tried with Genshin, Wuwa and Punishing Gray Raven. The error occurs with all 3 of these games.

<!-- gh-comment-id:2131374032 --> @ngocsok commented on GitHub (May 25, 2024): When it was first launched, Wuwa integrated mouse operations with the right mouse button for surfing and the left mouse button for attack. But in the latest update they removed the mouse action, which means you will be forced to assign attacks to the mouse, causing the camera movement error to appear more often. Also I tried with Genshin, Wuwa and Punishing Gray Raven. The error occurs with all 3 of these games.
Author
Owner

@bxb6668 commented on GitHub (May 25, 2024):

Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by XuYicong.

I started playing with the middle mouse button mapped for attack. The issue occured again

<!-- gh-comment-id:2131406065 --> @bxb6668 commented on GitHub (May 25, 2024): > Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by [XuYicong](https://github.com/XuYicong). I started playing with the middle mouse button mapped for attack. The issue occured again
Author
Owner

@kang49 commented on GitHub (May 25, 2024):

Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by XuYicong.

I started playing with the middle mouse button mapped for attack. The issue occured again

Why you use MMB? I mean you remove all mapping that can atk and by default WutheringWaves already can atk by LMB.

<!-- gh-comment-id:2131408950 --> @kang49 commented on GitHub (May 25, 2024): > > Try removing the left mouse button (LMB) mapping first and wait for this issue to be resolved. You can re-map it later as suggested by [XuYicong](https://github.com/XuYicong). > > I started playing with the middle mouse button mapped for attack. The issue occured again Why you use MMB? I mean you remove all mapping that can atk and by default WutheringWaves already can atk by LMB.
Author
Owner

@bxb6668 commented on GitHub (May 25, 2024):

Why you use MMB? I mean you remove all mapping that can atk and by default WutheringWaves already can atk by LMB.

By default my mouse cannot atk. I think they removed that functionality in recent patches.

<!-- gh-comment-id:2131411367 --> @bxb6668 commented on GitHub (May 25, 2024): > Why you use MMB? I mean you remove all mapping that can atk and by default WutheringWaves already can atk by LMB. By default my mouse cannot atk. I think they removed that functionality in recent patches.
Author
Owner

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

When the issue happens, if you press CMD+K twice, would it fix it?

<!-- gh-comment-id:2131411549 --> @XuYicong commented on GitHub (May 25, 2024): When the issue happens, if you press CMD+K twice, would it fix it?
Author
Owner

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

This didn't fix mine. When I press the Option key, the view doesn't move if i don't press the moust button.

Your issue is probably different from his. Can you provide a screen recording of it? Or describe what actions have you taken to trigger the issue. When you say "pan" is it like holding left mouse button and drag, or solely move without pressing anything? With cursor shown or hidden? I believe you don't drag screen and press option in normal play like he does right?

<!-- gh-comment-id:2131436516 --> @XuYicong commented on GitHub (May 25, 2024): > This didn't fix mine. When I press the Option key, the view doesn't move if i don't press the moust button. > Your issue is probably different from his. Can you provide a screen recording of it? Or describe what actions have you taken to trigger the issue. When you say "pan" is it like holding left mouse button and drag, or solely move without pressing anything? With cursor shown or hidden? I believe you don't drag screen and press option in normal play like he does right?
Author
Owner

@bxb6668 commented on GitHub (May 25, 2024):

Your issue is probably different from his. Can you provide a screen recording of it? Or describe what actions have you taken to trigger the issue. When you say "pan" is it like holding left mouse button and drag, or solely move without pressing anything? With cursor shown or hidden? I believe you don't drag screen and press option in normal play like he does right?

Sorry. I was not very clear. I don't know how to trigger it. But it happens after minutes of playing.

I just meant the view doesn't move when i don't press any button with cursor shown (which I activated with option key).
I press option to go to cursor mode, click some stuff and press option again to go normal keymapped gaming mode.

<!-- gh-comment-id:2131459182 --> @bxb6668 commented on GitHub (May 25, 2024): > Your issue is probably different from his. Can you provide a screen recording of it? Or describe what actions have you taken to trigger the issue. When you say "pan" is it like holding left mouse button and drag, or solely move without pressing anything? With cursor shown or hidden? I believe you don't drag screen and press option in normal play like he does right? Sorry. I was not very clear. I don't know how to trigger it. But it happens after minutes of playing. I just meant the view doesn't move when i don't press any button with cursor shown (which I activated with option key). I press option to go to cursor mode, click some stuff and press option again to go normal keymapped gaming mode.
Author
Owner

@LeeeSe commented on GitHub (May 25, 2024):

Why don‘t you open the map and shake the mouse at will, and everything will return to normal?

<!-- gh-comment-id:2131620254 --> @LeeeSe commented on GitHub (May 25, 2024): Why don‘t you open the map and shake the mouse at will, and everything will return to normal?
Author
Owner

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

Why don‘t you open the map and shake the mouse at will, and everything will return to normal?

Can you send me a demo on how to do it?
Following is my attempt. It changed nothing.
I tried both shaking the map with/without my alt active. with/without holding my left mouse button.
2024-05-25 22-24-02.mkv.zip

<!-- gh-comment-id:2131999840 --> @bxb6668 commented on GitHub (May 26, 2024): > Why don‘t you open the map and shake the mouse at will, and everything will return to normal? Can you send me a demo on how to do it? Following is my attempt. It changed nothing. I tried both shaking the map with/without my alt active. with/without holding my left mouse button. [2024-05-25 22-24-02.mkv.zip](https://github.com/PlayCover/PlayCover/files/15445845/2024-05-25.22-24-02.mkv.zip)
Author
Owner

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

Same issue here, none of the solutions described here work. Neither pressing option again and wiggling the mouse nor opening the map screen nor pressing CMD+R twice to rotate the screen.

EDIT: Pressing CMD+K twice (so opening and closing keymap editor) works for me

EDIT2: Worked a few times but not consistently...

<!-- gh-comment-id:2132160166 --> @Brawl345 commented on GitHub (May 26, 2024): Same issue here, none of the solutions described here work. Neither pressing option again and wiggling the mouse nor opening the map screen nor pressing CMD+R twice to rotate the screen. EDIT: Pressing CMD+K twice (so opening and closing keymap editor) works for me EDIT2: Worked a few times but not consistently...
Author
Owner

@ghdic commented on GitHub (Jun 3, 2024):

In the case of Genshin Impact, clicking RMB btn solves this problem, but Wuthering Waves has not yet found a solution. The only solution is to turn the game off and on again.

<!-- gh-comment-id:2144893533 --> @ghdic commented on GitHub (Jun 3, 2024): In the case of Genshin Impact, clicking RMB btn solves this problem, but Wuthering Waves has not yet found a solution. The only solution is to turn the game off and on again.
Author
Owner

@buzuosheng commented on GitHub (Nov 25, 2024):

same as I. The only solution is to turn the game off and on again. And some times solved with unknown reasons

image

my keyboard mapping

<!-- gh-comment-id:2496781801 --> @buzuosheng commented on GitHub (Nov 25, 2024): same as I. The only solution is to turn the game off and on again. And some times solved with unknown reasons <img width="1918" alt="image" src="https://github.com/user-attachments/assets/8597e5c4-71fb-4c94-8262-30c37ff03441"> my keyboard mapping
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/PlayCover#910
No description provided.