hey there. I’ve been working on my project all day without a hitch. I started a build and the build crashed. This was a shock because it has not happened to me yet, so I closed everything and now i can no longer start my project. The editor gets to roughly 93% loading and crashes out with basically zero information in the log and crash window.
I don’t know what to do and I really don’t want to revert a whole day of work. What I don’t get is that the project was working without a hitch when hitting the play button in the editor. It was the packaging process that caused me to notice that something was up.
Is there anything that can be done to read the dmp file? It’s gibberish for me. I tried the usual steps of deleting the intermediate and saved folders, but with no luck.
I now it sucks - but duplicate your project folder, delete your startup map and check if your editor comes back up. search for level build datas and remove that (it happens a lot to me that this is the cause). only do that all in your duplicated folder of course so you don’t lose anything
I’ve actually made a little progress. I removed the startup map from DefaulyEngine.ini and got back into the project. The crazy thing I have happening now is that I can’t load that map in the editor… BUT I can run the game, which loads that map. But I think I’ve narrowed down which blueprint is causing my crash. Even though it’s not in that map (but does get spawned from within it), it’s the only bp that I’m not able to open right now.
and it’s a BP-only project btw.
I’ll post back here if I find a solution, but my guess is that there’s a dependency issue going on.
ok. sounds good.
have you looged in the log? something is always written even if it crashes.
try adding a c++ class, so you have a c++ project. then open the project in visualstudio (from file menue in editor). close editor, and RUN the project WITH DEBUGGER attached from visual studio - you now have the power of a attached debugger you see exceptions, can set breakpoints and can narrrow down the problem.
yeah, the log stops at a point that’s unclear. It seems to be looking for a bp in the game folder that doesn’t exist, So it seems to be trying to access data that has not been built yet. I’m not sure how that’s possible, so I don’t think that’s the actual problem. I think it’s whatever that bp is compiling is throwing out an error. I did see a new error in the output log though, so I’ll have to solve that before getting further. What I don’t get is if i run the game from the my title screen map in the editor, it all works great. It has no problem loading the map that’s causing the crash.
I’m definitely going to try your idea of running via visual studio. hopefully I’ll get the missing piece of info.
so it turns out that I has a corrupt texture that was causing a kernel panic on build only. I removed it and a bunch of others (i was not using it nor the others but for some reason they were being built anyway) and now everything works like a charm. It took a while, but it for forced me to finally clean up some warnings I had been having for a while now. Now I have full play loops with zero errors and zero warnings.
Thanks for the replies Adnoh, it was much appreciated!
But I think I’ve narrowed down which blueprint is causing my crash. Even though it’s not in that map (but does get spawned from within it), it’s the only bp that I’m not able to open right now.