This question was created in reference to: [Data from region is still loaded after the region is unloaded in World [Content removed]
I would like to import different heightfields for each region, but once a heightfield has been imported to a region, the landscape proxies are not unloading for that region, leading that area to be affected by any heightfields that are loaded in other areas.
Any action that would allow me to force those to be unloaded would be helpful.
A level swap doesnt seem to help though i believe an editor bounce does
[Attachment Removed]
Steps to Reproduce
Create a new partitioned landscape.
Load only 1 or 2 partitions.
Import a heightfield for those partitions (subregion, loaded)
See that the relevant landscape proxies load after that import.
Unload those regions and load others in the World Partition Editor
See that landscape proxies do not unload in the unloaded regions
Import a heightfield to the newly loaded regions
see that it wipes the hightfield data in the other regions
[Attachment Removed]
Hi Karl,
This is actually expected behavior and is not linked to the import operation or even to landscape, for that matter. In World Partition, dirty actors (i.e. actors that have been modified by user action and therefore appear in the “Choose Files to Save” window) are not allowed to unload until they are saved. That is, I believe, to prevent data loss, where the user would modify some actor’s data and then mistakenly unload it, therefore losing any local change. You can validate this behavior with any actor : load a region in WP, then change a property on a given spatially-loaded actor. If you try to unload the region then, the actor will remain loaded (and at this point, it will remain loaded even after you save it : the only way to get it to unload again is to reload the entire level entirely), whereas if you save it before unloading, it will be properly unloaded.
As for importing the heightmap in the new regions, that is due to the import function, which does import on all loaded components, even if the import area is smaller (it zeroes out everything outside the import are). If you want to affect only some components, I suggest you only load them and then use the import function.
Cheers,
Jonathan
[Attachment Removed]
Thank you very much. Apologies for not responding sooner, but this had allowed me to move forward when i got your reply.
Its sub optimal when iterating, especially with the landscape proxies, just because you have to have the added time it takes to save, when you dont necessarily intend too, but I understand the need.
[Attachment Removed]