[GH-ISSUE #1978] [Bug]: Mouse input only moves view slightly; cannot rotate freely; cursor remains visible: Destiny Rising #1311

Closed
opened 2026-03-03 19:05:43 +03:00 by kerem · 4 comments
Owner

Originally created by @DaviSina on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1978

Describe the bug

•	The game natively detects keyboard input correctly (movement, menu navigation, etc.).
•	Mouse clicks are registered, but treated as touch input (clicks generate touch events).
•	The onscreen cursor remains visible during gameplay; it doesn’t hide or get captured.
•	Turning / rotating view with the mouse is severely limited: only small head movements.

Steps to reproduce

Because of the cursor’s presence and the low movement deltas, the game assumes touch input rather than continuous mouse movement, leading to a restricted “look” behavior. I have disabled all keymapping in PlayCover, because I already use the game’s native keyboard+mouse support and keymapping conflicts with it. I cannot selectively enable keymapping only for “mouse look” without impacting other native controls (that are already working).

Expected behaviour

When using mouse + keyboard (with keymapping turned off), the game should:
a) Hide and capture the cursor during gameplay (especially when in control/look mode).
b) Translate mouse movements into full “look around” camera rotation, not just small head movement or minor deltas.
c) Treat mouse clicks as proper mouse buttons, not as touch/tap input.

Thanks for your time and for developing PlayCover — really appreciate it.

Crash log


What version of PlayCover are you using?

3.1.0

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

  • Yes my issue is written in English
Originally created by @DaviSina on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1978 ### Describe the bug • The game natively detects keyboard input correctly (movement, menu navigation, etc.). • Mouse clicks are registered, but treated as touch input (clicks generate touch events). • The onscreen cursor remains visible during gameplay; it doesn’t hide or get captured. • Turning / rotating view with the mouse is severely limited: only small head movements. ### Steps to reproduce Because of the cursor’s presence and the low movement deltas, the game assumes touch input rather than continuous mouse movement, leading to a restricted “look” behavior. I have disabled all keymapping in PlayCover, because I already use the game’s native keyboard+mouse support and keymapping conflicts with it. I cannot selectively enable keymapping only for “mouse look” without impacting other native controls (that are already working). ### Expected behaviour When using mouse + keyboard (with keymapping turned off), the game should: a) Hide and capture the cursor during gameplay (especially when in control/look mode). b) Translate mouse movements into full “look around” camera rotation, not just small head movement or minor deltas. c) Treat mouse clicks as proper mouse buttons, not as touch/tap input. Thanks for your time and for developing PlayCover — really appreciate it. ### Crash log ```shell ``` ### What version of PlayCover are you using? 3.1.0 ### 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:05:43 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@joshrad-dev commented on GitHub (Sep 24, 2025):

I think a potential solution would be if PlayCover captured mouse input only in the touch input and doesn't pass it into DR as mouse input as well, then we can just map touch controls to KBM

<!-- gh-comment-id:3330381547 --> @joshrad-dev commented on GitHub (Sep 24, 2025): I think a potential solution would be if PlayCover captured mouse input *only* in the touch input and doesn't pass it into DR as mouse input as well, then we can just map touch controls to KBM
Author
Owner

@gao2linda commented on GitHub (Sep 28, 2025):

been having the same issue

<!-- gh-comment-id:3342128308 --> @gao2linda commented on GitHub (Sep 28, 2025): been having the same issue
Author
Owner

@viatearz commented on GitHub (Oct 9, 2025):

I think a potential solution would be if PlayCover captured mouse input only in the touch input and doesn't pass it into DR as mouse input as well, then we can just map touch controls to KBM

Now you can disable mouse input and use keymapping only in the latest Nightly version of PlayCover.
see https://github.com/PlayCover/PlayCover/pull/1979

<!-- gh-comment-id:3383683839 --> @viatearz commented on GitHub (Oct 9, 2025): > I think a potential solution would be if PlayCover captured mouse input _only_ in the touch input and doesn't pass it into DR as mouse input as well, then we can just map touch controls to KBM Now you can disable mouse input and use keymapping only in the latest Nightly version of PlayCover. see https://github.com/PlayCover/PlayCover/pull/1979
Author
Owner

@viatearz commented on GitHub (Oct 9, 2025):

The game has incomplete keyboard and mouse support, since this feature was mainly designed for the MuMu Android Emulator and has never been tested on iOS devices.
If you really want this feature, you should send feedback to the game developers and ask them to support playing on an iPad with keyboard and mouse.

<!-- gh-comment-id:3383688678 --> @viatearz commented on GitHub (Oct 9, 2025): The game has incomplete keyboard and mouse support, since this feature was mainly designed for the MuMu Android Emulator and has never been tested on iOS devices. If you really want this feature, you should send feedback to the game developers and ask them to support playing on an iPad with keyboard and mouse.
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#1311
No description provided.