Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
In Use: 22.7G Available: 41.0GB
Committed: 32.5/67.7GB Cached: 40.9 GB
Hope this gives you more of an idea of whats going on
And I also saw cached equaling available at times
So if you have 64GB of total RAM, with 22.7GB being actively in use, and 40.9GB of RAM having inactive code as cache. That means 63.6GB / 64GB of your RAM is actually being used. Available doesn't mean "free RAM", it means it can dump that inactive code if it really needs to and instead move active code into it. But it's still 99% RAM usage right now.
There's plenty of programs you can use that clear all inactive RAM, so in this case you'd get 41GB back. Just google "emptystandbylist"
While technically available, it doesn't just instantly poof out like magic. The OS will have to look at each program that has cached RAM, find the lowest priority of those, and then figure out what files to get rid of, to make room for new ones. This like I said, is extra processing and can cause stuttering in games. VS just having the RAM actually free, and skipping all the above, just moving files straight into free RAM.
Cool story but the GPU isn't the problem here. You prolly need to start reading the news more.
Those programs don't cause any issues. They just clear your RAM, it's the same thing as turning your PC off, without actually having to turn it off. That's just how windows works. When you're playing the game, you'll see like 10-12GB of RAM being used by the game. That number won't really change even after 5 hours. Because as you go through different levels / areas / bosses, you'll need different data. So once you beat an area, the code is no longer "active". But maybe you'll go back there again, so instead of just throwing it in the trash and needing to read it off a much slower SSD later, it goes to RAM cache instead.
So in my example, I have like 33gb being used by wukong. This is after completing an entire chapter, and going back and forth to 4 different chapters and beating around 12 bosses. That's what the 20GB of cached data is right now.
What news? What are you talking about? Why the snarky response with no actual answer?
What CPU do you have? I have a 4090 rtx strix desktop and mobile 4090 in a blade 18 laptop. The desktop has a 5900x amd cpu and my laptop has an Intel i9 13950h. Intel has been horrible with UE 5 games and results in what you are describing. Now it's not bad to me in this game as I think BMW plays UE5 pretty smoothly. But games like gray zone warfare is an example where I had horrible stutter. Even Jedi survivor was really bad and that's unreal 4. So if it's a 13th or 14th gen Intel it may be that and or one of the affected chips that are not that stable.
Guess that explains why there is no issues with 96gb ram. Oo
Tools like ESLC (Easy Standby List Cleaner) etc. are generally NOT RECOMMENDED because they CAN indeed cause crashes (in games with Denuvo and trigger happy Anti-Cheats) and they almost certainly will induce stuttering once they start cleaning up the ram because it is a sudden workload after all. Windows manages RAM perfectly fine without the need for additional help and any trained IT-Professional will tell you the same and confirm that.
Windows will delay freeing the RAM upto the last possible moment and that is by design. Stuff cached in RAM is ALWAYS quicker to retrieve then stuff cached/paged on your drive or stuff that needs to be loaded in at all.
As long as you have a pagefile setup (which is default in Windows anyways) Windows will NEVER crash because it is running out of RAM (except when your pagefile also get's filled but that is very unlikely unless you try on purpose). Windows ALWAYS has top priority over resources and the second prioritzed thing will ALWAYS be the application you currently have focused in the foreground which in this case would be Wukong. So Windows would always try (under ANY circumstances) to keep the OS and your foreground process alive. If it was an "Out of RAM" issue (which is impossible in this game with 64GBs of RAM) you would see unimportant background processes dying first before anything else would massively slowdown or even crash.
Again the "Cached RAM" being that high is actually on purpose as the OS keeps the things cached that are most likely to be used again and will free up those resources by itself if something else needs them. So the statement that "Available RAM" does not mean available ram is also only partially true because "YES, there is data in it, cached for quick retrival BUT it can be freed up ANYTIME if something else requests it."
Just a little bit of Windows heads-up for the self proclaimed IT-Specialists giving dumb advice like using thrid-party tools in these threads.