I am currently experiencing something extremely unsettling - I have a very complex shader which, when included in my level, completely breaks my project.
I get an error which states my cooking time took too long. Can the complexity of a material really cause such a crash?
And if so, how come do I not get a shader compile timeout, but a cook-error timeout?
This may have something to do with it
I have checked that particular thread, and I had a different error back when the SceneColour was the bug, now my error messages have to do with cooking, not material or ES3_1 - I have seen those keywords and fixed all errors that seem to fit that
@5Daydreams Thank you for your report! Can you please re-post using the “New Issue” option on the Issues and Bug Reporting forums? Posts with this feature are connected directly into our development team so we can quickly get to them!For more information, such as how to get the reference ID, please check out the article here: https://create.fortnite.com/news/using-the-creative-and-uefn-bug-reporting-form