I have a problem with UE4 crashing just after i load a level on which i was working. I can open the project just fine, use the base maps and all assets i’ve created, but i can’t load the map (my first one) nor export a package to test somewhere else.
My computer has more than the minimum settings required, and it was working just fine.
I dont understand the crash file, but it’s below to this post. I thanks any help you guys can give.
!Id:0630cdae5e3fd87e84b835c23ee45a31
Unknown exception - code 00000001 (first/second chance not available)
Thanks for the fast Reply, i’m kind new to foruns.
The project was created from the top down template from UE4, version 4.3.1 (last available). The Pc with the crash problem is a I7 pentium 950 3.07Ghz, with a Windows 8 64 bit system, instaled on a 240 SSD Drive with 60+ gb free space. 12 Gb DDR3, 2 video cards (ATI Radeon HD 5800 and NVidea Geforce GTX650 ti boost, this last current connected to the main monitor)
Finally, the map was a test project for studies, in which i had many meshes from maya, some with normals, lightmap, some BP e etc. Everything was fine.
I spend around 2 hours creating colision volumes for this meshes in the material properties. Everything was fine.
I decided to test everything and went to build light as preview. I got a message that 2 meshes were with overlaping uvs inside, which was expected. Everything was fine.
I gameplayed the map and worked perfectly.
Saved all assets, maps and everything. Next day, i could load the project, leading me to the template map. When i try to open the map i was working on the previous day, it crashed. I tried many times, reinstaled UE4 and even deleted the problematic meshes.
I couldn’t find an answer on the web but some people may have presented similar problems after building lights, the only thing i believe i made different from other times, other than creating colision.
While its not so important that i restore this map, i would like to know how to prevent this to happening again. And sae the map if possible.
I don’t have a surefire way to guarantee a project will never becomes corrupted. I have had a couple of my personal test beds get corrupted internally as well and couldn’t find a way to repair them. One became corrupted based off of foliage instances and the level had to be scrapped.
The best way to make sure that you don’t lose any work in the future would be to periodically make clones of your project. You can do this from the Library of the Launcher. I keep 2 versions of my important projects at all times and rotate a new cloned project in about twice a week (or more depending on how much I’m working).
We will take a look at your log files. But in the meantime, keep trying to pull .uassets out and retest the level. 9 times out of 10 it’s a blueprint or custom static mesh that is causing the issue.
I’m going to post this as an answer to resolve the question, but I am actually unsure of what caused the corruption. The important thing is though you have recovered and are working. If anything similar happens with your project again please post back here and let us know, we will continue troubleshooting.