I’m using arch with KDE Wayland and nvidia, ever since I did fresh install cyberpunk 2077 launches with a balck screen in the launcher, but I can still click elements in it, and trying to launch the game prompts and error saying its currupted. I have uninstalled and reinstalled with no avial. Any advice?
@[email protected] Did you get anywhere with getting this working? I have same problem (KDE,NVIDIA,2077)
Edit: Game works fine on my SD, just not desktop.
I never did, I did manage to fix my issue with steam launching but this issue is still there.
I had to set launch options to skip the launcher and use proton 7 or below, 8 is causing problems for me. Game is working now, some crashes but I think its one of my mods doing it
Have you got the latest proprietary drivers installed?
Have you tried in Xorg instead of Wayland?
KDE on xorg is basically unstable and freezes every 20 seconds. Might try GNOME, just kinda sad since it worked fine in my last install
Sounds like you have further issues then if KDE has problems on XOrg
yeah honestly unsure, it works fine on Wayland. I did always remember KDE on Xorg was buggy AF even on my old install
this is what I have been dealing with on steam both Xorg and Wayland, it will launch after a really long time, wondering if this has anything to do with. Other games also work fine one steam is opened however
Try a different proton version, or some of the GE versions?
undefined> Try a different proton version, or some of the GE versions?
I tired a ton, including GE, still the same issue.
I’ve got Cyberpunk into a corrupted state via mods before. Ultimately had to delete the Wine prefix and do a complete reinstall after that.
Yeah I tried that and it somehow still failed 😭 😭
Have you tried using different proton versions wit hit? Launcher uses .NET/C# so it can be problematic. After the first execution you should be able to just add
--launcher-skip
to the command and skip it.Execute steam with PRESSURE_VESSEL_SHELL=instead steam and launch the game. In the term it will open type
"$@"
(with the ") and paste output here, we’ll see what proton fusses about