Converting a file is one step in authoring
A format conversion can make content readable by another tool. It does not, by itself, establish that the object has the geometry, physical properties or motion model your robot needs.
The glTF specification describes scene structure, meshes, materials and other supported data. Inspect the source file and extensions it actually uses instead of assuming that all GLB files contain the same information.
Inventory the source before conversion
List the visible parts, dimensions, textures and animation. Identify which parts must move independently during the robotics task. A visual animation is not necessarily a physical joint definition, and a single merged mesh may need additional authoring before individual parts can interact.
Keep a copy of the original and a reference render. This gives you a concrete way to inspect scale, orientation and appearance after conversion.
Review the converted USD stage
Open the output in the target application and compare it with the source. Check hierarchy, transforms, materials and texture dependencies. Then inspect what is missing for simulation.
The USD physics schema defines data for physical representations. Authoring those properties is a separate responsibility from exporting a USD file. The right additions depend on whether the object is static, grasped or articulated.
Separate the acceptance checks
| Check | Evidence to keep |
|---|---|
| Visual conversion | Matching scale, orientation and relevant appearance |
| Physical authoring | Colliders, bodies and joints appropriate to the task |
| Packaging | Entry file and dependency paths that resolve |
| Profile validation | Named requirements and the resulting findings |
| Runtime behavior | A repeatable interaction in the target simulator |
A converter or packager should not be described as making any arbitrary object simulation-ready automatically. Review each stage and keep unresolved findings attached to the result.
If a suitable object already exists, start with the hand-authored library. For your own USD package, use the SimReady Packager and Validator. The packager bundles supplied content; it is not advertised as a GLB-to-USD authoring service.