any temp fix for the memory leak they created?

[Reaper]

They had a memory leak issue back in 2019 that they patched, but this latest DLC broke it again. There's no reason this game should fill 16GB of RAM and create an almost 10GB paging file after a few hours of playing

[Knives]

No but I am having the same issue, huge page file, filled up 16gb of RAM, significantly degrading performance over time, and it all started with tenticles dlc

[Nite69]

you can get apps to clear the pagefile after every game session, I use RamMap

https://docs.microsoft.com/en-us/sysinternals/downloads/rammap

[davidb11]

This game does not do that to me. What the heck.

[Nite69]

Originally posted by davidb11:

This game does not do that to me. What the heck.

It happens when ya load too many maps on the same play session, if ya work on one area at a time and don't change maps too often it will help it.

[Teefa]

Originally posted by FeaR_TH3_Reap3R:

They had a memory leak issue back in 2019 that they patched, but this latest DLC broke it again. There's no reason this game should fill 16GB of RAM and create an almost 10GB paging file after a few hours of playing

No reason?

I mean, the game files themselves are more than 100GB, and that probably includes some compression, and it doesn’t include any procedural/instanced data. Why do you think those files exist if not to be (eventually) loaded into memory?

And caching runtime data is an extremely common practice. Virtual memory is hardly a ground breaking technology.

IMO, your evidence of a memory leak is pretty dubious as it is *exactly* the behavior you should expect for such a large game.

[Reaper]

Originally posted by TheyAria:

Originally posted by FeaR_TH3_Reap3R:

They had a memory leak issue back in 2019 that they patched, but this latest DLC broke it again. There's no reason this game should fill 16GB of RAM and create an almost 10GB paging file after a few hours of playing

I mean, the game files themselves are more than 100GB, and that probably includes some compression, and it doesn’t include any procedural/instanced data. Why do you think those files exist if not to be loaded into memory?

And caching runtime data is an extremely common practice. IMO, your evidence of a memory leak is of limited utility as it is exactly the behavior you would expect for such a large game.

That's not even close to how computers work. It's easy to spot a memory leak if you actually know what you're looking at. The fact you think game size on a hard drive has anything to do with how much data is stored in RAM during a play session tells me you have no idea what you're talking about

[Teefa]

You’ve eyeballed some “unreasonably” large ram usage and claim that is because of a memory leak. I am saying one would absolutely expect that amount of usage for a game of this size. It is a huge game with a lot of assets.

Do you think those assets stay entirely on the HD during runtime?

I didn’t say the file size is directly related 1:1 to runtime memory footprint. I made a rough comparison of the relative scales involved.

It is obvious, or perhaps not, that a 100GB game might utilize more than 16GB of runtime memory, if only to speed up load times of common or recently used assets. A so called memory leak isn’t needed to explain that behavior.

In contrast, I wouldn’t expect that behavior in a 100MB game. 90MB of assets isn’t likely to fill up 16GB of ram.

Textures, sounds, animations, models. They all take up a lot of HD space and they are all loaded into main memory as they are used.

What do you think the game is doing at start up and between levels?

Keep banging those rocks together, guys.

[Reaper]

Originally posted by TheyAria:

You’ve eyeballed some “unreasonably” large ram usage and claim that is because of a memory leak. I am saying one would absolutely expect that amount of usage for a game of this size. It is a huge game with a lot of assets.

Do you think those assets stay entirely on the HD during runtime?

I didn’t say the file size is directly related 1:1 to runtime memory footprint. I made a rough comparison of the relative scales involved.

It is obvious, or perhaps not, that a 100GB game might utilize more than 16GB of runtime memory, if only to speed up load times of common or recently used assets. A so called memory leak isn’t needed to explain that behavior.

In contrast, I wouldn’t expect that behavior in a 100MB game. 90MB of assets isn’t likely to fill up 16GB of ram.

Textures, sounds, animations, models. They all take up a lot of HD space and they are all loaded into main memory as they are used.

What do you think the game is doing at start up and between levels?

Keep banging those rocks together, guys.

Thanks for confirming you still know nothing. Just continue to ignore the basics of how RAM even works as you try to sound smart. By your logic every game above 16GB would put every person's computer to 100% RAM usage, except that doesn't happen. Not to mention that even the devs think the game is playable with only 6GB so even they don't expect the game to use that much. But then again, I don't really care if you don't understand or not. Have fun with that.

[Teefa]

Originally posted by FeaR_TH3_Reap3R:

Originally posted by TheyAria:

You’ve eyeballed some “unreasonably” large ram usage and claim that is because of a memory leak. I am saying one would absolutely expect that amount of usage for a game of this size. It is a huge game with a lot of assets.

Do you think those assets stay entirely on the HD during runtime?

I didn’t say the file size is directly related 1:1 to runtime memory footprint. I made a rough comparison of the relative scales involved.

It is obvious, or perhaps not, that a 100GB game might utilize more than 16GB of runtime memory, if only to speed up load times of common or recently used assets. A so called memory leak isn’t needed to explain that behavior.

In contrast, I wouldn’t expect that behavior in a 100MB game. 90MB of assets isn’t likely to fill up 16GB of ram.

Textures, sounds, animations, models. They all take up a lot of HD space and they are all loaded into main memory as they are used.

What do you think the game is doing at start up and between levels?

Keep banging those rocks together, guys.

Thanks for confirming you still know nothing. Just continue to ignore the basics of how RAM even works as you try to sound smart. By your logic every game above 16GB would put every person's computer to 100% RAM usage, except that doesn't happen. Not to mention that even the devs think the game is playable with only 6GB so even they don't expect the game to use that much. But then again, I don't really care if you don't understand or not. Have fun with that.

Again, I’ve said nothing more complicated than 100GB > 16GB.

6GB is the *minimum* requirement. That is the minimum amount of data needed to run one scene at an arbitrary speed. At minimum specs, everything else needs to be dynamically loaded and offloaded to fit.

Do you think constant HD access makes the game faster or slower than caching assets in memory?

Why do you suppose they list 16GB as the recommended spec?

PS It’s kinda cute that you think of 16GB of ram as a lot or somehow beyond the capacity of modern games.