UPDATE: There appears to be a workaround discovered by a user on the DXVK discord (Zerofault) which works by using a vulkan layer to spoof the GPU as AMD. I’m unsure whether this is down to Nvidia to patch however I’ll keep this thread on here in case there’s a solution Nvidia can implement.
There appears to be severe performance issues with the new experimental Vulkan patch for NMS released yesterday via Proton/Wine specifically. Would of thought this might be a wine bug but it doesn’t occur on AMD cards, so I hope someone can take a look at it and determine whether the Linux Nvidia drivers are the culprit.
Update: NMS Beyond update has now been released which includes the vulkan renderer mentioned above as standard.
The performance issues still persist with this renderer on the 435.17 driver, VRAM usage also seems suspiciously low and usually caps off at around 1GB where on Windows it would be using around 4GB.
Here are some reports on the issue at the bottom: https://github.com/ValveSoftware/Proton/issues/438
The previous OpenGL renderer which has now been removed from the game used to run fine/near native on proton.
Steps to reproduce:
Play the game with Steam Proton 4.11 and log performance & VRAM usage.
Some renderdoc captures in this tar.xz file: https://drive.google.com/file/d/1Q0RUQaWi4L9ZKzZBgjrm3Nx6hAVVnmEW/view
nvidia-bug-report.log.gz (1.12 MB)