[Cook Failure] We hit an error while cooking this content

General Issues and Bug Reporting
, , ,
1

Summary

Since last week’s update, a cooking error has been occurring, preventing us from even entering the session.

Additionally, previously built playtest versions also fail to download when trying to join, making access completely unavailable.

We hit an error while cooking this content

errors.com.epicgames.content-service.cook_failure

CookJobId:8144cc5e-5ebd-4379-8c9b-e6b2be419abc

An error occurred while communicating with the game servers (failed to cook module deb6d30c-4cfd-2f38-0fbf-e885da18a89a (artifact 63630f3e-dddd-4d3d-ad56-11c6a4c748d2:linux-server) (cookJobId 8144cc5e-5ebd-4379-8c9b-e6b2be419abc) with error code errors.com.epicgames.cookplugin.cookfailure).

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Other

Steps to Reproduce

  1. Launch Session
  2. Edit Mode

Expected Result

  1. Launch Session
  2. Edit Mode

Observed Result

We hit an error while cooking this content
errors.com.epicgames.content-service.cook_failure
CookJobId:8144cc5e-5ebd-4379-8c9b-e6b2be419abc

Platform(s)

PC

2

UnrealEditorFortnite.log (6.4 MB)
this is my last log

3

Turning off Streaming solved it, but I still need Streaming for memory.

1 Like
4

Hello, I think it’s the same issue than this one : https://forums.unrealengine.com/t/unable-to-launch-a-session-we-hit-an-error-while-cooking-this-content-errors-com-epicgames-content-service-cook-failure

Really interesting, you found the issue was linked to world streaming, it’s also enabled in our project. And like you, we need it absolutly.

5

FORT-920814 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

6

I have removed all devices and still get the error.
It definitely seems to be an issue with world streaming.
Have you found a workaround?

1 Like
7

image
image1002×607 18.5 KB

My project is a LEGO project and the project size is also Error as shown in the screenshot.

8

image
image1000×604 41.3 KB

If turn off streaming, the project size is calculated.

9

image
image530×695 38.9 KB

Also, Changing only the values of Cell Size and Loading Range causes the Error

10

I recently encountered and resolved an issue after the 36.10v update, and I’d like to share the solution in case it helps others.

After the update, I started seeing the following error log:

/{MyProjectName}/Maps/{MyProjectName} Errors logged while validating asset  
Root Scene Component was not a Primitive component type, could not calculate overlaps for actor Actor_UAID_6C02E0519CA4F96702_1736387240.  
Root Scene Component was not a Primitive component type, could not calculate overlaps for actor FortPlaysetRoot_UAID_6C02E0519CA4F96702_1737382609.

Through investigation, I found that this error occurs when a LEGO asset is placed as a child of a Root Scene Component that is not a PrimitiveComponent. This prevents overlap calculation from working properly.

To resolve this, I made sure that LEGO assets are not attached under a non-primitive Root Scene Component, and that fixed the issue.

Hope this helps others facing the same problem!