Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After a server crash while in space, click on your ship honks off the UI #151

Open
ryllae opened this issue Mar 6, 2021 · 3 comments
Open

Comments

@ryllae
Copy link

ryllae commented Mar 6, 2021

Crash the server while mining roids (#101). When I log back in, I'm placed outside my last station with some of the ore. Double click your ship. All items in space disappear; the overview shows them at "1.$ AU".

No idea what's broken, but I repo'd it 3 times.

@zhyrohaad
Copy link
Owner

wow......ok, so solSystem State is off.
will look at this one rather soon.

@zhyrohaad
Copy link
Owner

ok, this is a good one.....
on segfault, current state is not saved, as i dont have a good way to validate dynamic data in server, including ship position, cargo, etc.
so, on restart and relog, things are reverted to last known 'semi-valid' state, which can be the station you last undocked from, the last gate you jumped thru, or a position in space other than those. if your ship's last position cant be validated, you will be placed in orbit around a random planet. this is the catch-all for bad ship position data.
the ore is saved occasionally, which is why it shows you have "...some of the ore...".
i think the positions on overview are off due to the ship being in that semi-valid state, where data will pass a shallow validity test, but arent quite 'right'.
at this time, there are no full validity tests for anything after a crash.

@ryllae
Copy link
Author

ryllae commented Mar 18, 2021

proposal: do a "logoff warp" after such any such disconnect or crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants