Vram leak

ozanuygur07

New member
I'm using an RTX 4060, but I'm having a serious issue with VRAM management. Even when I lower the graphics settings to the minimum, the VRAM usage exceeds the 8GB limit.

The performance is fine for the first 10 minutes, but after that, the VRAM usage spikes uncontrollably regardless of the settings I use. This causes massive stuttering and makes the game almost unplayable. Has anyone else experienced this 'memory leak' like behavior with an 8GB card, or is there a specific setting I should check?
 
I have the same GPU and the same happens to me. In my case it helped to lower the texture quality to medium, because it leaks slower and it kind of works. I think that they already know about this but I guess that they are prioritazing other things first, since it's a playtest
 
I have the same GPU and the same happens to me. In my case it helped to lower the texture quality to medium, because it leaks slower and it kind of works. I think that they already know about this but I guess that they are prioritazing other things first, since it's a playtest
I lowered the resolution, but the problem persists.
 
I have the same problem on Linux, the performance is good at the start (around 90 fps), but after the 30 min mark i have 10~15 fps, the problem is solved after restarting the game.

I use EndeavourOS with kernel : 6.12.66-1-lts, my gpu is an AMD ryzen 5 3600x and my gpu is an rtx 2060.
 
What Zullie is talking about only works before the leakage happend since that memory is already lost and changing that config wont do anything. Changing textures to low or mid makes you reach max vram usage much slower being able to play a whole game without stutter.

In my case i tested and with high textures i can only play around 20 minutes or less without stutter but with low textures it took around 70 minutes to fill my whole memory. I have a RTX 3060ti 8GB and my normal use of vram without leakage is around 6GB (Desktop environment included) maybe your normal vram usage is higher than mine at the moment of starting playing, keep this in mind.

I suspect this could be related to the breaking and generation of breakable object around the map as they are the most common texture related asset being loaded during the game, but i have no real evidence.
 
Last edited:
What Zullie is talking about only works before the leakage happend since that memory is already lost and changing that config wont do anything. Changing textures to low or mid makes you reach max vram usage much slower being able to play a whole game without stutter.

In my case i tested and with high textures i can only play around 20 minutes or less without stutter but with low textures it took around 70 minutes to fill my whole memory. I have a RTX 3060ti 8GB and my normal use of vram without leakage is around 6GB (Desktop environment included) maybe your normal vram usage is higher than mine at the moment of starting playing, keep this in mind.

I suspect this could be related to the breaking and generation of breakable object around the map as they are the most common texture related asset being loaded during the game, but i have no real evidence.
Yeah, excatly, you need to change this before reaching the limit. This works because texture quality has the bigger impact on vram usage, so by lowering it you are not solving the problem, you are just giving it a higher ceiling. In my case, in high settings it takes around 20 minutes to reach the limit too.

I don't think it's about the game actually. I have tested in both windonws 11 and linux (fedora). In my case fedora didn't seem to have this issue but I can't really prove that. I know that there are people with linux that have had this issue, so I guess that it's not because of the os. I haven't seen people with amd cards have this issue either, so my bet is that the problem are nvidia drivers. I don't think it a problem with the game. Nvidia will probably solve this issue once the game reaches beta and they officialy release a driver update for deadlock.
 
Yeah, excatly, you need to change this before reaching the limit. This works because texture quality has the bigger impact on vram usage, so by lowering it you are not solving the problem, you are just giving it a higher ceiling. In my case, in high settings it takes around 20 minutes to reach the limit too.

I don't think it's about the game actually. I have tested in both windonws 11 and linux (fedora). In my case fedora didn't seem to have this issue but I can't really prove that. I know that there are people with linux that have had this issue, so I guess that it's not because of the os. I haven't seen people with amd cards have this issue either, so my bet is that the problem are nvidia drivers. I don't think it a problem with the game. Nvidia will probably solve this issue once the game reaches beta and they officialy release a driver update for deadlock.
It could be a Nvidia problem, but i think is just coincidence since new AMD graphic card usually have more vram than Nvidia ones by default. I saw a post about the same problem with a RX 6700s "https://forums.playdeadlock.com/thr...resent-on-windows-as-well.101870/#post-193076".

The RX XXXXs models are laptop exclusive cards and they usually ship with less vram being 8GB the Magic number. I suspect that anyone with a 8GB vram graphic card and high textures Will suffer the same problem. Also i have seen many users saying this startes happening after "Old Gods New Blood", i can't prove this since i started playing after this update.
 
Last edited:
Back
Top