- Jun 19, 2018
- 641
- 1,166
Ok so after cleaning up 363 GB worth of .var files, I really struggle to see the purpose of .var files.
My understanding is .var is meant to somehow save space by giving creators the ability to break down their contet into modules and have them reference each other.
In an ideal scenario, if there are 10 creations that make use of a single asset, the asset would come in a separate .var file and all the other ones would be referencing it.
However it looks like instead every single .var file has all its dependencies bundled together. Just search for the term "eye" in the Clothing menu and see how many pages of the same duplicate item you get. It looks to me like this defeats the entire purpose of why .var was implemented.
I am still only a couple days new to VAM and still figuring out how things work, I don't understand how having duplicate assets across several .var files is meant to take up less storage space than throwing everything in one custom folder where duplicates just overwrite each other. I'm guessing the old system had flaws of its own.
My understanding is .var is meant to somehow save space by giving creators the ability to break down their contet into modules and have them reference each other.
In an ideal scenario, if there are 10 creations that make use of a single asset, the asset would come in a separate .var file and all the other ones would be referencing it.
However it looks like instead every single .var file has all its dependencies bundled together. Just search for the term "eye" in the Clothing menu and see how many pages of the same duplicate item you get. It looks to me like this defeats the entire purpose of why .var was implemented.
I am still only a couple days new to VAM and still figuring out how things work, I don't understand how having duplicate assets across several .var files is meant to take up less storage space than throwing everything in one custom folder where duplicates just overwrite each other. I'm guessing the old system had flaws of its own.