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
if just pure vanilla, yes that can be a bit abnormal - make sure you subscribe to LSMR, it's mandatory mod for memory management.
The more DLCs you have the more memory you need.
The more mods/assets you use, the more memory you need.
It is not a memory leak since this is expected behavior from the game. The content has to be available in memory in order to be quickly accessible.
"Standard" is relative. 8 GB was fairly common when the game was released. 64 GB may be standard in a decade. Games and software can certainly push the boundaries of hardware usage.
Quite a few games will easily make use of 32 GB RAM, and quite a lot more if mods come into the equation.
Star Citizen, Tarkov, this game itself, Cities Skylines 2, etc. Sure they may run with less RAM, via page file, but the point is they will make good use of that.
And considering the amount of modded content available for Cities Skylines, and the fact lots of people use them, higher memory usage than the vanilla game allows is often a given.
With 11k+ assets, my memory usage is at 90 GB+ RAM, and there are people that have even more.
Same applies to other games with lots of modded content too, such as Transport Fever. I play on maps there that regularly use over 40+ GB RAM.
Laughs in DCS World...
Maximum settings, VR, large maps, asset heavy mission, etc. It can easily be memory starved with 32GB.
They prove you wrong so you block them. That'll show them!
Don't bother. They'll never understand. :)
Try to optimize what you need. Don't go overboard with assets you won't ever use. The only assets I load are houses and high residential , high commercials I really only need.
The swap files is used by Windows at launch of Windows. It has nothing to do with the game.
The Windows Page file (Swap file), auto increases in size as it is being used. When you exit the game, the swap files stays at it's previous size, so it doesn't have to constantly resize itself forever, possibly killing your drive prematurely.
But the memory is always released upon shutdown/reboot, but it keeps the previous max page file size enabled. Otherwise, windows will remove unneeded files from RAM and put them in the page file if RAM becomes over full, to make room for more urgent RAM use.
But all games love the whole game loaded in RAM so it doesn't have to page stuff in and out of swap files, as it slows down the game.
Luckily CS1 is an ant farm type of game and will function in single digit FPS just fine. There is no high speed action like a shooter game, so this game will store excess assets/workshop in the page file, for when it needs it, at which point it is moved into RAM.
But if you're filling up your 32GB of RAM, then you are actually using nearer to 64GB of memory. Windows like to keep RAM half full at all times, so if 32GB is full, then you are using 64GB or more, then windows will automatically increase the pagefile up to twice the size of RAM, or up to 64GB of swap file. or 96GB total Virtual memory (32GB RAM + 64GB Swap file).
If you get a crash at this point, it should be from running out of memory, as auto pagefile for windows stops at x2 RAM size. Now you may need to manually set up a pagefile to exceed 96GB of memory.
PS, let me know of error in logic, I have to run right now! TTYL