Hi, I was working on my game in 5.3 all night and I went to restart the engine and now it won’t open. I’m getting this error and I’m not sure why or how to fix it.
I have Run into this as well! This also stopped every one of my projects from opening. I tried verify files nothing works. This seems like an internal engine bug, what ever is causing the editor to end is checked during post load and fails. Which is weird that every project in my unreal does not matter the version still doesnt open. Ive looked at the line in VSC which also doesn’t seem to help because the code is working like it is suppose to just why would they put a condition that shuts down the engine if i need to fix it in the editor…
Seems like it’s pointing towards a shader cache generation function void UMaterialInstance::CacheShadersForResources(...parameters ....){ ...... }
it crashes on a PostLoadCheck.
Maybe your shaders are corrupted / damaged or there is a problem during their generation.
Do you have enough disk space and ram to run your project?
Perhaps you added a lot more levels and now the system can’t handle the generation of extra shader data for some reason? (maybe disk space or too low page file, too little ram).
Did you add any large virtual shaders to your project?
You would try deleting DerivedDataCache and regenerating the shaders if something went wrong with them.
Precisely, the loader is checking those lines and only ends the editor if something seems corrupt or damaged. only thing i did prior to this crash was setting a bunch of skeletons to nanite. Can’t be memory or ram i have plenty. I can try deleting those cached files, would this be in the engine system files where the material instance.cpp is? because i cant do anything passed starting the unreal engine and it fails on everything. I did find the file pathing!
I’ve only ever needed to delete temp files from the project itself. I have never had to modify the engines data cache, though looking at the binary version of the engine it does seem to have it’s own cache directory
your engine path install\Engine\DerivedDataCache
where a singular Compressed.ddp seems to reside with a hefty 2,32 gb of data.
Perhaps try migrating the file to another folder and see if unreal reconstructs it without errors?
Everything. I even just tried making a new project unrelated and still crashes. I wish epic had actual support because this seems like something in their code is sort of now stuck in a loop somewhere. Maybe reinstalling is the only option? Which i also read in other forums did not work for others.
The error sends us to a piece of code that is working or doing its job which is odd.
Seeing as it’s a shader related error did you maybe update your gpu drivers lately. Perhaps it’s an error not linked directly to the engine but something to do with hlsl reading / generation? Maybe something is screwing up on the driver level?
Highly unlikely. The only other thing I can think of is we use a source control. As far as we’ve been using unreal never had an error or problem using any types of source control and saving files to our server. Unrelated opening another project wont even connect to source control so why would it still fail?
The other interesting thing is this happened to my other developer simultaneously ours both crashed while i was watching him flip stuff to nanite. These are the only other connections that make sense other than something on our end just maybe corrupted the system engine files. But no way of knowing what until being inside the editor.
I’d compress the skeleton assets that caused the crash into an archive and delete the pure uasset files temporarily (extract them later from the archive).
I’ve seen other threads on the forum regarding converting to nanite corrupting assets to the point where if you select them in the content browser they crash the engine.
I’m pretty sure nanite data is inside of the project though so it should not impact fresh projects.
Did you maybe install any new plugins on an engine level that could cause instability?
Nanite is the only thing that we did prior to the crash. I was on all day prior to the instance with no issues. Now seems like its pointing toward the nanite more specifically like you said. I wouldn’t know what assets would be causing this in the files to compress. Its 24gigs of content.
No new plugins.
Yes that did happen I remember when we did select some assets in the browser it did crash on his end a few times just from what you described. Trying to uninstall engine completely now.
I was suggesting to just compress the skeleton assets into an archive so that the engine does not calculate them on startup. You can go into the content folder and sort by last modified & you should see which assets were last changed.
Reinstalling does not work, I compressed a few recently modified files but it didn’t seem to change anything. Could be quite tricky to find the right asset if its just 1 thing.
