搜索
查看: 7686|回复: 10

关于服务器加速软件booster的设置说明

[复制链接]
发表于 2004-6-4 17:05:49 | 显示全部楼层 |阅读模式 来自 中国–浙江–宁波
我E文不是很好,有人能给份关于服务器加速软件booster的设置说明吗?另外有没有一个设置的标准,比如针对某一档次的服务器booster的参数该如何设置(我的服务器是C4 1.7G+256 ddr333)?谢谢!
发表于 2004-6-4 19:08:53 | 显示全部楼层 来自 中国–广东
本人没有用过,且手头上只有旧版(1.36)的说明:

这里是HL-Booster作者对HL-Booster的功能说明:
* Makes server run with higher fps.
* Makes ping to clients lower.
* Windows and Linux binaries included
也就是
*能让你的HLDS独立服务器运行在更高的FPS(一般是1xx左右,没装时最多9x,第一次安装后我在我的C300A的老爷机上做测试一开始峰值达到200FPS把本帮主吓了一条,不但是妖,而且是非常的妖)
*减低连接到你的服务器的客户的Ping值也就是我们常说的Lag。
*有windows版和linux版。

说到参数,其实用不着做什么修改,用hl-booster的默认值就完全可以胜任了。
这里有hl-booster的参数说明:我大概翻译了一下:

booster_targetfps
设置你想要你的HLDS服务器运行于的FPS值,默认133。注意:不要设抬高,比如像10000之类的,那样的话就好像没有安装过hl-booster一样。另不要在服务器上打开有flash的网页,和用media player之类的东西看视频文件和听音乐(非常消耗CPU)。

booster_maxsysticrate
booster_minsysticrate
这两个实际就是booster_targetfps的一个设定范围最大FPS值(默认500)和最小FPS值(默认100)。

booster_small_connmsg 0或1
设定是否在客户机显示一条连接信息。 默认0不显示。

booster_forcesettings 0或1
设定是否固定booster的设置:如果设置为1,当sys_ticrate或sv_maxupdaterate改变时HL-Booster会把它改会原来应有的值。

