Loading...
  OR  Zero-K Name:    Password:   

Forum index  > General discussion   > Help and bugs   >

Forcing spring 98.0 in springlobby

6 posts, 785 views
Post comment
Filter:    Player:  
sort
___DELETED___201545
10 years ago
I am using spring lobby with spring 98.0 on Linux. Spring 91.0's unit sync is very unstable .Spring lobby crashes very time I set spring 91.0 as the default engine. How do I force join zero-k games with Spring 98.0 instead of Spring 91.0?
+0 / -0


RUrankAdminikinz
10 years ago
A hack that may possibly work is replacing 91.0's libunitsync.so with the one from 98.0 in ~/.spring/engine. This will result in game hashes being different, but springie doesn't use them either way so it shouldn't matter in practice. I'm not so sure about map hashes though.
+0 / -0


AUrankAdminGoogleFrog
10 years ago
Everyone in the game has to use the same engine version so forcing SL to use the wrong engine will be pointless.
+0 / -0
USrankPowerGuy
10 years ago
wouldn't a different library generate different content, and thus not come to the same conclusion as the peers?
+0 / -0

AUrankAdminSaktoth
10 years ago
Yes precisely.

You should be able to use !setengine or play on the bleeding edge host, though I'm not sure of the current status of those options.
+0 / -0


RUrankAdminikinz
10 years ago
I should elaborate that the idea is to only replace the unitsync library (since 91.0 unitsync is a bag of segfaults), but not the spring executable. That way you can set the engine to 91.0 in SL without it crashing and play with spring 91.0 on springie hosts.

quote:
wouldn't a different library generate different content


Unitsync is not used for playing, it's a library that lobbies (except ZKL) use to see what mods and maps you have, get some info about them, calculate their checksums and a couple other things.
+0 / -0