|
|
| Line 1: |
Line 1: |
| If TDM does not work properly for you, the best thing to do would be to report the problem.
| | == Introduction == |
| | Doesnt run TDM on your system, when your start TDM and get errors. |
| | There are several ways to analyse these problems. |
|
| |
|
| You are welcome to post in Tech Support section of the [[The_Dark_Mod#Dark_Mod_Forums|forums]], even if you suspect the problem is with your machine or you want to get some help/clarifications.
| | == Creating Logs == |
| When there is clearly a problem with TDM itself, an issue is usually created in the [[The_Dark_Mod#Bugtracker|bugtracker]].
| | one of the ways are creating Logs. |
| But since the bugtracker is a rather technical place, it is more advised to report problems in the forum.
| | TDM places a logfile in his application folder, named darkmod.log. |
| Sooner or later someone will create the issue anyway if it is really needed.
| | This plaintext textfile can be opened with your favorite texteditor. |
|
| |
|
| This article describes some general information typically requested from everyone who reports a problem.
| | 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) |
|
| |
|
| == Baseline ==
| | To start tdm, create a log named, mylog.txt, and quit tdm. |
| | thedarkmod.exe +condump mylog.txt +quit |
|
| |
|
| This pieces of information are almost mandatory:
| | For videoproblems: start tdm, ask for grapicsinfo, save to log and quit |
| | thedarkmod.exe +gfxinfo +condump mylog.txt +quit |
|
| |
|
| # Contents of <tt>darkmod.cfg</tt>.
| | For starting a mission: |
| # Contents of game console at some moment (known as "condump").
| | start tdm, install a mission (for example trainingsmission and quit. |
| # In case of graphical issue, a screenshot showing the problem is often needed.
| | thedarkmod.exe +map training_mission +condump mylog2.txt +quit |
|
| |
|
| Don't worry if you forget to provide any of these bits on the forums: you will soon be asked for them anyway =)
| | To create a log with some arguments and loading a mission |
| | thedarkmod.exe +developer 1 +set logfile 2 +map training_mission |
|
| |
|
| However, when creating an issue on the bugtracker, it is highly desirable to include all of these things, as well as the repro steps.
| | == Log Examples == |
| | | A normal log. |
| === darkmod.cfg ===
| | (going to add a log) |
| | |
| The file named <tt>darkmod.cfg</tt> should be located in the root directory of TDM installation.
| |
| If in doubt, you can locate this directory by checking what executable is run when you start the game: it is in the same directory.
| |
| Let's assume for the rest of the article that root directory is <tt>C:\games\thedarkmod</tt>
| |
| | |
| This file stores the values of all switches and tweaks that player can change.
| |
| The game may work in completely different ways depending on these values, thus they are very important for reproducing the problem.
| |
| | |
| When reporting the problem on forums, you can do one of:
| |
| * Attach it to a forum post. In this case rename it to something like <tt>darkmod_cfg.txt</tt>, the forum forbids anything except txt files.
| |
| * Copy/paste the full contents of the file into the post. In this case, please wrap it into "spoiler" tag, so that readers don't have to always scroll across the 5 pages of it.
| |
| | |
| When reporting on bugtracker, just attach the <tt>darkmod.cfg</tt> file to the issue.
| |
| | |
| === condump ===
| |
| | |
| The term "condump" means all the text written to the game console.
| |
| You can usually open game console by pressing either Tilde(~) key or Ctrl+Alt+Tilde combo.
| |
| | |
| There are two ways to save the contents of game console into a file:
| |
| | |
| :'''1) condump.''' Open game console, type the following and hit Enter: <tt>condump unwrap my_nasty_issue</tt>
| |
| :Then find file named <tt>my_nasty_issue.txt</tt> in <tt>C:\games\thedarkmod</tt> (root TDM directory).
| |
| :Note: execute the command soon after the issue manifests itself.
| |
| | |
| :'''2) logfile.''' Open file <tt>darkmod.cfg</tt> in text editor.
| |
| :Find or create new line containing: <tt>seta logFile "?"</tt>
| |
| :Instead of the question mark, set digit 2 if you experience a crash. Otherwise digit 1 is also OK.
| |
| :Save the file, start TDM and reproduce the issue.
| |
| :Now find the file named <tt>qconsole.log</tt> in the directory of the currently installed FM, for instance in <tt>C:\games\thedarkmod\fms\newjob</tt>.
| |
| | |
| The first approach is better, but it is useless if TDM crashes or you cannot even get into game console.
| |
| In any of these cases, use the second approach.
| |
| | |
| When you have got the file, add it to your report just as you did with <tt>darkmod.cfg</tt>.
| |
| | |
| === Screenshot ===
| |
| | |
| If something looks wrong for you, posting screenshot is a good thing to do.
| |
| Otherwise, the guy who tries to reproduce your issue and fails will have hard time guessing if he sees the same picture as you.
| |
| You can of course try to explain what you see with words, but it is vague and subjective.
| |
| | |
| There are two ways to get a screenshot:
| |
| # Press a key in-game (F12 by default). Then find the screenshot in <tt>C:\games\thedarkmod\screenshots</tt>
| |
| # Ensure that you run game in Windowed mode. Press Print-Screen key to copy screen to clipboard. Start Paint and paste (Ctrl+V) it there. Trim the TDM window in it and save.
| |
| The first approach is preferred, but sometimes it fails to capture the glitch.
| |
| | |
| When you want to share a picture on the forums, you can do one of:
| |
| * Add it as attachment to your forum post.
| |
| * Upload it to some free image hosting, and insert a link to it (click on Image icon) into the post. Surround the link/picture in spoiler tag (unless it is low-resolution) !
| |
| | |
| When reporting on bugtracker, simply attach the file to the issue and mention it somewhere in the text.
| |
| | |
| | |
| == Advanced ==
| |
| | |
| Here a few more advanced tricks which may help debugging issues.
| |
| | |
| === Crashdump ===
| |
| | |
| When TDM crashes, you can record a "memory dump" or "crash dump" of it.
| |
| It often contains information invaluable for coders, but it is only useful for debugging crashes.
| |
| | |
| The article [[Save a Memory Dump for debugging Crashes]] explains in detail how to record it.
| |
| | |
| === Video ===
| |
| | |
| Some graphical issues are very obvious in dynamics, but when you take a still screenshot, it does not capture the tragedy well enough.
| |
| | |
| In such case you can record a video of the problem.
| |
| [https://obsproject.com/ Open Broadcast Software] is a free program which can easily record a high-quality and high-FPS game footage.
| |
| The program is quite complicated, but the main thing you need is to add a "source": either "Game Capture", or "Window Capture", or "Screen Capture".
| |
| | |
| When you have a video, you can either upload it to video hosting (like YouTube) and post a link, or upload it to cloud storage (like google Drive) and post a shared link.
| |
| If you copy/paste a link to YouTube video into a forum post, the forum will show embedded player automatically.
| |
| | |
| === Installation state ===
| |
| | |
| Sometimes there is a chance that your TDM installation is corrupt.
| |
| In such case it is great to give people a brief overview of it.
| |
| | |
| '''TODO''': write some simple way to get good textual representation of TDM installation directory.
| |
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)
