Push Changes update takes a very long time to load and "connection drops"

[2GHSamburskoy]

The problem is a massive one that inhibits the creation of islands:

All PROJECTS, Team of 10: Error communicating game servers.

Please select what you are reporting on: Creative What Type of Bug are you experiencing? Stability Summary All projects have warnings that end in an error making it impossible to test ANY island. Steps to Reproduce Try to test an island Expected Result the island loads Observed Result LogHttp: Warning: Lockout of 10.000000s on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/artifact/d0fac710-c14d-4a50-ae33-71ff9bac29dc%3Apc/cooked-content LogHttp: Warning: Retry 1 o…

Getting a bunch of random bugs when I try to Launch a Session

Here’s the fresh Output Log after I try to Launch a session. Id really appreciate it if there’s someone who’d be willing to hop on a zoom call with me and help me figure out what the issues are and how to fix them, cause I know its hard to tell just based on the code. Any ideas are appreciated thanks! LogHttp: Warning: Retry 3 on https://content-service.bfda.live.use1a.on.epicgames.com/api/content/v2/artifact/fcde39c5-5638-405c-9bf4-6c5647661504%3Apc/cooked-content LogHttp: Warning: Lockout of …

Lockout on cooked content getting out of hand

Affirmative. Same problem.

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? [LockoutUEFN]

Critical - Cooking a reasonably sized map takes more than 20 minutes and times out

Exactly the same issue here too

Session Launching is taking extremely long

Done. Thanks

Allow @editable on non-concrete classes by making editor/cooker validate mandatory fields

Currently we always need to initialize @editable fields, as they are only allowed in <concrete> classes. For example: @editable Teleporter : teleporter_device = teleporter_device{} This brings two problems: If the field value is not configured in editor, it might be hard to notice during debugging. Especially for custom devices, the default value might behave almost like a real device. E.g. it might do the same Print to console. There seem to be cooking performance problems with these defau…

Critical - Cooking a reasonably sized map takes more than 20 minutes and times out

I was able to find a workaround for our map (reduced cooking to just 2 minutes). The idea is inspired by this comment: Session Launching is taking extremely long - #5 by Rory_REDGamesCo. It seems that default values assigned to device fields are indeed related to the problem. The delay somehow scales with number of device references, especially between our complex custom devices. Since in our project we are using @editable, it was not possible to use something like var MyDevice : ?my_device_d…