HL-Booster还有一个UnderRun的工作模式,在这里就不介绍了,对大多数OP来说没什么用,而最主要的原因是作者在说明文档中写了这两句话:
!NOTE! Not use underrun if you don't know what you're doing!!
!!Bad values in booster_underrun causes server to run even laggier!!
所以只请有兴趣的朋友自己去研究吧。
以下有英文原版说明和更新历史记录:
其中有一条很有趣:
[1.13]
* Jumped over this version (I don't like number 13 :D)
呵呵,老外都信这个。
另,本人制作的这个版本直接安装到你的CS服务器上就可以了,不过前提是你安装过MetaMod。也欢迎各位服务器管理员或者CS脚本爱好者来本人的主页(http://nickcs.yeah.net)下载和讨论(http://nccsbbs.yeah.net)。
最近看了一篇文章深有感触,游戏玩到我们这个份上责任多过娱乐,各位OP的任务:
让各位CSer玩的更好,扫除一切Cheater,Lamper!!

原文:


HL-Booster Metamod Plugin v1.36!

by Jussi Kivilinna <hullu@hullu.cjb.net>

http://hullu.xtragaming.com/

[29.7.2002]


HL-Booster -=- Metamod Plugin
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

* Makes server run with higher fps.
* Makes ping to clients lower.
* Windows and Linux binaries included


INSTALLION
^^^^^^^^^^

1. You need Metamod or Adminmod. (see LINKS)

2. Extract booster_mm.dll and booster_mm.so to your "c:\halflife\moddir\dlls"-folder.

3. Add following two lines to "c:\halflife\moddir\metamod.ini":

win32 dlls/booster_mm.dll
linux dlls/booster_mm.so

If you reinstall Adminmod you have to add this line again!


CVARS
^^^^^
-=- booster_targetfps [default: 133]

Set here fps that you want to hlds run. Note that setting it to 10000
most like wont work ;). If you cannot get server run fast enough try
one of these tricks (windows only):
- Start webpage with flash animation
- Play some video with media player (loop)
- Play some sound file with media player (loop)
For some strange reason hlds gets higher fps counts with these tricks.
Note that hlds is made to run 100fps. Anything else might cause lagging.

Setting this to 0 will deactivate targetfps/sys_ticrate system if you
only want to use underrun mode.


-=- booster_maxsysticrate [default: 500]
Sets maximum sys_ticrate that target-fps system sets


-=- booster_minsysticrate [default: 100]
Sets minimum sys_ticrate that target-fps system sets


-=- booster_small_connmsg [0/1] [default: 0]

If set to 1 plugin shows small one line connection message to clients.


-=- booster_forcesettings [0/1] [default: 0]

If sys_ticrate or sv_maxupdaterate changes to something else that booster
has set then if this cvar is set 1 booster set sys_ticrate/maxupdaterate
to value it should be.


Underrun-help
-=============-

!NOTE! Not use underrun if you don't know what you're doing!!

These values are used to lower bandwidth per player (by lowering
sv_maxupdaterate) after X players have joined.

-=- booster_underrun_on [0/1] [default: 0]

-=- booster_underrun_players [default: 32]

* 0: Activates if more than 0 players on server
* 1: Activates when 2th player joins server
* ..
* 31: Activates when 32th player joins server
* 32: Doesn't activate at all

-=- booster_underrun_finalrate [default: 0]

sv_maxupdaterate gets this value when server is full.


Example (maxplayers 8)
-======================-
* booster_underrun_players is set to 4
* booster_underrun_finalrate is set to 50

4th player joins -- sv_maxupdaterate 100
5th player joins -- sv_maxupdaterate 87.5
6th player joins -- sv_maxupdaterate 75
6th player joins -- sv_maxupdaterate 62.5
8th player joins -- sv_maxupdaterate 50

!!Bad values in booster_underrun causes server to run even laggier!!


HISTORY
^^^^^^^
[1.36]
* Fixed targetfps system to work under linux
* Tested with DoD3 (works fine with me)

[1.35]
* sys_ticrate/targetfps system is now deactivated on listenservers!
* Setting "booster_targetfps 0" deactivates targetfps system (you can still use underrun mode with this)

[1.34]
* Trying to fix XP problems

[1.33]
* targetfps default value is now 133 ;)
* booster_maxsysticrate, booster_mixsysticrate cvars to
set maximum and minimum boundaries for target-fps system
* Small connection message is now default
* booster_underrun_scale changed to booster_underrun_finalrate (thanks to !2SX!)

[1.32]
* Booster's day off.. Sauna & Vodka

[1.31]
* sys_ticrate, sv_maxupdaterate are now visible in server info

[1.30]
* targetfps system for better function with 1.1.0.9

[1.21]
* [bugfix] Fixed (hopefully) current players counting :P

[1.20]
* Shows current map in connection message
* [bugfix] Now underrun even works :D .. fixed current players counting

[1.17]
* [bugfix] rewritten underrun code

[1.16]
* Comes with Linux binary by default (LinHL-Booster)
* Added 'booster_small_connmsg' for those who don't want that big connection message ruin other messages
* Speed tweaks (this was in 1.15 already)
* [bugfix] Underrun works now even if force settings is enabled

[1.15]
* Changed connection message 'made by' to 'plugin-url' so that people stop email-asking me for url ;)

[1.14]
* [bugfix] Removed "meta-interface version mismatch"-warnings

