Crashing when traveling to a partition-enabled map

I crash 100% of the time when attempting to travel to a level where partition is enabled (if that partition level had not already been visited).

  1. Enable World Partition
  2. Create a basic Title Screen level
  3. Using any kind of logic to execute any kind of command to open a partition-enabled level (such as the Open Level (by Object Reference) node, an ‘open’ console command, etc).
  4. Encounter null memory crash

This crash appears to occur regardless of level complexity or grid/load type composition for the actors within it.

Travelling from a partition-enabled world to a standard world does not crash.
If however I start in a partitioned level, and then load a standard level, I do not crash when returning to the previous partition level.
Non-partition level → Partition level = crash
Partition level → Non-partition level = doesn’t crash
Partition level → Non-partition level → Previous partition level = doesn’t crash

1 Like

Hey Buttersoft — appreciate you taking the time to report this! We’re escalating with our team, but would you mind creating a report via the Bug Submission Form to help our team dig in and track it?

Sure thing, just submitted! I tried to the other day but got a perpetual loading icon.

1 Like

I can confirm I get the same problems, I have tried loading level instancing prior to opening level and nada.

–Edit, it only seemed to work when I built the project and possession of pawn is not enabled.
–Hopefully we can work out what is going on here.

Doing the following allows me to load a World Partition map. Unloading the MainMenu map before loading the next map. I have not tried unloading menu after loading a map. I have had enough of crashes for one day.

1 Like

Same crash:

Fixed for 5.0.
You can grab the fix in the meantime here : cl 16981318

1 Like

Thank you for the fix. Can you give us git commit id?

I’m confused, what is a commit id? and, how can i use it to fix the teleport to world partition level?

A git commit ID (hash) is an identifier you can use to tell git to get that particular version/fix from some git server. Of course, that means that you need to build the engine yourself from source you checked out from git in the first place.

I will not recompile the entire engine, Just hope that they gona fix it in early v3

I don’t see the branch cl 16981318 on unreal git, could you post the link of the of the branch ?

The corresponding git commit id is 5cf2032d65039a6947a8399479117430e79ecf5c, you can find it if you search for the CL id in the commit descriptions. The branch is ue5-main.

1 Like

CL numbers relate to Perforce changelist numbers from Epic’s Perforce, which licensees get access to. Unfortunately right now it’s not easy to get a GitHub commit from a CL# as everything is merged to the GitHub accessible branches in huge monolithic commits. I believe this is something Epic were looking to address at some point in time.