The season got delayed, is there anyway to speed this up???
1 Like
FORT-1006754 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 40.00.
4 Likes
This hasn’t been fixed as of 40.00
1 Like
This has unfortunately not been fixed:
PlatformCook: Error: We hit an error while cooking this content
PlatformCook: Error: cook_failure
LogValkyrieRequestManagerEditor: Detected cook failure, cook job id df04c130-2e05-463d-912f-feae01dd9db7
PlatformCook: Error: Internal Error - Cooker Ran Out Of Memory
LogValkyrie: Display: ProjectSizeRequest::CancelFlow for 3101256a-4bda-600a-c1db-05b5d6358c1a - Content (re)cook error errors.com.epicgames.cookplugin.cookfailureoutofmemory.
JOB_ID=df04c130-2e05-463d-912f-feae01dd9db7
details: Launch session - Cook failure out of memory - #2 by Bug-Reporter
Still getting this
We’re also getting this; did not get it before v40.00 update.
Just like everyone else, unfortunately nothing has changed for us either this update. Issue still exists.
1 Like
Could we please get an actual update on this? It’s extremely frustrating at this point. This was promised multiple times that it would be fixed, yet here we are and nothing has changed. We’ve been hearing the same thing over and over, but there’s been no real progress.
It’s been months now, and we’re still stuck in the exact same spot we were back in mid 2025. That’s honestly unacceptable, especially for something that’s been acknowledged so many times. It’s getting really hard to stay patient when it just feels like we’re being told what we want to hear instead of seeing actual fixes happen
1 Like
If they could enhance logging during the cooking process, e.g. showing which assets are being processed, then we could most likely figure out which asset(s) are causing it to be going out of memory & resolve it ourselves.
This is a repeating pattern I recognized, lack of meaningful logs to resolve issues ourselves.
I’m now merely guessing which assets are causing the OOM and hopefully I can resolve it this way.
My post: Launch session - Cook failure out of memory - #6 by L10NHEART
Its not specifically assets causing it. If you delete half of you actors on your map, then try to cook it works, then if you revert those changes and try the full map again, it now will cook due to the other half being cooked. If it was a specific asset it would not cook under any circumstance
1 Like
I’ll try again to delete the actors on my map, I think I deleted about 80% of them and it didn’t want to cook. Will even try deleting all just in case. Any other idea’s?
try getting it down to roughly 20k actors then try it
1 Like
Maybe this can help. A while ago, I noticed these yellow lines in the output log: “LogMaterial: Warning: [AssetLog] MATERIALPATH: Failed to compile Material for platform PCD3D_SM6, Default Material will be used in game.” After fixing the asset, the project size succesfully calculated. Maybe it was just luck, because sometimes I get the error even when no assets have any fault or at least not in the output log.
It’s been 3 days and there’s still no update on this. We’re completely in the dark on when or if this will be fixed. Some of us can’t even publish projects because of it. Can we get a clear update? This was said to be fixed, but now even more people are running into it after 40.00
Hey this thread is set to close in about a month could we please get an update on this?
It’s been 15 days with no update so far and the topic is set to close in 23 days. Could you please let us know if this is being worked on and when we might expect a fix?
@Flak We’ve been lied to and still haven’t gotten any real updates on this. The memory cook error issue is still happening, and some of us haven’t even gotten a map since this started almost a year ago. I’m tired of this because we’ve been misled so many times. So when can we expect a real fix, especially with this form ending in 20 days?
2 Likes
My main projects with 70k+ actors cook completely fine since 40.00 after getting the error all the time before. I recommend to look through all your assets for errors (mainly materials and material functions), the output log will tell. If it’s the level causing it, save the level into a new level or copy and paste everything.