16 days 17 hours
Hearts of Iron IV
5 days 2 hours
METAL GEAR SOLID V: THE PHANTOM PAIN
3 days 18 hours
Crusader Kings II
22 days 2 hours
Europa Universalis IV
9 days 14 hours
Sword of the Stars II: Enhanced Edition
8 days 8 hours
No, it's not. This is a far too common misunderstanding of memory allocation works in a modern OS like win 10.
it'll use whats available is the short response.
unused RAM is wasted RAM.
Same goes for video memory. just cause a game uses 4-6 gig does not mean it needs it. it'll intelligently re-assign RAM and VRAM as needed.
nowadays you cannot take the amount of RAM or VRAM that has been used as being a good indicator of what is needed, but that is a good thing.
I'm not even sure what you thought I meant from a very simple statement, but your replies don't cover what I was referring to at all.
"it'll intelligently re-assign RAM and VRAM as needed."
That is specifically what I am referring to. Windows stores "freed" memory as "standby" memory, in case a program calls it back again. In some cases this speeds up poorly coded memory management. In other cases it makes better use of large ram pools than the program was designed for. Much more important for older software than it is for modern 64 bit programs.
In certain instances, programs and games that use and release memory too frequently, confuses windows. It will dump released memory into standby, even though the program is never going to call it back. Then it refuses to release that standby memory. This leads to a quasi-memory leak issue in certain cases which will fill your free memory completely with standby memory. This is an issue with windows, not the programs, since only windows controls standby memory.
When that happens, and standby memory has filled your ram completely, any further memory access has to go through windows first to release the standby, which slows the computer virtually the same way as full memory, even if you technically have a dozen gig of free ram. It only becomes an issue when completely full.
It's a problem that has existed since win introduced it, and a problem they continue to deny even exists. It was a major problem with superfetch in win 7, the reason most power users disabled it. It's less of an issue in 10, as far as superfetch and prefetch are concerned.
I've used ramap to clear standby cash in these instances across a dozen computers and laptops over the last decade, and shown countless others how to fix an issue that had them convinced they needed more ram. It's all because of windows "smart memory allocation."
I assume you posted this before the update. I'd have thought the same, but seems not.
"The new Game Mode will work for Win32 and UWP apps"
I get the insider builds, I'm gonna test this and if it's bullshit you better believe I'll be back saying that lol
For the record, I'll NEVER pay for a game from the windows store without many significant improvements to the entire thing.
I would take everything BuzzFeed says with more than just a grain of salt, so I'm inclined to agree with Tovias.
you don't want much, do you?
Sure thing, the guy who did the delidding on his 7700K was using an NZXT Kraken X62 cooler for his part - the PCGamesN test rig uses a Corsair H100i v2 for our CPU benchmarks.
He used multiple of the same civ
yes, and as i explained in the posts above, that was 3 weeks ago. 3 days after that, changes were made. so had the article been 3 weeks ago, it would have been accurate.
I'm not really sure what he said so I'll give you the benefit of the doubt. He's changed it now and it's accurate.
Clicking on links in articles to retailers or publishers may mean we earn a small commission. More