A few days ago there was an update, and it looked like we were able to launch, push, start, and end the game without any problems. Nothing was changed on the map, but the timeouts have returned again -_- .
We created another ticket due to spatial corruption across the map. I honestly don’t know what else to say.
Our team is dealing with a lot of bugs on the map and is trying to find solutions, but it looks like there’s nothing more we can do without intervention from Epic’s developers and fixes to UEFN itself.
Edit: Memory reduced to 80,600. The same error still occurs.
The output log shows the same connection timeout.
The project is stalled again, with no chance to test the map.
After starting the game, Fortnite shows this error after ~10 seconds.
Shortly after that, UEFN triggers a timeout event and disconnects the session.
Fixed all errors in output logs. Now there is none errors after and during disconects. Only error in Forntine (picture above).
92k memory. Here some logs:
And here we go again — the timeouts are back. The project is within the budget range, around 96k memory temp. No one from the team can start a session. The map is already optimized to its maximum level. The only improvement that might help is the code, but it will take a ridiculous amount of time to test which logic is draining so much memory.
@ChillyRider We meet again! I am also getting a similar issues again when I launch session it disconnects me and says timeout error. Disabling all my verse devices fixed it but when re-enabled it breaks again.
