overte-org
Wayland cursor capture issue
On Wayland running Overte on this commit returns:
[WARNING] [qt.qpa.wayland] Setting cursor position is not possible on wayland.
This has been an existing issue since I have started manually building Overte, however this has not been a debilitating issue until mouseLook.js was merged. Since this was merged, the mouse is never properly captured in the window, which results in the client spinning around uncontrollably.
This is the result of a native build on Arch Linux using Overte-builder
The distributed .appimage from our community chat is unaffected.
Definitely worth looking into. Meanwhile, as a workaround:
Make a file called qtlogging.ini in the same directory as interface. Put this inside:
[Rules]
qt.qpa.wayland.warning=false
It looks like there's similar problem happening on Windows with fresh settings? This needs to be invesitgated more.
I never had this on my main PC with V8_RC4, but installing it on a (fully updated) win 10 machine, the cursor was was invisible when within the main window. After installing V8_RC3 it works on both versions, so it makes sense it has to do with the default settings.
I can confirm that this happens on all platforms when there's no previous config extisting. I will have a fix today. It's a very serious issue so should we issue a hotfix when it's patched?
I think the issue patched in #629 is a different bug. A new build of Overte using the builder on the most recent commit still has this issue.
I just got this issue when using Hyprland 0.40.0. On X11/i3 it works fine.
Looks like an upstream issue. The code is still the same on the newest development version of Qt: https://github.com/qt/qtwayland/blob/c2f61bc47baacf2e6a44c6c3c4e4cbf0abfa4095/src/client/qwaylandcursor.cpp#L339 Apparently, Wayland only has "unstable" and "experimental" support for locking cursors: https://wayland.app/protocols/pointer-constraints-unstable-v1 I opened an issue on the Qt bug tracker: https://bugreports.qt.io/browse/QTBUG-127077
