Confusing error message

[doopeyX3]

Hello, for the past few days I’ve been working on a map and have been experiencing an error message in the message log every time I have tried to start and load into a session, and it’s preventing me from working on the map. The error message is below, any help would be appreciated.

"We encountered an error preparing your project. Error: errors.com.epicgames.content-service.cook-failure, An error occurred while communicating with the game servers (Content (re)cook error errors.com.epicgames.cookplugin.cookfailure.
JOB_ID=32217558-5832-40c2-a50b-15b46aa2e823)., CookJobId:32217558-5832-40c2-a50b-15b46aa2e823
LogSlateStyle: Warning: Missing Resource from ‘CoreStyle’ Style: ‘Unable to find Brush ‘Sequencer.Timeline.VanillaScrubHandleDown’.’
LogWindows: Error: appError called: Assertion failed: PositionPrecision >= -8 [File:D:\build++Fortnite\Sync\Engine\Source\Developer\NaniteBuilder\Private\NaniteEncode.cpp] [Line: 875]

LogWindows: Error: Error reentered: Assertion failed: PositionPrecision >= -8 [File:D:\build++Fortnite\Sync\Engine\Source\Developer\NaniteBuilder\Private\NaniteEncode.cpp] [Line: 875]"

[Hardcawcanary]

Is that a sequencer issue ?

[doopeyX3]

How can I figure that out? it displays under the “Platform Cook” section

[DustinREDGames]

Others have been reporting the same cook errors that seem to be something related to material nodes that were removed/disabled in v26.00, but are not being flagged as an issue in UEFN before trying to launch a session. We are having the same problem in our project.

Content (re)cook error

I’m experiencing a pretty critical bug that won’t let our team launch a session. When we try and launch a session, we are presented with the following error: We encountered an error preparing your project. Error: errors.com.epicgames.content-service.cook-failure, An error occurred while communicating with the game servers (Content (re)cook error errors.com.epicgames.cookplugin.cookfailure. JOB_ID=8f290273-7564-49c8-aa97-da3c0f792b7b)., CookJobId:8f290273-7564-49c8-aa97-da3c0f792b7b The Out…

[Hardcawcanary]

oh yeah the custom material change up for mobile and switch.

This thread has info

Critical - SceneColor node not allowed

Hi, In 26.00 we made it an error to use SceneColor without adding handling for platforms where it wasn’t supported. Prior to 26.00 it wasn’t an error, but users on those platforms would have seen visual issues. This change should have been called out in release notes, apologies. To use SceneColor (or any other nodes that aren’t supported on mobile/Switch) just use the FeatureLevelSwitch to supply a different default value for those platforms. E.g in this image the default value is from Scene…

which I found in this thread

Critical - Distance Fields nodes not allowed because "Switch" doesn't have them.

Since 26.00 any Material using any Distance Fields node is now disallowed because Distance Fields aren’t allowed on PCD3D_ES3_1. Please, blocking a node because Switch and other “weak” platforms don’t allows them is ridiculous. Stop blocking, start warning, we’re not throwing away our work because certain platforms don’t allow it, let us manage it, we’re aware it doesn’t work and aware it’ll look worse, it’s only a risk for us.