Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 97

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 101

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 109

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 120

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 124

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 132

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 201

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 421

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/class_core.php on line 2384
<br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/archive/global.php</strong> on line <strong>26</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3249</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<meta name="keywords" content="Q3F Server Fundamentals, vbulletin,forum,bbs,discussion,jelsoft,bulletin board" />
	<meta name="description" content="[Archive] Q3F Server Fundamentals Quake Trilogy" />
	
	<title>Q3F Server Fundamentals [Archive]  - Main</title>
	<link rel="stylesheet" type="text/css" href="http://www.gameadmins.com/forums/archive/archive.css" />
</head>
<body>
<div class="pagebody">
<div id="navbar"><a href="../index.php/">Main</a> &gt; <a href="f-25.html">GameAdmins.com</a> &gt; <a href="f-4.html">Server Setup Forums</a> &gt; <a href="f-12.html">Quake Trilogy</a> &gt; Q3F Server Fundamentals</div>
<hr />
<div class="pda"><a href="?pda=1" rel="nofollow">PDA</a></div>
<p class="largefont">View Full Version : <a href="http://www.gameadmins.com/forums/showthread.php?t=1415">Q3F Server Fundamentals</a></p>
<hr />

<div class="post"><div class="posttop"><div class="username">Stager</div><div class="date">01/24/01, 11:56 pm</div></div><div class="posttext">I haven't seen hardware requirements for running a Q3F server. From my experience below it seems that the number of nodes a server can successfully operate is directly related to the hardware. What am I missing, or what upgrades do I need???<br />
<br />
I have a machine sitting outside our Firewall (for outside-the-Firewall-testing purposes) that I can run a dedicated server on. To me an NT4SP6 400MHz Celeron w/128MB machine on a T1 should be able to handle 20 nodes, right? Well, a configuration of 18 public and 2 private nodes produces an unplayable environment - with only a single connected client! Symptoms are the frequently recurring &quot;unplugged&quot; network icon and 100 pings sporadically exceeding 1000... (unplayable)<br />
<br />
I did all kinds of tweaking - RWIN/MTU (via dslreports.com suggestions), fresh OS and SP6 install, killed unnecessary services, latest NIC drivers (3C905B-TX at 10Mb), hunkmegs from 36 to 96 (wasn't sure which way was correct for a server environment). The only positive results achieved occured when I decreased the nodes to 12 or 10.<br />
<br />
Any ideas anyone?</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Dekard</div><div class="date">01/25/01, 07:08 am</div></div><div class="posttext">Whats your sv_maxrate set too? Try lowering it to about 7000-8000 will probably make it much better if it's not set there already.</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Stager</div><div class="date">01/25/01, 12:32 pm</div></div><div class="posttext">Thanks for the advice.<br />
<br />
sv_maxRate is set to 8000<br />
<br />
I will try a setting of 7000</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Stager</div><div class="date">01/25/01, 12:54 pm</div></div><div class="posttext">I just did some checking into the sv_maxRate setting and found this:<br />
<br />
New Updates to version 1.16j<br />
----------------------------<br />
The Auto-download rate is controlled by 'sv_maxRate', specify this value in bytes per second. The maximum band rate caps out around 25K per second.<br />
----------------------------<br />
<br />
Since I've disabled map downloading (sv_allowdownload 0), I've now set sv_maxRate to 0.</div></div><hr />


<div id="copyright">vBulletin&reg; v3.6.9, Copyright &copy;2000-2012, Jelsoft Enterprises Ltd.</div>
</div>
</body>
</html>