Hey guys, having trouble with this sound asset when running the shipping dedicated server of the game, which was converted from a UE4 project to UE5. The asset works just fine in the UE5 editor and the builds/cooks/packs successfully, but when I try to start the game’s dedicated server, I get:
I believe this could mean that the file sound have been incorrectly exported with only 52 bytes sent instead of 3724 bytes.
Would it be possible to examine file files in Windows File Explorer and check they are the same size and not corrupted.
Maybe you could copy the file over from UE4 to UE5 project to see if that fixes it.
Seems like the file size changes during the cooking/packing process. On the screenshot attached, the left is project Content folder while on the right there’s the packed game’s content folder. You can see that the .uasset file sizes are different.
Hi @Kaspi ,
After examining the code for many days I may have come up with a fix. It involves patching the source and rebuilding the UE5 EA.
I have noticed in the supplied dump that many other files have been corrupted on the move, but the one in your message has seeked too far hence the report.
I have a patch that may work.
Open the UE5 EA source build and enter “AsyncLoading.cpp” in the Solution Explorer
When the code opens type Control + G, in the Go To Line box type 7961 and enter
Edit the code so as seen below adding the “+1”
checkf(CurrentPos + Count <= 1 + TotalSizeOrMaxInt64IfNotReady(), TEXT(“Seeked past end of file %s (%lld / %lld)”), *PackagePath.GetDebugName(), CurrentPos + Count, TotalSize());
Having the exact issue on UE 5.0 with run-time mounting pak file. The weird thing here is that only sound wave files trigger the issue, as long as no wave sounds are used, everything else can be loaded normally (i.e class, textures, materials)
Hi @JakeTee ,
I agree but they say its not a high on the list of bugs to be fixed in 5.2 even Lighting Shadows wont work. I am working on 5.3/5.4 now so just dont know
This was apparently caused by packaging various versions of the game with the -iterate flag on automation tool. For example, if I cooked windows client after linux dedicated server, this happened. The solution for me was to remove the -iterate flag from the RunUAT scirpt (automation tool).
My understanding is that the -iterate flag/argument makes the cooking process to use the previously cooked resources, which may have been cooked for a different platform/target and fails. Then the client and server have a mis-matched size on cooked assets (one of which was cooked normally and the other has no/empty asset files).
If I am correct, the -iterate flag is added automatically if you cook from the editor. For full control over the packaging process, you can use the RunUAT script with the parameters you can find in the Output log after you start the packaging process (without the -iterate flag), example.
