-
-
Hi Guest!
Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.
Details about the security patch can be found here.
- Thread starter bill_prime
- Start date
bill_prime updated VAR Manager with a new update entry:
Fixed issue with root folder exception settings.
Read the rest of this update entry...
Fixed issue with root folder exception settings.
Read the rest of this update entry...
Something that would let me backup all unreferenced vars that are older than a certain date would be nice.
edit: Actually I can just backup all unreferenced and then manually copy newer vars back. So maybe not really needed as a feature since that is easy enough to do already.
edit: Actually I can just backup all unreferenced and then manually copy newer vars back. So maybe not really needed as a feature since that is easy enough to do already.
Last edited:
bill_prime updated VAR Manager with a new update entry:
Added move old versions of vars function. Added skip button to duplicate item resolver.
Read the rest of this update entry...
Added move old versions of vars function. Added skip button to duplicate item resolver.
Read the rest of this update entry...
bill_prime updated VAR Manager with a new update entry:
Updated "Restore All Referenced vars" to only restore versions needed/latest vars.
Read the rest of this update entry...
Updated "Restore All Referenced vars" to only restore versions needed/latest vars.
Read the rest of this update entry...
bill_prime updated VAR Manager with a new update entry:
Added backup/restore var config functions.
Read the rest of this update entry...
Added backup/restore var config functions.
Read the rest of this update entry...
The VARManager_DisableDuplicateLog.txt is just a log file showing you what duplicate items where hidden. It will be overwritten next time you use the duplicate item resolver.
The Save button below saves the current .var configuration (list of all .vars) to a text file of your choosing.
The Restore button below allows you to choose a .txt file from the above Save function, and it will backup/restore vars until only the vars in the saved text file are active.
This is pretty awesome tool, great job! Now, I have a question/suggestion:
Would it be possible to have selective/specific filters? Let's say I want to quickly filter out clothes, so I back up specific type vars. It works nicely, but there are bunch of files where there is a scene with a look and morphs, and some clothing slapped on top of it. Even though it should be in a 'look' category, it will be detected by whatever you're filtering. If possible, I think having and/or checkboxes would be great. Idea is to be able to filter out vars that have only specific types of content in them, but not others. Or however many selected categories, but not others.
To give an example, if working with manual sub-folder structure, you could filter out .vars that have only scene file and morphs, that would result in filtering out majority of looks that happen to not have an appearance preset. Filtering out files only with morphs could easily separate scene vars from pure morph packages. Or files with only clothing and morphs could be easily found and put into clothing sub-folder manually. For some more complex vars, if they have morphs, looks preset, clothing, and a scene, they're most likely look scenes.
If you have many not sorted .vars, it's tedious to e.g. backup only clothing and then have to check many files manually because clothing is often included in scenes that should be in looks category, so it kind of defeats the purpose. It would be nice if that kind of filtering was possible.
Would it be possible to have selective/specific filters? Let's say I want to quickly filter out clothes, so I back up specific type vars. It works nicely, but there are bunch of files where there is a scene with a look and morphs, and some clothing slapped on top of it. Even though it should be in a 'look' category, it will be detected by whatever you're filtering. If possible, I think having and/or checkboxes would be great. Idea is to be able to filter out vars that have only specific types of content in them, but not others. Or however many selected categories, but not others.
To give an example, if working with manual sub-folder structure, you could filter out .vars that have only scene file and morphs, that would result in filtering out majority of looks that happen to not have an appearance preset. Filtering out files only with morphs could easily separate scene vars from pure morph packages. Or files with only clothing and morphs could be easily found and put into clothing sub-folder manually. For some more complex vars, if they have morphs, looks preset, clothing, and a scene, they're most likely look scenes.
If you have many not sorted .vars, it's tedious to e.g. backup only clothing and then have to check many files manually because clothing is often included in scenes that should be in looks category, so it kind of defeats the purpose. It would be nice if that kind of filtering was possible.
This is good feedback and the flexibility would be nice, but its too difficult to determine automatically if something is a look or a scene etc.
For example some clothing items include a scene, some looks include scripts like expressionrandomizer, looks don't always include morphs, etc.
One thing I was planning on adding next is a checkbox to "Ignore Disabled Items" for the Specific-Type filters. So for clothing and hair items, it will check if the item is hidden and if so it it will not mark the .var as "having clothing/hair".
Have you used the duplicate item resolver to hide duplicate clothing/hair? I think this feature would be helpful and definitely prevent a lot of vars from being marked with clothing/hair that don't need to be.
I did use it and I guess it would hide duplicate clothing or hairs. Still, some looks have non duplicates.
About filtering - obviously it would be super hard for it to be fully automatic, but I think that having more specific filters should make manual cleanup much easier. As you said, some looks include clothes/scripts and some don't.. some and + or combinations would be needed for this. If your filter checks for folder names inside .vars, perhaps it's not too hard to do. For example, for filtering out looks you could use filter like "has a look preset and can have optionally morphs/clothing/whatever" and second one "has a scene file and optionally morphs/scripts/etc" - I'd imagine it could have 2 tabs for categories: 1. must have; 2. can have. If you select morphs only in "must have", it would backup files that have only morphs in them and nothing else. If you add categories in "can have" on top of that, it would show files that must have morphs and could have anything from the "can have" categories, and multiple categories chosen in "must have" would mean it would show files that consist only of those categories.
Another example that would work for clothing items: setting clothes in "must have" and scripts, morphs, and clothing presets in "can have" would filter out accurately all clothing in one go, as some clothing comes with scripts or morphs (it would ignore files that have all categories mentioned before but have also a scene file, which is unlikely for clothing vars). Right now doing that sort of thing it's de facto checking almost all of your vars manually anyway.
Ignore disabled items is also a neat idea for sure. It would be great if .meta files on the hub included their category, that would make everything much easier..
I'll have to think about that, it would require a lot of changes to the UI and many new functions to filter things accordingly.
I was also just doing some testing/thinking about another way to detect Scenes with animation/mocap. I could just add a simple file size check that checks the scene file vs a minimum size (most mocap scene.json files are 20MB+, though some scenes that have animation can be as small as 500kb).
I could add a new filters for "Large Scene Files/Small Scene Files" and allow the user to enter the minimum value? This can be used to distinguish betewen small scenes (probably looks) and large scenes with animation.
This seems like a decent way to do it as reading every scene.json to find animation seems like it would be pretty inefficient.
Don't suppose you could add the ability to "Always Enable Plugins From This Package Without Prompting" to all installed VARs? Clicking "Always Allow" for every plugin in every scene gets old. Couldn't find anything that does this but it should be possible. It just writes a small .prefs file under AddonPackagesUserPrefs.
- Messages
- 3
- Reactions
- Points
- 1
Keep getting this error when trying to install it.
Is there something I am missing?
Is there something I am missing?
Try moving the .exe to the VAM directory, or you don't have the proper permissions in place. You may need to run the application as administrator, or set your Windows user as an admin.
While that would not be difficult, I don't want that to part of the VARManager as this function is meant to try to prevent malicious plugin code.
bill_prime updated VAR Manager with a new update entry:
Fixed potential infinite loop with scan local files functions.
Read the rest of this update entry...
Fixed potential infinite loop with scan local files functions.
Read the rest of this update entry...
Try new version!
EMPIR
-
- Messages
- 179
- Reactions
- Points
- 28
Thanks for quick fix. I'll use it and if there is a problem i'll let you know
Same loop happened with "Scan local presets for references > Appearance checked" no vars added but var manager is not responsive.
Maybe it will happen to clothiing, hair, morphs etc too. Please fix it if posssible...
Strange, which function are you using?
