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

Desyncing Stable Server #5831

Closed
DorpsGek opened this issue Dec 18, 2013 · 5 comments
Closed

Desyncing Stable Server #5831

DorpsGek opened this issue Dec 18, 2013 · 5 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

Jam35 opened the ticket and wrote:

My suspicion is that NUTS (V0.6.2) http://dev.openttdcoop.org/projects/nuts/wiki
has something to do with it.

Reported version: 1.3.3
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/5831
@DorpsGek
Copy link
Member Author

The_Dude wrote:

This bug report is very badly described, but I would ask to not remove it yet though.

I have been reported on my servers, that we had some desyncs, which happen only on games where FIRS or ECS are presented. I was not able to find out what exactly causes that even with desync debug level 2. When I added more DEBUG lines into both server and client, I found out, that when tile with house is cleared, sometimes the cost differs on server and client (there might be more cases, I was actually only watching clear tile command).

I have no solid conclusion, but I suspect that some NewGRF (because it only happens with more complicated NewGRFs) change between 1.3.2 and 1.3.3 is source of this, maybe the r25956. I am currently thinking about some deeper ways how to found out where this happens, so please, let this task stay open for a while.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5831#comment12826

@DorpsGek
Copy link
Member Author

frosch wrote:

NUTS 0.6.0 is known to cause desyncs, specifically some WET vehicles. I don't know whether they have been fixed (in NUTS), or postponed.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5831#comment12827

@DorpsGek
Copy link
Member Author

Jam35 wrote:

If it is badly described, well I have no other information to give.
Thought I attached a save though.
Try this one:

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/5831#comment12828

@DorpsGek
Copy link
Member Author

The_Dude wrote:

I tried simple solution of reverting the r25956, and the result is desync was no more on server with FIRS newgrf.
So in short, patch that fixes desyncs of some stupid newgrf (coded and reported by me), causes desyncs with newgrfs that were ok before. I'd vote to revert that one, unless anyone comes with better solution.

I might try yet to track where the sync state breaks up on server and client to see what exactly happens.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/5831#comment12834

@DorpsGek
Copy link
Member Author

frosch closed the ticket.

Reason for closing: Fixed

in r26371


This comment was imported from FlySpray: https://bugs.openttd.org/task/5831

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
@DorpsGek DorpsGek mentioned this issue Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant