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

error in handling scenario data when joining (first sync) in career mode #710

Open
zeus2425 opened this issue Mar 8, 2014 · 9 comments
Open
Labels
Milestone

Comments

@zeus2425
Copy link

zeus2425 commented Mar 8, 2014

When my friends join on my server in career mode they most often get kicked "error in handling scenario data". Weve played on the server for about one week without problems and now it doesnt work anymore. The error only appears in career mode

@godarklight
Copy link
Collaborator

There's been a change since 0.1.5.1 in this area, can I get you to try the development version?

In 0.1.6 we only send the science (and things like kethane data) once during the connect which seems to make this problem go away. However, you're having errors on the initial sync - which might mean this is a different bug.

EDIT: The database should be compatible - But just back it up first just in case. If you still get the error it's worth sending to us so we have a good test case for it :)

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

So I installed the de version and sent it to my friends. Database was not fully compatible. R&D tree was saved but 50% of the orbits from already launched ships were fucked up. And then also the bug came back. I was like gggrh but now I know where the problem was. I deleted all the vessels via sqlite editor and started the server. And the error seems to be gone. With all the vessels cleaned up it works. Before we had like 50 so i dont think too many vessels was the problem. Somewhere the server must've saved a vessel wrong which caused the sync to fail. But the dev version is awesome so many features for the hoster and gamedata sync :D Keep on doing that even though ksp is working on an official mp mod if you want to the mp mod will better than the official mp :D

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

Oh fuck school english that text looks more like a class test than an email :D

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

Ok I tested further and now I can say it always occurs when I have my kinda large space station in orbit (for testing prposes I used hyperedit) and now I can guess why I didnt have the problem only my friends. Here my theory: The space station is huge, they all have notebooks and I have a lower high end class desktop pc. Maybe their notebooks take too long to load that thing or so

@godarklight
Copy link
Collaborator

If you ran into the error during the initial sync, uploading the server database would have made a good test case for us :-/

Notebook/desktop shouldn't have made a difference apart from the lack of fps...

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

I can upload the db if you want but I used mods so maybe could be a problem with the mods even though the mods all worked until I built the giant space station thats why I write here cos I dont think its the mods, just turned my computer off so wait a sec for the db

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

Here you go thats the db from the backup before I installed the dev version cos updating messed up all active vessels. https://db.tt/lVQwJYCR

@zeus2425
Copy link
Author

zeus2425 commented Mar 9, 2014

Oh if you want to test the database you need the modcontrol and my gamedata folder right? I can upload that tomorrow but I again turned my pc off and now dont want to boot it again ^^

@zeus2425
Copy link
Author

https://db.tt/ICyiDXii thats the mods

@TehGimp TehGimp added the bug label Mar 11, 2014
@TehGimp TehGimp modified the milestones: v0.1.6, v0.1.7 Mar 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants