For me, this issue was resolved by removing my Verse devices.
Did anyone find a fix for this yet? I’m still getting this error message on any of my maps created before V35.
@Flak is there any plans to push a fix for this next week to release alongside the main Fortnite update?
2 Likes
we also still get the same cook error unfortunately and it blocks us from playtesting and results us in having to delay again,
i can provide my logs in a private message if that helps @Flak
1 Like
after the update also the HLOD build and build world partition minimap are infinite, I think it is related to the cooking error
did you ever find a fix for this? I’m still getting this error on any of my maps created before v35 and getting no update from an EPIC dev on if they’re looking into a fix still is sad to see
unfortunately not 
I still run into it 5-10 times every day.
is it hit or miss for you on if it happens or is it just depending on the map? If i get the error should i leave the session and reconnect as a work around?
In my case it is an error on the project, if I go into a new project there is no problem. I don’t know if something like this will appear in new and clean projects, as I don’t work with them.
I used to get an error like this before, but it was a different error and 2-3 restarts allowed me to use project.
yeah that’s the same issue for me, any project I’ve got before v35 I get the content cooking error and can’t launch a session but any map created after the new season released is fine, I’m hoping it gets fixed tomorrow
Commenting on this thread again to say that this bug has been fixed as of V35.10 from what I can tell when testing, if it can be confirmed by an EPIC dev too then it should be ok to close this thread now.
Thanks EPIC for fixing it so quickly!
how ?