Assuming C:S2 uses DX and you’re running it through proton/dxvk, it’s ultimately the Vulkan driver’s job to page to system memory correctly. This honestly sounds like you’re seeing a bug. In that circumstance, it shouldn’t crash, it should just hurt performance from all the paging.
I see a couple of older issues where people were seeing exactly this kind of issue with DXVK+Nvidia.
This old Witcher 3 one where they blamed it on Nvidia’s memory allocator not playing well with linux THP (transparent huge pages). Disabling THP was a workaround.
This other issue for several titles that were hitting memory alloc failures despite having tons of system memory, just as you describe. They try several workarounds, but ultimately they believe it was fixed by a driver update.
One other thing to try is, idk if you’re running the game in dx11 or dx12 mode, but apparently both exist. If it’s currently running in dx11 mode, try the launch flag -force-d3d12. If you’re already using dx12, maybe try swapping back to dx11. Good luck!
Well, it probably is. I’ll soon be getting a GPU with a bigger VRAM and putting that GPU into my home server for Jellyfin as a replacement for QuickSync (NVENC is better, imo).
Assuming C:S2 uses DX and you’re running it through proton/dxvk, it’s ultimately the Vulkan driver’s job to page to system memory correctly. This honestly sounds like you’re seeing a bug. In that circumstance, it shouldn’t crash, it should just hurt performance from all the paging. I see a couple of older issues where people were seeing exactly this kind of issue with DXVK+Nvidia.
One other thing to try is, idk if you’re running the game in dx11 or dx12 mode, but apparently both exist. If it’s currently running in dx11 mode, try the launch flag
-force-d3d12. If you’re already using dx12, maybe try swapping back to dx11. Good luck!Well, it probably is. I’ll soon be getting a GPU with a bigger VRAM and putting that GPU into my home server for Jellyfin as a replacement for QuickSync (NVENC is better, imo).