Current Server Issues
As you may have recognised, we have some problems with the latest Nightlies of OpenTTD (beginning with r10300 and higher).
The problem is a desync of the game due to the YAPF of trains. The devs are already looking at this problem and started their work:
-Codechange [YAPF]: added DEBUG_YAPF_CACHE macro that (when set to 1) allows to track YAPF “cache errors”. They are probably responsible for current MP desyncs. (thanks Rubidium for this great idea!).
I will deal with those errors/desyncs tomorrow.
I hope they will be able to fix the problem tomorrow.
Unfortunately we can’t revert to an older revision because the savegame version changed and we can’t load them with older revs.
Update:
Good News! The Problems with YAPF will be fixed with the next nightly release.
Commit by KUDr :: r10394 /trunk/src/yapf/yapf_costrail.hpp:
-Fix [YAPF]: MP desync caused by incorrect last-red-signal penalties applied when cached segment was reused. Players that connected more recently (didn’t have these segments cached yet) calculated those penalties correctly. This caused different YAPF results.
Public Server game #47 unfotunately has been played with r10343, from which we can not revert back to ‘safe’ version, however if we start a new one for any reason it should probably be r10295 (laterst nighty with fully functionaly YAPF, but there is a known issue.with limits on cargo packets) or even r10261 (pre-cargo packets).
On a bright side – PS #46, hosted at Alanin’s server (thanks again dude), is doing fine with r10295.
The issue is fixed. 🙂