Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
edit: also there's def NOT a memory leak. Everyone knows I'm running this on one of the oldest rigs and had a comfortable 4hr session this afternoon crash-free, issue-free.
It is not a case of ''It's not happening to me so it doesn't exist''. This is just a case of hyperbole about memory leaks caused by a vocal minority. Lets agree to disagree and move on.
I had problems with Grey Zone Warfare in UE 5.1 that game was using too. I guess the moral of the story is to not use AMD tech on Nvidia hardware lol.
Indeed. The game had and has memory leaks. Even with the current patch (1.0.2. at time of writing) I can at least indentify 3 situations when VRAM and / or RAM is filled to a point where constant swapping let's suffer the fps:
What most people doesn't seem to understand is that mem leaks are a pest - they are very hard to reproduce and it can be tiny details which make them show up or not. (hardware, specific user action, specific user action frequency ...). They are kind of an esoteric problem but at the end can be logically explained [by a tech - if the real cause is finally found].
Disclaimer: my PoV is that of a software developer and I'm monitoring this behaviour since release on my i7 9700k | 32 GB RAM | 4070ti super 16 GB VRAM. The latest patch (1.0.2.) did stabilize the system a bit, but GSC still has to do some work here.
If I have a phone book that can hold 10 phone numbers you might need, and I write down those 10 phone numbers, but you need 11 phone numbers, that's an "out-of-memory" error and what OP is describing.
A memory leak would be you needing 10 phone numbers, but there is no space in the phone book because I didn't erase the previous 10 numbers, or I wrote the same number several times. Technically, you are still out-of-memory, but it's the fault of the application (in this case me). So the games fault for not recognizing when a phone number (texture/material/in-game asset) is no longer required to be available to fetch quickly (think something like still rendering anomalies that are too far away for you to even see or interact with, or what the walls inside Slag Heap are supposed to look like even though you're in the Lesser Zone and have been for 45 minutes).
This means there is no available space to load things that you are actually close to into the fast-fetch memory (VRAM).
In OP's example, it's your own fault because you didn't buy me a phone book with enough space to fit all the numbers (I.e your fault for not having enough memory to run the game).
A solid way I've found to reproduce a persistent memory leak error is to keep loading a save. I've noticed that I can play for a sufficiently long time, sometimes hours with no noticeable drop in performance until I die and have to reload a save.
What usually happens is I'll save before engaging enemies, get killed, reload the save, engage the enemies again and this time my FPS has dropped by 10-20. I then die again due to the lag, reload the same save, and my FPS will now drop seemingly exponentially with every subsequent reload.
My guess is that it re-caches almost EVERYTHING into memory every time you reload a save, and there might even be a compounding error for subsequent reloads without restarting the game.
A remedy is often to look at the ground/your feet for a few minutes and the game will seemingly eventually refresh it all on its own (Although this only seems to buy you a few minutes of optimal performance at a time). Pressing Escape and waiting also seems to work, but standing still and staring while lagging doesn't seem to work. You gotta obscure much of the rendered game world by looking at the ground or pausing the game.
call it memory leak or not, there is this issue of game suddenly and randomly stopping performing normally and going into slideshow out of nowhere.
it is widespread, tons of threads about it here and everywhere people discuss this game with all sort of different setups, even youtubers experiencing it live or people that do benchmarks with all sort of hardware will confirm this is an issue within the game.
CSG tried to fix it in the first patches, it´s better than before but it´s still there.
it´s in the patch notes, they say fixed various potential memory leaks and crashes !
let´s not pretend this shipped in a good shape. lol
it´s not done with the first few patches, it will take tons of patches just like with Cyberpunk.
and i dont believe they doesnt know that problem exist at launch, and so there would be a fast fix if they let it ship with those problems.
Well this is a topic about mem leaks specifically so looks like you are in the wrong place. Maybe you can find the general performance thread somewhere. Cya. *Alias turns his back to unknown and starts whistling the Ukrainian nation anthem as the poor, misinformed troglodyte slowly fades into non-existence.
Random user on steam forums "ThErEs No MeMoRy LeAk"
Holy coolaid
no clowns for u, fade in non-existence lmao
They said they fixed potential mem leaks. Stop trying to flame. All performance tests in this game that I have seen have not had a mem leak (I watched maybe 2 dozen) before I bought the game.. Sounds like potato problems. Should have upgraded. ''I bOuGht My PC 6 yEaRs aGo.......ShOuLd PlAy GaYmE!!!!!!!''
Just for the sake of reflection: who is flaming now?