Question Help understanding the Sub-Dependencies

ShinyAndroid

Well-known member
Featured Contributor
Messages
81
Reactions
619
Points
83
So I just made an update to a scene. I only changed two pieces of clothing to version that had a less restrictive copyright. But they didn't have any new dependencies.

However, the scene jumped to 41 dependencies in this update, VS 21 dependencies before the update. And two of them aren't on the hub so it's causing the scene to not show up in the HUB with the default search.

I have no idea what these are or why they're showing up now. I went looking through the JSON, and I couldn't find them there at all. I'll admit I'm not super clever when it comes to the JSON and how to read it...but usually if there's a wayward dependency I can go in there and remove it.

I could maybe see some of the hand morphs referencing them...but again, I don't see them in the actual JSON.

Anyone understand the sub-dependencies and how to get rid of them?
 
You don't get rid of sub-dependencies : )

Sub-dependencies are produced by your dependencies. ie:
  • Your resource
    • > dependency A
      • > dependency A - 1 (or sub-dependency)
    • > dependency B...
The meta file will give you a proper idea of the dependency hierarchy.
If you want to control your sub-dependencies. You need to control your dependencies. Check each dependency you wanna use and their own dependencies.
 
Upvote 0
Maybe I'm just doing it wrong then but I can't FIND the sub dependencies in the meta file. I'm usually pretty particular about using as few dependencies as I can. I always scrub through the JSON file and confirm everything. I can find all of the direct dependencies, but not the subs.

This is the resource in question for me: https://hub.virtamate.com/resources/girlfriends-surprise.40576/dependencies

I know what every single one of the Direct - dependencies are and what they are in the scene. And I've gone through them to confirm they aren't part of another resource or have other dependencies. So now I'm just confused where the Subs are coming from.

Would you be able to provide an example in a JSON file of how to see the sub dependencies and the dependencies they are attached to?

I'll admit I'm very amateur at this stuff so it's very possible I'm just overlooking something obvious.
 
Upvote 0
I'd suggest checking every piece of active clothing and hair to make sure what you referenced came from the original creator, not some random scene. Hover the mouse over the little cube next to the check box. The name may say hazmox.something, but the resource might actually be joebagofpeanuts.something. It's tedious. You also have to do that for morphs, which is even worse. One fire asset I used pulled in a whole other scene once. It took a while to chase that down and swap it out.
 
Upvote 0
Well never mind lol. There was ONE dependencies I didn't recognize after I looked through it and sure enough every single sub dependency comes from that one.

Thanks for the help everyone!
 
Upvote 0
I'd suggest checking every piece of active clothing and hair to make sure what you referenced came from the original creator, not some random scene. Hover the mouse over the little cube next to the check box. The name may say hazmox.something, but the resource might actually be joebagofpeanuts.something. It's tedious. You also have to do that for morphs, which is even worse. One fire asset I used pulled in a whole other scene once. It took a while to chase that down and swap it out.
Yeah! Thats usually what I do. Go through every one and make sure they're by the creator and not a reference to another resource. Thank you!
 
Upvote 0
Part of the problem is that the latest var containing the resource will be shown first. In the case of duplicated entries for one resource, the latest entry might be from another scene or resource.
 
Upvote 0
Back
Top Bottom