For the last couple of days I’ve ben trying to work on some Level Design for our Open World (with World Partition) project and I keep getting this error “Failed to save dependant map packages” after updating a Procedural Foliage Volume.
I basically press the Load Unloaded and then Simulate.
All goes well, until I hit the Save button.
When saving, the list shows the .umap and the external actors now in the scene.
The error shows up immediately, followed by a series of errors for each actor, making me unable to save any of the changes.
I hadn’t touched the foliage in a while, so I don’t know what caused this to start happening, but all other assets, as far as I can tell, don’t cause this issue, as I can move rocks around and save them with no errors.
Anyone know what might be causing this?
Edit: the only thing I did that might be influencing this was increase the size of the Runtime Grid’s Cells and Loading Range in our World Partition settings (in World Settings). Could this have caused the issue?
After some tinkering with my foliage I found out that only the foliage within two or three of the grid quadrants are the only ones not being able to save.
Not sure if it’s noticeable here, so here’s an explanation:
I’ve temporarily hid the Instanced Foliage Actors that are not being saved;
I turned the World Partition Grid Preview ON;
The hidden IFAs (the ones not being saved) are inside these particular quadrants (in the image - you can see the foliage missing right until the edges of the quadrants), while others are fine and saved properly.
Additionally, most of the foliage in these quadrants was placed with a single Procedural Foliage Spawner, including the ones that are being saved, in other quadrants.
Really don’t know what’s going on here and was hoping someone could help
Deleting the Instance Foliage Actors (not saving ones) solves it temporarily. I can save the map in that case, but re-adding the foliage results in the same way.
Also deleting the Spawners and adding new ones has the same result.
Try accessing each tile separate and adding/painting foliage just on that tile.
Mind you that in the end, you have to make triple sure your foliage actors don’t show up at a distance, so you have to bake them into a mesh of some sort to link into the landscape impostor mesh/level.
So in theory, all foliage should always be instanced in its own tile.
In practice, I too have played fast and loose, and it doesn’t matter too much until you have a massive zone with over 9 tiles to deal with.
Anyway, if you cant save stuff on a new level, OR, on an individual tile, I would say its safe to say you found yet another 5.1 bug… file a report and link it here in a month or so when you get a reply and a tracker…
