Hi, I’m posting for a colleague who has been investigating a lot of warning output like this:
FPackageName: Skipped package /Interchange/gltf/Textures/T_White_srgb has a valid, mounted, mount point but does not exist either on disk or in iostore. The uncooked file would be expected on disk at ‘D:/Engine/Plugins/Interchange/Runtime/Content/gltf/Textures/T_White_srgb.uasset’. Perhaps it has been deleted or was not synced?
and
Skipping non mounted imported package /Interchange/gltf/Textures/T_White_srgb
My colleague ran with -DebugCoreRedirects, and found that while the redirect of the asset’s object in the package succeeded, the redirect for the package itself was failing, leading the above the warnings. He then modified BaseInterchangeAssets.ini to change
+PackageRedirects=(OldName=“/Interchange/gltf/Textures/T_White_srgb.T_White_srgb”, NewName=“/InterchangeAssets/gltf/Textures/T_White_srgb.T_White_srgb”)
to
+PackageRedirects=(OldName=“/Interchange/gltf/Textures/T_White_srgb”, NewName=“/InterchangeAssets/gltf/Textures/T_White_srgb”)
and the warnings disappeared. Furthermore, we’re in the process of removing all of our uses of the Interchange assets and have data validation that flags any references to InterchangeAssets. After this change, he noticed hundreds of older assets started failing that validation as their references started resolving to InterchangeAssets.
Looking at other Engine ini files with PackageRedirects, I’m seeing a large mix of redirects that only specify the package name, some that only specify the package.object path, and some that actually specify both. What’s the correct way to set up PackageRedirects to avoid the mounted warnings and to ensure that things resolve correctly in all contexts?
Cheers,
Peter