Waiting forever while trying to disconnect (single player host)

Same here.

Spoiler

The game does not exit gracefully. It looks like the game closes but its process keeps running and its name in the Steam library is displayed in green. Worse yet, if world has been launched, disconnecting and exiting the world makes the game simply freeze on the loading screen immediately. This problem appeared all of a sudden recently without altering anything noteworthy on the system (it runs an up-to-date Arch Linux installation, 64-bit).

This pertains to the 64-bit version of the game. No other game or program is behaving like this.

I have tried to verify the integrity of the files of the game through Steam and reinstall the game completely.

I used to have the following launch parameters: "-tick_rate 60 -threaded_renderer". I removed them now to see if it would make any difference but they do not.

I have never installed any mods on this machine.

I have neither opted in on any betas on this machine in the last year or longer.

Only DST has this problem. It started recently although not in conjunction with any system or game update.

The game logs don't provide any error messages what I can see.

Debugging and creating a coredump in GNU/Linux does not provide any information either, from my understanding.

Running either steam-native (uses the system libraries, which tend to be newer) or steam-runtime (uses the libraries Steam provides, which should be more stable) makes any difference.

What could be wrong? DST worked perfectly since I built this computer 3-4 years ago. Now this super annoying issue started. Thank you for your time.

 

Yesterday I discovered that the background server process might be the culprit, since when the game gets stuck indefinitely on the loading screen after disconnecting and saving a world it does actually resume once you kill the server process (a separate entity).

The game does still not close properly on exit however.

 

 

same, also arch.
it looks like the cave server can't recive the close event from master server.
c_shutdown in cave server also stucked.

Edited August 31, 2023 by AlPt

I found a weird solution:
input "c_shutdown()\n" to stdin of dst(or stdin of steam if you start the game by steam) at least 4 times(master, cave, client, client in main menu), will close the game as expected.

Also came with that problem, including also a fact that I am on openSuse Tumbleweed

I can confirm this is still a problem. I am on openSUSE Tumbleweed with KDE Plasma. I tried looking through the game scripts to find the problem, but it seems to be an entirely engine-side issue. I noticed in the logs that this line appears for the master shard, but not the caves one:
[IPC] Received shutdown signal.

Logs from while the game is stuck are attached.

caves_server_log.txt master_server_log.txt client_log.txt

Can confirm the bug is still present

On 4/5/2024 at 11:42 AM, grisi said:

Can confirm the bug is still present

The only solution w/o using third party instruments and forget in fidelity this issue was for me to use "Force Steam Play compatibility" and then select "Steam Linux Runtime (1.0)" at the bottom of the list