Here is this again!
"Wolverine333.INITIATION_DAY.1" : {
"licenseType" : "Questionable",
"dependencies" : {
"Mofme.AssetBundle_Decadent_Dungeon.latest" : {
"licenseType" : "CC BY-NC-ND",
You have exactly the same issue that Me and Pesadilla are talking about. But were not sure what is causing it.
My first suspicion though would be the morphs you are using creating unnecessary dependencies. I think some creators are accidently clicking this box when they are creating VAR's.
View attachment 1370476
This is something I had to fix for the actors on the scenes I released earlier.
Search your active morphs and look for any with a
View attachment 1370475
Then check the VAR file it is pointing to, do you really need it? Do you have the morph loose or in a common VAR?
So one that kept cropping up on my actors was the BigPenis morph, the morph they were using was on the Splines Dyson, which would have made that a dependency, and all of its dependencies, dependencies ... all for a 2kb morph file.
View attachment 1370479
Default it, then select either a loose morph, or preferably one from a common morph packs, like Spacedog Import etc.
It should only take a couple of minutes to do as the
View attachment 1370481
morphs are pretty easy to spot. See if that process reduces your dependencies list a bit.
If you go through all of them without seeing any reduction, and get down to a single critical morph that you cannot match, that has a scene file as a dependency, that is probably your culprit. Might be just as well to find the morph in its VAR file and extract it into custom Morphs.
Also... I suppose it could also be a texture file. Either way, I'm pretty sure now that I have thought it through, its got to be a look VAR somewhere in your Addon Packages that is using a scene as a dependency causing this issue.
Pesadilla I just manually changed the tag in [s p l i n e VR.THE_DYSON_POV.1.var] to "preloadMorphs" : "false" and the duplicate morph, and associated risk of accidently making a scene a dependency on a look has gone. Would it be possible to run a scan of all VAR files, to check for this flag against a list, there should only be 66 Hub hosted VAR files with this tag (50 free/16 paywall). Then if its not one of them, prompt "is this a morph pack (Y/N)" and change the flag if requested? It might end up breaking some looks, but if I'm right, it would kill at least one cause of this dependency bloat issue. Thoughts?