Ah, OK, that makes sense. To be honest, we’ve gone ahead with the change in ChangeBundleStateForPrimaryAssets already since it was blocking us and we’ve not really noticed any change in cooking or runtime performance so far.
I believe the source of the intermitent nature of this is due to build machines performing cooks over time and that somehow resolving this issue, it’s not really clear why though.
I see that FixupRedirectedAssetPath is used reasonably extensively in the Engine at runtime in other locations, like World Parition for example, are those usages incorrect as well? Not to mention the underlying FixupCoreRedirects() is called in some seriously deep Engine classes.
It feels to me like while the concept of redirectors exist then bundles should handle the redirect, it seems more like the issue is that the redirection itself could be slow so the optimisation effort should be towards making the efficient.
I guess ultimately what I am asking for here is…
“What is the correct way to handle redirectors for assets referenced in bundles?”
I will try to get you the data but it might take a while.