You either need to lower the number of players on the server, kill other programs that are using CPU, or get a faster machine to run the server. If you are running the server and see "long server frame" messages, it probably means your CPU is drowning. Note that you could do: set autoexec "exec /myconfig.cfg" to have it run a cfg file in the game/ directory after running autoexec.cfg, so you don't have to put all the settings on the command line The autoexec cvar is a special cvar we added that is evaluated after autoexec.cfg is run, so you can override settings in autoexec.cfg using that variable. If you want to pass in things on the command line that will be evaluated after the game has finished starting up, you can do the following: silverback.exe set autoexec "command here" It is ALWAYS safe to put the variable settings in autoexec.cfg.Ĭommands you pass in on the command line will be run right after startup.cfg is loaded, far before many variables have been registered. autoexec.cfg is loaded after everything has been initialized, so all the variables are sure to exist at this point. Here's a general rule for setting variables in Savage: svr_ variables are in the core engine, and usually it's fine to put them in startup.cfg sv_ variables are in the game code, and they should be put in autoexec.cfg in the game/ directory. You have about 30 chars that display in the client. To set the name of the server, you want to set the svr_name cvar to the name you want to appear.
You can set the maximum number of clients by setting the svr_maxclients cvar either on the command line (like silverback.exe set svr_maxclients 16), or in a file called startup.cfg in your Savage directory (or in ~/.savage/ if you are running a Linux server). We run 48 player servers on a 1 GHz P3 easily though, and it uses around 50-80% cpu. CPU usage will be inconsistent, but it might spike high if people are doing a lot of shots against buildings (which does per-poly collision tests). The server will probably never use more than 90 megs of ram, it doesn't really grow much with players, so ram shouldn't be an issue on servers. Incoming bandwidth is usually around 1-4 kilobytes/sec per player. So a 32-player game will use up to about 500 kbytes / sec. If a player is using the DSL/LAN settings (most are), they will suck down between 8 and 15 kilobytes / sec.
Savage servers take a fair amount of uploading bandwidth. In Linux, to run a dedicated server you run.
#SAVAGE XR LAN SERVER 64 PLAYERS WINDOWS#
To run a Windows dedicated server, just run dedicated_server.bat.
1.6 Administering Your Server Remotely:.
0 kommentar(er)
