[SaveGame] How to handle Dynamic ActorComponents

[Grogger]

@cmartel;543825

Inline serialization would still work for this – the information for creating dynamic components is serialized after the “InstancedSubObjectTag”. It’s changing the order of default subobjects that can cause issues since they don’t have the data to create or destroy themselves if encountering unexpected data in the save stream.

Honestly, I can’t think of why it wouldn’t work to simply destroy old default subobjects and reinstance them as they are encountered in the save stream.

As for saving all objects – since the data we want to save is contained within actors, we iterate on those rather than all UObjects. The actor and subobjects is iterated for any CPF_SaveGame flags and those who fail that check get excluded. Build a “tree” of all the subobjects in the hierarchy, save them going from deepest to the root.

Using a similar approach to what you mentioned, I’ve got something working pretty well. I didn’t end up sorting anything by depth, because the references were circular in our setup, rather than purely hierarchical; instead, I kept track of what was serialized already and stored simple references if it was encountered again (instead of all the data needed to store if it didn’t exist).

Thanks one last time for the help cmartel, I wasn’t going to solve that one very well by myself!