USDCHECKER(1)

📦
version 26.11.1 · 5 versions
, in arch rolling

🦋 usdchecker(1) — NAME ✨

Bestie, this is the manual page for usdchecker 26.11.1 — that’s the whole name section, periodt. 💖

🎀 SYNOPSIS 🎀

usdchecker [OPTIONS] [inputFile]

🌸 DESCRIPTION 🌸

Okay so usdchecker is the utility for checking the compliance of a given USD stage or a USDZ package. 🧚 Only the first sample of any relevant time-sampled attribute is checked, currently. That’s the vibe check, no cap.

📍 Positionals:

  • inputFile FILE — Name of the input file to inspect. 🫶

💅 OPTIONS 💅

Every flag, every argument, every little detail — here we go, bestie. ✨

  • -h, --help — Print this help message and exit. 🍼
  • --includeKeywords KEYWORDS — If specified, only validators from the included keywords are run. Multiple keywords can be specified as a comma separated list. If not specified, all validators are run. 🔍
  • -s, --skipVariants — If specified, only the prims that are present in the default (i.e. selected) variants are checked. When this option is not specified, prims in all possible combinations of variant selections are checked. 🌀
  • -p, --rootPackageOnly — Check only the specified package. Nested packages, dependencies and their contents are not validated. 📦
  • -o, --out FILE — The file to which all the failed checks are output. If unspecified, the failed checks are output to stdout; if "stderr", terminal coloring will be suppressed. 🌈
  • --noAssetChecks — If specified, do NOT perform extra checks to help ensure the stage or package can be easily and safely referenced into aggregate stages. 🚫
  • -d, --dumpRules — Dump the enumerated set of rules being checked for the given set of options. 📜
  • -v, --verbose — Enable verbose output mode. 🗣️
  • -t, --strict — Return failure code even if only warnings are issued, for stricter compliance. 👑
  • --variantSets TEXT ... — List of variantSets to validate. All variants for the given variantSets are validated. This can also be used with --variants to validate the given variants in combination with variants from the explicitly specified variantSets. This option is only valid when using the new validation framework. 🧚
  • --variants TEXT ... — List of ',' separated variantSet:variant pairs to validate. Each set of variants in the list are validated separately. Example: --variants foo:bar,baz:qux will validate foo:bar and baz:qux together but --variants foo:bar --variants baz:qux will validate foo:bar and baz:qux separately. This can also be used with --variantSets to validate the given variants in combination with varuants from the explicitly specified variantSets. This option is only valid when using the new validation framework. 🦋
  • --disableVariantValidationLimit — Disable the limit set to restrict the number of variants validation calls. This is useful when the number of variants is large and we want to validate all possible combinations of variants. Default is to limit the number of validation calls to 1000. This option is only valid when using the new validation framework. 🔥

💖 Later, bestie! This was usdchecker 26.11.1, dated October 2026. Stay compliant! 🎀

📦 where this page comes from