Submit Feedback

[1.205.023 b1] Server Bug causes NUL after a random save.

Xero shared this bug ago

Won't Fix

Frequent enough issue every few weeks/months that at random my sandbox_config file will corrupt and the world will no longer load anymore.

I honestly couldn't tell you how to reproduce it, just let the world run for a while, people joined here and there, but other than that, it was mostly an idle world.

you may have to let it run for a few minutes, may have to let it run a few weeks or even a month or more... it's seemingly a random occurrence.

However, i did figure out that it occurred during a save, and right after that, the entire save turned NUL.

save 2024-08-19 105111 is the unaffected save. This should load up fine.

2024-08-19 110111 is the save where the sandbox_config was overwritten and turned into NUL and will not load. they are 9 minutes apart as far as the backup goes.

I included the log file, you can go to the very end of the log to see the NUL error out. after this happens, the NUL takes over the sandbox_config and causes the world not to load and boot loop repeatedly.

This could be an edge-case, but I have seen a few others say they have similar issues with NUL overwriting configs.

Files:

I have the same bug

Replies (2)

Keen SWH QA Agent 2 ●

Hello engineer,

Thank you for reaching out to us on the forum.

It appears your server is running on Torch, and multiple MODs/Scripts are active. The issue you're encountering may be related to potential incompatibilities between the MODs/Scripts over time, which could be causing the issue. Since Torch is being used, have you tried reaching out to Torch support for assistance? If not, please reach out to them as they might be able to help resolve this issue as well.

Please let us know if the issue gets resolved with their help.

Kind Regards,

Keen Software House: QA Department

Reply URL

Xero ●

Unfortunately this Occurred not long after this on a new server that was running using vanilla DS and no mods or scripts at all.

I specifically let it run with vanilla DS and it happened again. It appears to be save related if i had to guess, since it happens right after a save.

I'll still reach out to them, but i don't believe it's torch related.

URL

Keen SWH QA Agent 2 ●

Hello Engineer,

Thank you for providing additional information.

Could you kindly share the vanilla DS save file and the log file from the time the issue occurred? This will help us investigate further to determine if the issue is specifically related to the save or if there is something bugged in the game.

You can access your Dedicated Server (DS) save files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineersDedicated\Saves.
Please zip the file and attach it here. If you are having difficulty attaching files you can optionally use Google Drive. When sharing a google drive link please make sure it is set to be downloadable by anyone with the link.
You can access your DS log files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineersDedicated.

Kind Regards,

Keen Software House: QA Department

URL

QA KeenSWH ●

Hello Engineer,

as there has been no reply to this thread in some time, we will close it. If you're experiencing this issue, please create a new thread.

Kind regards,

Keen Software House: QA Department

Reply URL

Xero ●

This was not a torch issue.

I believe the issue was due to having an incorrect configuration file... not sure how this happens Because it's random when the save occurs, set to every 10min.

The <loadworld> tag had 'sandbox.sbc' put on the end of it.

I didn't originally setup this server and didn't notice it at first (apparently neither did any of you).

Somehow this caused that file to be filled with NUL. I assume because it's somehow trying to write data into the file when it saves, but not every time...

DOESN'T MATTER IF USED WITH TORCH OR NOT.

NOT A TORCH ONLY ISSUE.

Again, for future reference, if anyone encounters this, is due to an incorrect configuration file having sandbox.sbc appended to the world file.

This could probably be fixed easily...

URL