From: <no...@so...> - 2001-05-29 18:15:09
|
Bugs item #420236, was updated on 2001-04-30 12:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100882&aid=420236&group_id=882 Category: Networking Group: Minor Status: Open Resolution: None Priority: 5 Submitted By: William Black (psychopheles) Assigned to: Nobody/Anonymous (nobody) Summary: Client disconnect from server problems.. Initial Comment: Version: QF-Client-Win 0.3.0 Running: 733MHz Celeron w/ 64MB RAM, 56K v.90- complaint POS!, Windows Me (Mayhem edition ;). Summary: Seems that when I request QuakeForge to disconnect from a Quakeworld server, it does drop its connection but I do not see a "server disconnect" message. When I try getting back on, however, it takes a while before the server accepts the connection. There has been an instance when I am actually able to reconnect with little delay, but it usually disconnects me with an overflow message, or -- worse -- messages saying I am "back buffered", but allows my connection, only to have it dropped minutes later. The server I am connecting to is a Quakeworld 2.30 server. Perhaps the server needs to switch to Quakeforge? Also, Quakeworld Client has a similar problem, but when I do disconnect I almost always get a message saying (?) "server disconnected". ---------------------------------------------------------------------- Comment By: Adam Olsen (rhamphoryncus) Date: 2001-05-29 11:15 Message: Logged In: YES user_id=12364 I've noticed this too, although I don't know what causes it. The client sends off 3 "drop" messages before it quits, so either those aren't getting sent properly or they're not getting processed by the server. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100882&aid=420236&group_id=882 |