Fix UDIM file resolving when no "1001" file exists #1787
Merged
Conversation
This file contains 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
… resolution was removed, so was any testing for whether or not the "Resolve" call succeeded. This change restores the looping to look for an existing tile file rather than always returning the attempted resolution of the first tile file.
|
Filed as internal issue #USD-7245 |
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.
Description of Change(s)
Correct problem with fix for #1329. When symlink resolution was removed, so
was any testing for whether or not the "Resolve" call succeeded. This change
restores the looping to look for an existing tile file rather than always
returning the attempted resolution of the first tile file.
Fixes Issue(s)
UDIM resolution broken for symlinks to non-UDIM paths #1329
I have submitted a signed Contributor License Agreement