proton + nvidia

[jArjAr_binX_69]

tried this, didn't work. there are reported issues with this setup from 3 years ago. will it ever be fixed?

[Death Approaches]

Of course it works. Works perfectly. 3 years ago the game was new, give some people a chance to make things function, sheesh. But 2.5 years ago? worked fine. Still does, more stable than Windows, and that's a fact. Buy with confidence.

caveat: that's assuming your PC is semi-modern and gaming ready, hex/octocore minimum and multi-gigahertz and 16G RAM at least and your "nvidia" is at least a 10 series with 8G VRAM, but hopefully 20, 30, 40 series with at least 12G VRAM. And a fast, SSD, preferably NVMe and bolted directly to the adapter PCIe card, no cables. 7G or 12G/sec reads would be outstanding. Anything less than 3G/sec is going to be... less than ideal for this game, even NVMe, even at "just" 1920x1080.

[jArjAr_binX_69]

i have an i9-12900KF and a 3080. game starts, i get a frozen window that looks like a screenshot of my steam menu when i started the game

[apocalyptech]

Yeah, I just started having problems launching the game with Proton today (it's been over a week since I'd last started the game). For me it just gives me a black screen which stays there for a long time -- if I wait long enough, it'll eventually go away and a "crash reporter" process will sit in my process list for awhile until I kill it off. Otherwise I just kill the main process ahead of time to save some time. A week or so ago when it was working fine, it would get into the main startup videos (logos, etc) pretty much right away.

Unfortunately for me, I've had a number of system upgrades and other environmental changes inbetween my last successful run and now -- many long-overdue OS updates, finally getting on the new (awful, IMO) Steam client, etc. So it's difficult for me to say it's the game's fault for sure. I did go so far as to reinstall the game entirely, and even wiped out my wineroot (compatdata/1091500) so that I'd have a totally clean slate, and get the same behavior.

I've been able to run every other game that I've tried, including some using the same version of Proton that I'm using for CP2077.

