sarah wrote:
Baker I am not using wireless and Dark PLaces does stay connected
Others thought you were using wireless ... I thought you were too.
Well, that changes things quite a bit.
The main differences between classic Quakes (ProQuake, Qrack, etc.) and DarkPlaces:
1) If you have pq_maxfps in ProQuake set too high -- like using a crazy number like 500 or 9999 --- your connection might not be able to handle how often your client is trying to send messages to the server. AFAIK, DarkPlaces probably doesn't have that problem and may limit messages sent.
2) DarkPlaces may not give up so easily on the connection if it is having trouble sending/receiving and may just carry on until a timeout period is hit. The classic engines abort on any failed communication attempt because they must. (DarkPlaces uses what is called "connectionless connections" and can get away with that behavior. Classic Quakes network code uses a "connection" which any failure breaks the connection. This is why if you try connecting to a server ProQuake it has to wait for the server to establish the connection and it takes a split second or 2, but if you try connecting with DarkPlaces there is basically no delay because the client isn't trying to establish a connection. Yes, I know this info is of limited value to almost anyone reading this because it's too technical.)
The above is quite different than the wireless acting up scenario I thought you were experiencing.
So Sgt-Pieface +100