SimReady Packager
Your asset. Ready to hand over.
Bring your asset and its dependencies together. Validate, generate the report, and download a package with the metadata your next workflow needs.
Open packagerMore than a file in a folder.
Asset content, thumbnail, metadata, and validation records in one ZIP.
Package once. Hand over with confidence.
Validate as you package
Run the selected checks and include their results in the package workflow.
Keep the details together
Add a thumbnail and package identity alongside the asset and its supplied dependencies.
Download one package
Export a ZIP with content hashes, a bill of materials, and conformance records.
From file to next step.
Keep the workflow focused on the asset you are preparing.
Load the complete asset
Choose your asset files or folder, including referenced USD layers and textures.
Set the package details
Review the thumbnail, package identity, licence, and selected validation profile.
Package and download
Run packaging to validate the asset, generate its records, and download the ZIP. Review the findings alongside it.
Before you start.
What to bring, what your browser needs, and what to expect.
Bring the complete asset.
USD, USDA, USDC, USDZ, ZIP, or an asset folder. Keep referenced layers and textures in their original folder structure.
Work in your browser.
Local files are read and processed on your device. Use a current desktop browser with WebGL2 and WebAssembly. Allow a moment for the runtime to load on your first visit.
Package the asset. Keep the findings.
Packaging includes validation and its report. Validation findings do not block the existing packaging workflow; review the report to understand the asset’s status. Packaging carries your USD content into the archive and adds supporting files. It does not author missing geometry, collision shapes, or physics.
A few useful answers.
Common questions about SimReady Packager.
What does the SimReady package contain?
The ZIP contains your asset payload and supplied dependencies, a thumbnail, root-layer metadata, a SHA-256 bill of materials, validation conformance records, a packaging definition, and a WRAPP catalogue file.
Can I package an asset when validation reports issues?
Yes. The packaging workflow runs validation, generates the report, and creates the package even when validation reports failing checks. The findings remain available for review and in the generated records. A completed package does not mean every validation requirement passed.
Does packaging make any 3D model simulation-ready?
Packaging organises a USD asset and adds supporting metadata. It does not create missing articulation, collision shapes, mass properties, or other authored physics. Those properties need to be prepared in your asset-authoring workflow.
Do I need to install anything or sign up?
No installation or account is required. The tool runs in your browser, and packaging and downloads are free. Use a current desktop browser and include all files referenced by your asset.
Keep working with your asset.
The other free tools pick up where this one leaves off.
Find your next simulation asset.
Explore the library or work with us on custom assets for your stack.
