That is so stupid, but `PROTON_HIDE_NVIDIA_GPU=1` fixes `Fatal D3D Error (6, E_OUTOFMEMORY)`

> That is so stupid, but `PROTON_HIDE_NVIDIA_GPU=1` fixes `Fatal D3D Error (6, E_OUTOFMEMORY)` I can confirm the option ...

Seems this is the fix for Nvidia cards: PROTON_HIDE_NVIDIA_GPU=1 %command% VRAM leak seems fixed with this.

I'm confirming that on a clean Linux install, `PROTON_HIDE_NVIDIA_GPU=1` is definitely required for Nvidia based systems ...

... In any case, using Proton 5.13 requires `PROTON_HIDE_NVIDIA_GPU=1` for Nvidia powered PC. With this the game ...

Really your launch options aren't much different. > PULSE_LATENCY_MSEC=60 PROTON_HIDE_NVIDIA_GPU=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_LOG=1 ...

> > > have you guys with nvidia cards tried PROTON_HIDE_NVIDIA_GPU=1 ? > > > > Hide Gpu only fixes the black areas for me ...

... bleeding edge, nvdia drive 550 and those args `PROTON_HIDE_NVIDIA_GPU=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%` I can play ...

... Applying `PROTON_HIDE_NVIDIA_GPU=1` fixed it but now I can't use DLSS, only FSR (expected since the game ...

... WINE_HIDE_NVIDIA_GPU=1, for proton users that would be PROTON_HIDE_NVIDIA_GPU=1. I have observed the same as was mentioned ...

... Also, about testing the DLSS update, we should remember that `hidenvgpu` or `PROTON_HIDE_NVIDIA_GPU=1` is forced in the ...

... 0.5.17 The problem was solved by the variable "PROTON_HIDE_NVIDIA_GPU=1" In this case, the AMD driver ...

... forgetting some things Fresh prefix, Cleared shader cache, PROTON_HIDE_NVIDIA_GPU=1, __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 system-wide Nothing worked, didnt have ...

... Tested with "PROTON_HIDE_NVIDIA_GPU=1 %command%" and then it won't even load the main menu.

... Advanced Launch Options: `PROTON_LOG=1 DXVK_HUD=compiler PROTON_HIDE_NVIDIA_GPU=1 gamemoderun %command%` 2. Use an (official) Sony PS4 controller ...