SE still running in steam after exit.

Beacon of Wierd shared this bug 2 years ago
Investigating

During the whole survival updating play-test every time I exited SE it was still running in steam. Not sure if anyone else has had this problem, steam support site is saying that it's most likely do to bad exit procedures on the games side.

Comments (7)

photo
1

same

photo
1

This started for me right after the playtest ended.. have to force close using Task Manager now. Also cannot save game.. autosave not working.. conveyors stop working when this happens as well as grinded blocks continue to be rendered although I can pass right thru them. Never had any of these issues until the playtest.

photo
1

My sound wasn't properly working so I exited SE, fixed my sound and tried to start SE again. But steam kept saying that SE was already running... however not even taskmanager could find anything about SE.

I rebooted steam and all worked fine, after playing and testing in SE I exited and got it again....

b868ff0e82541886c100973ab5fe4108

photo
1

If Steam does this to you again, you can find the Space Engineers process as a drop down option in task manager listed under Steam Client Bootstrapper as a sub-process. Saves you restarting steam this way.

photo
1

All the other games I own, when I exit the game, it exits quickly, but Space Engineers is different, and takes nearly an entire minute to exit. Says, "Space Engineers running", minute later, just "Space Engineers"


FYI

I noticed another directory on my computer located in "appdata/local" called "GameAnalytics", and inside of that is another folder called "SpaceEngineers.exe". Inside of that folder, 2 files (ga.sqlite3 and ga_log.txt)

photo
photo
1

yea, I also have this issue, had it for as long as I can remember,

I have had to create a "bat file" on my desktop that kills all space engineers processes so that I don't have to find the task in the task list every single time.


Content of batfile:

Taskkill /IM SpaceEngineers.exe /F


Best Regards

Me

photo
1

Hello, Engineer!


Thank you for your feedback! Yourtopic has been added between considered issues.

Please keep voting for the issue asit will help us to identify the most serious bugs.


We really appreciate your patience.


Kind Regards

Keen Software House: QA Department

photo
1

I did experience this issue from time to time before Frostbite. After Frostbite, Space Engineers always remains marked as "running" in Steam. I need to close and re-open Steam before it goes away and more importantly, allow me to launch SE again.

photo
1

Hello!

I appreciate this thread is quite old. I hope that this issue no longer persists and you can exit properly. I will close this thread if it is no longer an issue. We have had a number of updates since this post and are now on 197.075. If you're still having issues, also please let me know so this can be looked into :)

Kind Regards

Laura, QA Department

photo
1

I am still having this issue as recently as last month. Happens almost every time I exit the game and try to start it. Sometimes restarting steam fixes it, but most of the time I just give up and do something else for a while, then it works a few hours later.

photo
1

Hello!

Thank you for letting me know. Does this happen after a particular game mode has been played or if you have been on a multiplayer server? Does it happen after a crash or purely just closing it as you're off to do something else? Do you have to force quit it in the processes or are you waiting it out each time? Any extra information would be great :)

Kind Regards

Laura, QA Department

photo
1

I usually play single player creative mode, but it has happened when I play multiplayer too. The game rarely crashes, the problem happens when I exit the game normally. The game is still running in the task manager even though the game has been closed down and the window has been closed. Force quitting it through the task manager sometimes fixes the issue, sometimes it doesn't. The only thing I usually have running in the background while playing is the Firefox browser, but I have had the problem happen even with no other programs running.

photo
1

I recently had this happen to me too.

photo