VAR dependencies seem incorrect

[WolfmanVR]

Hey fellow VaMers! I'm hoping someone has ran into this issue before, because this is a strange one....

Packaging a new scene into a VAR results in a HUGE dependency list. There are things in there I have no idea what they are, let alone me actually using them in the scene. Looking at the scene's .json file, I see no references to any of the suspected incorrect dependencies. But when I look at the prepared VAR's .json file, I see them all listed (which makes sense, because VaM thinks it needs to add them into the meta.json file).

Any idea why all of those incorrect VARs (many of which aren't even on my computer!) are showing up as dependencies? Perhaps another VAR is referencing them all?

I tried: shutdown VaM, cleared cache, relaunched, and still see all of those VARs in the package builder.

I could probably hack the meta.json file in the VAR to exclude the incorrect VARs I know for a fact aren't in the scene, but would rather take care of it "properly".

Another idea I have is to slowly remove plugins, one-by-one, save, prep, and see if the bad dependencies disappear. I'm thinking this is my best bet, but hoping someone has a shortcut that I'm not aware of yet.

Any other ideas, suggestions?

Thanks!

--WolfmanVR

 

[Acid Bubbles]

If you don't see the unexpected dependencies in the scene json, try inspecting the meta.json file, the most common reason if when you use a morph, texture, etc. from a scene, that itself references other scenes, etc. Usually authors will package looks (morphs, textures) separately from their scenes, but if not you might be pulling a thread.

 

[WolfmanVR]

@Acid Bubbles - Thanks for the response. That's the road I was just going down (looking at the meta.json file more carefully). I now see there are a couple resources that were added in that require a TON of dependencies. I'll have to figure out how to roll back those changes that required them, because I'd rather not release a VAR with 78 dependencies!

 

[WolfmanVR]

Turns out I was using a "CC BY" hair asset that was embedded in a large VAR with a bunch of dependencies, as well as a couple more issues. Acid Bubbles was spot on --> Checking out the meta.json of the package is probably the easiest way to determine what's going on...

 

[Acid Bubbles]

Yeah would've been nice to have a "dependency tree viewer" while building the scene rather than after doing the packaging!

 

[WolfmanVR]

No doubt! Maybe VaM 2.x will have it, although I assume nice-to-haves like that are at the bottom of the implementation list.