User Preferences / Performance 2 Tab
“Memory Optimizer” New to update 1.21 this panel was added as a convenient way to quickly see how much memory is currently being used and then to trigger a memory optimization if needed.
”Optimize Memory Usage On Scene Load” If enabled, skins, clothing, hair, and morphs that aren’t in use will be unloaded when a new scene is loaded.
This can prevent VaM from crashing if your system runs low on memory.
Recommended to turn on if your physical memory is 16GB or lower. The downside is these items will take longer to load if they are used again later in the same session.
”Optimize Memory Usage On Preset Load” If enabled, skins, clothing, hair, and morphs that aren’t in use will be unloaded when a new preset of that type is loaded.
This can prevent VaM from crashing if your system runs low on memory. Recommended to turn on if your physical memory is 16GB or lower.
The downside is these items will take longer to load if they are used again later in the same session.
”Total Physical Memory” This indicates the amount of installed Physical (RAM) Memory installed on your system.
”Physical Memory Usage” This indicates the amount of installed Physical (RAM) Memory that VaM is currently using.
”Paged Memory Usage” or Virtual Memory is the amount of memory resources your computer is currently storing on your local drive as temporary files.
If VaM goes over the physical size of memory you have in your system it will start using Virtual Memory.
In most cases this shouldn't affect performance because there are a lot of unused objects in memory that can stay in Virtual Memory and are infrequently used, but Unity (which VaM is built on) still requires those objects to be allocated and referenced even if they are never or infrequently used. VaM was optimized to try to purge as many unused objects out of memory as possible
”Heap Size” is the amount of memory that is set aside for a program to use when it needs to store data that it has created dynamically. VaM is based on Unity and uses a C# programming language that requires a heap. Anytime a C# program needs memory to run tasks (e.g. save items in a list or other structure) it has to allocate memory from the heap to store that data. Once that data is no longer used, that data is not immediately deleted and the memory is not immediately freed due to how heap storage works. It is later freed during a process called garbage collection. This process can take some time and may hang the application briefly which is why it is done at convenient times like on scene loading.
”Trigger Memory Optimization Now” Purges all dynamically loaded items like clothing and hair, releasing them from memory, so they will have to be reloaded again if they are used later. This is the same function as using the “Optimize Memory” function in the “Performance Monitor”.
”Report Usage” Breaks down the amount of assets loaded within memory of your current VaM session. The following are examples of scene reports:
VaM at startup empty scene:
A 2 person animated scene:
A 3 person animated scene:
”Reset All Settings to Default” Resets all settings in the User Preferences tab to default. This is a global reset, not just for this specific tab. Clicking this returns you to the “First Time User Startup Page”
“Memory Optimizer” New to update 1.21 this panel was added as a convenient way to quickly see how much memory is currently being used and then to trigger a memory optimization if needed.
This can prevent VaM from crashing if your system runs low on memory.
Recommended to turn on if your physical memory is 16GB or lower. The downside is these items will take longer to load if they are used again later in the same session.
This can prevent VaM from crashing if your system runs low on memory. Recommended to turn on if your physical memory is 16GB or lower.
The downside is these items will take longer to load if they are used again later in the same session.
If VaM goes over the physical size of memory you have in your system it will start using Virtual Memory.
In most cases this shouldn't affect performance because there are a lot of unused objects in memory that can stay in Virtual Memory and are infrequently used, but Unity (which VaM is built on) still requires those objects to be allocated and referenced even if they are never or infrequently used. VaM was optimized to try to purge as many unused objects out of memory as possible
VaM at startup empty scene:
A 2 person animated scene:
A 3 person animated scene:
Last edited:
