VaM 1.x Ghost dependencies

[murn]

Welcome to my campfire ghost story of a ghost asset while exporting a ghost model... told straight.

So I was about to export a model and there had been some dependencies that I had removed (well one) showing up in the list. Even after closing and opening VAM it still showed. I then removed the hair and started packaging to export to see if that was the problem and it seems that it was the hair but I rechecked and it was not a dependency to the haiir asset so I reapplied the hair and check and the ghost dependency was now gone. I don't know if this is just a one off thing but others should try something like this when they have dependencies that for some reason show up even after removal. I think it's something to consider that it may just be a bug with the dependency list yet in the same time don't just use that as the reason for having assets linked to your stuff. Basically I'm saying check things over as much as you can before you finalize the package.
As the saying goes "each dependency comes from somewhere".

 

[atani]

This is a useful tool for that:

VAR Inspector - Plugins + Scripts -

VAR INSPECTOR CC-BY-NC-ND What is it: Var Inspector is a desktop application written in Python which will scan the save files and presets in your var and tell you where the dependencies are located How does it work: Var Inspector creates a...

hub.virtamate.com

 

[murn]

This is a useful tool for that:

VAR Inspector - Plugins + Scripts -

VAR INSPECTOR CC-BY-NC-ND What is it: Var Inspector is a desktop application written in Python which will scan the save files and presets in your var and tell you where the dependencies are located How does it work: Var Inspector creates a...

hub.virtamate.com

The amount of times I have forgot about that app. Thanks atani.