I was downloading some maps from a server this afternoon and UT crashed. After that, it’s impossible to launch the game again. I keep getting the error ‘An unknown process has crashed’. I’ve tried uninstalling/installing UT, even did the same with the launcher. Same thing happens.
The crash reporter won’t give me an option to send diagnostic files, just to close without sending.
I would really love to be able to play the game again. Any suggestions?
I can’t tell for sure what was the specific map because I wasn’t looking at the screen at the exact moment when the game first crashed, but looking at the latest file in the DownloadedPaks folder, it was probably Cynosure (CTF-Cynosure2), downloaded from the Unreal Prime France server. The error finally disappeared after I deleted the entire \Documents\Unreal Tournament\saved\Paks\DownloadedPaks folder.
Looking at the logs, this seems to be the error:
Fatal error: [File:D:\BuildFarm\buildmachine_++depot+UE4-UT-Releases\Engine\Source\Runtime\PakFile\Private\IPlatformFilePak.cpp] [Line: 324]
Corrupted index offset in pak file.
It may have been a corrupted map during download. Are you able to play after deleting that folder? Have you tried downloading any other maps, and if so do they experience the same error?
It was definitely a corrupted map. Like I said, after deleting the folder the problem went away and I was able to start the game. Then I joined the same server (UnrealPrime France) and clicked to download all content. Sure enough, after downloading a few maps the game crashed again, and once more I wasn’t able to restart it without crashing. So I went to the DownloadedPaks folder and deleted the most recent file. That solved the problem again.
Whatever the problem was with that map, it’s already fixed, because today I downloaded all the content from the server without problems.
The annoying thing about this was that the crash message wasn’t very informative (actually, it wasn’t informative at all). It just said that ‘an unknown process has crashed’. Which isn’t exactly helpful.
I’m glad to hear that you are no longer experiencing the issue. The bad file was likely fixed by the person running the hub. I agree the crash message is not very clear. Let us know if you experience this issue again and I will attempt to repro it and see if there is a way to get a better message in there.