VaM 1.x Regarding scene releases

[Aipas]

Some doubts, just so I can finalize the process.

- I have a look that has custom textures and a custom morph and is already released on the hub. I'm trying to release a scene that uses this look. I got the textures to be "pulled" from the var, but the morph is "pulled" from local files. Is there a way to avoid the two identical custom morphs, namely the var one, and the local file one that the package builder asks for?

- I'm using a plugin that has MeshedVR.PresetsPack.2 as a dependency. I believe this is already a part of VAM, but if I upload the scene, the hub will tell me the this pack is non-hub hosted, so the scene itself will be labelled non-hub hosted. MeshedVR.PresetsPack.2 is a small pack. Should I just include it? Can I even include a var of my choosing? Package builder only lets me include files from saves and custom folders. Edit the meta-json? Won't that plugin keep asking for the dependency? I think sub-dependencies are handled differently but I'm not sure if it will still anoy users.

- If on, say, a monday, I schedule a scene to release on a saturday, will the scene be reviewed immediately and, if approved, be released on saturday, or will the review process only start on saturday? If I'm not supposed to post this question here, I'll edit my post.

 

[atani]

1. That's because you are using the local (grey/white) morph in the Morphs tab, change it to the VAR version (red) if that's what you want. Alternatively, if you don't need the local morph anymore, delete it
2. I think the Hub will ignore it and still give you the Hub-hosted tag if all else is hub-hosted. If not, check with AshAuryn. Do not include other VARs in your resource if they're not your own.
3. No idea, ask a moderator.

 

[Aipas]

1. Found the issue. Wasn't using pre-load morphs on the var options.
2 and 3 Gotcha.