Lockout on push changes is getting a bit much, what can I do?

As you can see on the picture, every time I restart a session it locks out for about 6-9 times * 10s. So a minimum of a one minute wait. Iteration becomes pretty slow with this. What can I do?

@soulwizard7 Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative

1 Like

Hi @soulwizard7 those lockouts are due to our cloud cookers cooking your project as far as I’m aware. Cook times are usually around 1 minute so this is likely to be expected.

2 Likes

The problem is that every change you make in the project you have to cook and it scales with memory I suppose, but when your map has a bit too much it dose literally a minimum of 10 min each time which is impossible to work with.

I tried everything and I didn’t get any clue why this scales of why happens at all, because it started occurring in patch 25.10 I think.

I don’t know if before you did not show this messages but then pushing changes to test its been a pain in “big” maps (just above 50.000 mb memory). If you know any way we can accelerate this process or what we are doing wrong to trigger this messages it would be a great improvement.

It is strange because every Lockout it’s about the same artifacts, seems like a problem of one asset not the whole project.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.