Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
wine-staging
Staging repository for Wine; mirror of https://gitlab.winehq.org/wine/wine-staging - Bugtracker and Patches: https://bugs.winehq.org/
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
I've been using yuiiio's wine-lol fork (which updates wine to 5.18 and adds fsync support) and the client still works in low spec mode. I do, however, get terrible frame drops when games start which mostly subside after a minute or two.
Running into an issue where I run League with the new .deb packages from here: https://github.com/ekistece/wine-lol/releases/tag/Release installed and run the League start-helper script from here: https://www.reddit.com/r/leagueoflinux/comments/j07yrg/starting_the_client_script/ but end up with a completely black Client. While not having any visuals sound works and I can even interact with the client and get into a custom game where League runs normally, but the client does not have any visuals. Not installed via Lutris but only through wine.
Here is a guide about reinstalling LoL from scratch. I'd recommend you to see Lutris' logs tho in case it has to be with something related to Lutris itself rather than the Wine prefix
I've been using it for some weeks and after today's update it still runs the client + game fine. It's what i'm using with the leagueoflegends script: https://github.com/kyechou/leagueoflegends
If anyone wants to try, you can grab the wine-tkg source tarball from https://github.com/Frogging-Family/wine-tkg-git/releases/tag/6.14.r6.g1bc4da9d and make the following changes to customization.cfg:
This one could be a candidate for fixing this (but I have not tried what happens if I don't apply this to a recent wine version): https://github.com/wine-staging/wine-staging/blob/534f6ae34e89615fa424ee3e3002b1b3d419a8ba/patches/winebuild-pe_syscall_thunks/0002-winebuild-Call-__wine_syscall_dispatcher-through-the.patch
That's why I created a solution, which allows to install the patched glibc separately, some years ago: https://github.com/M-Reimer/wine-lol. At first a patched glibc is built and installed to /opt/wine-lol on the system. Then a patched Wine is built with compile parameters to force it to link to this specially patched glibc version. This means that actually only wine-lol will use the patched glibc and only wine-lol itself can suffer if something is wrong with it.
Weird, I tried what you said, and the building your wine didn't work ( the process was kinda scuffed tho ) In reinstalling LoL and trying to follow your instructions, I found that reinstalling LoL with the first install script on lutris.net configured a different version of wine **lutris-ge-lol-6.16-x86_64**. It seems to work perfectly: I even have the practice tool running atm. Maybe if someone sees this, they might try just reinstalling LoL with stable installer on Lutris's site.