I’m having a rather terrifying issue with my game project.
Whilst changing constraints on a Physics Asset (Tongue) to attempt to fix an issue (described [HERE][1]) I pressed “simulate” to see how the changes would effect the physics simulation.
This is when the engine crashed. Since this has happened, I can no longer open this project. I instantly get a crash report every single time.
This is a 4.2.1 project. I have also tried cloning it, as well as opening a copy in 4.3. The really strange thing is, when opening a copy in 4.3, I get the following disk error:
11030-
Disk F is actually part of my multimedia card reader - which is not in use most of the time. It should certainly have no use for Unreal Engine, since I use it purely for my DSLR card.
I’ve spent a good few months working on this and I’m extremely worried. Any help would be greatly appreciated.
The thought just occurred to me to suggest this: Have you checked your backups? Unreal saves backups of your projects periodically. You might have a backup that still works!
Mine are stored at: C:\Users\Jonathan\Documents\Unreal Projects
Alright, so we’re escalating this to someone higher up the line. So!
First, we’re gonna need your .LOG and .DMP files from your [project]\Saved\Logs folder.
Second, we need your CrashReportClient.log file from C:\Program Files\Unreal Engine\4.0\Engine\Programs\CrashReportClient\Saved\Logs .
Finally, if you could pass along your dxdiag, we should have enough information to write our report and get this information to someone who can hopefully sort this all out for you.
Hopefully we can finally get this fixed and go back to worrying about the tongue.
Okay, I’m trying to get that moved along over here.
In the meantime, are you sure it’s the tongue that’s causing the crash? If so, you could probably move the tongue’s uasset out of the project, which should let you open it up and get back to work. If it’s not your tongue, that makes things a bit harder.
Ah, also: If the project crashes every time you open it, that could be because it’s automatically opening the ‘broken’ level, even if the other levels work fine.
If you have any levels other than the one that broke, then you should be able to open one of those to work on (while we work on getting the broken level up and running).
You would do that by changing the DefaultEngine.ini file under UE4/[ProjectName]/Config .
Aha! Brilliant advice. I removed the three tongue uassets (Mesh, Skeleton and Physics Asset) and the project opened perfectly, with an error saying those files were not found, of course.
Hopefully we have a fix coming for the thing that happened to the tongue, but at least you can work again. I’ll mark this as ‘Resolved’ for now, but feel free to let me know if you have any other troubles!