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

desync in r20080 #3945

Closed
DorpsGek opened this issue Jul 13, 2010 · 8 comments
Closed

desync in r20080 #3945

DorpsGek opened this issue Jul 13, 2010 · 8 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

planetmaker opened the ticket and wrote:

Attached find the data gathered by debug_level desync=3 and a complete command log gathered by the attached patch applied to clean r20080.

Attachments

Reported version: Version?
Operating system: All


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

planetmaker wrote:

by chance we found an inconsitency in our screenshots, taken by different players, in the same company. It was said that it cannot always be re-produced which colour is chosen. Maybe this is the place to look for the desync?

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8311

@DorpsGek
Copy link
Member Author

planetmaker wrote:

just to add another piece of information: the colours of the trains around the HQ started after some time to change colour for me somewhat randomly. The same applies to the train colours in the purchase menu, if I opened one. Attached the savegame from my connection to the server.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8312

@DorpsGek
Copy link
Member Author

planetmaker wrote:

note the purchase list colours... Referencing the 2nd CC doesn't seem to work correctly

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8313

@DorpsGek
Copy link
Member Author

Rubidium wrote:

On IRC it is said that it happens on multiple clients and that the colours change "daily". Furthermore it is the first time this version of the 2cctrainset is used, so it might be that it is the trainset that does something fancy.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8317

@DorpsGek
Copy link
Member Author

Rubidium wrote:

The issue is somehow related with initialisation; without debug desync you'll "desync" from the server, with debug desync you don't "desync" from the server. The server in this case is the commands log from the above.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8318

@DorpsGek
Copy link
Member Author

frosch wrote:

The game uses special liveries for EMU, electric trains and freight wagons. Usage of these special liveries is a client setting.
So likely the colours are just right.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8319

@DorpsGek
Copy link
Member Author

frosch wrote:

First result: Var43 can desync due to _settings_client.gui.liveries. But 2CC does not use the variable.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3945#comment8320

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Fixed

In r20137


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

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels 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