VaM 1.x Can anyone help with cleaning up reductant scene

[One-Headlight]

There are a couple of creators’ scenes that I really like, but I don’t want the 50+ dependencies that come bundled with them. My first idea was to go through the parts of the scene I actually want, then repack it for personal use so I could have a clean set of dependencies. Even after doing that, I still ended up with missing addon package errors.

I’m also still confused about the difference between the Standard Reference Version option and the Script Reference Version option. I’ve read explanations, but they never fully click. I tried looking directly at the scene.json file too. I kind of understand it, but also kind of don’t — one wrong bracket breaks the entire scene, and it’s stressful to edit. It feels like way too much work just to get a clean scene for personal use.

I’ve searched online and checked the forums, but nothing has really helped. The closest thing I found was using QVARO to disable a package (VAR), but that doesn’t actually fix the problem once the package is enabled again.

Honestly, I wish VAM had something like a node‑based workflow system (similar to ComfyUI), where each asset, plugin, or VAR dependency was represented as a node. Then you could visually see what connects to what, and simply delete a node to remove that dependency cleanly. That would make understanding and editing scene.json files so much easier. I’ve tried some online JSON tools, but importing a full VAM scene into them is insane they freeze or break instantly.

If anyone knows how to do this properly or can point me toward a guide, I’d really appreciate it. And yes, I know there’s a plugin/script that hides the error log window, but that just masks the problem instead of solving it.

 

[SlimerJSpud]

One option is to use Package Manager to mark a creator's scene var to Ignore and hide missing dependencies. Then the scan for missing dependencies won't be nagging you all the time. Save a local copy of the scene without those dependencies, then use that to play the scene. You might still get some issues with things like texture file pathnames pointing to things you don't have. Just clear those and re-save. I do this all the time. There's also this Python script to list dependencies:

Script for listing all dependencies

I've found what looks like a bug in the script. If a custom preset exists, the script seems to skip, or not report actual var dependencies. The first pass below is with the preset removed. The second pass is after I put it back in Custom/Atom/Empty. This tripped me up a couple of times. I use...

hub.virtamate.com