Migrating from omniverse-asset-validator#
usd-validation-nvidia is the successor to the omniverse-asset-validator (OAV)
Python module. The engine, rule interface, and CLI are the same; only the package and
import names change, and compatibility shims keep most existing code working.
What changed#
omniverse-asset-validator |
usd-validation-nvidia |
|---|---|
|
|
|
|
|
|
run inside Kit / |
the |
The rule API is the same: rules still subclass BaseRuleChecker, override the same
Check* callbacks, report with _AddFailedCheck / _AddWarning / …, and register
with register_rule. See Authoring rules.
Compatibility shims#
The package ships an omni.asset_validator namespace that re-exports everything from
usd_validation_nvidia, so existing imports keep resolving:
omni.asset_validatorandomni.asset_validator.corere-export the public API.omni.asset_validator.testsre-exports the test helpers.python -m omni.asset_validatorruns the new CLI.
These shims ease the transition. New code should import usd_validation_nvidia directly;
the omni.asset_validator aliases are kept for backward compatibility and may be
deprecated in a future release.
Updating your project#
Replace
omniverse-asset-validatorwithusd-validation-nvidiain your dependencies. Add the[usd]extra if your environment does not already provideusd-core(see Installation).Update imports from
omni.asset_validator/omni.asset_validator.coretousd_validation_nvidia.Replace any
omni.asset_validatorcommand-line invocation withnvidia_usd_validate(see Command Line Interface).Custom rules carry over unchanged: keep your
BaseRuleCheckersubclasses andregister_ruledecorators, and confirm they appear in a defaultValidationEngine.