This object is in archive! 

Sandbox.sbc File Corruption on Save

LordChicken shared this bug 3 years ago
Won't Fix

Last night I discovered when saving all the dates in Sandbox.sbc and Sandbox_config.sbc is not being saved in a valid AllXsd format and if one or both being saved with non-standard formatting seems to be random.


Example from an affected Sandbox_config.sbc:

<LastSaveTime>2021-01-09T05:28:23.++('+-'-06:00</LastSaveTime> 
Example from an affected Sandbox.sbc:

<LastLogoutTime>0001-01-01T06:00:00./*-+.</LastLogoutTime>
I validated the game files and tested to see if this issue was still persistent. The issue was still present. I then uninstalled, reinstalled the game, and cleared the game cache in %AppData%\SpaceEngineers. The issue still persists.


I have attached the log and the Sandbox.sbc and Sandbox_config.sbc files from the most recent test to this topic. I am able to get the world save to load by manually replacing the offending character with zeros, for example:


This:

<LastSaveTime>2021-01-09T05:28:23.++('+-'-06:00</LastSaveTime> 
To This:

<LastSaveTime>2021-01-09T05:28:23.0000000-06:00</LastSaveTime>
While investigating I have left the save files open in Atom Text Editor and watch as I save in-game after fixing the save the non-standard values are populated in the files. This also occurs on autosave.


This issue has appeared completely at random as I have been playing this game for years without an issue like this and I don't think there was an update within the last few days. I searched on here before submitting this topic and did not see anyone else reporting this, so perhaps I am the only one experiencing this?

Replies (6)

photo
1

Hello, LordChicken,

thanks for letting us know about this issue that you are experiencing. The issue has been reported into our internal system.

Kind Regards

Keen Software House: QA Department

photo
1

Hello, LordChicken,

I see that you write that this issue happens completely at random, but if you have and repro steps, hint, idea... anything, that could possibly point us on the right track, that would help tremendously!

Please let me know if you have something.

Kind Regards

Keen Software House: QA Department

photo
1

Hello, LordChicken,

don´t know if you catch my last comment. So just to remind you:

Can you please specify how to reproduce this issue? By any means possible... the repro steps would be the best, but even any idea, hint, direction when and under what circumstances it´s happening would help us!

Kind Regards

Keen Software House: QA Department

photo
1

Hello Ondrej,

I have no idea how to reproduce this error. It seems to have gone away on its own, however, at the time the only way for a couple of days to get around this was to manually fix the LastSaveTime entries and disable autosave.

photo
1

Hello, LordChicken,

thanks for coming back.

That´s great to hear that you are no longer experiencing this issue!

Will let this thread open for a while so you can inform me if it happens again. But if no, I would most likely close it in about 14 days as it might be just some weird one-timer or very specific coincidence.

Kind Regards

Keen Software House: QA Department

photo
1

Hello, LordChicken,

as there is no now comment from your side, I take it, this issue is no longer happening to you.

Will close this thread now.

Please if you will experience it again in the future, open new thread providing all necessary information.

Kind Regards

Keen Software House: QA Department

Replies have been locked on this page!