VaM 1.x Remove dependencies

[Piet]

How can I modify a var package? I purchased a look that's missing the resource Yass.ROKA_uniform. I simply want to remove the dependency. I unpacked the package and deleted the dependencies from the JSON file. Then I tried to recreate the same var package using the package builder. Unfortunately, that didn't work. The newly created package doesn't show me any look.

Is it possible to modify the dependencies? It often happens that clothing or shoes are missing. It's not a big deal, but I don't want an error message in the log saying that the dependencies can't be met.

 

[SlimerJSpud]

Don't disturb the original var, or keep a backup of it if you do. The easy way to not have the missing dependencies flagged is:

Go into Package Manager (in game)
Click on Missing Dependencies
Find the var you just downloaded
Go to the User preferences and check the box for Hide and ignore missing dependencies.

When you open the scene for that look, or apply the Appearance preset, you will still have the error, but if you substitute some other uniform, and save a local scene/appearance, then your local copy will not have the dependency at all.

This may sound like a lot, but it isn't, really. It's better than trying to edit the original files, possibly breaking something.

 

[hazmhox]

Slimer is right:

1. You could break something
2. You would interfere with proper dependency computation if you'd publish something

The startup warning is nothing critical and does not mean you should have the deps, I have a bunch of these and leave it that way.

 

[Piet]

I don't intend to publish anything. I just want to keep it clean for myself.

It would be nice if I could edit a var file so I could replace or remove clothing and then adjust the dependencies. I'm not trying to hide the error messages in the log. I know that with most content, a lot is missing anyway, and that's why the corresponding error messages appear. That doesn't bother me. But I want my basic VAM setup with a few models, scenes, and content to be error-free.

One question about the JSON files: Are these created by VAM when you build a package, or do you have to create them yourself?

 

[Piet]

Don't disturb the original var, or keep a backup of it if you do. The easy way to not have the missing dependencies flagged is:

Go into Package Manager (in game)
Click on Missing Dependencies
Find the var you just downloaded
Go to the User preferences and check the box for Hide and ignore missing dependencies.

When you open the scene for that look, or apply the Appearance preset, you will still have the error, but if you substitute some other uniform, and save a local scene/appearance, then your local copy will not have the dependency at all.

This may sound like a lot, but it isn't, really. It's better than trying to edit the original files, possibly breaking something.

So, I've been saving my scenes and appearance presets incorrectly? Because my scene and appearance presets on a newly set up VAM do require the corresponding files. Is there a way to save the scenes so that everything is included – clothing, skins, morphs, etc.?

 

[SlimerJSpud]

The meta.json file inside the var is created by the Package builder in game when you build a var. Scene json files, are just the save file for the scene. There could be all kinds of reasons for you to have dependencies you can't seem to get rid of. This could be caused by sub-dependencies. In general, if you load up somebody else's scene that is missing something, then re-save it locally, you won't have those errors when you load your local copy. Same for Appearance presets. Paths to texture files might still be hiding in there. Those won't get cleared until you clear them in the UI.

 

[Piet]

Thanks in advance for your patience. I'm getting deeper and faster into VAM, and my brain often can't keep up. Another question about dependencies. I've now added more content to my basic VAM setup. If I run the initial dependency check and manually add all the dependencies not already on the hub, everything should theoretically work without any problems, right? Because if I run another check, it shows packages that need to be downloaded again. But those are dependencies on dependencies, aren't they? I don't need those anymore, do I?