I was normaly working on my scene, and then UE crashed. When I restarted Epic Launcher, project just gone from list. In project directory I have only Content folder with packages and crash log
UECC-Windows-A02E2F2D484CF9FCD3FF09AD1D902D02_0000.7z (174.2 KB)
Welcome to the Club!
I’ve had this happening on any 5.x.x Version but never on any UE4 version.
My solution is to constantly backup the entire project folder after any meaningful amount of work has been done. It’s tedious and stupid but it is what it is… I’ve lost all my hopes that Epic will fix this Version of the Engine.
I almost never had any issues in UE4 but to UE5 i’ve lost multiple MONTHS of work already because i thought it would be reasonable to assume that the Engine does not break things without user intervention.
My last project broke shortly before i finished it. 8 months of work are now unuseable because the engine is constantly crashing when opening the project altough the last time i was able to work on that Project everything was fine and i closed the editor normally (without any crash or something)
Imo just go back to UE4, UE5 almost has no benefits anyway because most of the new stuff is too broken or unperformant to be used reliably. For my current Project i disabled all the new features (Nanite, Lumen & Virtual Shadow Maps) and everything so far seems to be working great without any crashes.
One beneficial approach is setting up your project as a C++ one, even if you’re using blueprint. This helps minimize the chances of file corruption and ensures that the restore option always works - which is a huge relief in case of a crash.
That being said, utilizing a source control system like Perforce or Git is still the best way to go. It helps prevent any potential loss of files and maintains project continuity. Don’t hesitate to set up your projects smartly - it’ll always pay off in the long run!
1 Like
Thanks for the tip regarding the c++ project.
Sadly im unable to use source control efficiently as i’m on a limited data plan at my home. I can’t just throw gigabytes out of the window.
It should not be necessary in the first place if the engine would work correctly.
I recently had another problems where all and/or nodes stopped working permanently. So that engine is like a time bomb except you don’t know the time left.
You could always just use git with a local repository. No need to upload anywhere just to a local folder.
1 Like