Win-hlbooster 2.40

жмем спасибо

какой смысл в 1000 fps на сервере? пинг все равно не от этого зависит, все зависит от типа и качества линии, booster сводит пинг к минимальному значению

ping это время затраченное на передачу пакета от клиента к серверу и обратно, измеряется в миллисекундах

booster_show_connmsg 1
booster_autofps 1000
booster_minsleepms 0
booster_force_systicrate 10000
booster_cpu_enabled 1
booster_cpu_spikemax 3
booster_cpu_spikelevel 75
booster_cpu_mminc 2

booster_show_connmsg 1 // Показывать информацию игрокам о Booster при их подключении к серверу (0 = не показывать, 1 = маленькое сообщение, 2 = большой сообщение)
booster_autofps 1000 // Автоматическое изменение значение команды sys_ticrate и управлением FPS сервера. (X = значение от 0 до 1000) Настройки booster_autofps требует значение booster_lite_mode 3.
booster_minsleepms 1 // Что-то связано с CPU. По-моему спящий режим для HLDS. (x = от 1 до 10)
booster_force_systicrate 0 // Управление значением sys_ticrate. Использование этой опции установит booster_autofps в 0 и booster_lite_mode в 3. Настройте sys_ticrate в server.cfg. (x = 0 до 10000)
booster_cpu_enabled 1 // Booster монитор CPU. Может понижать нагрузку, когда требуется. (0 = выключить, 1 = включить, 2 = сообщать CPU, но н еуправлять им)
booster_cpu_spikemax 3 // Управляет CPU.
booster_cpu_spikelevel 75 // Управляет CPU.
booster_cpu_floor 50 // Управляет CPU.
booster_cpu_mminc 2 // Управляет CPU. (x = от 1 до 10)
booster_cpu_quiettime 300 // По-моему время в секундах, когда без CPU используется booster_cpu_floor.
booster_cpu_mmmin 3 // Управляет CPU. (x = от 1 до 10)
booster_cpu_mmmax 8 // Управляет CPU. (x = от 1 до 10)
booster_lite_mode 3 // Управление Booster-ом.
booster_lite_extra_sleep_frequency 0 // Управляет HLDS сервером, устанавливая его в спящий режим, когда получает пакеты. Понижает загрузку на процессор.

Народ,плиз помогите)))Как включить Booster?

// 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 1000

// 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 1

// 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 10000

// 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 1

// 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 1

// 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 95

// 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 1

// 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