One of our level editors is frequently encountering an issue where the map they’re working on becomes corrupted, seemingly out of nowhere.
The issue appears as a map save failure, with the following error:
`Attempting to save bulkdata 1DBDCD5549A843CD844EC9B0643C9A6B with an invalid payload to package ‘/Game/Map/MVault32’. The package probably needs to be reverted/recreated to fix this.`
We’ve managed to recover prior versions every time, but it leads to them losing work frequently, and is in general a bit worrying.
Any insight as to why this happens and how to prevent it is highly appreciated.
Steps before it happened:
Basic things are done (assets integration, materials application, layout (I don’t touch the landscape or lighting tools)) Import new meshes > Place meshes in the level > Apply materials > Move them around > reimport meshes (after correction) > Try to save > Issue
Steps to Reproduce
Unable to reliably reproduce.
Hi there,
I believe that you are likely attempting to save a corrupted asset. It would be valuable to try to track down if there is anything consistent between these crashes, and if there is a consistent asset that is being added into the level before saving, which is causing the crash.
Is the 1DBDCD5549A843CD844EC9B0643C9A6B referring to an external actor ID? You should be able to search for this in your world outliner to see if it matches any of the “Package Short Name” fields of your level actors. If this is the case, would you be able to try to identify any meshes on this actor that could be the cause of corruption? If this asset was the culprit though, and you lost the progress made to editing the level (including adding this new asset), it may not be present in your world outliner.
Otherwise, the next best path forward would be to try to isolate the problem in a way that is more reproducible. Have you found any method to consistently reproduce this crash, or is it frequent, but seemingly random?
Any additional information would be greatly appreciated.
Regards,
Thomas