If I save all my work, it usually is reasonably fast. But sometimes, it takes HOURS, when many _Auto<1…n> (n can be 10 or higher) maps seem to be saves, even after I saved the currrent level itself. If one fails and saveAll is given again, the whole sequence is repeated. In itself that is not a problem but each map is save extremely slow.
Hey there @WillemGr! Is the map in question a large world partition map? Are most of the autosave files level proxies? Does this occur during short sessions or only extended ones? Does it seem like the saves themselves are saving objects that have not been edited?
It is a large environment indeed, but over 95% is just that landscape. I have two levels, one that contains the assets I placed, the second is a working area where I process imported or created assets. This time, it was a long session but I saved several times, and I encountered a few crashes, bit not that many. It appears that each of the ‘autosave’ files does very little on disk, most of the time UNREAL is ‘not responsive’ (and does indeed not respond on any input), until the next file is to be processed: it will ask for the name and continue when it is entered. I have no idea what’s in the resulting .umap files, but all are about the same size, a bit larger than the .umap of the level that contains my scene.
The resulting umaps themselves should actually be just snapshots of your map as is but there shouldn’t be nearly that many. The primary workaround I’ve seen when working with larger landscapes is to disable autosaving, however this is a bit of a gamble as when working with large landscapes the stability of the editor can sometimes drop.