We’re have an issue with World Partition Builder not loading actors that are inside level instances and assigned to a data-layer, when that data-layer is loaded via IncludedDataLayers.
Example:
ActorA is in the persistent level.
ActorB is in a level instance added to the map.
Both are assigned to a data-layer.
Test 1: The data-layer is loaded by default (i.e. the checkbox is ticked in the editor).
ActorA + ActorB are loaded.
Test 2: The data-layer is not loaded by default, but added via IncludedDataLayers during PreRun.
ActorA is loaded.
ActorB is not loaded.
All other actors in the Level Instance not assigned to the data-layer are loaded.
I’m struggling to find how the level instance system and data-layers interact when loaded via the builder. Is this a known problem, or do you have any suggestions?
I found that the state of the Datalayer instances can get reset by the local user settings while running the commandlet. ( See PerWorldEditorSettings entry in <Project>\Saved\Config\WindowsEditor\EditorPerProjectUserSettings.ini)
That file should not exist on build farms so it should be possible to run Builders there although it’s impractical for local runs (dev\debug…)
The engine team submitted a fix for the problem. You should be able to integrate the fix in version 5.6. The new code cannot be added to hotfixes so you will also need to integrate the code when (if) you migrate to version 5.7.