Server crash after successful memory calculation – map loads infinitely then disconnects

General Issues and Bug Reporting
, , ,
1

Summary

I’m experiencing a critical issue while trying to update my UEFN map. After successfully completing the memory calculation, Fortnite launches but gets stuck on an infinite loading screen. After about 30 seconds, I receive the error: “Network connection lost” and the session fails to start.

This issue only occurs with one specific map. It used to work perfectly — the problem started when I attempted to publish a new version. To troubleshoot, I reverted to a previous version of the project that was known to work, but the issue still happens, even on that version.

Other maps work fine, which confirms this is not related to my internet connection or system setup.

There are no Verse compilation errors, no warnings in the memory report, and no issues during the memory calculation phase. The problem only occurs at runtime, during the loading screen after launching Fortnite from UEFN.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

  1. Run memory calculation (completes successfully)
  2. Launch live session
  3. Fortnite starts → infinite loading screen
  4. After ~30 seconds: “Network connection lost” error

Expected Result

After completing the memory calculation and launching a live session, Fortnite should load the map normally and allow me to test the updated version in-game, as it did before.

Observed Result

Fortnite launches and gets stuck on an infinite loading screen. After ~30 seconds, the session fails with the error “Network connection lost”.

Platform(s)

All platforms

2

Hey B970,

Something is behaving differently this update.

May have to make a snapshot then progressively troubleshoot.

If your using World Streaming, use DeleteHLODs and don’t build them again until you sort the issue.
It’s a pity your test phase is attempting to play the game, people who crash straight away should consider themselves lucky… lol
How many actors have you got ?

What could be causing it… do you have actors attached to other actors
a recent update made it important to set your props to Movable if they are being attached to a device that moves like an Explosive Device, but any previously attached Static props are still attached, but causing issue.
I’ve seen a post process volume cause a memory check to crash
sequencers with deleted stuff that are still referenced
do you have any custom stuff ?