UE 5.6 World Partition – Level streaming causes crash in packaged build

Development World Creation
, , , , , , , ,
1

Hello,

We are experiencing crashes related to level streaming while using World Partition in Unreal Engine 5.6.

Details:

  • UE version: 5.6
  • World system: World Partition
  • Project: Blueprint-only
  • Crashes occur during level streaming / cell loading
  • Editor works fine, crash happens mainly in packaged build

The crash seems to happen when streaming cells load or unload at runtime. We suspect it may be related to actor references, loading order, or streaming timing.

Has anyone encountered similar World Partition streaming crashes in UE 5.6?
Are there known causes or recommended debugging steps to identify which actor or cell causes the crash?

Any advice would be appreciated.
Thank you.

cad52739-c204-48f5-866f-db596796b14e
cad52739-c204-48f5-866f-db596796b14e1501×803 126 KB

2

We change from Direct 12 to Direct 11- same thing
We Optimized Enemies - Same thing
We Optimized Water and other assets - same thing
We change Hlods- same thing
We did everything what anypost says in internet or CHatgpt, even we put in upwork and no-one find a reason. please help guys

3

Hello there @AyaGamesinc!

Checking your provided data with my peers, when your levels stream/load at thar particular point in your footage, the engine tries to change the state of a streaming cell that it believes has already been “Removed” from the world, but is actually in the “Unloaded” state, or the other way around, hence the error you are getting:

Assertion failed:
CurrentState == ELevelStreamingState::Removed
CurrentState == ELevelStreamingState::Unloaded

Meaning, the crash has no relation with rendering, or enemy AI, hence why your attempted changes returned no results. To pinpoint what’s going on here, and reach a solution, there are a few options to try:

  • Enable streaming logs (add LogStreaming=Verbose to your Core), so you can identify which cell is being used during the crash.

  • The logs should also help you look for specific BPs or actors active while the error happens. Check for redirectors has well, if you haven’t already do so.

  • Adjust your streaming parameters and your logic to incorporate a short delay between loading/updating levels, which could prevent the engine from “missing” the next level to target.

  • Make a backup of your current 5.6 project, then test migration to 5.7.

For further reading, the community guide below has been quite useful to tinker and adjust level streaming setups, please give it a look: