Team Workflow - Nested Level Hierachy

Hello everyone,

I’m trying to set up a project structure that is more conducive to a team environment. I am trying to set up nested levels through the level manager. The following Illustrates what I am trying to achieve:

  • Master Level
    • Level_1
      • Level_1_SubLevel_1
      • Level_1_SubLevel_2
    • Level_2
      • Level_2_SubLevel_1
      • Level_2_SubLevel_2

In the “Master” level, Level 1 and 2 are loaded into the level manager and are set to “Always Loaded” and I have a Blueprint that allows the player to switch between the two levels on runtime. For explanation purposes, let’s say there is a plane in “Level_1”, a cube in "Level_1_SubLevel_1, and a sphere in “Level_1_SubLevel_2”. If I am loaded into “Level_1” and both sub levels are loaded in the level manager as “Always Loaded” then I get the expected result where I see all three objects… plane, cube, and sphere.

The problem comes when I then nest “Level_1” into the “Master_Level.” I then only see the plane and no longer see the cube or sphere. Is this to be expected from the route I’m taking? If so, are there any work arounds or alternative solutions to breaking a level up into parts that multiple team members can work on?

Thank you for any input,
-Craig

I would also like to know more about if this is possible. Having a structure inside the level manager like:

Base Level
- Level 1
- Level1SubStuff1
- Level1SubStuff2
- Level 2
- Level2SubStuff1
- Level2SubStuff2

Would be really useful.