i3 & games - will never launch

[NoahRR]

I absolutely love i3 - but there's one super annoying thing that I can't seem to solve.

I cannot get any games to run. For example: terraria (steam) and league of legends (lutris). They run perfectly when I switch over to GNOME on same setup. (but this is very annoying to do, as I have to close everything I'm doing just to swap over and play a game)

For league, here is the debug log (not very helpful):
lutris-wrapper: League of Legends
Running /home/noahray/.local/share/lutris/runners/wine/lutris-ge-lol-6.16-2-x86_64/bin/wine /home/noahray/Games/league-of-legends/drive_c/Riot Games/League of Legends/LeagueClient.exe --locale=en_US
Initial process has started with pid 434483
Start monitoring process.
wineserver: using server-side synchronization.

Same thing happens with all games: after I click play, they just never load, in a continuous state of loading -- or maybe they are loaded but hidden for some reason?

I've tried installing other dependencies, fiddling around with setting windows to floating / borderless, and tested with other WMs. Maybe this is an issue with tiling window WMs in general. From my testing: works on gnome, does not work on i3 or awesome wm.

Anyone experience similar issues or have any ideas about how to resolve? Any feedback would be greatly appreciated!

(edit) OS: arch (lts kernal)

Let me know if I need to post this question somewhere else - but really trying to find a solution for this!!! I really want to stick with i3!!

[Airblader]

What's your compositor situation? Are you running one?

[NoahRR]

I'm using picom. Issue was happening before I installed that though.

[Airblader]

Does it only affect games running under Wine?

[NoahRR]

Right -- ok I'll dig into the issue with a focus on wine & i3. Hopefully that should lead me to an answer! Thanks for the help!

(edit) if I do find a solution that works for me I will post it here for others' future reference

[Airblader]

Another thing to try would be running the game under xtrace to see what happens on the X level. This can be somewhat painful to dig through when dealing with complex clients that do lots of things, but if nothing else helps this is something we could try. It'll likely make the client unbearably slow, but since it "crashes" anyway that shouldn't matter.

[NoahRR]

right on. I'll try that too!

[Airblader]

If you aren't familiar with X you'll probably need our help here to dig through that. If it comes to it you can upload the output somewhere and post the link here.

[NoahRR]

You are so helpful! Thanks!

I can't look into this right now, but will do so in the next few days. I'll report back either way (with solution or a linked log).