You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: