• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.

200. Errors in the VaM log

Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
error.png
Errors you may find in the error log


VAR file... <creator>.<name>.<version>
VAR file AddonPackages\AlmightyPatty.RE8_WeaponsPack1.var is not named with convention <creator>.<name>.<version>
  • The VAR is not named using the pattern creator.name.version.var, notice the version part does not exist.
  • Solutions:
    • correct the VAR name to follow the expected pattern, and do tell the creator of the VAR about the mistake
      • Tip: search in File Explorer using this pattern: ~="(1)"; this will only bring copies and not legitimate VAR versions as .1.var; if needed replace 1 with 2 and so on
    • if you redownload the VAR and a existing copy exists in that folder, Windows will add a (1) to the name. In this case delete the copy(ies) with (#) and move only the correct VAR to AddonPackages
  • Impact: VAR contents will not be accessible
Duplicate package... Cannot register
Duplicate package uid AshAuryn.Pose_Tools.2. Cannot register
  • You have a duplicate copy of the VAR
  • Solution: remove the copy; subfolders in the AddonPackages folder is usually the source for this error
  • Impact: no impact besides reporting in the log as one copy will be usable
Missing addon package... depends on
Missing addon package theagle.COCO.latest that packageArk1F1.Olivia_McAllister.1 depends on
  • You're missing a dependency (theagle.COCO) requested by a VAR (Ark1F1.Olivia_McAllister.1.var)
  • Solution: download the missing dependency from the Hub or use the built-in Hub Browser for Hub hosted content; non-Hub hosted content is your task to find them
  • Impact: depends; can go from having no impact on the listed VAR to breaking it completely
JSON Parse: Too many closing brackets
Exception during process of meta.json from package tptpsg.tptp12.1: System.Exception: JSON Parse: Too many closing brackets
  • The meta.json file inside the listed VAR has a invalid JSON structure
  • Solution: fix the JSON structure in the VAR's meta.json and/or tell the creator to fix it; this error's source comes from the creator manually editing this file and making a mistake
  • Impact: depends; if the error happens in the dependencies list of the meta.json file it will not be able to provide you a list of needed dependencies and give you invalid dependencies (Hub Browser)
Exception during zip file scan... Cannot find central directory | Exception during read of morph binary file...
Exception during zip file scan of AddonPackages\cc.big.3.var: ICSharpCode.SharpZipLib.Zip.ZipException: Cannot find central directory
Exception during read of morph binary file AddonPackages\Shapes.WendyVIP.1.var:\Custom\Atom\Person\Morphs\female_genitalia\Wendy - Genital.vmb ICSharpCode.SharpZipLib.Zip.ZipException: Wrong local header signature
  • Problems with the VAR file
  • Solution 1: redownload the file, the file could be corrupted; if the redownloaded VAR gives the same error tell the creator about it
  • Solution 2: repairing with WinRAR
  • Impact: unable to use the VAR contents; if this is pervasive your VaM folder may have permission issues (see FAQ)
Atom type... Cannot add
Atom type <type> does not exist. Cannot add
  • This error occurs when the scene is trying to load a specific item type that doesn't exist in your VaM version (aka "out of date" client)
  • Solution: update VaM or ask the creator if they have a version for older VaM versions (doubtful)
  • Impact: the scene may not work correctly without that atom type

Unity's error log:
Not all errors are shown inside VaM. See Unity's error log in C:\Users\yourUser\Appdata\LocalLow\MeshedVR\VaM\output_log.txt


Contribute to this error list

If you have seen a error that is not shown on this list, please include it on this thread. If you're a wiki contributor, you can edit this page, if you're not, please add a reply and a wiki contributor will add it in.

Please report it following this structure:

  • A single type of error message - not the whole log please - that wasn't shared already
  • If you know the cause and how to fix it, please provide that information too

Thank you for your contribution.
 
Thanks very much atani - you've really put in a lot of work on these pages!

I don't have an additional error message to contribute, but I do have a question about what appears in the error log panel within VAM.

I have always had a lengthy list of missing dependency errors, some of which don't really make any sense to me: "Frief.cuffs.1 is missing? The file is right there and there's nothing wrong with it!"
That aside, presumably because of the long list of missing dependencies, somewhere in the middle will be a "<Truncated>" token with blank lines before and after.
Can you shed any light on that <Truncated> token? Specifically, how to get a complete list? I'm obviously not seeing ALL the errors.
I have played around with using that error data to try to identify and prune some of the main offenders (I have a LOT of old junk, what can I say; I'm a pack rat). Like, order by packages that HAVE missing dependencies and work my way UP the tree, if that makes any sense.
I know when the VAR system was implemented there was a lot of confusion around dependencies set incorrectly. I think that's the bulk of my problem, because none of the stuff I use day-to-day seems to be affected much.

Anyway, thanks again for your hard work, and let us know if there is any way to control that <Truncation> parameter, or if it's even possible.
 
Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
Back
Top Bottom