I have been working on my project for a few days now, I had to restart my computer, so after saving everything / closing UE4 and restarting my computer, the project wont load. I get:
We apologize for the inconvenience.
Please send this crash report to help improve our software.
What do I need to fix? I don’t want to lose all of my work if possible.
I uploaded the dump and log files here.link text
Just uploaded the files for you.
It seems to be only happening with my project. Just opened a clean project with no issues.
Does this happen when you attempt to open a clean project with no additional content? Can you please post your crash logs here? Thank you!
What was the most recent update you made to the project you were working on?
If my memory serves me correctly I deleted a trigger box that had a reference to take me to a different level when i pressed a button, but I thought that I removed all references to it.
You could try to rename your editor startupmap to something else. This way you might be able to load the editor and you can attempt to fix your problem. Also your log files might tell you what the problem is.
EDIT: Have you played with
C:/Users/Ben/Documents/Unreal Projects/Shadow/Content/Props/SM_MatPreviewMesh_02.uasset ? they seem to be broken or invalid
From what I remember, those have been that way for awhile and have not made an impact on loading the project. But I could be wrong.
It seems as though the issue is within the level blueprint. How would I be able to get access to the level blueprint?
When looking through the reference viewer I see in the “Building1_One_Floor” map it references “showText” and “button” however those are no longer any blueprints that I have. I deleted them earlier today, while working on the project. Putting them back in does not fix the issue.
Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.
If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.