Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wayland dont lock mouse #16367

Open
Caua726 opened this issue Dec 2, 2024 · 1 comment
Open

Wayland dont lock mouse #16367

Caua726 opened this issue Dec 2, 2024 · 1 comment

Comments

@Caua726
Copy link

Caua726 commented Dec 2, 2024

Quick summary

When try to use mouse as gamepad, on wayland only the mouse are not locked on the screen, but if try to use
env QT_QPA_PLATFORM=xcb rpcs3
works perfectly

Details

In Wayland, the mouse does not lock to the application window, causing the cursor to move outside the RPCS3 screen during gameplay. This behavior disrupts games that rely on mouse input.

Workaround:
Running RPCS3 with env QT_QPA_PLATFORM=xcb rpcs3 works as expected, indicating the issue is specific to Wayland's handling of input locking.

Attach a log file

RPCS3.log.gz
RPCS3.log

Attach capture files for visual issues

No response

System configuration

OS: Arch
WM: KWin (Wayland)
DE: KDE Plasma 6
CPU: Ryzen 5 5600X (Single Channel)
GPU: RX 560
RAM: 8GB DDR4
Vulkan: 1.3.289 - RADV [Mesa 24.2.7-arch1.1]

Other details

No response

@layercak3
Copy link

Qt probably needs an API that better matches how pointer locking is supposed to be done on Wayland. You can't do it by repeatedly warping the cursor on the global coordinate space with QCursor::setPos. https://bugreports.qt.io/browse/QTBUG-116493
RPCS3 could probably do something with QNativeInterface to bypass Qt limitations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants