BrowserAssist v1.33.0
Added 2025-04-18 15:13:06 +0000 UTCBrowserAssist is a plugin that provides an alternative browser to VAM's built in Scene Browser. It has a range of features beyond those provided by the default VAM Scene Browser and aims to be more performant. Full details are on the hub here.
New Features:
In VAR Packages browsing, a new resource tab to see Direct Dependencies - i.e. VARs that are immediate dependencies of a selected VAR. This view will also show where dependencies are missing.
In VAR Packages browsing, a new resource tab to see All Dependencies - i.e. VARs that are immediate dependencies of a selected VAR and all of their sub-dependencies. This view will also show where dependencies are missing. Where a Direct Dependency is a 'latest' version dependency, then this view will show the specific version (e.g. creator.varname.1 or creator.varname.2) of the VAR that will be considered dependent currently.
In VAR Packages browsing, a new resource tab to see Used By dependent VARs - i.e. VARs that are currently Used By the selected VAR. Effectively this is the inverse of a Dependency.
Where VAR Management is active (i.e. Offloading or Disabling VARs automatically), manual dependencies can now be added. These manual dependencies (and their sub-dependencies) will be automatically Enabled by VAR Management when required. This allows the correction of VARs packaged with dependencies missing from their meta.json files.
Some minor improvements to the plugin startup time.
Bug fixes:
Fixed a bug that was causing Combi tags on Clothing items to be duplicated as VAM Clothing tags.
Available to Patreons here.
Free version will be available on hub here (normally a week after Patreon release).
Please report any issues on Discord here: https://discord.gg/qrqt2SBzdW
Comments
So currently you have to add them manually. The main use case is scenes where Timeline is animating morphs - which typically results in dependent morph packs being excluded from the VARs meta.json. In this scenario, scanning the scene for dependencies wouldnt work as the dependencies aren’t in the scene file (if they were then VAMs packaging tool would find them and include them in the VAR). Are you aware of other scenarios where dependencies are missing from VARs meta.json but a scan of the scene would find them?
jayjaywon
2025-04-20 06:05:12 +0000 UTCI love how you’re continuing to improve VAR management and dependency visualization. So awesome! I hope you continue and port this for VaM2!
Logovore
2025-04-19 00:11:09 +0000 UTCUmmmh ... I don't quite understand the last feature: "Where VAR Management is active (i.e. Offloading or Disabling VARs automatically), manual dependencies can now be added. These manual dependencies (and their sub-dependencies) will be automatically Enabled by VAR Management when required. This allows the correction of VARs packaged with dependencies missing from their meta.json files." What does the term "manual dependency" mean in this context? The rest of the paragraph suggests that BA will scan the scene.json (or preset) and AUTOMATICALLY enable/onload any dependencies not listed in the meta.json - but "manual" suggests we have to do that ourselves? Or does it mean that I can manually trigger a deep scan of a specific var's scene json file, and BA will then enable any dependencies that were disabled/offloaded because the meta.json was incomplete? (similar to the functionality for local scenes/presets that already exists)
CaseEP
2025-04-18 20:41:28 +0000 UTC
