-
Notifications
You must be signed in to change notification settings - Fork 27
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
joined battle room, game is downloaded from rapid but user remains unsynced #118
Comments
very likely there is a bug in generating the .sdz. can you try what happens when you use rapid for the spads autohost, too? |
also, please paste springlobby.log: it should contain more info, i.e. the hashes. |
here's the springlobby log: |
any news? I haven't done the """can you try what happens when you use rapid for the spads autohost, too""", is it still important? |
yes, because the generated .sdz maybe is invalid. |
That's odd because i can play on single player using both the .sdz from the builds or the package downloaded through rapid. i've put one of my spads hosts, nebula3, using the v1.141 (that's the one only generated through the rapid tag and without sdz uploaded to springfiles). The spads host is using the .sdz (i don't really know how to get it to download the file using the pool yet) i've compared the spads server's archivecache with the one on my pc and the checksums don't match! --- spads server (.sdz i got from http://repos.springrts.com/metalfactions/builds/) .../var_normal2/cache/104dev-maintenance/ArchiveCache15.lua
--- springlobby (auto-downloaded from rapid after joining the game room) ...\Documents\My Games\Spring\cache\104dev-maintenance\ArchiveCache15.lua
|
the modified field doesn't matter, its basicly the date/time when the file was written / downloaded. now the difficult part begins: why doesn't the checksum match :-/ |
IMHO the rapid file is the "reference" and the zip must match to it. so the bug could be in either: https://github.com/spring/pr-downloader/blob/master/src/MakeZip.cpp or in spring, when parsing the zip file. |
I've tested touching or replacing the sdz file again on the spads server and indeed the "modified" changes but the "checksum" remains the same. A thing to note is that the checksum matches the one from the previous version (1.14)
this may be because the only file that changed was the changelog, though. |
Thinksome set one of his spads hosts to get MF 1.141 through rapid, and there i'm shown as synced when i join the battle room from my springlobby client which has 1.141 downloaded from rapid also. On both archivecaches the checksum is On Thinksome's springlobby pc, though, the archivecache shows that same checksum for 1.07 and 1.141, which makes no sense at all! ./ArchiveCache15.lua-803- { I've also noticed that the checksums shown on the archivecache don't match the ones shown on the infolog when starting a game (this with engine 104.0.1.1327 maintenance). I checked some times with engine build 1370, but the checksums seem the same. start mf 1.07, infolog mf 1.07 archivecache15 start mf 1.141, infolog mf 1.141 archivecache15 |
ArchiveCache15.lua is created by spring/unitsync, so this looks like an engine bug. |
is it reported on mantis? |
i've reported it on spring's mantis |
ok, thanks! maybe already fixed spring/spring@4d672d0 |
I've been having an issue with the latest metal factions builds (versions 1.1 and later, which I released on the past few weeks).
when i join the battle room (spads host 0.12.5), it prompts to download the game version and I accept, it downloads, but even after it completes I remain unsynced and can't start the game, although I can start the game on single player. It seems to happen for everyone else as well!
--- failed attempts to work around the sync issue
(doing both doesn't work either)
--- successful attempts
NOTE: after I make the commit that triggers the generation of the game sdz here:
http://repos.springrts.com/metalfactions/builds/
I download from there and upload that sdz to springfiles and to the server running my spads hosts.
The text was updated successfully, but these errors were encountered: