I see how that works, or doesn't. I don't understand WTF is going on with some of the dependencies for things I never added to the scene, like VAMx, or why the three point lighting setup that is part of vam flags as being an external dependency. I don't know enough about editing JSON to go into the package and edit the dependencies out. I looked at a tutorial and did my best on a previous scene and just felt frustrated. I may have to just update it and put back the 50 dependencies.
Reason why vamx is pulled as dependency is because inside scene.json you have equipped:
"hair" : [
{
"id" : "
vamX.1.13:/Custom/Hair/Male/Jackaroo/JulianBuzz.vam"
If you mouseover on little cube on equipped hairstyle it should tell you it's from vamx package.
if you search hairstyle for "JulianBuzz" it should also list local version (local hairstyle=white background)
That hairstyle is included inside vam by default locally (inside custom folder, not inside package), so everyone with v1.20.77/even lower should have it.
If you use default local stuff there's no need to include it inside package and make duplicates for others (one example Simone (REN) hair)
Simply manully select/remove before finalizing package, it's gonna report "possible issues" but it's default stuff so not a big deal.
Ofc if you have own custom stuff you wanna include everything inside package.
For that particular dependency simple fix would be: edit json and remove
vamX.1.13:/ part (leave Custom/ part) or equip local version (not one from vamx).
Sadly current system is not perfect and it's super easy to make unintentional duplicates (even with base local stuff) and pull extra dependencies.
.
