Open ghost opened 2 years ago
That's weird, as I've used many wine apps with no issues, havent used league though... Will test.
Can't reproduce, all of my wine games and programs (tested: photoshop, homm5, civ4, civ5, terraria, hyperdimension neptunia) work properly. Have you tried changing the window's size when it goes blank?
Blank window resizing:
As for the 'invisible' ones I've discovered that if I can locate it and move/drag the window, it will become visible again. Does not work with the blank ones though.
As for the 'invisible' ones I've discovered that if I can locate it and move/drag the window, it will become visible again. Does not work with the blank ones though.
Yeah this one makes sense, some windows do that and I've yet to find out why (my example is always ario)
with the blank ones I don't know what's causing this. The app itself should spew errors if that happens though, have you tried launching it from a terminal and seeing the output?
I had a look at the wine logs but to be honest interpreting them is a bit beyond my scope.
I realize this entire issue is difficult to troubleshoot when there are no direct log entries and you're not able to reproduce it in your wine applications, so if you want to close this that's fine.
Ideally someone else would report their experience with League of Legends and Hypr so we could rule out my setup being the cause.
I'm experiencing similar issues however I have achieved a somewhat usable setup with the following rules in hypr.conf:
windowrule=float,class:leagueclientux.exe
windowrule=size 1286 726,class:leagueclientux.exe
windowrule=workspace 2,class:leagueclientux.exe
windowrule=move 650 360,class:leagueclientux.exe
windowrule=float,class:explorer.exe
windowrule=size 0 0,class:explorer.exe
windowrule=workspace 2,class:explorer.exe
windowrule=move 650 360,class:explorer.exe
windowrule=float,class:riotclientux.exe
windowrule=size 1286 726,class:riotclientux.exe
windowrule=workspace 2,class:riotclientux.exe
windowrule=move 650 360,class:riotclientux.exe
windowrule=workspace 2,class:league of legends.exe
With this windows will spawn floating and in their correct sizes preventing odd rendering issues when Hypr attempts to tile them. It is not sufficient to set it to floating as this results in a ~20x40px window.
There are still odd problems which do not arise in other WMs.
Assigning a fullscreen window rule in Hypr's config does not solve these issues. The somewhat workable solution is to use borderless and either continue to switch back and forth between workspaces until it fixes itself or toggle Hypr's full-screen setting on and off. Not ideal but at least you don't have to restart the game.
Unfortunately I do not know what is causing these issues to arise in Hyper but not other WMs.
videos are broken for me (cant play them), but nevertheless all of this seems to arise from some miscommunication issue between hypr and Xorg (damn it, xorg!), where windows do not get their initial size and pos (state) correctly applied.
I can reproduce the partially visible bug on fullscreen with vlc, although moving the mouse over the invisible area fixes it. It's been annoying me for ages, but I have no idea either on what causes it.
I might try to see if I'm missing something - If you say it works on other WMs, I'll try spectr and bsp
Fullscreen mode results in other workspaces being non-interactive and maintaining the League cursor.
I have suspicions this is partially due to Xorg being Xorg - does this happen on, say, dwm?
videos are broken for me (cant play them).
Seem to be broken for me too. Opening their links with mpv e.g. mpv https://user-images.githubusercontent.com/102994494/164995159-77de14ea-489a-49ac-8e73-9af7d997c1af.mp4
seem to work.
I can reproduce the partially visible bug on fullscreen with vlc, although moving the mouse over the invisible area fixes it. It's been annoying me for ages, but I have no idea either on what causes it.
Does not work with League as moving the cursor to the edge of the screen moves the camera (I do move the cursor there in the video).
I have suspicions this is partially due to Xorg being Xorg - does this happen on, say, dwm?
Yes this is entirely possible. Since borderless is the go-to setting when it works I have not tried fullscreen in other WMs. I will fire up bsp and check.
I have suspicions this is partially due to Xorg being Xorg - does this happen on, say, dwm?
You are correct. This one occurs on bspwm and leftwm as well. The others do not.
ok. will look into.
partially visible fullscreen fixed in 8bad02d1155bcbc83a6f7fe6a6ed71c53febd3c2
partially visible fullscreen fixed in 8bad02d
Can confirm. League no longer cuts off parts of the screen. Thanks!
Please describe the bug Certain Wine windows do not render their content, and instead show a still frame of other content visible on the workspace. Window borders are still rendered. Can also disappear entirely at times; whilst still being visible as running processes.
Steps to reproduce: I don't expect you to install League of Legends, but as I do not run other Wine applications I don't know how widespread this is, but these issues do not exist in dwm, Gnome or Openbox for me, on the same system, and should therefore be Hypr-related rather than a problem with the Wine installation. Regardless, to reproduce:
For Windows rendering a still frame with a border
For Windows disappearing entirely After following the previous steps queue up for a match and swap to a different workspace (leaving the client where it was). When the queue pops the client will disappear if you're not on the same workspace. If you are on the same workspace as the client it will work as expected. The client will also disappear after a match is complete, rather than showing the post-game lobby. The process is still running, but it is either not rendered at all or hidden somewhere, requiring killing the wine process for it to reappear (will of course happen next match and so on).
Expected behavior Windows rendering their content.
Screenshots This is a screenshot showing the desktop wallpaper behind a Wine window rather than its content. Notice the window borders are still rendered.
This is what it should look like:
Anything else? Different states like floating or tiled or specified size/position rules do not make a difference.
Possibly useful xprop of the window pictured above:
Log: log.txt It was too long to post on pastebin.