Debugging TDM systemerrors: Difference between revisions
Restored back original content |
|||
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. | ||
Revision as of 09:48, 3 May 2019
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)