Game crash upon rejoining server - "Camera entity from checkpoint does not exists!"
My friend and I have been playing a survival server recently (me hosting, him joining) and have run into this bug twice now.
The bug:
Upon him attempting to rejoin my server - whether from invite/join from server list/etc - his game will start to load in, but then freeze (during the "Streaming" part of loading), and then the game will crash to desktop. SpaceEngineers.log shows this line of note towards the end:
2020-01-06 15:11:06.195 - Thread: 1 -> ERROR: Camera entity from checkpoint does not exists!
He only gets this problem trying to join this specific server. I spun up a different server and he was able to join just fine.
What we've tried to get around it:
When this happened for the first time yesterday, we eventually "fixed" it after deleting his shader caches, purging all references to him or his steam ID we could find in Sandbox.sbc (done manually as SEToolbox is apparently broken ATM), and kicking him from the faction. After all this he was finally able to rejoin. Today, it happened again - notably, it started again when he tried to rejoin after his connection temporarily dropped and he disconnected - and after doing the same steps we did yesterday, he is still not able to join. Edit: Though he can get past the faction selection screen, it crashes on the spawn point select screen.
His SpaceEngineers.log and VRageRender-DirectX11.log are both attached. If it helps, I can provide the save file as well (though it will be the version after we attempted to purge him).
In the meantime, if anyone has a suggestion on how to better make a server "forget" about a player, it would be appreciated, as right now we currently cannot play together on our survival world.
I have the same bug
Hello, Engineer!
Do you still have this issue on the latest game version 197.075?
Thank you!
Kind Regards
Keen Software House: QA Department
Hello, Engineer!
Do you still have this issue on the latest game version 197.075?
Thank you!
Kind Regards
Keen Software House: QA Department
I have the same issue while joining the official server "KEEN EU #1" during the same server session. At that point the game wither crashes or hangs up indefinitely. After the server restarts, I can join and my ship is moved away from asteroids. I suspect this happens when I leave the game with my ship parked near an asteroid. If I join any other server where I have no progress, there is no issue.
I have the same issue while joining the official server "KEEN EU #1" during the same server session. At that point the game wither crashes or hangs up indefinitely. After the server restarts, I can join and my ship is moved away from asteroids. I suspect this happens when I leave the game with my ship parked near an asteroid. If I join any other server where I have no progress, there is no issue.
I'm now, as of today, having this same issue, with the same line in the logs.
I'm now, as of today, having this same issue, with the same line in the logs.
Ditto! Cheers!
Ditto! Cheers!
Same. My spawn point is also on an asteroid. AM I locked out of this server now?
Same. My spawn point is also on an asteroid. AM I locked out of this server now?
This is happening to me too, seemingly randomly. Not on an Asteroid spawn point, but a respawn pod survival kit spawn.
One thing that seems to have helped was downloading the world from the server, loading it locally (which also goes *much* quicker and uses way less CPU than trying to join the DS), saving it, uploading that save and then joining again.
This is happening to me too, seemingly randomly. Not on an Asteroid spawn point, but a respawn pod survival kit spawn.
One thing that seems to have helped was downloading the world from the server, loading it locally (which also goes *much* quicker and uses way less CPU than trying to join the DS), saving it, uploading that save and then joining again.
I worked around this by setting the following in Sandbox_config.sbc in the world directory:
<StartInRespawnScreen>true</StartInRespawnScreen>
<EnableAutorespawn>false</EnableAutorespawn>
(these options likely already exist in your config, so make sure to update them, not duplicate them).
The downside is now you will respawn each time, so if you have inventory you will lose it, even if you're in a cryopod. But at least I can get into the game now...
I worked around this by setting the following in Sandbox_config.sbc in the world directory:
<StartInRespawnScreen>true</StartInRespawnScreen>
<EnableAutorespawn>false</EnableAutorespawn>
(these options likely already exist in your config, so make sure to update them, not duplicate them).
The downside is now you will respawn each time, so if you have inventory you will lose it, even if you're in a cryopod. But at least I can get into the game now...
Hello, Engineers!
I appreciate this is an old thread. Is this still an issue or, something that has since been resolved?
Kind Regards
Laura, QA Department
Hello, Engineers!
I appreciate this is an old thread. Is this still an issue or, something that has since been resolved?
Kind Regards
Laura, QA Department
I also get "ERROR: Camera entity from checkpoint does not exists"
Deleting client 'cache' and 'temp' folders bypasses my problem 1 time, but the problem comes back next time this client tries to join.
I also get "ERROR: Camera entity from checkpoint does not exists"
Deleting client 'cache' and 'temp' folders bypasses my problem 1 time, but the problem comes back next time this client tries to join.
I am also seeing this issue on my dedicated server, also with an asteroid spawn.
so far none of these suggestions work and I'm the only player affected, other players spawning on the same base are fine
I am also seeing this issue on my dedicated server, also with an asteroid spawn.
so far none of these suggestions work and I'm the only player affected, other players spawning on the same base are fine
2 years later and this bug still exists. What more information do you need to fix this? I again cannot join official Keen server due to this bug. See attached logs.
2 years later and this bug still exists. What more information do you need to fix this? I again cannot join official Keen server due to this bug. See attached logs.
i am also having this same problem if i reboot my dedticated server i can join in with no issue but as soon as i leave and try to come back i can not join until the server software is rebooted than i can join right in - also an astroid spawn point.
the client etiher crashes or just hangs after world request sent right after i hear the sound in game of the suit initializing,
i am also having this same problem if i reboot my dedticated server i can join in with no issue but as soon as i leave and try to come back i can not join until the server software is rebooted than i can join right in - also an astroid spawn point.
the client etiher crashes or just hangs after world request sent right after i hear the sound in game of the suit initializing,
I have also ran into this bug. For me, it seems to be related to loging out of the server while in a cryo chamber or bed when you are in, or close to an asteroid. I wonder if it has something to do with how asteroids arn't persistent world objects and however cryo tubes/beds work. I had a server admin from Discord help me, they went to my base and ground down my cryo chamber. I was able to log onto the server after that.
I have also ran into this bug. For me, it seems to be related to loging out of the server while in a cryo chamber or bed when you are in, or close to an asteroid. I wonder if it has something to do with how asteroids arn't persistent world objects and however cryo tubes/beds work. I had a server admin from Discord help me, they went to my base and ground down my cryo chamber. I was able to log onto the server after that.
same problem as everyone else, on EarthLike planet no cryo chamber, no beds even no asteroid involved,
exactly as @Brian Paajanen :
the client either crashes or just hangs after world request sent right after i hear the sound in game of the suit initializing,
same problem as everyone else, on EarthLike planet no cryo chamber, no beds even no asteroid involved,
exactly as @Brian Paajanen :
the client either crashes or just hangs after world request sent right after i hear the sound in game of the suit initializing,
Problem happening on our server, started after I messed with some asteroids. Everyone can join the server exactly one time after which if they try again they get stuck on loading or MOTD which to me suggests that it messes with the client files. Server logs don't show anything, player logs show this error: ERROR Camera entity from checkpoint does not exists!
Problem happening on our server, started after I messed with some asteroids. Everyone can join the server exactly one time after which if they try again they get stuck on loading or MOTD which to me suggests that it messes with the client files. Server logs don't show anything, player logs show this error: ERROR Camera entity from checkpoint does not exists!
Leaving a comment to say this bug is still present on my dedicated server. First connection is fine, second one gets to 100% on loading screen, then switches back to 50% and stays there. "ERROR: Camera entity from checkpoint does not exists!" in the logs. Clearing cache and temp folders does not resolve. So far only restarting the server works, and will bug again when connecting for a second time.
When I disconnect my character is just standing on a ship in space, not in cryo or bed. The ship is parked next to an asteroid, which aligns with other reports of this issue.
Leaving a comment to say this bug is still present on my dedicated server. First connection is fine, second one gets to 100% on loading screen, then switches back to 50% and stays there. "ERROR: Camera entity from checkpoint does not exists!" in the logs. Clearing cache and temp folders does not resolve. So far only restarting the server works, and will bug again when connecting for a second time.
When I disconnect my character is just standing on a ship in space, not in cryo or bed. The ship is parked next to an asteroid, which aligns with other reports of this issue.
Replies have been locked on this page!