SimReady prop journey
Use this as the user-facing orchestrator. Keep each specialist gate independent; later physics success does not repair failed authoring or export.
Workflow
- Preserve the supplied source and work on a caller-owned derivative. Use
blender-content-safety-and-privacyfor untrusted inputs. - Run
simready-addon-install-and-authoring. Require the real add-on surface, its supported authoring structure, named validators, and a reopened USD. - Run the pinned OVRTX SimReady conversion test described by that skill. The current public example supports a deliberately narrow uni-body shape; stop on its structured unsupported cases rather than rewriting the asset silently.
- When the prop needs a behavior check, run
ovphysx-drop-contact-acceptancethrough the officialrun_ovphysx_drop_probe.py --require-realpath. Authoring eligibility and runtime behavior remain separate results. - Use
usd-copy-and-flattenonly when the recipient needs localization or a flat derivative, then inspect the exact candidate withusd-inspect-and-provenance.
Completion
Call the requested journey complete when the add-on validators pass, the USD reopens, the current conversion boundary accepts the prop, and any requested native behavior check passes. Summarize the prop, outputs, pass/blocker, and important limitation. Produce a manifest, hashes, screenshots, or full reports only when the caller needs a reproducible handoff or review artifact.