What’s New?#

1.1.4#

Content Requirements “Early Access”#

We’re introducing a new feature that allows you to validate your content against a set of requirements. Over time, this will replace the existing “Categories” method of organization and feed into higher level features such as configurable “Asset Profiles”.

Requirements are extensively documented in the Asset Requirements

You can enable this feature in the Asset Validator UI by moddifying the config/extension.toml file in the omni.asset_validator.ui extension:

exts."omni.asset_validator.ui".capabilities.enabled = true

Once enabled, you can select the “Requirements” tab in the Asset Validator UI to see the requirements and validate content against them.

../_images/requirements_whats_new.jpg

Important

Not all documented requirements can be validated yet and whilst the list of validators is growing, some will always require manual validation.

For more information please see the “Requirements” section of the Asset Validator Core Extension Documentaion.

1.1.0#

Apache License 2.0#

The Asset Validator is now licensed under the Apache License 2.0. This will make it easier to integrate with other projects. In particular, this change matches the license used by the USD Exchange SDK and should allow users deploy the Asset Validator in their development pipelines without any additional licensing.