Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

0. reboot (no apps or games or anything)

2.3 gb physical memory

2.9 gb  system

 

1. fresh reboot + steam + firefox + discord

3.8 gb physical memory

4.8  gb  system

 

2. fresh reboot + starting up strive / loading save

4.2 gb physical memory

 5.2 gb  system

 

3. fresh reboot + running strive, idling on main mansion slave menu w/ 10 residents

4.5 - 4.9 gb physical memory

 5.5  gb  system

 

4. fresh reboot + running strive + looking at portrait folder in game

10.5 - 14.2 gb physical memory

 19.2 - 19.8 gb  system

closing the portrait menu doesn’t immediately drop the memory usage. It stays at its peak levels unless I  return to the main menu.

Same thing happens with bodies menu.

 

5. fresh reboot + running strive + fighting a 4v4 battle

no change from mansion. Will run like ass if I didn't reset via main menu after using portraits menu.

 

 

What stat are you looking at? committed memory? I mentioned that is fairly high for the game, but it's not actually memory that's allocated and in use, it's a sort of pre-allocation where something says "I think i'm going to want to use this, reserve it for me".  If you have virtual memory then this will never really impact actual memory usage.  Be better if it didn't do it, but it's not really much of an issue in my opinion.  More useful is to look at the private working set size and that's what I was referencing in my numbers.

As a note, for #4:

4. fresh reboot + running strive + looking at portrait folder in game

That's basically expected behavior with base game, it loads every single portrait into memory, and it's loading their uncompressed raw format which is significantly larger than their on-disk size.

Now that I re-read the other numbers, it actually seems your memory usage is basically in-line with my own. At least I assume #2 is an add-on to #1, and thus it's using around 300-400mb. Not sure why you're looking at system wide values though, much simpler to just look at Strive.exe. Working set numbers are the more useful ones, they show up in Physical Memory if you do properties on Strive.exe in process explorer.

If you want to reduce memory for loading of the portraits folder, that's why I added the delayed loading mod.