It seems other folks might be having problems, too: https://steamcommunity.com/app/1091500/discussions/7/3803901559409260857/ -- I assume not all of them are also on Linux/Proton? Of course for some people, mods might be a factor.

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: TUF B450-PLUS GAMING
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 2600 Six-Core Processor
CPU Family: 0x17
CPU Model: 0x8
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 3400 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.3.9-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12101008
X Window Manager: IceWM 3.4.0 (linux-gnu/x86_64)
Steam Runtime Version: steam-runtime_0.20230509.49499
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 535.54.03
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1c03
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.04" x 11.26" (22.95" diag), 50.9cm x 28.6cm (58.3cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 6144 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Nvidia GPU 84 HDMI/DP
Memory:
RAM: 32025 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 583502 MB
Largest Free Hard Disk Block: 50465 MB
Storage:
Number of SSDs: 4
SSD sizes: 1000G,1000G,0B,0B
Number of HDDs: 0
Number of removable drives: 0

[apocalyptech]

Okay, so, I've been occasionally poking at this myself, since my cp2077 stopped launching recently and I'd rather like to finish up this playthrough before 1.7 drops. Debugging on my end was rather more complicated than it could've been because I had a *lot* of system changes inbetween my previous successful cp2077 run than just the 1.63 update. However, I did finally narrow it down that for me, the issue is actually an nvidia driver version, rather than the cp2077 patch itself.

Specifically, for me, v530.41.03 works (the last version I'd run successfully with), and v535.54.03 fails (frozen black screen which eventually bombs out, sometimes successfully launching a crash report window, but not usually).

On Arch Linux, downgrading to 530.41.03 will also require hopping on an older kernel, it seems -- I wasn't able to get 530.41.03 to compile against the current 6.4.1 kernel, so I had to compile it against linux-lts instead (which is currently at 6.1.37). The kernel I was originally running alongside v530.41.03 was 6.2.12, but I didn't feel like compiling a kernel, so just hopping back to linux-lts did the trick fo rme.

So anyway, if anyone else on Linux/Proton + Nvidia is having issues, try downgrading to 530 and see if that takes care of it for you.

Edit: Also, a bit more info for Arch users, I suppose. To downgrade `nvidia-lts` to a v530 version, you can grab some old tagged releases from Arch's package github; for instance, I'd grabbed from these tags:

https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-utils/-/tree/530.41.03-1
https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-lts/-/tree/1-530.41.03-5

Once you've got those in a dir, running `makepkg` should start 'em building (you may be given some extra dependencies which need installing before they'll build). I believe you need to build/install the nvidia-utils one prior to building nvidia-lts.

I'd picked the exact same version of "nvidia-lts" that I'd had installed back when things were working for me (1-530.41.03-5) even though I don't ordinarily use the LTS kernel. It probably makes sense to pick the most recent of the v530 tags instead, but I can't personally verify that does the trick (though I'd be surprised if it didn't): https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-lts/-/tree/1-530.41.03-14

[Shin Coldfire]

Originally posted by apocalyptech:

Okay, so, I've been occasionally poking at this myself, since my cp2077 stopped launching recently and I'd rather like to finish up this playthrough before 1.7 drops. Debugging on my end was rather more complicated than it could've been because I had a *lot* of system changes inbetween my previous successful cp2077 run than just the 1.63 update. However, I did finally narrow it down that for me, the issue is actually an nvidia driver version, rather than the cp2077 patch itself.

Specifically, for me, v530.41.03 works (the last version I'd run successfully with), and v535.54.03 fails (frozen black screen which eventually bombs out, sometimes successfully launching a crash report window, but not usually).

On Arch Linux, downgrading to 530.41.03 will also require hopping on an older kernel, it seems -- I wasn't able to get 530.41.03 to compile against the current 6.4.1 kernel, so I had to compile it against linux-lts instead (which is currently at 6.1.37). The kernel I was originally running alongside v530.41.03 was 6.2.12, but I didn't feel like compiling a kernel, so just hopping back to linux-lts did the trick fo rme.

So anyway, if anyone else on Linux/Proton + Nvidia is having issues, try downgrading to 530 and see if that takes care of it for you.

Edit: Also, a bit more info for Arch users, I suppose. To downgrade `nvidia-lts` to a v530 version, you can grab some old tagged releases from Arch's package github; for instance, I'd grabbed from these tags:

https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-utils/-/tree/530.41.03-1
https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-lts/-/tree/1-530.41.03-5

Once you've got those in a dir, running `makepkg` should start 'em building (you may be given some extra dependencies which need installing before they'll build). I believe you need to build/install the nvidia-utils one prior to building nvidia-lts.

I'd picked the exact same version of "nvidia-lts" that I'd had installed back when things were working for me (1-530.41.03-5) even though I don't ordinarily use the LTS kernel. It probably makes sense to pick the most recent of the v530 tags instead, but I can't personally verify that does the trick (though I'd be surprised if it didn't): https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-lts/-/tree/1-530.41.03-14

For anyone, who want to try downgrading, I recommend using "nvidia-all" package. It is much simplier solution. https://github.com/Frogging-Family/nvidia-all

[Baron Von Sucko]

Originally posted by Death Approaches:

Of course it works. Works perfectly. 3 years ago the game was new, give some people a chance to make things function, sheesh. But 2.5 years ago? worked fine. Still does, more stable than Windows, and that's a fact. Buy with confidence.

caveat: that's assuming your PC is semi-modern and gaming ready, hex/octocore minimum and multi-gigahertz and 16G RAM at least and your "nvidia" is at least a 10 series with 8G VRAM, but hopefully 20, 30, 40 series with at least 12G VRAM. And a fast, SSD, preferably NVMe and bolted directly to the adapter PCIe card, no cables. 7G or 12G/sec reads would be outstanding. Anything less than 3G/sec is going to be... less than ideal for this game, even NVMe, even at "just" 1920x1080.

"That's a fact!" Maybe for you. I don't know if the root cause is the same, but it's crashing in a way that's very reminiscent of how it crashed when the game was first released. You start playing and maybe it'll crash in 5 minutes. Maybe it'll crash in two hours. A lot of linux users are experiencing this, always with the same error in dmesg:

Xid (PCI:0000:01:00): 31, pid=33457, name=GameThread, Ch 0000005e, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x52c0_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

That's with a 4070, btw.

[Toast]

Nvidia is tracking this bug at this page. Add your logs if you are able to.
https://forums.developer.nvidia.com/t/cyberpunk-2077-1-62-1-63-crashes/260799/9