[1.13]
* Jumped over this version (I don't like number 13 :D)

[1.12]
* [bugfix] booster_forcesettings should work right way now.
* [bugfix] booster_underrun should work right way now.
* [bugfix] Current players on server counter function fixed.

[1.11]
* Added 'booster_forcesettings'
* [bugfix] Removed debugging message that I left in 1.10

[1.10]
* Added 'booster_underrun_on', 'booster_underrun_players' and 'booster_underrun_scale' cvars for servers with low bandwidth.

[1.02]
* Shows how many players are present on server to joining player.

[1.01]
* Small code tweaks

[1.00]
* -


CREDITS
^^^^^^^
* -[SBV]-MeGaHuRtZ, Rage, Mikee and all others for betatesting


LINKS
^^^^^
Unitedadmins:
http://unitedadmins.com/

Metamod:
http://www.metamod.org/

Adminmod:
http://www.adminmod.org/
回复

使用道具 举报

 楼主| 发表于 2004-6-4 22:10:36 | 显示全部楼层 来自 中国–浙江–宁波
现在UA上booster最新的版本是2.3.5.0,我把其说明文件贴一下:

Booster MM Plugin v2.35 (Booster)
- by Jussi Kivilinna (hullu) <hullu@hullu.cjb.net>
- CPU management, source code merge and on-going maintenance by BuzzKill <buzzkill@100acrebloodbath.com>

04/12/2004

[INSTALLATION]

1) You need Metamod installed to use Booster2.
2) Extract booster_mm.dll to your "...\<MOD>\addons\booster" folder.
3) Add following line to either "...\<MOD>\metamod.ini" or "...\<MOD>\addons\metamod\plugins.ini":

win32 addons/booster/booster_mm.dll



[CONFIGURATION]

The following cvar settings should be copied to your server.cfg or to booster.cfg (which you then need to 'exec' from server.cfg). By default, these settings will target an FPS of 200 via autofps and a change to the multimedia timer.

// booster_show_connmsg x (0 = disabled, 1 = small message, 2 = large message)
//        Shows a console message to players with booster information when they connect.
booster_show_connmsg 1

// booster_autofps x (x = 0 to 1000, 0 = no target FPS)
//      Automatically changes value of sys_ticrate to achieve and maintain the desired server FPS (if possible).
//        It is not recommended to target FPS greater than 200 or so.
//        Note that autofps adjusts sys_ticrate, which makes it incompatible with any booster_lite_mode other
//        than 3. Setting booster_autofps will force booster_lite_mode to 3.
booster_autofps 200

// booster_minsleepms x (x = 1 to 10, 10 = no change to multimedia timer)
//      This adjusts the multimedia system timer to trick HLDS into sleeping for less time. Note that
//        the lower the value set, the higher the CPU consumption will be for HLDS. Values lower than 3
//        are not recommended, as they can cause massive CPU consumption and/or system instability.
booster_minsleepms 3

// booster_force_systicrate x (x = 0 to 10000, 0 = let Booster2 manage the value itself (no force))
//        Booster2 will force this sys_ticrate value. Note that using this option will set booster_autofps to 0
//        and booster_lite_mode to 3, as these methods rely on a sys_ticrate value untouched by user settings.
//        You should avoid directly setting sys_ticrate in your server.cfg, as manually adjusted values can
//        cause problems with various parts of Booster2.
booster_force_systicrate 0

// booster_cpu_enabled x [0 to 2] (0 = off, 1 = on, 2 = report CPU only - don't actively manage CPU)
//        Booster2 can monitor CPU usage and adjust the multimedia timer to reduce load when necessary
booster_cpu_enabled 0

// booster_cpu_spikemax x
//      If CPU management is enabled, number of times booster_cpu_spikelevel needs
//        to be exceeded in order for mmtimer to increase and CPU load to be reduced.      
booster_cpu_spikemax 3

// booster_cpu_spikelevel x [0 to 100]
//        If CPU management is enabled, level which CPU utilization needs to exceed
//      (booster_cpu_spikemax times) for mmtimer to increase and CPU load to be reduced.
booster_cpu_spikelevel 75

// booster_cpu_floor x [0 to 100]
//        If CPU management is enabled, level which CPU utilization needs to stay under
//      (for booster_cpu_quiettime seconds) for mmtimer to decrease and FPS to increase.
booster_cpu_floor 50

// booster_cpu_mminc x [1 to 10]
//        If CPU management is enabled, amount mmtimer will increment (Booster2 will also decrease
//      the mmtimer by 1 for every 5 minute period that booster_cpu_spikelevel is not exceeded.
booster_cpu_mminc 2

// booster_cpu_quiettime
//        Seconds required without CPU spike exceeding booster_cpu_floor before
//        mmtimer value is decreased by 1.
booster_cpu_quiettime 300

