Debugging TDM systemerrors - Revision history

Freyk: /* Creating Logs */

2019-07-24T08:27:10Z

Creating Logs

← Older revision		Revision as of 08:27, 24 July 2019
Line 17:		Line 17:
	to		to
	seta logFile "2"		seta logFile "2"
	and save the file.		and save the file.<br>
	After this, start tdm and there will be a file qconsole.log created in the fm folder.		After this, start tdm and there will be a file qconsole.log created in the fm folder.


	==== Creating a log using start-arguments ====		=== Creating a log using start-arguments ===
	open your command prompt (terminal, etc) and navigate to your darkmod folder.		open your command prompt (terminal, etc) and navigate to your darkmod folder.
	From there, call your call tdm executable with several arguments.<br>		From there, call your call tdm executable with several arguments.<br>

2019-07-24T08:26:38Z

← Older revision		Revision as of 08:26, 24 July 2019
Line 4:		Line 4:

	== Creating Logs ==		== Creating Logs ==
	~~one of the~~ ways are ~~creating Logs~~.<br>		There are several ways to create Logs.<br>
	TDM places a logfile in his application folder, named darkmod.log.<br>		All these logs are plaintext textfile that can be opened with your favorite texteditor.<br>
	~~This plaintext textfile can be opened~~ with ~~your favorite texteditor.<br>~~		These known methods are:
			* TDM places a logfile in his application folder, named darkmod.log.<br>
			* Change the logfile setting in the darkmod.cfg.
			* Start tdm with arguments

	~~=== Create a log ===~~		=== Setting the logfile option ===
	~~To create a log, you can change the the logFile-option in the darkmod.cfg or run tdm using start-arguments.<br>~~
	~~The log files can be opened with a texteditor.~~

	==== Setting the logfile option ====
	Open darkmod.cfg in a text editor<br>		Open darkmod.cfg in a text editor<br>
	Change the following line:		Change the following line:
	seta logFile "0"		seta logFile "0"
	to~~<br>~~		to
	seta logFile "2"		seta logFile "2"
	and save the file.		and save the file.

2019-07-24T08:20:53Z

Create a log

@@ Line 8: / Line 8: @@
 This plaintext textfile can be opened with your favorite texteditor.<br>
-== Create a log ==
+=== Create a log ===
-To create a log, open your command prompt (terminal, etc) and navigate to your darkmod folder.
+To create a log, you can change the the logFile-option in the darkmod.cfg or run tdm using start-arguments.<br>
 From there, call your call tdm executable with several arguments.<br>
 <br>

2019-05-03T09:55:03Z

Creating Logs

@@ Line 4: / Line 4: @@
 == Creating Logs ==
-one of the ways are creating Logs.
+one of the ways are creating Logs.<br>
-TDM places a logfile in his application folder, named darkmod.log.
+TDM places a logfile in his application folder, named darkmod.log.<br>
-This plaintext textfile can be opened with your favorite texteditor.
+This plaintext textfile can be opened with your favorite texteditor.<br>
 To create a log, open your command prompt (terminal, etc) and navigate to your darkmod folder.
-From there, call your call tdm executable with several arguments.
+From there, call your call tdm executable with several arguments.<br>
      tdmexecutable +<argument>
 (for the following examples, we use the tdm-executable for windows)

2019-05-03T09:48:16Z

Introduction

← Older revision		Revision as of 09:48, 3 May 2019
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	Doesnt run TDM on your system, when your start TDM and get errors.		Doesnt run TDM on your system, when your start TDM and get errors.<br>
	There are several ways to analyse these problems.		There are several ways to analyse these problems.

2019-03-11T13:35:46Z

Restored back original content

← Older revision		Revision as of 13:35, 11 March 2019
Line 1:		Line 1:
	~~#REDIRECT [[Reporting Problem]]~~		== Introduction ==
			Doesnt run TDM on your system, when your start TDM and get errors.
			There are several ways to analyse these problems.

			== Creating Logs ==
			one of the ways are creating Logs.
			TDM places a logfile in his application folder, named darkmod.log.
			This plaintext textfile can be opened with your favorite texteditor.

			To create a log, open your command prompt (terminal, etc) and navigate to your darkmod folder.
			From there, call your call tdm executable with several arguments.
			tdmexecutable +<argument>
			(for the following examples, we use the tdm-executable for windows)

			To start tdm, create a log named, mylog.txt, and quit tdm.
			thedarkmod.exe +condump mylog.txt +quit

			For videoproblems: start tdm, ask for grapicsinfo, save to log and quit
			thedarkmod.exe +gfxinfo +condump mylog.txt +quit

			For starting a mission:
			start tdm, install a mission (for example trainingsmission and quit.
			thedarkmod.exe +map training_mission +condump mylog2.txt +quit

			To create a log with some arguments and loading a mission
			thedarkmod.exe +developer 1 +set logfile 2 +map training_mission

			== Log Examples ==
			A normal log.
			(going to add a log)

2019-03-06T17:43:19Z

Stgatilov moved page Debugging TDM systemerrors to Reporting Problem: Most of errors being reported are not related to OS.

New page

#REDIRECT [[Reporting Problem]]