Pipeline stages
Run lightweight checks before upload, deeper checks after export, and target-engine checks after import. A practical sequence is: source-scene lint, export validation, file package validation, engine import validation, and final delivery receipt.
Severity policy
Use blocking errors for issues that break import, runtime behavior, or delivery reconstruction: missing textures, incorrect scale, invalid skeleton, non-manifold collision proxy, or wrong axis. Use warnings for naming style, unused materials, high triangle count near budget, or missing optional preview images when the asset can still be reviewed.
Stable exit codes and events
Keep CI exit behavior simple: success when no blocking errors exist, failure when blocking errors exist, and warning summaries without changing pass status. Use stable rule IDs such as `texture.missing_path` or `transform.unfrozen`; dashboards and artist documentation depend on names not changing every week.
Receipts
Store checker version, ruleset version, asset hash, source path, export preset, failed rule IDs, severity counts, and target importer version. Receipts make it possible to explain why yesterday’s asset passed and today’s failed.
Human override
Allow explicit owner overrides for known exceptions, but require reason, expiry, and rule ID. Overrides should be visible in the report, not silently ignored by the validator.
Multilingual production terms
| 中文 | English | 日本語 | Workflow usage note |
|---|---|---|---|
| 自动化检查 | Automated Validation | 自動チェック | Use this term when a rule is checked by scripts, CI, or import validation rather than by manual review alone. |
Term notes for multilingual briefs
Use the English term Automated Validation with matching Chinese/Japanese notes where relevant: Unfrozen Transform / Unused Material / 自動チェック. Keep the technical term beside the local-language note so reviewers can map it back to DCC and engine settings.
Related pages and next step
FAQ
What should automated validation block?
Block issues that make the asset impossible or unsafe to import, render, animate, collide, or reconstruct from the delivery package.
Should warnings fail CI?
Usually no. Warnings should remain visible but not fail unless the project explicitly promotes that rule to blocking.
Why use stable rule IDs?
Stable IDs let artists search fixes, dashboards track trends, and CI compare failures over time.
What is a validation receipt?
It is the stored proof of checker version, ruleset, asset hash, failed rules, severities, and import context for a specific run.
Worked review example
In a CI pipeline, an uploaded prop first runs source-scene checks for naming, transforms, and material slots. After export, the package checker verifies texture paths and file naming. The engine import step then reports scale, collider, and material binding. If `texture.missing_path` fails, CI exits with failure and posts the exact missing file. If `material.unused_slot` warns, CI passes but keeps the warning in the receipt so cleanup can be planned.
A practical creative-production workflow evaluation checklist
Related-search decision guide
Use one representative input and follow it through edit, export, and destination testing. Treat “free” and “best” as search intent—not a promise about current access or quality.
Searches mapped to this route include “3d pipeline”, “ai art pipeline”, and “pipeline model”. Confirm the actual job and destination instead of assuming every wording is equivalent. Clarify output, inputs, destination, constraints, and reviewer. Use a reversible test, preserve editable source, and verify the real runtime result. AI-assisted output still needs human review for rights, editability, technical fit, and release readiness.