Choose a VAO client

“Supports VAO” is only the beginning of a compatibility statement. A client can support a particular contract, offer only selected capabilities, or be designed for a specific runtime. The exchange standard and the application release use independent version numbers. The comparison below records the documented states audited for this notebook edition.

Choose by the operation you need#

Inspect before attempting playback#

• Identify the exact object release and the format contract declared in its manifest.
• Check the client’s own version and supported profiles; distinguish final specifications from pinned candidates.
• Establish which resource groups must be available for the intended operation.
• Verify the required realizations before interpreting an image, model or audio result.
• Retain unsupported-capability messages with the report of what was actually tested.

A client can be useful even when it cannot execute an entire experience. Metadata inspection, file-integrity checking and geometry import are meaningful operations with narrower requirements than sampled playback or XR. The interface should explain the level of support rather than implying that a successful import validates every aspect of the package.

A practical compatibility note#

Object release and version DOI:
VAO format version:
Client name, version and platform:
Operation tested:
Required profiles and resource groups:
Validation result:
Unsupported capabilities or substitutions:
Output artifacts and checksums:

Keep the source package unchanged when testing interchange. A newly materialized carrier or derived project is a separate artifact, even when it refers to the same semantic release. If a runtime needs a conversion, document that conversion and preserve a route back to the exact input.

A loaded package is not necessarily an executed object#

The Unity source documentation distinguishes MetadataOnly, SelectedGroups and RuntimeRequired materialization. Those modes describe different local resource states, while the runtime’s supported behavior adds another layer. Preserve unsupported data for inspection where the client provides that capability, and record which operation was actually performed. Features documented in the later source candidate must not be attributed wholesale to the archived 0.6.0-rc.1 release.

For Blender 0.4.0-rc.2, the modern VAO path supports validation, inspection and verified visual materialization. It does not provide modern VAO runtime execution, impulse-response convolution or acoustic simulation. Legacy interaction support belongs to a different format path. This makes Blender useful for checking geometry without presenting it as a complete acoustic player.