I noticed the longer i work the higher the chance the engine craps its pants and starts detecting its own autosaves as assets that need saving. If i do a Shift+S I can end up with 4-5 iterations of the same level (i aleady saved previously) but within the autosave subfolder, example:
I am having the same issue. I’ve only noticed it after testing level switching while playing in the editor, but that might just be coincidence.
Bump. Coincidence or not, its clearly a bug. Any idea if they even check threads like these or if we should submit it somewhere else? The issue tracker is not open to the public.
Yup, very annoying. Anyone find a work around besides turning off auto-save?
same problem
same issue here
Still here in 5.1
Yup, still in 5.1, but it seems a tad less often.
I’m still on 5.0.3 and it’s a real pain in the a**. I’m very tempted to turn off the autosave feature altogether.
Still a bug in 5.1.1 not sure about 5.2…
Can reproduce in 5.2 ( a lot).
Yeah, this happens to me nearly every time I run the Fix Up Redirectors command on a folder in my project.
Once I’ve saved all the autos as “Untitled” over each other, the editor crashes with the fatal error:
Fatal error: [File: ..\Engine\Source\Runtime\TypedElementFramework\Public\Elements\Framework\TypedElementData.h] [Line: 276]
Element 'World None.None - ID: 5' is still externally referenced when being destroyed! Ref-count: 2; see above for reference information (if available).
This happens every time I do this. Unfortunately, this is a hard crash, so the bug report window doesn’t even show up afterwards.