https://bugs.winehq.org/show_bug.cgi?id=55995 --- Comment #7 from Grigory Vasilyev <h0tc0d3(a)gmail.com> --- (In reply to alexandros.frantzis from comment #4)
1. Please attach a log of the problem with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1"
See wine1.log It's Hyprland fractional scale = 1.25
2. It's very likely that the Blizzard launcher is using Chromium Embedded Framework, which utilizes cross-process rendering, which is not yet supported by the upstream driver.
Yep, Battle.net use CEF.
3. Thanks, I have a fix here: https://gitlab.winehq.org/wine/wine/-/merge_requests/4668 . Let me know how it works for you.
Thx. Solved.
4. Since with the Wayland driver the toplevel windows are normal Wayland xdg-toplevels, Sway does its normal thing and places them tiled (in contrast to X11/Xwayland windows which are treated specially). If you prefer a "float" state, you will need to tell sway use that state (although that may be tricky at the moment since the Wayland driver doesn't yet set app_id or title).
Yep. But we have other bug, drop-down menus are also drawn full screen. Example: changing the windows version in winecfg. https://imgur.com/a/fzMVMtf
5. Please attach a log of the problem with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard,+vulkan WAYLAND_DEBUG=1". Do you see this issue in other compositors?
In all compositors. Sway and Hyprland have frame limit in ~55 frames. See wine1.log It's Hyprland fractional scale = 1.25
6. This would indicate that relative motion is not being properly enabled. Please attach a log with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1".
See wine1.log It's Hyprland fractional scale = 1.25
7. Please attach log as above.
See wine2.log It's sway fractional scale = 1.00
8. Not currently implemented. BTW, are you using a scaled output?
See comment above. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.