Game Development Community

Server and client have different protocoll versions

by AIDan · in Torque Game Engine · 10/27/2001 (10:26 am) · 10 replies

Hi

How could it be?? I use the same version for hosting the game as for joining the game and it does not work.

greetings
Daniel
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner Matthew Shapiro
#1
10/27/2001 (10:33 am)
you using 1.1?
in 1.0 the ports were the same so you would have to change the ports manually so they use different ports. that is also assuming your using the same machine

Torque Owner AIDan
#2
10/27/2001 (10:38 am)
A few days ago, it worked. Both v1.1

Torque Owner Matthew Shapiro
#3
10/27/2001 (10:59 am)
can you not see the server or you try to connect and get an error?

Torque Owner AIDan
#4
10/27/2001 (11:20 am)
He does not list the server and when I try to connect, I get the error. It's the same error it shows while querying the master server.

Torque Owner Matthew Shapiro
#5
10/27/2001 (11:22 am)
what error?

so you get an error when trying to connect to the server and when you query the master?

also remember that it may not be showing up in the master server if the server has a differetn game name (gametype variable in game.cs) and the server is set up as default to look for test app! he changed this recently.

Torque Owner Tim Gift
#6
10/27/2001 (5:24 pm)
I've started bumping up the protocol version numbers as I've been making changes that affect networking (to avoid network errors between different version of the SDK). If the client and server are different, the server won't even show the join server list.

Torque Owner AIDan
#7
10/28/2001 (2:17 am)
I have changed the name back to "Test App", but it still does not work.

Changed in joinServerGui.gui and game.cs

Torque Owner Tim Gift
#8
10/28/2001 (7:57 am)
Let me get this straight... You are running off the same executable? From the same directory? or from two different dirs? Doesn't matter if they say they are the same game version, if you've compiled them a different times, they may have different protocol versions.

Torque Owner AIDan
#9
10/28/2001 (9:04 am)
Compiled and copied
Both have the same version.

Torque Owner Tim Gift
#10
10/29/2001 (9:45 am)
I'm running out of ideas here. The next think would be to actually trace through that connection code in the debugger and see where why you get the error.

The place to set a breakpoint would be on the client in netDispatch.cc, the handleConnectRequest method. After it reads in the packet data, the first thing it checks is the protocol version and sets the reject string if they don't match.