Alright thanks.  My logging attempts have got me nowhere so far bar a
127meg log file with no hits for msg57.   Gonna have to have a few
releases with this logging in place by the looks of it >:(

This request as to Valve : Would it possible for this error not to cause
the client to be dropped unless they were running with -dev or a high
developer cvar setting.  This would allow us to continue tracking down
this bug without whole chunks of one team being dropped at random while
playing.

Ben
The Battle Grounds Lead Programmer

Charlie Cleveland wrote:

We never did figure out why this error was happening, but I did manage to
fix it.  Tom is right, it was happening when a player was kicked off the
server.  The way I fixed it was by removing a UTIL_SayToAll (or whatever
it's called), that was telling everyone that the player was being booted off
the server.  That seemed to fix it, though I have no idea why.  That was
quite awhile ago, and for some unknown reason, this error has seemed to come
back again in a recent playtest build, so I have no idea what's happening.

-Charlie
--
Charlie Cleveland
Game programmer and designer
http://www.natural-selection.org
http://overmind.org


I'm one of NS playtesters, and if Charlie doesn't get
back to you... I do believe it was part of his custom
authentication code for handling the playtesting that
was doing it. If a player who wasn't authenticated to
play joined a server, he could get so far as the
readyroom fine. But if he joined the team, the
authentication would kick him. If I recall correctly,
it was a bug in the authentication process where an
unauthorized player joining would kick everyone.

Tom Grim
aka Elven Thief

--- Ben Banfield <[EMAIL PROTECTED]> wrote:


I have just encountered this bug in the latest
version of bg and am
about to start debugging using the method botman
prescribed in this
thread.  However I'm just wondering what you're
findings were for ns on
this bug.  Was it a special ns message?  Is there
anything I can do to
help narrow this down?  And help is appreciated as I
fear this could be
a long sunday afternoon otherwise :/

Thanks

Ben
The Battle Grounds Lead Programmer

Charlie Cleveland wrote:

We're running some NS playtests under Steam, and


one of the big problems were having is something called a Host_Error. Suddenly, everyone on the server will get kicked off the server, and will be back in their Steam UI. Written to everyone's console is this ominous error message:


Host_Error: UserMsg: Not Present on Client 57

Does anyone have any idea on what might be causing


this, or how to fix it?


-Charlie



_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders



Reply via email to