Have you tried dropping in a newer steamclient binary? As far as I'm aware, they're completely backwards compatible with each other (apart from some initialisation functions that I *think* changed at some point).
Kind regards, Saul Rennison On 21 November 2012 16:37, Miles Sutcliffe <[email protected]> wrote: > Hi, > > I'm in the process of butchering the Linux binaries for The Ship. I really > love the game and I am determined to get it working on Linux again. > > So far I've got it talking to the master server. I edited the old server > values of 207.173.177.12/11 to be 208.078.200.65 and .39. I have no idea > why the second octet needs to be set to 078 to get it to translate to 64? > The only reason the 0 is in there is for padding reasons. If someone could > explain this to me that would be great. > > So great, it's up! But insecure. > > Now I want to get it working with VAC. My digging has lead me to believe I > need to edit the steamclient binary and my TCP Dump shows it's going > to 68.142.64.163 on port 27014 from source port 26900 on UDP. I cannot > find > any documentation as to what the current VAC IP address is. > > If anyone could help me out it would be very much appreciated. > > Regards, > > Miles > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
