Since about 6-17-23 (approximately) sessions have bee taking 20+ minutes with “Pushing Changes” waiting “Preparing…”. Previously this was not nearly this long.
Last log line before the wait is
LogValkyrie: ProjectSizeRequest::GetProjectDownloadSize for 7e681cac-4de4-e350-c279-e5a0bbf3650b`
and once it finally finishes
LogValkyrie: ProjectSizeRequest::GetProjectCookedSize for 7e681cac-4de4-e350-c279-e5a0bbf3650b
LogValkyrie: ProjectSizeRequest::GetDependencyDownloadSizes for 7e681cac-4de4-e350-c279-e5a0bbf3650b
LogValkyrie: ProjectSizeRequest::Completed for 7e681cac-4de4-e350-c279-e5a0bbf3650b
LogValkyrieSummary: Server Summary - Successfully activated content on all platforms
Project Size is only 16%. Is there something that we are doing that can be causing this turnaround time to be so great?
Simple verse recompile seems to not at all and need everything to shutdown and reopen in order to Push another session.
@Rory_REDGamesCo 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
I am sorry I missed this reply. Yes we did figure out one cause. Our scripts were using a lot of variables as members to another device. E.g.
var MyTeleporter : teleporter_device = teleporter_device {}
We would then resolve these with tags later to get the real device we were looking for. We did not realize that this also created a default version of the device and I am guess that the Prepare set goes through the verse scripts and creates these devices on Preparing. This step was mostly unnoticeable until we had a custom device with a number of these member variables and then places a few hundred of this device.
The solution was to do something like this to prevent the default device from getting created.