VaM 1.x How free up space in the vam folder

[Yarnybasi]

1. How I can sort the looks and scenes that I need. to remove unnecessary things, including unnecessary packeges.. associated with deleted scenes and looks
2.Can I somehow collect everything I need in one place and remove the unnecessary without any problems, tell me about your experience. and will it read files if in addon packeges I create folders looks , scenes and drop my var files in .

 

[SlimerJSpud]

There's no simple solution. Sometimes, you have to wade in there with the hip boots on and shovel out the muck. There is a Python script I use heavily that lists dependencies. This can help you find vars that aren't used by other vars. It also checks your local appearance, clothing, and skin presets, but not locally saved scenes. What you can do is create a holding area folder that's not scanned by Vam. After running this script on some group of vars, start dragging the orphans out to the holding area. It also helps to launch the tool after doing some of this to see if Vam thinks you need one of those relocated orphans. Put that one back and keep going. Once you've moved all the orphans out, and the missing dependencies list in Vam is empty, then you can nuke the holding area.

For the script, you have to install Python, then you have to copy and paste the code into a file. I put it in the root Vam folder. To run it, cd into the vam root folder, and do:
python List_Deps.py -p . -n toyser

Script for listing all dependencies

For a while I've been thinking of making a script that can list all dependencies in all vars and presets, or list which vars depend on a specific var. After getting inspired by le_hibous pyhton script (https://hub.virtamate.com/threads/too-many-heap-sections.38525/#post-108718), I finally got...

hub.virtamate.com

 

[stealthsonic]

1. How I can sort the looks and scenes that I need. to remove unnecessary things, including unnecessary packeges.. associated with deleted scenes and looks
2.Can I somehow collect everything I need in one place and remove the unnecessary without any problems, tell me about your experience. and will it read files if in addon packeges I create folders looks , scenes and drop my var files in .

You can use an external app called VarManager. I have over 5,000 models and looks, and the number of duplicate resources inside the VARs has become overwhelming. VAM’s loading times have worsened, and improperly named resource files are causing the resource manager to stop loading. I often have to repeatedly press the reload button to get all the resources to load, and occasionally I encounter the “too many heaps” error. These issues are primarily due to having too many VAR files.


So far, VarManager has been doing a great job of creating and organizing VAR files outside of the VAM app.

 

[Hipper]

My experience.

I only have some 2,000 items in the VAM/AddonPackages folder.

My main annoyance was having a lot of of 'scenes' on the scene screen, some 1,000. Of course these can be segregated by using 'Favorites, 'Hidden', and the 'Template' screen. You can also select different orders of the scene screen, such as A to Z, New to Old etc.. In the end I found a combination of all these better then spending time weeding out all the stuff I'd never use.

I do have moments of 'house cleaning' though which gives me some satisfaction. You can accumulate a lot of 'rubbish' by downloading environments for example and they might have a Person Atom in them which is of no use to you. I at last realised that when you download an environment you can select the bits you want to download and don't have to accept stuff you don't want.

I never noticed any improvement in VAM loading times after house cleaning having removed some 400 scenes out of the 1,000 I had.

I also tried an idea I had - load up an environment, get rid of atoms you don't want in that scene, then save it under a new name that suits your sorting methods. This saved scene is now filed in your VAM/Saves/scene folder. However I thought by doing that I could then delete the original but it didn't work. Maybe it could if I put more effort into it but how much time do you want to spend on this sort of work when it doesn't really yield any benefit. Also I now see little point in cleaning up an environment scene until I actually come to use it.

 

[hazmhox]

I never noticed any improvement in VAM loading times after house cleaning having removed some 400 scenes out of the 1,000 I had.

Because scenes don't matter.
Scenes are basically json files and generally (if packed well) maybe textures, sounds and a couple of plugins.

This is not what slows you down. The offenders on loading times are anything vam related ( Morphs and hairs )

 

[Hipper]

Because scenes don't matter.
Scenes are basically json files and generally (if packed well) maybe textures, sounds and a couple of plugins.

This is not what slows you down. The offenders on loading times are anything vam related ( Morphs and hairs )

I was referring to the initial loading from the VaM (Desktop Mode).bat file. What affects the loading time of this?

 

[hazmhox]

I was referring to the initial loading from the VaM (Desktop Mode).bat file. What affects the loading time of this?

What I said
Any loading time in VAM pretty much, is building the whole "database" (if I can say so) of assets available at a click or two ( so morphs, clothes, hairs ) and are permanently at least a tiny bit preloaded.

Scenes, or assets, or textures packs are not in this type of database, so then don't have much influence. Even tho .var need to be listed.
That being said, if you have 3 millions of scene/assets .vars in your VAM, it will also have an impact of course

 

[Venom515]

There's no simple solution. Sometimes, you have to wade in there with the hip boots on and shovel out the muck. There is a Python script I use heavily that lists dependencies. This can help you find vars that aren't used by other vars. It also checks your local appearance, clothing, and skin presets, but not locally saved scenes. What you can do is create a holding area folder that's not scanned by Vam. After running this script on some group of vars, start dragging the orphans out to the holding area. It also helps to launch the tool after doing some of this to see if Vam thinks you need one of those relocated orphans. Put that one back and keep going. Once you've moved all the orphans out, and the missing dependencies list in Vam is empty, then you can nuke the holding area.

For the script, you have to install Python, then you have to copy and paste the code into a file. I put it in the root Vam folder. To run it, cd into the vam root folder, and do:
python List_Deps.py -p . -n toyser

Script for listing all dependencies

For a while I've been thinking of making a script that can list all dependencies in all vars and presets, or list which vars depend on a specific var. After getting inspired by le_hibous pyhton script (https://hub.virtamate.com/threads/too-many-heap-sections.38525/#post-108718), I finally got...

hub.virtamate.com

Apologies in advanced as this may be a dumb question relating to the script, as I may just be using this incorrectly. Is there a way to take a package that I am interested in deleting, and have it show which var files it has dependencies for that are not shared by others?

For example, I am contemplating removing a scene which has a lot of different files it references, can I have it list the files this scene has as dependencies that are not used by others? I may be using this scrip wrong but how I have been using it is going through the different dependencies listed in the Hub for this scene one by one and seeing if they are referenced else where. I used to just delete all of them and then run the scan for missing packages but somewhere along the line I think I removed something that was no longer on the Hub and screwed myself a bit

 

[SlimerJSpud]

The Python script tells you what other vars or local presets depend on a particular package you scan. It's like a reverse lookup, which doesn't exist in game. The package manager in game tells you what a given package needs as dependencies. This info is in the meta.json file, which can be opened for viewing in an editor without unpacking the var.

In order to do what you ask, you need to first get the list of direct dependencies of the scene you want to delete, then scan each one of those dependencies separately with the Python script. It sounds like you've been doing that. It's not automated.