I’ve got a bug where the game does not create a window after champion select, but it is open in the background and loads into SR. If you stop the game process and press reconnect in the client, it usually still does not work, but ~1/10 of the time it may eventually let me into the game. At the same time, (could be the same or a different bug) the game may decide to create a 1x1px window that I cannot interact with instead. This also has the same issue, where I just have to close and reopen the game and hope if I try enough times I can load in time for it to not be a remake. These issues happens interchangeably - may have no window one time and 1x1px window the next time.
If I attempt to reconnect enough times, it may let me join back, and work fine, and I can play the game, OR;
Occasionally, the game will run at a higher speed than it should. Minions teleport backwards and forwards when they are running down lane, damage from minions doesn’t apply to the other wave, champions also microstutter when they move (including your own) tp-ing forwards and backwards by small amounts. Abilities and autos have ~50% chance of not going through when you press buttons, so you could mash your flash summ or q/w/e/r and nothing happens, regardless of how many times you press. Champions and minions move faster (the MS number is the same, but in practice it’s very clearly far higher than what it should be). I have only had this happen recently in my games with akali, and I’ve also noticed that my smoke just doesn’t render at all (literally can’t see when i’m invisible). After using rocketbelt, the timer bar at the bottom of your screen just stays there for the entire game.
I can tell that the game itself is at a higher speed or something as the in game timer is ahead of the actual game time - I was still getting platings and the in game timer said it was at 14:30. Platings went down when the game said it was at ~16min, so it’s approx 14% faster than it should be.
This issue doesnt go away after closing the game and pressing reconnect or closing the game and launcher and reconnecting, it persists for the entire game and only seems to go away after the game finishes. This is incredibly frustrating, as it’s simply unplayable to have abilities not go through.
Anyone recognise any of these bugs or how to resolve them?
Specs: NixOS 23.05 with gnome 44.2
Bottles flatpak with wine-ge 8.7-1, dxvk2.2 and fsync.
(my bottles config for league: https://pastebin.com/paHFix46 )
A quick note on “Abilities and autos have ~50% chance of not going through”: this is because the timers are desync’d due to the speedup. If you’re trying to use an ability immediately after the client thinks it’s come off cooldown, it’s actually still on cooldown. You can verify by pinging your ability right as it comes off cooldown to see when it actually comes back up. For example if I’m spamming Q on Alistar, when the client says it’s off cooldown, it still has ~2s left before coming up. Higher CD abilities will have a bigger discrepancy.
This post is like 2 different issues I’ve been having combined into one. Since gnome 44 (on arch, so 44.1, 44.2, and 44.3 so far; didn’t have this issue on gnome 43), if I’m on wayland, I can’t load into a game without it being invisible in the background, with no window I can see. The wine virtual desktop alleviates this issue, but I opted to switch back to X11 until this is fixed.
On X11, my game sometimes fails to transition from champ select to loading screen. A fullscreen window pops up for a fraction of a second and disappears, followed by the client coming back up with the “reconnect” button. The first couple games where this happened, I was able to launch the game after ~3-5 reconnect attempts, and the game played like normal. Lately however, it will continue crashing no matter how many times I reconnect. The only way for me to launch into the game is to completely stop league (kill it via lutris) and relaunch, and that’s what appears to trigger the game to be a desynchronized mess, as the OP described. One silver lining is that it sometimes fixes itself mid-game after a while.
I’m also on lutris-ge-lol-8.7-1, with an RX 6700XT fwiw.
I’ll try out the gstreamer file fix mentioned by @auracon (I have the same error messages in my lutris logs, but they also appear without the desync bug) and if that doesn’t work, I’ll try switching to the wine virtual desktop
Please let me know how it goes. Mine’s been running ok so far after the workaround with libgstflac.so. (if the file exists in the wine runner already, rename it for backup and replace it with the system’s version of libgstflac.so found in /usr/lib/gstreamer-1.0/ ) I straight up copied in/replaced both of the ones under the lib and lib64 folders for the wine runner with the same system libgstflac.so file because I got sick of it.
I don’t know if it worked because of the workaround or if someone fixed it for arch linux though. LOL. Good luck!
Maybe a suggestion that may help: I realized that is not the only way to restart the game. You can close the client when you see the RECONNECT button. Shutdown the riot launcher gracefully. Then start it again.
By any chance, was anybody of you playing while using the team voice chat?
nope
I just had the same problem right now first time in ranked.
Didn´t even update anything on my system. Yesterday I played like 6 matches and all were fine.So far, I’ve had best luck while using the wine virtual desktop - suggests to me that there’s a wine renderer bug causing the invisible game issue. Not sure about the speed though.
Which Wine-lol version are you using? Here I am on lutris-ge-lol-8.7.1
also, if you press alt+enter, the game toggles between windowed and fullscreen, which may help if it loses focus.
After switching to lutris-ge-lol-p8-12 I had to reconnect and the game was not broken. The speed was totally normal. Unsure yet if this is generally the case or I was just lucky, as I am slow to replicate such states.
I have been having a similar problem and I had a “MAYBE” working solution so far.
OS: Arch Linux
CPU: i5-11600K
GPU: Radeon 6700XT
Played like 3 games so far and haven’t got that lag/sped up game issue yet.The main issue was the libgstflac.so under the gstreamer-1.0 folder of the wine-ge-lol-8.7-1-x86_64 runner inside both “lib” and “lib64” folders. This was the log file that lutris gave me back then:
…
(wine:26885): GStreamer-WARNING **: 22:17:24.871: Failed to load plugin ‘/home/(username)/.local/share/lutris/runners/wine/lutris-ge-lol-8.7-1-x86_64/lib64/gstreamer-1.0/libgstflac.so’: libFLAC.so.8: cannot open shared object file: No such file or directory(wine:26885): GStreamer-WARNING **: 22:17:24.872: Failed to load plugin ‘/home/(username)/.local/share/lutris/runners/wine/lutris-ge-lol-8.7-1-x86_64/lib/gstreamer-1.0/libgstflac.so’: /home/(username)/.local/share/lutris/runners/wine/lutris-ge-lol-8.7-1-x86_64/lib/gstreamer-1.0/libgstflac.so: wrong ELF class: ELFCLASS32
…The issue then seems to be that there’s no libgstflac.so or a wrong version of it inside the lib folder of lutris-ge-lol (for some reason). So, these are what I did.
- I went to my system gstreamer-1.0 folder at /usr/lib/gstreamer-1.0/ and copied the “libgstflac.so” file and
- Replace/copy it into both the lib and lib64 folders for the wine runner.
-
/home/(username)/.local/share/lutris/runners/wine/lutris-ge-lol-8.7-1-x86_64/lib/gstreamer-1.0/libgstflac.so
-
/home/(username)/.local/share/lutris/runners/wine/lutris-ge-lol-8.7-1-x86_64/lib64/gstreamer-1.0/libgstflac.so
So far, no more errors regarding the plugin anymore. Haven’t got that lag issue yet, but need more sample size (maybe you guys can try that and increase the sample size altogether).
Gotta be something else. In my runner this file exists and I just got the speed bug.
I don’t know if they somehow fixed the issue already, but I haven’t had this issue anymore in a while so far.
I do remember having the file (libgstflac.so) in the wine runner as well, but a different size to the system gstreamer’s libgstflac.so. So I just replaced the one in the wine runners (both from the lib and lib64 folders). Can’t tell if it worked or they just fixed it lol.