Scope USDZ load-perf advice to OVRTX; cite OpenUSD primary for USDA - #2
Merged
jshrake-nvidia merged 1 commit intoApr 29, 2026
Conversation
The bullet conflated a renderer-specific load behavior (OVRTX front-loads all materials/textures and bypasses runtime caches when opening USDZ) with a general OpenUSD best practice (prefer binary USDC over ASCII USDA for production assets). Splits them: USDA guidance now cites Maximizing USD Performance as the OpenUSD primary; USDZ guidance is scoped to OVRTX with a note that USDZ itself is just an uncompressed zip designed for random access — load behavior is consumer-dependent and other Hydra renderers may differ. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For NVIDIA-Omniverse/LearnOpenUSD#71, follow-up to my pending review note. Splits the bullet that conflated a renderer-specific load behavior with a general OpenUSD best practice:
Diff is minimal — same bullet structure, scoped accurately.