Administrator at 20:36, 5 September 2011

2011-09-05T20:36:43Z

← Older revision		Revision as of 20:36, 5 September 2011
Line 1:		Line 1:


	The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be useful in debugging. This BF2 engine log file can be written to from Python programs by using the <code>host.log(msg)</code> method. Unfortunately, no one seems to know how to turn this logging on right now--maybe it's a command-line option? It's even possible that the debugging features were stripped out of the retail version of the BF2 server, and so the log may be non-existent.		The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be useful in debugging. This BF2 engine log file can be written to from Python programs by using the <code>host.log(msg)</code> method. Unfortunately, no one seems to know how to turn this logging on right now--maybe it's a command-line option? It's even possible that the debugging features were stripped out of the retail version of the BF2 server, and so the log may be non-existent.

Line 11:		Line 9:
	So, why is this any good if <code>host.log</code> is a black hole? Because you can redirect redirect stdout and stderr yourself, to your own log file. . . inside <code>bf2.init_module</code> (in the file <code>Battlefield 2 Server/python/__init__.py</code>, then look for the line that says "<code>def init_module():</code>"), look for the code that reads		So, why is this any good if <code>host.log</code> is a black hole? Because you can redirect redirect stdout and stderr yourself, to your own log file. . . inside <code>bf2.init_module</code> (in the file <code>Battlefield 2 Server/python/__init__.py</code>, then look for the line that says "<code>def init_module():</code>"), look for the code that reads

	<pre> sys.stdout = fake_stream('stdout') sys.stderr = fake_stream('stderr') </pre>		<pre style="white-space: pre-wrap">
			sys.stdout = fake_stream('stdout')
			sys.stderr = fake_stream('stderr')
			</pre>

	and replace it with:		and replace it with:
			<pre style="white-space: pre-wrap">
	<pre> logFile = open('mylogfile.log', 'a') sys.stdout = logFile sys.stderr = logFile </pre>		logFile = open('mylogfile.log', 'a')
			sys.stdout = logFile
			sys.stderr = logFile
			</pre>

	(The <code>'a'</code> means that Python should "append" output to the end of the log file, as opposed to erasing it first). This change will cause anything every error message and the output of every <code>print</code> statement to be routed to the file <code>Battlefield 2 Server/mylogfile.log</code>.		(The <code>'a'</code> means that Python should "append" output to the end of the log file, as opposed to erasing it first). This change will cause anything every error message and the output of every <code>print</code> statement to be routed to the file <code>Battlefield 2 Server/mylogfile.log</code>.

Administrator: Created page with " The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be ..."

2011-09-05T20:31:49Z

Created page with " The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be ..."

New page

The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be useful in debugging. This BF2 engine log file can be written to from Python programs by using the <code>host.log(msg)</code> method. Unfortunately, no one seems to know how to turn this logging on right now--maybe it's a command-line option? It's even possible that the debugging features were stripped out of the retail version of the BF2 server, and so the log may be non-existent.

The core DICE Python code includes a Python debugging feature that sends it's output to the BF2 engine log file via <code>host.log</code>. It does this by redefining the stdout (standard output) and stderr (standard error message) I/O streams so that instead of going to the console (which is basically non-existent for the embedded Python interpreter), they are routed to <code>host.log</code>, where they will be recorded along with any log information from the BF2 engine. Once this redefinition is done, a simple Python <code>print</code> statement will send its output to the log file.

The classes used to accomplish this output redirection are defined in <code>bf2.__init__</code>, but the actual redirection itself doesn't happen until the BF2 engine calls the <code>bf2.init_module()</code>. . . so any <code>print</code> statements executed before this will go nowhere.

In the <code>bf2.__init__</code> module, close to the beginning of the file, is a line that says: <code>g_debug = 0</code>. <code>g_debug</code> serves as a global flag that activates (=1) or deactivates (=0) the printing of debugging information throughout all BF2 Python modules. Throughout the DICE Python code, whenever the program has a bit of information that might be useful in debugging (often just a statement that "we reached this point"), the code checks the value of <code>g_debug</code>, and if it's 1, it prints the debugging information. (If you want to use g_debug as a switch for debugging information from your own modules, be sure to put <code>from bf2 import g_debug</code> in those modules).

So, why is this any good if <code>host.log</code> is a black hole? Because you can redirect redirect stdout and stderr yourself, to your own log file. . . inside <code>bf2.init_module</code> (in the file <code>Battlefield 2 Server/python/__init__.py</code>, then look for the line that says "<code>def init_module():</code>"), look for the code that reads

<pre> sys.stdout = fake_stream('stdout') sys.stderr = fake_stream('stderr') </pre>

and replace it with:

<pre> logFile = open('mylogfile.log', 'a') sys.stdout = logFile sys.stderr = logFile </pre>

(The <code>'a'</code> means that Python should "append" output to the end of the log file, as opposed to erasing it first). This change will cause anything every error message and the output of every <code>print</code> statement to be routed to the file <code>Battlefield 2 Server/mylogfile.log</code>.

You can now use <code>print</code> statements in your own Python code as a way of getting feedback about what's going on in your programming.

IMPORTANT: Because of the way your operating system buffers I/O, you may not see anything in your log file until the <code>stdout</code> and <code>stderr</code> streams are closed or until the operating system's internal buffer is full--which may not happen for quite a while. . . and maybe not until the server is shut down--and even then, your output may vanish completely if the server isn't shutdown in an orderly way. For example, if you are using the server GUI tool available from EA and you push the "Stop" button when the server is running, the server will shutdown abruptly without flushing it's buffers--and you'll find nothing in your log file. To shut the server down gracefully, type the "quit" command into the server's window directly. If you've sent some particularly important information to the log file and you want to insure it gets there, you can use the <code>sys.stdout.flush()</code> method.

NOTE: You can use host.rcon_invoke('echo "..."') to print things directly to the server console.

Debugging - Revision history

Administrator at 20:36, 5 September 2011

Administrator: Created page with " The BF2 engine has some debugging features, one of which is a log file that it can produce during the course of a game that records various pieces of information that would be ..."