How to mount pak files without breaking the loading of other assets?

[NicolasDev84]

Thank you for your time and your detailed answer.

My initial misunderstanding was to think that registering a mount point would preserve the previous ones, and that loading a mesh/texture file with “/Game/” in its path would make Unreal Engine look in all registered mount points.

I didn’t try the plugin method for now because I feared it would be more complicated (as suggested in this topic where the developer created a subsystem) but I will have a look. I just want to avoid extra developments.

@Chatouille

Since you are loading PAKs from other projects into yours, I assume those PAKs are not encrypted, or that you have already decrypted them. That means you have capability to unpak and repak assets. This will not help you remap references between assets, however by doing that you can change the real path of files within the PAK. So instead of having files at ../../../OtherProject/Content/something you can repak them at ../../../YourProject/Content/something. With that, the content from both your main PAK and the inspected PAK should be reachable simultaneously from the standard /Game/ root.

They are indeed not encrypted. For now we generate these pak files ourselves (our users may need to do it too later).
I was naive but I thought it was possible to change the location of files in the pak by simply using the last argument of FPakPlatformFile::Mount(const TCHAR* InPakFilename, uint32 PakOrder, const TCHAR* InPath)

@Chatouille

Disable texture streaming. This should at least correct the error you are getting. Maybe there’s streaming for Mesh LOD as well though, not sure. Maybe it can be disabled as well.

I prefer not doing this because we want to take advantage of all optimizations of Unreal Engine.