Just adding onto this- Been a bug most of the time I’ve been working in UE5- it’s just very annoying and I have a feeling is causing VRAM loss as the more UE has wanting me to manually save, the more I get ‘out of VRAM’ errors.
Wanted to add for visibility:
started happening to me too recently on 5.1.1 after working with terrain for a while and minimizing alot.
I didnt have the problem with 5.0.3 (but didnt have a terrain either, if I would just assume things), worldpartition is off and was never turned on for this map aswell.
Also happening here and it’s within the first week of me using UE5.1.1. I migrated a 4.27 project to UE5 an at first all was well. Then I saved the first couple auto saves but now I’m up to 8 or 9 as of this posting during this session.
11/5/2023, UE5.2 latest version, Bug still persists.
Also running into this bug in 5.2…
Still a thing in 5.1.1
Is there any investigation by EPIC?
This happens when you create a new level, don’t save it, and then modify a different blueprint and wait for autosave to happen. You may also have to modify the map in some way, otherwise it won’t trigger an autosave for the map. It seems like autosave doesn’t know where to save the map since it was never saved, has no name, and no file in the content browser. If it auto saves over and over it has no idea it is the same map so it just autosaves it like its a different map. If I make a new map, save it right away and give it a name, autosave never does the annoying save thing. There may be other ways to trigger the bug, this triggers it 100% of the time though(for me).
I recognized the error appearing after renaming a referenced BP and fixed up the redirector
I’m working with UE5.1, and it happening very often in these few days.
Usually it happen after I force delete some assets that be referenced in auto-save level, or I move some assets to new folder.
Fix-up redirectors not working well for this, because it will ask you to save the auto-save level to static assets in content browser, and you have to manually delete them after you do.
Maybe disable auto-save is a most effective way for now, or manually select the assets that what you need to save.
2 Likes
Also happening in 5.3. This is one of the more annoying things of upgrading to UE5. It definitely is due to the level autosaving; which UE4 also had, except it never asked you to save the autobacked levels, it just did it and asked you which to restore in case of a crash. In UE5 it asks you to both save and restore, but it gives you no option to clear the autosaves. This gets particularily annoying when you have to fixup redirectors as you either have to save the auto backups (canceling this also cancels the redirector fixup), disable autosave, or restart and then fixup redirectors.
Been using Ue4/5 since highschool. Glad to see Im not the only auto-save victim.
Here’s to another 10 years of restarting the editor because Ctrl+S dosent work properly
1 Like