zzz wrote:
I've unpacked them with QuickBMS, and on the first one I had to change some filenames from garbled unicode back to their original Chinese, but when trying to open them with their respective versions of UE4 editor, both crash.
Map 1 tries to allocate 286GB of RAM to D:\ (have changed UE4 install to my D:\ but still same error). Map 2 says its .umap is an asset and not a map (indication of corruption).
There is no corruption, you're using packaged files, a shipped .umap file is **not** the same as an editor version at all, thats why it doesn't work.
What you're attempting to do is effectively attempting to placing sushi back in the ocean and waiting for it to swim.
The extension is similar, thats largely where the similarities end.
Maps in unreal are counted as 'assets' they're just maps, everything in unreal is an asset, regardless of what it is or what its for.
Additionally simply opening a .umap file on its own wouldn't work, umap files contain references to the object files and paths, along with the texture references etc, you'd still need to have all the actual uasset files in order to correctly open a map, otherwise it'd just be a blank map that can't find any references.
