You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UsdUtils.ComputeAllDependencies appears to work differently for USDZ and USD files in that the checker seems to miss that the assetInfo dictionary is pointing to an invalid asset path when the file is a USDZ, but It works correctly when you unzip the same file
This is with USD 23.8.
The attached script will run over the two files and print when it misses the check
Ah this seems to be because UsdUtils_FileAnalyzer has this bit to mention.
// If the newly opened layer is a package, it we do not need to traverse
// into it as the entire package will be included as a dependency.
if (_layer->GetFileFormat()->IsPackage()) {
return;
}
So at least the cause is clear, though I think maybe the assumption in the code isn't accurate, because a USDZ may have external references that are unresolvable (per our previous discussions)
I'll submit a PR with that removed. I don't believe there are any side effects to the removal in my testing
Description of Issue
UsdUtils.ComputeAllDependencies appears to work differently for USDZ and USD files in that the checker seems to miss that the assetInfo dictionary is pointing to an invalid asset path when the file is a USDZ, but It works correctly when you unzip the same file
This is with USD 23.8.
The attached script will run over the two files and print when it misses the check
Steps to Reproduce
The text was updated successfully, but these errors were encountered: