@BlueMountainsIO I was wondering if it’s a necessary requirement to package for shipping for this to work, and if so why? Past experiments I’d done with paks, had them working fine when packaging for development. I know there is the loghelper you’ve provided for logging when packaging in shipping mode, but for other reasons i was wanting to have it work packaged for development as well. I’ve tested PakLoader with development mode and it all seems to work the same for me as i can tell so wanted to check.
Also mounting and registering are both working for me at Engine level …/…/…/ as was suggested, however I’m mounting multiple paks into the same mount root /ModPlugin/, and the AssetRegistry.bin that I’m reading won’t update registry since the AssetRegistry.bin file always has the same path. Is there a way to have the AssetRegistry.bin append to the existing registry at the mountroot?
Essentially I have a whole bunch of small paks with a few files in them that I want to mount and register beneath the same root each time… But the AssetRegistry.bin won’t register because there was already an existing one at the path for that mount root ( it seems ). Not sure how to solve this. If I don’t read in AssetRegistry.bin then I have to spawn them with your getpakfilestaticmesh in order for the registry to know about them. What I’m seeing currently is the first AssetRegisty.bin I read updates the registry and the rest don’t update so i’m stuck with the registry only knowing about the first one…
My asset AssetRegistry.bin in all of my small paks is always at:
Pod/Plugins/ModPlugin/AssetRegistry.bin
Is there a way I can manually add the object paths mounted from the pak to the registry object by object instead of serializing the AssetRegistry.bin?
EDIT:
Nevermind I got it registering!