So i'm sorta new to vam. I followed all the instructions to install the updater but I get this message when installing the latest version, can anyone assist? Thanks.
Unity Virt-A-Mate [v1.22.0.3] [Meshed VR]
Did you download easy mate or something? Version 1.19 is outdated.
For a clean install I recommend downloading the updater zip from the official patreon page. Then just drop and run it on an empty folder.
- Dec 1, 2018
- 2,169
- 2,089
Anna invited the kitty over (last optimization results before moving to 3070)
You don't have permission to view the spoiler content.
Log in or register now.
Last edited:
- Jul 13, 2020
- 331
- 1,299
How did you get it to look that clean? I have all settings set to MAX and my scenes still look like PlayStation 3.
- Feb 5, 2021
- 921
- 1,364
- Jul 13, 2020
- 331
- 1,299
Laptop:
Acer Nitro 5
Intel Core i5 10300H
Nvidia GTX 1650ti 4GB
8GB memory
Desktop:
AMD FX6100 Black Edition
AMD Radeon RX580 8GB Black Edition
Corsair Vengence Extreme 16GB
I built the desktop in 2012, upgraded the memory and upgraded the GPU from an Nvidia GT 630 4GB to the RX 580. It's old, but still works fine with whatever I throw at it. Mainly GTA V +Mods, 3DS Max, DAZ, Blender, Gimp, PS. I am building a new rig in June. Still deciding if I should go AMD or Intel CPU. What I DO know is there is an RTX 3090 calling my name.
Acer Nitro 5
Intel Core i5 10300H
Nvidia GTX 1650ti 4GB
8GB memory
Desktop:
AMD FX6100 Black Edition
AMD Radeon RX580 8GB Black Edition
Corsair Vengence Extreme 16GB
I built the desktop in 2012, upgraded the memory and upgraded the GPU from an Nvidia GT 630 4GB to the RX 580. It's old, but still works fine with whatever I throw at it. Mainly GTA V +Mods, 3DS Max, DAZ, Blender, Gimp, PS. I am building a new rig in June. Still deciding if I should go AMD or Intel CPU. What I DO know is there is an RTX 3090 calling my name.
- Nov 24, 2018
- 167
- 111
I got a issue when i replace VaM_Updater.exe solve it by.. not replace it.
- Dec 1, 2018
- 2,169
- 2,089
Anna Shy
Not so shy at all
You don't have permission to view the spoiler content.
Log in or register now.
Not so shy at all
You don't have permission to view the spoiler content.
Log in or register now.
Last edited:
dumb question do i download all the parts and put them into the same folder after extracting them or do i just need one?
Are there any third party tools for managing var file dependencies? I'm looking for something that will show me files that I can safely remove without breaking a dependency somewhere else. Package Manager shows you what files a var depends on but you can't seem to see if any other vars depend on the file you have selected.
Just above I posted asking if there was a way to see what addons had a dependency on a selected var file. The issue was that if I removed something I didn't want to break something else. Since there didn't seem to be a way to do it I created one.
Dependency Viewer is a C# program that queries all the var files in a specified AddonPackages directory recursively and attempts to determine who depends on a selected var file. Once this is done the user can select a var file in the UI and can see which other vars have it as a dependency. I use the word "attempt" here because more than a few vars come out with broken meta.json files and while I have attempted to catch all the errors this can cause you may find you have issues.
There is help available in the form of text/html document and an image indicating the steps you need to follow to scan a directory. I will try to help where I can but I've got limited time to spend on this, I wrote it for myself and decided to share. The application produces a log which it overwrites on each run if you want to try to track down problematic vars.
The full source is provided so you can compile it yourself (C# VS2017) or scan it for viruses if you so wish. The only external libraries it uses are Newtonsoft JSON and NLog.
Limitations
So yeah, knock yourself out if you think you can get some use out of it.
Dependency Viewer is a C# program that queries all the var files in a specified AddonPackages directory recursively and attempts to determine who depends on a selected var file. Once this is done the user can select a var file in the UI and can see which other vars have it as a dependency. I use the word "attempt" here because more than a few vars come out with broken meta.json files and while I have attempted to catch all the errors this can cause you may find you have issues.
There is help available in the form of text/html document and an image indicating the steps you need to follow to scan a directory. I will try to help where I can but I've got limited time to spend on this, I wrote it for myself and decided to share. The application produces a log which it overwrites on each run if you want to try to track down problematic vars.
The full source is provided so you can compile it yourself (C# VS2017) or scan it for viruses if you so wish. The only external libraries it uses are Newtonsoft JSON and NLog.
Limitations
- I don't attempt to resolve ".latest" dependencies into the actual version number you have installed. In fact this program doesn't care if you have a dependency installed or not. It just uses the metadata in the var files.
- I don't check dependencies of dependencies. Realistically if you have it installed I should pick it up when I scan the dependent var file. Maybe sometime in the future.
- This may be slow if you have a lot of addons. My AddonPackages directory is 50GB and it takes about 5 seconds.
- Plenty of other limitations I'm sure, this has only been tested against my install, my day job is not as a programmer, C# is not a language I'm strong with and this was written over a two day period.
So yeah, knock yourself out if you think you can get some use out of it.
You must be registered to see the links
- Dec 1, 2018
- 2,169
- 2,089
isskini
Dependency Walker for VAM awesome work
I think .var is overall pretty much frozen for now i think it makes sense to work it continuously out now, there shouldn't be to heavy surprises with VAM 2.0 i hope
This already is super helpful
Lets see which problems it catches that the official parser does
Currently testing against a dataset of 73,6 GB (79.062.065.152 Bytes) with some non standard corruptions on USB3 (ASmedia)
20:27:56.9823 |Starting directory scan of: M:\VAM\AddonPackages
20:27:57.8933 |Generating Dependency List
20:27:58.4674 |Generating Dependency List View
ok starts to become interesting already it shows only round about 250 (42 per page) entries out of 1863 physical existing .var files in the current dataset
Spacedog_Import_Reloaded_Lite.latest <- is the top used dependency here in the dataset according to your scan (39 dependant)
Dependency Walker for VAM awesome work
I think .var is overall pretty much frozen for now i think it makes sense to work it continuously out now, there shouldn't be to heavy surprises with VAM 2.0 i hope
This already is super helpful
i also thought about this seeing all the erorr messages by the official parser lately getting so heavy
Lets see which problems it catches that the official parser does
Currently testing against a dataset of 73,6 GB (79.062.065.152 Bytes) with some non standard corruptions on USB3 (ASmedia)
20:27:56.9823 |Starting directory scan of: M:\VAM\AddonPackages
20:27:57.8933 |Generating Dependency List
20:27:58.4674 |Generating Dependency List View
ok starts to become interesting already it shows only round about 250 (42 per page) entries out of 1863 physical existing .var files in the current dataset
Spacedog_Import_Reloaded_Lite.latest <- is the top used dependency here in the dataset according to your scan (39 dependant)
Last edited:
Thanks, It sounds like I've got a lot more work to do on validation. I'll look at adding a page of metrics and maybe a way to view the data generated by the initial scan. There could be files missing from the list simply because nothing depends on them, but 250 vs 1863 is probably too large a margin for error.
- Dec 1, 2018
- 2,169
- 2,089
Let me see i guess |Found meta.json. Reading... is a file got parsed and found correctly hit ?
so easiest would be parsing for (Reading...) as a physical hit ?
197 matches for .meta.json
197 matches for Reading...
20:27:57.8743|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\Captain Varghoss.Tara.2.var
20:27:57.8743|INFO|DependancyViewer.frmMain|Found meta.json. Reading...
20:27:57.8743|INFO|DependancyViewer.frmMain|Attemping to parse metadata as JObject
20:27:57.8743|INFO|DependancyViewer.frmMain|Creating Varfile Class Instance forCaptain Varghoss.Tara.2.var
20:27:57.8743|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\Cgomes.1_scene_thamara.1.var
20:27:57.8933|INFO|DependancyViewer.frmMain|Generating Dependency List
hmm it seems to just stop here Cgomes.1_scene_thamara.1.var
it's also not checking the dependencies later of it anymore so it seems to have simply stopped the parsing of the other files after it
20:27:58.4514|INFO|DependancyViewer.frmMain|Checking deps forCaptain Varghoss.Tara.2
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for MeshedVR.3PointLightSetup.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for Hunting-Succubus.Enhanced_Eyes.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for NoStage3.Hair_Short_Pixie.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for VaMChan.Hair_Lightning.latest does not exist, creating and adding to existing dependency List
20:27:58.4674|INFO|DependancyViewer.frmMain|Generating Dependency List View
so easiest would be parsing for (Reading...) as a physical hit ?
197 matches for .meta.json
197 matches for Reading...
20:27:57.8743|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\Captain Varghoss.Tara.2.var
20:27:57.8743|INFO|DependancyViewer.frmMain|Found meta.json. Reading...
20:27:57.8743|INFO|DependancyViewer.frmMain|Attemping to parse metadata as JObject
20:27:57.8743|INFO|DependancyViewer.frmMain|Creating Varfile Class Instance forCaptain Varghoss.Tara.2.var
20:27:57.8743|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\Cgomes.1_scene_thamara.1.var
20:27:57.8933|INFO|DependancyViewer.frmMain|Generating Dependency List
hmm it seems to just stop here Cgomes.1_scene_thamara.1.var
You must be registered to see the links
it's also not checking the dependencies later of it anymore so it seems to have simply stopped the parsing of the other files after it
20:27:58.4514|INFO|DependancyViewer.frmMain|Checking deps forCaptain Varghoss.Tara.2
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for MeshedVR.3PointLightSetup.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for Hunting-Succubus.Enhanced_Eyes.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for NoStage3.Hair_Short_Pixie.latest already exists, adding to existing dependency List
20:27:58.4514|INFO|DependancyViewer.frmMain|Key for VaMChan.Hair_Lightning.latest does not exist, creating and adding to existing dependency List
20:27:58.4674|INFO|DependancyViewer.frmMain|Generating Dependency List View
Last edited:
I wonder if there is something up with Cgomes.1_scene_thamara.1.var it's odd that it finds it but can't seem to open it as a zip, or it can't find a valid meta.json inside. I'll have to add something to handle that or at least log it.
As far as the app goes it thinks a valid var file has a .var extension and a meta.json file at the root. There is logic to catch and log a missing dependencies block or a general failure in parsing the json.
"Found: <Filename>" means the file was located and successfully identified as a var file (it must have a .var extension).
"Found meta.json. Reading." Means that the var was opened as a zip and has an accessible meta.json file inside it.
The next log line should be "Attemping to parse metadata as JObject" which means it's opened the meta.json as a Streamreader and is going to attempt to parse the json.
- Dec 1, 2018
- 2,169
- 2,089
isskini
lets do a to be checked folder wherever your parser has problems with and see what happens if we take it out
congrats that was most probably a download failed corrupted file detection
28,7 KB (29.389 Bytes)
Your parser shouldn't have crashed tough and continue trough the rest marking this as (probably corrupted)
though interesting to see what the official parser does with this case in a separated test
lets continue...
456 matches we getting there
so lets see if we have another corrupted download here
i keep the useless data away now
this is now the possible problem at least for your parser
20:42:55.6965|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\FlamingFire.[look]Elvira.1.var
35,3 MB (37.114.578 Bytes)
from the filesize itself you wouldn't guess it could be a corrupted download and maybe this time it isn't
lets do a to be checked folder wherever your parser has problems with and see what happens if we take it out
congrats that was most probably a download failed corrupted file detection
28,7 KB (29.389 Bytes)
Your parser shouldn't have crashed tough and continue trough the rest marking this as (probably corrupted)
though interesting to see what the official parser does with this case in a separated test
lets continue...
456 matches we getting there
so lets see if we have another corrupted download here
i keep the useless data away now
this is now the possible problem at least for your parser
20:42:55.6965|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\FlamingFire.[look]Elvira.1.var
You must be registered to see the links
35,3 MB (37.114.578 Bytes)
from the filesize itself you wouldn't guess it could be a corrupted download and maybe this time it isn't
Last edited:
Fair enough, I guess we need a try/catch on the streamreader.20:42:55.6965|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\FlamingFire.[look]Elvira.1.varYou must be registered to see the links
35,3 MB (37.114.578 Bytes)
from the filesize itself you wouldn't guess it could be corrupted
- Dec 1, 2018
- 2,169
- 2,089
1249
21:07:59.4373|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\VariousScientists.ExplosionLady.latest.var
there seems to be a interesting pattern if downloads failed in the hub interface over chrome
28,7 KB (29.390 Bytes)
though it's still not easy to id this with filesize it's possible that scripts or just preset var files could be in that range
so we are now at
1618
1822
1857 done (problems quarantined mostly broken (queued) hub downloads that failed so full structure wrong it seems)
1863 scanned (6 found to be problematic and causing the parsing to finish correctly)
So lets take a look at the Final Performance results of 1857 Files 78.994.285.086 Bytes .var scanned and 1st level dependencies analyzed from External USB3 HDD
21:46:40.8834 | Starting directory scan of: M:\VAM\AddonPackages
21:46:49.7329 | Generating Dependency List
21:46:57.2193 | Generating Dependency List View
RAW Parsing Time = 8.8495 seconds
Generating Dependency List/View = 7.4864 seconds
Total Runtime = 16.3359 seconds
Lets check if this fixed some of the Parsing errors of VAMs Internal parser
no extreme errors anymore except 1 <Truncated> else only the normal missing dependencies or wrong meta.json data format
Lets take a look at those 6 files
5 = corrupted hub queue failed internal chrome downloads (easy id able totally broken)
1 = uknown yet can be opened (file structure seems intact)
i gonna test this 1 file again
it's this one
it doesn't look corrupted on the first view in any way thus while i gonna retest first to make sure the parser really crashes on it
21:07:59.4373|INFO|DependancyViewer.frmMain|Found: M:\VAM\AddonPackages\VariousScientists.ExplosionLady.latest.var
there seems to be a interesting pattern if downloads failed in the hub interface over chrome
28,7 KB (29.390 Bytes)
though it's still not easy to id this with filesize it's possible that scripts or just preset var files could be in that range
so we are now at
1618
1822
1857 done
(problems quarantined mostly broken (queued) hub downloads that failed so full structure wrong it seems)1863 scanned (6 found to be problematic and causing the parsing to finish correctly)
So lets take a look at the Final Performance results of 1857 Files 78.994.285.086 Bytes .var scanned and 1st level dependencies analyzed from External USB3 HDD
21:46:40.8834 | Starting directory scan of: M:\VAM\AddonPackages
21:46:49.7329 | Generating Dependency List
21:46:57.2193 | Generating Dependency List View
RAW Parsing Time = 8.8495 seconds
Generating Dependency List/View = 7.4864 seconds
Total Runtime = 16.3359 seconds
Lets check if this fixed some of the Parsing errors of VAMs Internal parser
no extreme errors anymore except 1 <Truncated> else only the normal missing dependencies or wrong meta.json data format
Lets take a look at those 6 files
5 = corrupted hub queue failed internal chrome downloads (easy id able totally broken)
1 = uknown yet can be opened (file structure seems intact)
i gonna test this 1 file again
it's this one
You must be registered to see the links
it doesn't look corrupted on the first view in any way thus while i gonna retest first to make sure the parser really crashes on it
Last edited: