Linux VRAM leak

[lonkalsim]

I'm not sure if it's correct to post it, but I'd imagine Valve being interested in Deadlock's native port, so yeah.
When running through GE-Proton 10-32 Deadlock's VRAM usage is acceptable (3,3GB for the lowest settings is still a lot), but when shaders are done compiling it's 5,8GB.

 

[lonkalsim]

It gets much worse by now, the game is literally unplayable in 20 minutes on Vulkan, on DX11 you can play one match without restarting.
Linux community would appreciate a native build, but since it's difficult to make, especially at this stage of development, it would be nice if you could fix this issue which everyone on Linux is facing right now.

 

[Rotekoppen]

Second this, it was bearable until like a week ago on only 4gb vram.
I am pretty certain its a vram issue, because its the worst when moving (culling etc) and while standing still I get almost smooth 60fps.
I dont think a native build will solve this.

 

[c0bra]

It gets much worse by now, the game is literally unplayable in 20 minutes on Vulkan, on DX11 you can play one match without restarting.
Linux community would appreciate a native build, but since it's difficult to make, especially at this stage of development, it would be nice if you could fix this issue which everyone on Linux is facing right now.

I have similar vram usage, but game runs normally. Have you tried switching proton versions? Im using proton experimental. More specs here: https://forums.playdeadlock.com/thr...e-linux-vulkan-wayland-amd.110616/post-214862

 

[c0bra]

If switching proton version fixes it you should report it here: https://github.com/GloriousEggroll/proton-ge-custom/issues