MegaGlest Forum
Archives (read only) => Vanilla Glest => Multiplayer => Topic started by: narcisgarcia on 12 April 2009, 09:35:30
-
Both environments: Ubuntu GNU/Linux 8.10
Couldn't process event: Error connecting socket (Error: Operation now in progress)
Exception: Server and client versions do not match (v3.1.2 - Sep 6 2008 - 16:05:56). You have to use the same binaries.
The error occurs connecting from a 32-bit system to a 64-bit system, and also from the 64-bit system to the 32-bit system. The error message is the same in both cases.
Booting the 64-bit computer with a 32-bit Live-CD (Ubuntu 8.10 too) and then installing and running Glest, there is no problem with the other 32-bit player.
-
Yes, that's like it is.
32bit and 64bit get out of sync when playing multiplayer :( . Thats why it is forbidden.
You can switch this check off in glest.ini ( something like network consistency check )
and see for yourself. After a while the game gets out of sync and crashes. This can take some time, but it will happen :( .
-
This problema has a logical reason, or is a bug?
-
https://forum.megaglest.org/index.php?topic=3866.msg24098#msg24098
-
If it's the same problem, there is a BIG base problem!
Linux32, Linux64, Windows32, Windows64, MacOS, PlayStation, etc. people cannot interoperate because of the different calculation method used by each compilation (?!). May the source code be more near the standards?
Who compiles Glest by itself, I suppose then can't play with anybody (because of compiling for i386, i586, i686, or with other options) without deactivating the binary check.
-
Yes :( this is the way it is.
and it's very very sad :'( :'( :'( :'( :'(
I hope it can be fixed one day.
And by the way, if they disable the check, they will have a really good chance to get out of sync ( from what I tested! )
Marthino and Matze Braun where once discussing this problem in a chat, and they said that it could (probably) be fixed when all calculations where changed to integer operations ( as far as I understood it )