ETTV:Server Configuration - Revision history

Bani at 08:36, 25 November 2015

2015-11-25T08:36:23Z

2006-07-30T11:42:49Z

added ettv_netblast 2

2006-07-17T14:03:28Z

Fusen missed a spot :-)

2006-07-16T15:28:25Z

updated to explain the file extensions for windows

2006-05-01T09:21:45Z

‎Miscellaneous

2006-02-07T16:11:00Z

ettv flags is default 3

2005-11-29T09:11:13Z

‎Troubleshooting

2005-11-12T04:51:40Z

‎ETTV Demos

2005-11-11T09:38:55Z

‎ETTV Demos

2005-11-08T09:55:22Z

add chained slave to pic

@@ Line 1: / Line 1: @@
-<dot_graph>
+<graphviz>
 digraph ettv {
 master -> slave1
@@ Line 11: / Line 11: @@
 chained_slave1 -> "...client150"
+}
-</dot_graph>
+</graphviz>
 ==Installation - "Master" (gameserver)==

@@ Line 223: / Line 223: @@
 '''ettv_netblast''' (default 1)
-:by default, ettv tries to send all fragments at once. some networks may handle this badly. setting this to 0 disables. warning: setting this to 0 without increasing ettv_mtu will result in severely laggy slave playback.
+:by default, ettv tries to send all fragments at once. some networks may handle this badly. Possible values are:
 '''ettv_mtu''' (default 1400)

@@ Line 36: / Line 36: @@
 ==Installation - "Slave" (broadcast server)==
-Copy ettv.(x86|exe) to the same directory your etded.x86 is located.
+Copy ettv.(x86|exe) to the same directory your etded.(x86|exe) is located.
 Copy tvgame.mp.i386.(so|dll) to the same directory as your etpro/qagame.mp.i386.(so|dll) is located.
@@ Line 205: / Line 205: @@
 :<tt>echo "524288" > /proc/sys/net/core/rmem_max</tt>
 :<tt>echo "524288" > /proc/sys/net/core/wmem_max</tt>
 FreeBSD can try this:
@@ Line 231: / Line 238: @@
 ===Article Reference===
 (x86|exe) refers to the file extension of the ettv file, for linux use .x86 and for windows use .exe
-(so|.dll) refers to the file extension of the slave file, for linux use .so and for windows use .dll
+(so|dll) refers to the file extension of the slave file, for linux use .so and for windows use .dll
 [[Category:ETTV]]

@@ Line 15: / Line 15: @@
 ==Installation - "Master" (gameserver)==
-Copy ettv.x86 to the same directory your etded.x86 is located.
+Copy ettv.(x86|exe) to the same directory your etded.(x86|exe) is located.
-Start your gameserver as normal, but run ettv.x86 instead of etded.x86.
+Start your gameserver as normal, but run ettv.(x86|exe) instead of etded.(x86|exe).
 ===Set some cvars===
@@ Line 36: / Line 36: @@
 ==Installation - "Slave" (broadcast server)==
-Copy ettv.x86 to the same directory your etded.x86 is located.
+Copy ettv.(x86|exe) to the same directory your etded.x86 is located.
-Copy tvgame.mp.i386.so to the same directory as your etpro/qagame.mp.i386.so is located.
+Copy tvgame.mp.i386.(so|dll) to the same directory as your etpro/qagame.mp.i386.(so|dll) is located.
 ===Set some cvars===
@@ Line 74: / Line 74: @@
 ===Connect the slave===
-Now start your slave server by running ettv.x86
+Now start your slave server by running ettv.(x86|exe)
 Tell the slave server to connect up to the master server:
@@ Line 228: / Line 228: @@
 '''ettv_sv_iptos''' (default 0)
 :same as ettv_tv_iptos, but affects packets for normal ET clients.
 [[Category:ETTV]]

@@ Line 188: / Line 188: @@
 ==Miscellaneous==
+* Slaves may send chats to the master with the command msay
-Slaves may send chats to the master with the command msay
+* Slaves may list players on the master with the command players
 Slaves may list players on the master with the command players
 ==Performance tuning==

@@ Line 26: / Line 26: @@
 :Password for ettv slaves.
 :Must be set, or no slaves will be able to connect!
-'''b_ettv_flags''' (default 1)
+'''b_ettv_flags''' (default 3)
 :1 = prevent slaves from being callvote kicked
 :2 = grant shoutcaster status to slaves

@@ Line 185: / Line 185: @@
 * It is a good idea to keep the master server pk3 list to a minimum.
 * If you are using the autorecord/autoplay feature for running delayed feeds, you will usually want to make sure you clear out the demos directory first. Autorecording will start numbering demofiles using the first available number, so if you have old recorded demos then ettv might start recording from eg demo0017. If your scripts expect to start playback from demo0000 then you might end up broadcasting a game recorded at some earlier date...
 ==Miscellaneous==

@@ Line 123: / Line 123: @@
 ==ETTV Demos==
 You may record the match in progress to a file, with the command:
 :<tt>record <'''demo name'''></tt>
@@ Line 169: / Line 171: @@
 This is essentially the same as delayed feeds above.
 * Configure your server as described in [[ETTV:Server_Configuration#Installation_-_.22Slave.22_.28broadcast_server.29|Slave Installation]] section
-* Obtain the .tv_84 demos and place them in <tt>''fs_game''/demos</tt>
+* Obtain the <tt>.tv_*</tt> demos and place them in <tt>''fs_game''/demos</tt>
-:''note'': ETTV only plays back <tt>.tv_84</tt> files
 * Start the ettv executable with pb disabled
 * <tt>set ettv_autoplay 1</tt> if you want to play back sequential demos named <tt>demo0000.tv_84</tt>, <tt>demo0001.tv_84</tt> etc.

← Older revision		Revision as of 09:38, 11 November 2005
Line 165:		Line 165:

	Automated delayed feeds are supported in ettv beta 8. See the above.		Automated delayed feeds are supported in ettv beta 8. See the above.
		+
		+	===Playing back previously recorded ETTV demos===
		+	This is essentially the same as delayed feeds above.
		+	* Configure your server as described in [[ETTV:Server_Configuration#Installation_-_.22Slave.22_.28broadcast_server.29\|Slave Installation]] section
		+	* Obtain the .tv_84 demos and place them in <tt>''fs_game''/demos</tt>
		+	:''note'': ETTV only plays back <tt>.tv_84</tt> files
		+	* Start the ettv executable with pb disabled
		+	* <tt>set ettv_autoplay 1</tt> if you want to play back sequential demos named <tt>demo0000.tv_84</tt>, <tt>demo0001.tv_84</tt> etc.
		+	* <tt>demo '''<yourdemoname>'''</tt>
		+	* connect a client and enjoy the show!

	==Troubleshooting==		==Troubleshooting==

@@ Line 7: / Line 7: @@
 slave2 -> "client51.."
 slave2 -> "..client100"
+}
 </dot_graph>