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...
Hello! I've been trying to get league to install on my new steam deck and it's kinda giving me a hard time. I'm following this guy's guide step by step on YouTube https://youtu.be/hNe3OLn9czE and all is good up until the part where I have to run the LoL.sh executable and let wine do its thing. That's where I'm encountered with the error "The program RiotClientUxRender.exe has encountered a serious problem and needs to close". I tried clicking the button reading "Show Details", but then Wine crashes and gives me the same error popup all over again. I can't find what I've done wrong and I can't find a solution online that either works for me or I can understand how to get to. Is there anyone here that has any idea how this can be solved and can explain in a simple way? I'm linking a pic of the error popup and the app crashing when I press the "show details" button plus the app looping eternally when I try to close it: https://imgur.com/a/kw5BpMm Thank you all in advance!
@gabriele97 That's what I did on my first try installing League about a week ago, but at some point after the Riot Client stopped updating, it would minimize in tray and wouldn't let me shut it down or bring the window back up. The installation on Lutris wasn't showing as "complete" either, so after a couple of times of running it back and trying to find a solution, I gave up and looked for another way.
League client and game crash with multi-monitor setup.
Issue
Hello, I can play LoL on Linux (Artix Linux with NVidia) just fine, with great game performance and no issue at all, except one:
When a window appears (either the client's window or the game\s window), if I am using my main monitor (HDMI-1) and leave my eDP-1 monitor off, everything works fine.
However, I love to copy my monitors with xrandr --output eDP-1 --same-as HDMI-1
If the client window is active and open, the window appears on both screens just fine when duplicating the two displays.
If the game window is active and open, the window appears on both screens just fine when duplicating the two displays.
If the client window is active and open, duplicate the two displays and launch a game, the client window hides (as expected) but the game window doesn't appear and I get an error dialog instead. Current fix: switch to single-display mode as quickly as possible, and duplicate the display once the game window was successfully launched.
If I click on "close" on the wine error dialog while switching to a single-display mode, the client window reappears and let me reconnect to the game (which is good, but time wasting because the client is so slow)
This behavior is similar to the one happening when launching the Client:
If I launch the client with duplicated displays, I get an error dialog.
If I launch the client in single-display, then go in another workspace and wait a bit, duplicate the displays and go back in the workspace containing the client window, the very same error message appears.
A reminder from a sentence above:
If the client window is active and open, the window appears on both screens just fine when duplicating the two displays.
But if I duplicate in another workspace and that the client has "slept" for a while, then going back breaks the client and the client window will try to relaunch itself which will only work if I quickly switch back to single-display mode.
A final point:
If I boot my system, duplicate my displays, and then launch Lol, the client window will never appear but error dialogs instead and launch-looping until I go back to a single-window mode.
Issue TLDR
If any window (client or game) tries to "show" itself while in a duplicated screen state, it will break and show an error and try to restart the client.
It only works if the window is active and that I duplicate the two displays using a keybinding. Then I can go in other workspace just fine, come back, no issue.
Installation Method and Wine Version
OS: Artix Linux x86_64
Kernel: 6.3.6-artix1-1
Resolution: 2560x1440
WM: dwm
CPU: Intel i7-7700HQ
GPU: Intel HD Graphics 630 (unused)
GPU: NVIDIA GeForce GTX 1050 Mobile
ram/storage: enough
Shell level:
wine --version: wine-8.10 (Staging)
League (installed trough lutris-0.5.13):
Wine build: wine-4.11-21066-g82c1eae4413
Runner: lutris-ge-7.0.8-x86_64
The global reddit situation has devolved to the point where reddit admins have been overtly lying and actively changing their site policies in order to remove and replace protesting moderators, despite having previously claimed they would “respect the community’s right to protest", among many other lies....
happening on the new proton-ge-lol-8-27 and the original 9.0-RC fix. anyone else getting this? also getting the game frozen on my screen after every match and have to close "leagueoflegends.exe" manually
Got win-ge-lol-8-27 but was unable to enter the match and i got a window saying Process Monitor was detected so it needs to be unloaded blah blah. This didn't show up before and I'm fairly new to linux. Any help?
I know about the recent Vanguard news, but it looks like the Mac binary will be maintained without Vanguard (since Vanguard is a Windows kernel specific). Would that mean using something like Darling on top of the Mac binary could be a way forward?
I have been playing League on my Arch system for about half a year now without issues. Ever since patch 13.22 dropped, whenever I go into game it runs smooth, but once every 30 secs to maybe 2 minutes it runs like I have sub 60 FPS, although the FPS number doesn't change (I constantly get 200+ FPS). After that it goes back to...
