Contribute to a list of Error Log errors to help users fix their problems

[atani]

Hi, everyone,

VaM's Error Log can show messages that for many users, especially new ones, look like technical gibberish. I am calling for your help in compiling a small list of common errors shown in the Error Log, and for each state what is the issue and how to potentially fix it.
This is a page that will be added to the FAQ or somewhere else if proposed and more suitable.

What I would like for you to add on this thread:

• 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.

 

[atani]

Collected error types:

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

 

[DJ]

A common .var file error:

If you download, say, someUser.someScene.1.var, then download it again, windows recognizes that it's a duplcate, and renames it someUser.someScene.1(1).var. Download it again and you get someUser.someScene.1(2).var.

These vars wont open until you edit the file name to remove the "(#)". Since this is an issue created on the users end, notifying the creator is not helpful or necessary.

It's a good idea to take a quick look at your addonPackages directory to find and fix any files with this form.

 

[atani]

A common .var file error:

If you download, say, someUser.someScene.1.var, then download it again, windows recognizes that it's a duplcate, and renames it someUser.someScene.1(1).var. Download it again and you get someUser.someScene.1(2).var.

These vars wont open until you edit the file name to remove the "(#)". Since this is an issue created on the users end, notifying the creator is not helpful or necessary.

It's a good idea to take a quick look at your addonPackages directory to find and fix any files with this form.

Thanks for this option, the solution was remade to account for this
Any other types of errors you've seen not in the list?

 

[RandomVAMUser]

!> Atom type <type> does not exist. Cannot add

Where <type> could be any newly added atom that's missing.

Some examples:
from v1.22.0.0: UIButtonImage, UIImage, CensorPanel, CensorCube
from v1.21.0.4: ImagePanelTransparentEmissiveOverlay
from v1.20.77.2: all cyberpunk themed assets (enviroment, furniture, props,...)
from v1.20.0.4: SubScene atom

This error occurs when scene is trying to load atom that doesn't exist inside current client version (aka "out of date" client).
Solution: update VaM client or contact content creator for workaround (if any).

 

[atani]

!> Atom type <type> does not exist. Cannot add

Where <type> could be any newly added atom that's missing.

Some examples:
from v1.22.0.0: UIButtonImage, UIImage, CensorPanel, CensorCube
from v1.21.0.4: ImagePanelTransparentEmissiveOverlay
from v1.20.77.2: all cyberpunk themed assets (enviroment, furniture, props,...)
from v1.20.0.4: SubScene atom

This error occurs when scene is trying to load atom that doesn't exist inside current client version (aka "out of date" client).
Solution: update VaM client or contact content creator for workaround (if any).

Thanks. Added to the list.

 

[ICannotDie]

Some updates for errors I've encountered:

1)

.var filename not matching convention

Error
VAR file AddonPackages\Fen.1.var is not named with convention <creator>.<name>.<version>

Cause
The .var's filename doesn't match the expected convention of <creator>.<name>.<version>.var

Resolution
In this case there is no creator name, so just add one. It doesn't matter what it is, so if you don't know the creator's name just add anything. So in this example Fen.1.var becomes Creator.Fen.1.var

2)

Cannot find central directory during zip file scan

Error
Exception during zip file scan of AddonPackages\Riddler.Skin_5_8k_addon.4.var: ICSharpCode.SharpZipLib.Zip.ZipException: Cannot find central directory
at ICSharpCode.SharpZipLib.Zip.ZipFile.ReadEntries () [0x00000] in <filename unknown>:0
at ICSharpCode.SharpZipLib.Zip.ZipFile..ctor (System.IO.FileStream file) [0x00000] in <filename unknown>:0

Cause
The .var archive has been corrupted and cannot be opened/uncompressed by VAM.

Resolution
Download and install WinRAR.
Open WinRAR and browse to AddonPackages.
Select the corrupted .var and click 'Tools' in the top menu.
Click 'Repair Archive'.

Make sure to select 'Treat the corrupt archive as ZIP' in the popup, then click OK.

WinRAR should create a new file in AddonPackages prefixed with rebuilt. Delete or move the corrupt .var and remove the prefix from the newly fixed one.

3)

Additional info for Duplicate package... Cannot register & .var filename not matching convention (number 1 above)

Windows autogenerates filenames for duplicate files when you attempt to save them, appending a number in parentheses to the filename. For example, myfile.var becomes myfile (1).var. Not only does this cause errors when VAM tries to process the files, as it expects a specific convention, but searching for these files in Windows Explorer is difficult as searching for (1) returns all files with 1 in their names. Instead, search using this expression ~="(1)", which will force the search for an exact phrase. You can put anything you like between the double quotes, so this works for things like ~="(2)" too...