26
MegaGlest / Re: Rock Solid Stable - Release Time
« on: 16 November 2013, 19:33:13 »
So I just tested 3.8.0-beta1 and 3.8.0 joining by setting
beta1 can try to join 3.8.0; upon joining, beta1 gets an error "Invalid message type: 76", becomes very slow, and gets disconnected.
If 3.8.0 tries to join beta1, the beta1 host gets "Invalid message type: 76", becomes very slow, and then crashes; 3.8.0 gets disconnected and goes back to the main lobby.
(I tested on gnu/linux, don't know if crash also happens on windows.)
So 3.8.0 and 3.8.0-beta1 can never be in the same game together, although they can try to join each other and it is very inconvenient for (only) the beta1 side. Is that good enough to keep the 3.8.0 number? If possible, maybe a note can be put into the masterserver message telling beta1 users to upgrade.
Code: [Select]
const string glestVersionString = "v3.8.0";in source/glest_game/facilities/game_util.cpp for current svn (r4824).beta1 can try to join 3.8.0; upon joining, beta1 gets an error "Invalid message type: 76", becomes very slow, and gets disconnected.
If 3.8.0 tries to join beta1, the beta1 host gets "Invalid message type: 76", becomes very slow, and then crashes; 3.8.0 gets disconnected and goes back to the main lobby.
(I tested on gnu/linux, don't know if crash also happens on windows.)
So 3.8.0 and 3.8.0-beta1 can never be in the same game together, although they can try to join each other and it is very inconvenient for (only) the beta1 side. Is that good enough to keep the 3.8.0 number? If possible, maybe a note can be put into the masterserver message telling beta1 users to upgrade.
