Examples: Add direct USDZ import from export #31665
Open
+309
−1
Conversation
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
|
I was hoping we could test such things via unit tests instead, see #31662. A verification on scene graph level (like matching hierarchy or material properties) is maybe sufficient? |
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.
Adds an example that immediately exports the scene to USDZ (via
USDZExporter), and then imports it via theUSDLoader, displaying the result. This serves as I think a useful very quick e2e visual test/spot check and demo of both. It differs from the existingUSDZExporterexample that exports and saves files to disk.--
I'd rather not change
USDZExporteras done here but doesn't matter much. It was required to for the screenshot generation due todeterministic-injection.jsmessing with fflate's ability to set proper mtime values in the ZIP entries.