I guess this goes here: Discuss your problems with the latest release of the engine here. Problems with games, maps or other utilities belong in their respective forums.
Since a few weeks maybe spring-dedicated and the client don't sync. See also: https://springrts.com/mantis/view.php?id=4705
I also noticed that the versions the lobbies try to download now include the word "develop" after the version name, and that pr-downloader does not produce a folder with that name. If I rename the folder that pr-downloader downloaded to include the word "dedicated", then Spring WebLobby and NotaLobby do sync, but tasclient does not. Springlobby doesn't work for me so could not test*.
Since this apparently does not belong in mantis (not engine issue), i wonder if someone could direct me to the appropriate forum for this issue, At the moment the only way to test non-98.0 versions of the engine is with SWL, NL or by launching spring directly.,
* In windows it detects engine version wrong, in linux mint the latest supported version is 0.169, which does not handle multiple engine versions, and building from source does not work because of failed dependency.
Problem with syncing dedicated and client
Moderator: Moderators
Re: Problem with syncing dedicated and client
Read this!https://springrts.com/mantis/view.php?id=4705 wrote: You are just using wrong dedicated version. Netprotocol was changed a little. Means when you got desyncs it means you, using diff versions of dedi & client.
infolog.txt is missing, which versions of programs are used, steps to reproduce the problem.
please, try to write more technical!
Re: Problem with syncing dedicated and client
There is no infolog because game is not started. It's not a desync in game but rather that lobbies report that versions don't sync.
If you want technical output read this: http://pastebin.com/sAxvJhNf
Maybe this is indicative of the problem:
[Error] ../../tools/pr-downloader/src/Downloader/Http/HttpDownloader.cpp:212:verifyAndGetNextPieces(): md5 sum missmatch
If you want technical output read this: http://pastebin.com/sAxvJhNf
Maybe this is indicative of the problem:
[Error] ../../tools/pr-downloader/src/Downloader/Http/HttpDownloader.cpp:212:verifyAndGetNextPieces(): md5 sum missmatch
Re: Problem with syncing dedicated and client
whats with that?
and no, this message isn't the cause, also the paste is incomplete.
for me it looks more like your spring data dirs are broken -> infolog.txt is needed!steps to reproduce the problem.
and no, this message isn't the cause, also the paste is incomplete.
Re: Problem with syncing dedicated and client
There is no infolog until the game starts.
It's not a problem with the download: the engine downloads to my computer but it does not sync with dedicated. But as I already wrote before, if I launch spring.exe directly then it works just fine. You want one of those infologs that have no problems in them?
It's not a problem with the download: the engine downloads to my computer but it does not sync with dedicated. But as I already wrote before, if I launch spring.exe directly then it works just fine. You want one of those infologs that have no problems in them?
Last edited by Jools on 17 Mar 2015, 02:09, edited 1 time in total.
Re: Problem with syncing dedicated and client
is that your problem? if so, don't use tasclient, its broken. also there is no maintainer / bug tracker for it.Spring WebLobby and NotaLobby do sync, but tasclient does not.
you should learn to write understandable text, your initial post is very difficult to understand.
Re: Problem with syncing dedicated and client
Still requires manual intervention for making SWL and NL to work. But maybe let's wait for more people to give their input.
Re: Problem with syncing dedicated and client
locked: thats lobby specific. use the dedicated forums/bug tracker for that.
even after 4 (!!!) posts i didn't understand your problem.
please, learn how to write proper bug reports. "It doesn't work" isn't useful. you must give at least instructions how to reproduce the problem.
even after 4 (!!!) posts i didn't understand your problem.
please, learn how to write proper bug reports. "It doesn't work" isn't useful. you must give at least instructions how to reproduce the problem.