Hello!
I know this issue has been reported a bunch of times, but this is really ticking me off. I'm working on a prototype of a game with 3 other guys. We all created our map files earlier this week and one of the guys took those maps and put them together in a leveled map. The map I created worked just fine earlier this week. Now when I try to load ANY of our maps, they all crash UDK:
I've tried loading the maps on two different computers, each with the same install of UDK (2012 November Beta2 version 10499 changelist 1426632). They're still crashing. The other guys in my group are not having this problem. The maps are located in the maps folder.
I know people have been posting logs for this problem. How do I do that? What could be the problem and how do I go about fixing it? It's got me upset.
Any help would be greatly appreciated. Thank you!
Replies
Here's some things to try:
-Try temporarily moving all your packages out of the entire UDK tree and see if you can load the maps then. (it'll spit out missing asset warnings like crazy, but youre just testing to see if its a upk or a umap problem). If it loads ok, DONT save, but close down, move back half your upks, and repeat. Do this until you can narrow down the problem upk(s). sometimes certain assets can cause things like this (non powers of two textures used to be one of them, but i think they fixed that).
-Also, you can try deleting temp files like the shader cache (called global/localshadercache, right in content), the UDKconfig files (but not the default ones), etc.
-If you guys have custom scripts, you could remove them from the classes folder and see if you can load up any maps. Again, try and get the maps to LOAD first, even with warnings, and then DONT save. That should help you narrow down the problem a little.
-grab a newer version of UDK and see if that can open the file?
Also, I uninstalled and reinstalled my copy of UDK (and put our work back into it). Still having the same issue.
Specifically the "PackageVersion 865, MaxExpected 864" bits.
Are you SURE no one on your team is using a later version of UDK? That's exactly the kind of thing that spits out errors like that.