There seems to be quite a lot of different reasons for this occuring with it
happpening in many mods to everyone on the server at the same time, and also to
individuals with weird routers.
But why is it always UserMsg 57? I think the only person who can answer this is
someone at valve by looking
I think that has been talked about, but mayb not
looked into
Quote from lower down
On Behalf Of Alfred Reynolds
There is no usermsg 57, the engine defined ones stop
at 56 (and mod created ones start at 64). Sounds like
you are corrupting your network steam (by mismatching
what the server sends
There is an interesting thread on thewavelength regarding an error like
this ( usermsg 67 ).
http://forums.thewavelength.net/index.php?showtopic=10455hl=usermsgst=15
It seems to suggest that it isn't about us sending a msg which got
regged with number 57, as that gives a different error (UserMsg:
Humm... call me naive but...
I suggest to create a dummy usermsg 57 that catch and try to fix
network stream corruptions (TCP packets assembling errors?)
A aproach can be to ignore the full frame (posible?).. well.. that its
better than crash or unconnect
Ben Banfield wrote:
There is an
tei wrote:
Humm... call me naive but...
I suggest to create a dummy usermsg 57 that catch and try to fix
network stream corruptions (TCP packets assembling errors?)
A aproach can be to ignore the full frame (posible?).. well.. that its
better than crash or unconnect
As Alfred stated earlier,
Good point and I would agree with you if it was just one mod or even
two. But we're talking about 50% of the 10 top 3rd party mods on steam
(I just searched and saw the specialists have it as well). I also can't
find an occurrence of usermsg 57 before the steam time period. We could
be
Sorry for the double post but I've come off like I'm flaming people and
valve. Thats not what I've been trying to do. I'm simply a bit
exasperated and am just looking for more information to hunt this down
or for this bug to not cause half the clients on the server to quit.
Sorry
Ben
Ben
Ben Banfield wrote:
Sorry for the double post but I've come off like I'm flaming people and
valve. Thats not what I've been trying to do. I'm simply a bit
exasperated and am just looking for more information to hunt this down
or for this bug to not cause half the clients on the server to quit.
When it happens in FA its completely random, it does not discriminate
between teams and such, and no its not always 50% of the players, sometimes
only 3 to 5 on a 28 player server will drop, sometimes 20 will drop. They
all drop at the same time too.
-Cale
-Original Message-
From: [EMAIL
I have this behaviour. I have never seen it drop everyone. This led me
into thinking it could be a pvs/pas message for a while or broadcast as
that goes to unreliable iirc.
50% was me being lazy writing. However, iirc ns drops all however i'm
not sure.
Cale Dunlap wrote:
When it happens in FA
If I recall correctly, yes, everyone on the NS server
dropped. This occured a lot back in the playtesting
when steam started. I'm unsure if Charlie has
determined what caused it, but the last post he made
here mentioning it said that he wasn't 100% sure it
was cleared up.
Unfortunately, I only
11 matches
Mail list logo
