Hi all, this is taking longer than expected, and we’re still working on it. I will post here when I have more information. My apologies for the lack of updates.
6 Likes
Hi. Just experienced this too earlier today. Any more information on how to fix it?
1 Like
Still not fixed in 39.20. Any word on when we might finally see a fix?
1 Like
Still not fixed could we please get an update? this been going on for so long.
1 Like
It’s been a while could you please provide an update on this?
I’m getting this now since the latest update. Very frustrating.
It’s been 3 months since this issue was first reported here, it’s been nearly a month since the last Epic reply on this.
Many creators are currently completely locked out of publishing their larger maps. Many other creators have to cook numerous times just for one to succeed. Rapid testing larger maps is borderline impossible. This isn’t even the first time this cook error has been a problem either.
Do we not see a problem here? This is many creators livelihoods, I have friends who have been waiting for months to publish their maps but physically can’t, some of which need payouts in order to live, this has gotten genuinely unacceptable.
Please do something to address this issue, I know this kind of thing isn’t the simplest task to address from experience, but 3 months to fix an issue this critical feels absurd, especially when it’s happened before and already had to have been fixed. Even just an ETA would help at this point, we’ve been left largely in the dark about what is going on here, and the problem somehow seems to be only getting worse and worse.
9 Likes
FRRRR
It’s been over a month since the last update, and this issue still hasn’t been fixed. Can we please get some kind of update on what’s going on? At this point it’s getting really frustrating especially since we were told multiple times that it would be resolved. After more updates finally came out, not only was the problem still there but it actually got worse over time. Because of this my map ended up getting taken down since I wasn’t able to update it, and it’s still down now. This has been impacting my work for months, and there’s been no clear communication on when it will be addressed. We’ve already had three different threads about the same issue before it was moved here so this isn’t something new.
I’m really just looking for a realistic ETA or at least an update on the current status. Any clarification on when this might be fixed would be greatly appreciated
5 Likes
I got this error for like 3 months on one of my maps, and recently it finally calculated the project size by some miracle, and today I did very little changes to the map and it’s giving this error again, meanwhile the map would be ready to release.
@Flak Do we at least know if it’s a memory issue. I’m able to load in on mobile with very small maps but when using my map, it can’t load in. I’m under memory budget.
@Flak Can we get ANY updates on this? this is getting out of hand, more creators can’t upload islands over this and the last update you gave us on this was a month ago now. I’m also experiencing this and can’t post a single update to my main BR map, and can’t resume development on two others. for me its a hobby, but this is some peoples livelyhood. please give us some sort of answer or comment
3 Likes
Could we get an update on this?
I’ll see if I can get the status today.
1 Like
The team is working on a potential fix for 40.00.
9 Likes
Hi @Flak,
Here are my log files after running into this issue for the first time today (my map has just exceeded 40,000 actors).
Logs.zip (20.0 MB)
Hope this helps.
I’m having this issue too. Just added about 10 actors to my map and got this error for the first time ever. I have a fairly active map with over 50+ players at all times and I need to push an update but I can’t. Any workarounds until the update in 40.0?
This is why we need local playtesting. I understand concerns surrounding things like the game server being needed which would put the anticheat at risk of being reverse engineered but stuff like that is not needed when playtesting locally, so why not just remove it from a build made specifically for public use. As AllyJax said, rapid testing larger maps is borderline impossible. I believe local playtesting will fix these issues and help SO SO MUCH with map making and testing. Plus we wouldn’t need to worry about network issues either, so its just better for everyone.
3 Likes