// booster_cpu_mmmin x [1 to 10]
//        If CPU management is enabled, Booster2 will never set the mmtimer below this value.
booster_cpu_mmmin 3

// booster_cpu_mmmax x [1 to 10]
//        If CPU management is enabled, Booster2 will never set the mmtimer above this value.
booster_cpu_mmmax 8

// booster_lite_mode x [0 to 3]
//        Controls how the Booster-Lite approach is implemented:
//        0 - HLDS sleeps 10ms if no network packets are received. If HLDS
//            receives a packet, it stops sleeping. (this mode has been added
//            to provide backward compatibility with how BL v1.00 worked).
//        1 - HLDS attempts to sleep 10ms. If a packet is received,
//            HLDS stops sleeping. Otherwise it attempts to sleep another 10ms.
//        2 - HLDS attempts to sleep 50ms. If a packet is received, it stops sleeping.
//        3 - HLDS will sleep the standard amount (this value turns this feature off).
booster_lite_mode 3
   
// booster_lite_extra_sleep_frequency x
//        Forces HLDS server to sleep x milliseconds even if a packet is received.
//        This setting helps to lower CPU usage.
booster_lite_extra_sleep_frequency 0

// booster_stats_cpu_counter
// Sets the string Booster will use to query cpu performance. By default this is
// "\Processor(_Total)\% Processor Time". Manually set this only if you need to
// support non-english counter names or to query a specific processor.
// This cvar is only used if booster_cpu_enabled is turned on.

// booster_stats_in_counter
// Sets the string Booster will use to query bandwidth in. By default this is
// "\Network Interface(NDIS 5.0 driver)\Bytes Received/sec". Manually set this only
// if you need to support non-english counter names or to query a specific interface.
// This cvar is only used if booster_stats is turned on.

// booster_stats_out_counter
// Sets the string Booster will use to query bandwidth out. By default this is
// "\Network Interface(NDIS 5.0 driver)\Bytes Sent/sec". Manually set this only
// if you need to support non-english counter names or to query a specific interface.
// This cvar is only used if booster_stats is turned on.

// booster_stats [0-1]
// This turns on statistics gathering. This options is not supported. See info at the end
// of the readme regarding this option.

// booster_trigger_cmd
// Sets a command to be executed the first time (during any given map) that CPU consumption
// trips booster_cpu_spikemax. This allows admins to do things such as turn off wallhack
// blocks or other CPU intensive systems under heavy load.
回复

使用道具 举报

发表于 2004-6-4 22:16:40 | 显示全部楼层 来自 中国–北京–北京
好样的,,,DT有你真的很好,,,大家又有幸福了哦  

幸福中......................
回复

使用道具 举报

 楼主| 发表于 2004-6-4 22:18:07 | 显示全部楼层 来自 中国–浙江–宁波
说明文件里“The following cvar settings should be copied to your server.cfg or to booster.cfg (which you then need to 'exec' from server.cfg). ”是否必须把这些设置参数写入server.cfg才可以使得booster正常工作?谢谢斑竹回答
回复

使用道具 举报

匿名  发表于 2004-6-5 13:25:21 来自 Invalid
就是要让这些参数运行,你可以直接把这些参数添到server.cfg;
也可以另外搞个cfg文件,比如booster.cfg,里面加入这些参数,然后在server.cfg里面加上exec booster.cfg。
发表于 2005-2-10 21:04:30 | 显示全部楼层 来自 中国–重庆–重庆
我顶顶顶,BOOTER
回复

使用道具 举报

发表于 2005-2-22 16:48:35 | 显示全部楼层 来自 中国–云南–昆明
我的加速软件出错了
回复

使用道具 举报

发表于 2005-2-23 14:33:45 | 显示全部楼层 来自 中国–广东–佛山
真有性福呀..
回复

使用道具 举报

发表于 2005-4-1 18:08:08 | 显示全部楼层 来自 俄罗斯
我用过以后感觉效果为什么不是特别明显??
回复

使用道具 举报

游客
回复
您需要登录后才可以回帖 登录 | 注个册吧

快速回复 返回顶部 返回列表