Skip to main content

VQS Checker Plugin

Run VQS (Virtual Quality Standard) checks against garments live in VStitcher, with per-check pass/fail/warn/skip results and an exportable report.

Overview

VQS Checker validates the currently open garment against a brand's Virtual Quality Standard — 10 built-in checks covering VStitcher version, seam library compliance, colorway materials, grid size, file naming, seam/material displacement, avatar, avatar pose, and snapshot presence. Checks and their valid values are configured per brand profile. Everything runs against the live garment through Browzwear's plugin API — nothing leaves the user's machine.

Requirements

  • VStitcher 2025.3 or newer (any patch), cross-platform: macOS and Windows

  • No third-party dependencies

Who It's For

  • 3D garment designers — a quick self-check before handing off to QA

  • QA reviewers — a consistent, audit-able pass/fail report instead of manual inspection

  • Standards owners — centrally configure the rules once; designers and QA pick up the profile automatically

How to Run a Check

Step 1: Open a Garment and Select a Profile

Open a .bw file in VStitcher, click VQS Checker in the menu, and select the correct profile (e.g. Default, PUMA) from the dropdown.

Step 2: Run Checks

Click Run Checks — progress is shown in real time.

Step 3: Review Results

Each check shows a PASS / FAIL / WARN / SKIP status. Review any FAIL or WARN items — each shows details about what failed and why.

Step 4: Export

Export from the results panel or settings page:

Format

How

Saved to

CSV (full results)

Results page → Export CSV

~/Downloads/VQS_Report_<profile>_<timestamp>.csv

JSON (tag lists / naming rules)

Settings → Export JSON next to any tag list or the file-naming rules

~/Downloads/tag-list-<name>.json or naming-rules.json

PDF

Export PDF — generates an HTML report opened in your browser (print → Save as PDF)

After a successful export, the file is automatically revealed in Finder/Explorer with a confirmation toast.

The 10 Checks

#

Check

What it validates

1

VStitcher version

Minimum required app version — checked against the version the .bw file was actually saved on, not the version currently running. A file opened in a newer VStitcher still validates against the policy it was saved under.

2

Seams from VS ISO library

Seam names match approved list

3

Colorway standards

Required colorway materials are present

4

Grid size

Fabric grid does not exceed max size

5

File naming

.bw filename matches required pattern

6

Seam displacement

All seam displacements are zero

7

Avatar

Garment uses an approved avatar

8

Avatar pose

Pose matches garment type (T-Pose / I-Pose)

9

Hollow final snapshot

Required snapshot is present

10

Material displacement

All material displacements are zero

Checks can be enabled or disabled per profile.

Profiles (Brand Configs)

Each profile is a JSON file defining which checks run and what values count as valid (approved avatar names, required colorway materials, file naming regex). Define as many profiles as needed — e.g. one per product line, season, or team — so a single install covers different rule sets without reinstalling. Switch profiles from the dropdown at the top of the panel; clone or create new ones from within the panel. Changes save automatically.

Troubleshooting

Symptom

Likely cause

Fix

Menu item doesn't appear

Plugin not in correct folder

Re-check install path and restart VStitcher

"Requires VStitcher 2025.3 or newer" popup

VStitcher version is below the minimum

Upgrade VStitcher to 2025.3 or newer

All checks show SKIP

No garment is open

Open a .bw file first

Check #1 (VS Version) fails on a supported VStitcher

The garment file was saved on an older VStitcher than the profile requires

Re-save the garment on a newer VStitcher, or relax required_vs_version in the profile

Export "didn't do anything"

The success toast is small and auto-fades after 3.5s

Check ~/Downloads/ — the file is almost certainly there

Export lands in a temp folder

Downloads folder unavailable

Check system permissions on ~/Downloads

Did this answer your question?