USDRESOLVE(1)

✨ USDRESOLVE(1) ✨

okay bestie, welcome to the usdresolve manual page — literally your glow-up guide to resolving asset paths. This is the usdresolve(1) page, and the star of the show is usdresolve 26.11.1. 🦋

🎀 NAME 🎀

usdresolve — manual page for usdresolve 26.11.1. 💅

🌸 DESCRIPTION 🌸

okay so here’s the whole vibe. usage:

usdresolve [-h] [--createContextForAsset CREATECONTEXTFORASSET | --createContextFromString CREATECONTEXTFROMSTRING] [--anchorPath ANCHORPATH] inputPath

It resolves an asset path using a fully configured USD Asset Resolver. No cap, that’s main character energy. 👑

🐚 positional arguments:

• inputPath — an asset path to be resolved by the USD Asset Resolver. This is the path you’re handing over for the resolve treatment, periodt. ✨

💅 options:

• -h, --help — show this help message and exit. Your little escape hatch, bestie. 🫶
• --createContextForAsset CREATECONTEXTFORASSET — run CreateDefaultContextForAsset with the given asset path to create the context used for resolution. It’s giving set the scene before the resolve. 🎬
• --createContextFromString CREATECONTEXTFROMSTRING — run CreateContextFromString with the given string to create the context used for resolution. This accepts strings like [<URI Scheme>:]<Configuration String> and may be specified multiple times. ex: usdresolve --createContextFromString 'config_primary' --createContextFromString 'my_uri_scheme:config_uri' — yes, you can stack these, iykyk. 🌈
• --anchorPath ANCHORPATH — run CreateIdentifier with the input path and this anchor asset path and resolve the result. ex: usdresolve --anchorPath /asset/asset.usd sublayer.usd — anchor it and let it cook. ⚓

---

cute little sign-off: usdresolve 26.11.1, October 2026. Love that for us. 💖