-
Notifications
You must be signed in to change notification settings - Fork 217
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
[Feature Request] Support Wine's native wayland driver #1107
Comments
hmmm looks like wine is complaining that gamescope doesn’t implement Not sure if that is the sole reason wayland wine isn’t running w/ gamescope…
OR a partial solution (would only work in nested sessions, on wayland hosts):
|
Since I won't be creating a new issue, I don't feel too bad tagging some potential parties of interest. Not requesting the feature here, it's just the data for posterity. If you are one of the tagged, please disregard if occupied or simply uninterested. Apologies in advance for pinging. Barebones UGLY HACKY diff for getting a window running in the post below. TL;DR in the end. @Joshua-Ashton @emersion @romangg @sharkautarch Here are the findings: 0 (skip if caught up). Originally this was about announcing that Wine waylanddrv wasn't rendering in Gamescope due to missing wl_subcompositor. See the reg edit above to enable on newer Wine.
Additionally, after applying a hack to proceed, same throw in the lines:
TL;DR. 1.Nested already works; 2.wl_subcompositor is missing; 3/5.zwp_pointer_constraints_v1 implementation is needed; 4.There's a C++ runtime throw in MouseCursor::paint; 6.Text and window elements flicker and black textures where there aren't any; 7.Cage Kiosk already works embedded, looking there may prove useful. Note: I will be away from the PC soon, so likely I won't be able to reply for a few hours, so sorry. |
HACKHACKHACK
|
Full backtrace of 4.:
|
Update!! Wine wayland on embedded mode progress thanks to @sharkautarch !! The solution (for now) of the bad variant access was adding edit: Nope, couldn't get a working cursor :/ Not skilled enough atm |
I just realized, setting WAYLAND_DISPLAY to something other than gamescope's wayland display just runs the app without gamescope :/ |
Not sure if Wine bug or a Gamescope bug.
Wine's wayland driver works correctly, but not under gamescope by using the flag
--expose-wayland
Forcing a new enough (or patched) wine to use (non x)wayland with "
wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d wayland
" (does not need to unset DISPLAY in this way) makes it so launching undergamescope --expose-wayland -- wine (insert program)
cannot produce a viable window with the following logs:For notepad or
gamescope --expose-wayland --debug-layers --debug-focus --debug-events -- wine notepad
:Log without gamescope (opens correctly):
For a game running on DXVK/Vulkan or
gamescope --expose-wayland --debug-layers --debug-focus --debug-events -- wine DBXV2.exe
:Log without gamescope (opens correctly)
:
Setting
WAYLAND_DISPLAY
and/orDISPLAY
on the right side of gamescope command to various strings including blank,wayland-0
andgamescope-0
does not help like it does to Firefox for example (#808). Foregoing--expose-wayland
doesn't help either as, as stated above, with this registry edit wine will ONLY use native wayland, which rules out theDISPLAY=""
requirement and associated interfecences with gamescope.I have observed the same behavior from at least one other user, and I'm waiting on a second. A quick and dirty way to get access to a precompiled wine with wayland driver ability if your distro does not offer it is to grab one of the binaries over at Tk-Glitch's wine-tkg avaiable for a variety of distros: link
gamescope: git master (dc81258)
wine: 9.0.r2.ge045af48 ( TkG Staging Esync Fsync )
wm: sway 1.9-dev-ae33f4eb
mesa: 24.1.0-devel (git-c3a64f8dd1)
kernel: 6.7.1 (CachyOS)
The text was updated successfully, but these errors were encountered: