|
|
(11 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
| == Introduction ==
| | If TDM does not work properly for you, the best thing to do would be to report the problem. |
| Doesnt run TDM on your system, when your start TDM and get errors.
| |
| There are several ways to analyse these problems.
| |
|
| |
|
| == Creating Logs ==
| | 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. |
| one of the ways are creating Logs.
| | When there is clearly a problem with TDM itself, an issue is usually created in the [[The_Dark_Mod#Bugtracker|bugtracker]]. |
| TDM places a logfile in his application folder, named darkmod.log. | | But since the bugtracker is a rather technical place, it is more advised to report problems in the forum. |
| This plaintext textfile can be opened with your favorite texteditor.
| | Sooner or later someone will create the issue anyway if it is really needed. |
|
| |
|
| To create a log, open your command prompt (terminal, etc) and navigate to your darkmod folder.
| | This article describes some general information typically requested from everyone who reports a problem. |
| 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.
| | == Baseline == |
| thedarkmod.exe +condump mylog.txt +quit
| |
|
| |
|
| For videoproblems: start tdm, ask for grapicsinfo, save to log and quit
| | This pieces of information are almost mandatory: |
| thedarkmod.exe +gfxinfo +condump mylog.txt +quit
| |
|
| |
|
| For starting a mission:
| | # Contents of <tt>darkmod.cfg</tt>. |
| start tdm, install a mission (for example trainingsmission and quit.
| | # Contents of game console at some moment (known as "condump"). |
| thedarkmod.exe +map training_mission +condump mylog2.txt +quit
| | # In case of graphical issue, a screenshot showing the problem is often needed. |
|
| |
|
| To create a log with some arguments and loading a mission
| | You can omit this information when writing a post on the forums: maybe your issue is trivial and someone will quickly explain what's wrong. |
| thedarkmod.exe +developer 1 +set logfile 2 +map training_mission
| | If it is not obvious, then you will soon be asked for it anyway =) |
|
| |
|
| == Log Examples ==
| | However, when creating an issue on the bugtracker, it is highly desirable to include all of these things, as well as the steps to reproduce. |
| A normal log<code>
| |
| TDM 2.05 #6755 win-x86 Feb 14 2017 09:33:34
| |
| 2694 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 & HTT
| |
| 8096 MB System Memory
| |
| 1024 MB Video Memory
| |
| Winsock Initialized
| |
| Found interface: {22A86CE4-579D-4864-B49F-4BA5E69D8F58} This Killer Ethernet Co
| |
| ntroller connects you to the network. - 0.0.0.0 NULL netmask - skipped
| |
| Found interface: {5F687104-0410-4281-804B-67264ED04AEA} Bluetooth PAN HelpText
| |
| - 0.0.0.0 NULL netmask - skipped
| |
| Found interface: {927EDBFC-40E6-47AF-BAE5-E6E176DF9F7A} VirtualBox Host-Only Et
| |
| hernet Adapter - 192.168.1.40/255.255.255.0
| |
| Found interface: {4CE21EA4-7EA6-4A35-A9FD-553D3F892729} Intel(R) Dual Band Wire
| |
| less-AC 3160 - 192.168.178.26/255.255.255.0
| |
| Found interface: {7B37B022-77CA-4A36-8B0F-E00D9139BA2C} Microsoft Wi-Fi Direct
| |
| Virtual Adapter - 0.0.0.0 NULL netmask - skipped
| |
| Sys_InitNetworking: adding loopback interface
| |
| Found Intel CPU with Hyper-Threading enabled, features: MMX SSE SSE2 SSE3 CMOV
| |
| tdm using MMX & SSE & SSE2 & SSE3 for SIMD processing.
| |
| enabled Flush-To-Zero mode
| |
| enabled Denormals-Are-Zero mode
| |
| ------ Initializing File System ------
| |
| Current search path:
| |
| c:\games\darkmod/
| |
| c:\games\darkmod\tdm_textures_wood01.pk4 (360 files)
| |
| c:\games\darkmod\tdm_textures_window01.pk4 (374 files)
| |
| c:\games\darkmod\tdm_textures_stone_sculpted01.pk4 (451 files)
| |
| c:\games\darkmod\tdm_textures_stone_natural01.pk4 (129 files)
| |
| c:\games\darkmod\tdm_textures_stone_flat01.pk4 (289 files)
| |
| c:\games\darkmod\tdm_textures_stone_cobblestones01.pk4 (224 files)
| |
| c:\games\darkmod\tdm_textures_stone_brick01.pk4 (513 files)
| |
| c:\games\darkmod\tdm_textures_sfx01.pk4 (68 files)
| |
| c:\games\darkmod\tdm_textures_roof01.pk4 (72 files)
| |
| c:\games\darkmod\tdm_textures_plaster01.pk4 (142 files)
| |
| c:\games\darkmod\tdm_textures_paint_paper01.pk4 (63 files)
| |
| c:\games\darkmod\tdm_textures_other01.pk4 (122 files)
| |
| c:\games\darkmod\tdm_textures_nature01.pk4 (275 files)
| |
| c:\games\darkmod\tdm_textures_metal01.pk4 (494 files)
| |
| c:\games\darkmod\tdm_textures_glass01.pk4 (51 files)
| |
| c:\games\darkmod\tdm_textures_fabric01.pk4 (43 files)
| |
| c:\games\darkmod\tdm_textures_door01.pk4 (174 files)
| |
| c:\games\darkmod\tdm_textures_decals01.pk4 (420 files)
| |
| c:\games\darkmod\tdm_textures_carpet01.pk4 (92 files)
| |
| c:\games\darkmod\tdm_textures_base01.pk4 (388 files)
| |
| c:\games\darkmod\tdm_standalone.pk4 (4 files)
| |
| c:\games\darkmod\tdm_sound_vocals_decls01.pk4 (28 files)
| |
| c:\games\darkmod\tdm_sound_vocals07.pk4 (1111 files)
| |
| c:\games\darkmod\tdm_sound_vocals06.pk4 (696 files)
| |
| c:\games\darkmod\tdm_sound_vocals05.pk4 (128 files)
| |
| c:\games\darkmod\tdm_sound_vocals04.pk4 (2872 files)
| |
| c:\games\darkmod\tdm_sound_vocals03.pk4 (743 files)
| |
| c:\games\darkmod\tdm_sound_vocals02.pk4 (1299 files)
| |
| c:\games\darkmod\tdm_sound_vocals01.pk4 (82 files)
| |
| c:\games\darkmod\tdm_sound_sfx02.pk4 (605 files)
| |
| c:\games\darkmod\tdm_sound_sfx01.pk4 (931 files)
| |
| c:\games\darkmod\tdm_sound_ambient_decls01.pk4 (8 files)
| |
| c:\games\darkmod\tdm_sound_ambient03.pk4 (24 files)
| |
| c:\games\darkmod\tdm_sound_ambient02.pk4 (157 files)
| |
| c:\games\darkmod\tdm_sound_ambient01.pk4 (216 files)
| |
| c:\games\darkmod\tdm_prefabs01.pk4 (569 files)
| |
| c:\games\darkmod\tdm_player01.pk4 (125 files)
| |
| c:\games\darkmod\tdm_models_decls01.pk4 (98 files)
| |
| c:\games\darkmod\tdm_models02.pk4 (1948 files)
| |
| c:\games\darkmod\tdm_models01.pk4 (2555 files)
| |
| c:\games\darkmod\tdm_gui_credits01.pk4 (49 files)
| |
| c:\games\darkmod\tdm_gui01.pk4 (694 files)
| |
| c:\games\darkmod\tdm_game02.pk4 (2 files)
| |
| c:\games\darkmod\tdm_game01.pk4 (2 files)
| |
| c:\games\darkmod\tdm_fonts01.pk4 (696 files)
| |
| c:\games\darkmod\tdm_env01.pk4 (152 files)
| |
| c:\games\darkmod\tdm_defs01.pk4 (174 files)
| |
| c:\games\darkmod\tdm_base01.pk4 (172 files)
| |
| c:\games\darkmod\tdm_ai_steambots01.pk4 (24 files)
| |
| c:\games\darkmod\tdm_ai_monsters_spiders01.pk4 (82 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_undead01.pk4 (50 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_townsfolk01.pk4 (95 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_pagans01.pk4 (10 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_nobles01.pk4 (48 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_mages01.pk4 (8 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_heads01.pk4 (97 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_guards01.pk4 (376 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_females01.pk4 (169 files)
| |
| c:\games\darkmod\tdm_ai_humanoid_builders01.pk4 (91 files)
| |
| c:\games\darkmod\tdm_ai_base01.pk4 (8 files)
| |
| c:\games\darkmod\tdm_ai_animals01.pk4 (80 files)
| |
| File System Initialized.
| |
| --------------------------------------
| |
| ----- Initializing Decls -----
| |
| WARNING:file materials/gen_textures_different.mtr, line 82: material 'textures/
| |
| genetic/different/lichtschalter1_d.tga' previously defined at materials/gen_tex
| |
| tures_different.mtr:70
| |
| WARNING:file materials/gen_textures_floor.mtr, line 161: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 169: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 177: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 281: Expecting '{' but foun
| |
| d 'copy_d.tga'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 282: Missing decl name
| |
| WARNING:file materials/gen_textures_floor.mtr, line 377: material 'textures/gen
| |
| etic/floor/PAT0006_grey_blue_d.tga' previously defined at materials/gen_texture
| |
| s_floor.mtr:183
| |
| WARNING:file materials/tdm_epi_shader.mtr, line 425: material 'transformer_gaug
| |
| e' previously defined at materials/tdm_epi_shader.mtr:300
| |
| WARNING:file materials/tdm_epifire_furniture.mtr, line 35: material 'leather_ch
| |
| air_001' previously defined at materials/tdm_epi_shader.mtr:701
| |
| WARNING:file materials/tdm_stone_natural.mtr, line 2065: material 'textures/dar
| |
| kmod/stone/natural/rough_greyblue01' previously defined at materials/tdm_stone_
| |
| flat.mtr:2139
| |
| WARNING:file skins/tdm_gen_metal.skin, line 596: skin 'iron_flat' previously de
| |
| fined at skins/tdm_gen_metal.skin:103
| |
| WARNING:file sound/tdm_ai_commander.sndshd, line 1909: sound 'tdm_ai_commander_
| |
| there_you_are' previously defined at sound/tdm_ai_commander.sndshd:1407
| |
| ------------------------------
| |
| ------- Initializing renderSystem --------
| |
| using ARB renderSystem
| |
| renderSystem initialized.
| |
| --------------------------------------
| |
| I18N: SetLanguage: 'english'.
| |
| I18N: Found no character remapping for english.
| |
| I18N: 1229 strings read from strings/english.lang
| |
| I18N: 'strings/fm/english.lang' not found.
| |
| WARNING:Couldn't load image: guis/assets/splash/launch
| |
| Couldn't open journal files
| |
| Couldn't exec editor.cfg - file does not exist.
| |
| execing default.cfg
| |
| Unknown command 'grayman'
| |
| Unknown command './devel/release/default.cfg.'
| |
| Unknown command 'a'
| |
| Unknown command 'new'
| |
| Unknown command 'NOT'
| |
| Unknown command 'anyone'
| |
| Unknown command 'use'
| |
| Unknown command 'console'
| |
| Unknown command 'next'
| |
| Unknown command 'prev'
| |
| Unknown command 'previous'
| |
| Unknown command 'next'
| |
| Unknown command 'crouch'
| |
| Unknown command 'Lean'
| |
| Unknown command 'lean'
| |
| Unknown command 'Readables'
| |
| Unknown command 'spyglass'
| |
| Unknown command 'compass'
| |
| Unknown command 'lantern'
| |
| Unknown command 'maps'
| |
| Unknown command 'objectives'
| |
| Unknown command 'keys'
| |
| Unknown command 'lockpicks'
| |
| Unknown command 'lean'
| |
| Unknown command 'Inventory'
| |
| Unknown command 'Mantle'
| |
| Unknown command 'creep'
| |
| Unknown command 'frob'
| |
| Unknown command 'inventory'
| |
| execing Darkmod.cfg
| |
| execing autoexec.cfg
| |
| I18N: SetLanguage: 'english'.
| |
| I18N: Found no character remapping for english.
| |
| I18N: 1229 strings read from strings/english.lang
| |
| I18N: 'strings/fm/english.lang' not found.
| |
| ----- Initializing Sound System ------
| |
| sound system initialized.
| |
| --------------------------------------
| |
| ----- R_InitOpenGL -----
| |
| Initializing OpenGL subsystem
| |
| ...getting default gamma ramp: success
| |
| ...registered window class
| |
| ...registered fake window class
| |
| ...initializing QGL
| |
| ...calling LoadLibrary( 'opengl32' ): succeeded
| |
| Couldn't find proc address for: wglBindTexImageARB
| |
| Couldn't find proc address for: wglReleaseTexImageARB
| |
| Couldn't find proc address for: wglSetPbufferAttribARB
| |
| ...created window @ 878,115 (1042x815)
| |
| Initializing OpenGL driver
| |
| ...getting DC: succeeded
| |
| ...creating GL context: succeeded
| |
| ...making context current: succeeded
| |
| Couldn't find proc address for: wglBindTexImageARB
| |
| Couldn't find proc address for: wglReleaseTexImageARB
| |
| Couldn't find proc address for: wglSetPbufferAttribARB
| |
|
| |
|
| ------- Input Initialization -------
| | === darkmod.cfg === |
| Initializing DirectInput...
| |
| mouse: DirectInput initialized.
| |
| keyboard: DirectInput initialized.
| |
| ------------------------------------
| |
| sound: STEREO
| |
| Checking portable OpenGL extensions...
| |
| v - using GL_ARB_multitexture
| |
| v - using GL_ARB_texture_env_combine
| |
| v - using GL_ARB_texture_cube_map
| |
| v - using GL_ARB_texture_env_dot3
| |
| v - using GL_ARB_texture_env_add
| |
| v - using GL_ARB_texture_non_power_of_two
| |
| v - using GL_ARB_texture_compression
| |
| v - using GL_EXT_texture_compression_s3tc
| |
| v - using GL_EXT_texture_filter_anisotropic
| |
| maxTextureAnisotropy: 16.000000
| |
| v - using GL_EXT_texture_lod_bias
| |
| v - using GL_EXT_texture3D
| |
| v - using GL_EXT_stencil_wrap
| |
| v - using glStencilOpSeparate
| |
| X - GL_NV_register_combiners not found
| |
| X - GL_ATI_fragment_shader not found
| |
| X - GL_ATI_text_fragment_shader not found
| |
| v - using GL_ARB_vertex_buffer_object
| |
| v - using GL_ARB_vertex_program
| |
| v - using GL_ARB_fragment_program
| |
| X - EXT_depth_bounds_test not found
| |
| v - using ARB_pixel_buffer_object
| |
| ---------- R_NV20_Init ----------
| |
| Not available.
| |
| ----------- R200_Init -----------
| |
| Not available.
| |
| ---------- R_ARB2_Init ----------
| |
| Available.
| |
| ---------------------------------
| |
| ----- R_ReloadARBPrograms -----
| |
| glprogs/test.vfp
| |
| glprogs/test.vfp
| |
| glprogs/interaction.vfp
| |
| glprogs/interaction.vfp
| |
| glprogs/bumpyEnvironment.vfp
| |
| glprogs/bumpyEnvironment.vfp
| |
| glprogs/ambientLight.vfp
| |
| glprogs/ambientLight.vfp
| |
| glprogs/shadow.vp
| |
| glprogs/R200_interaction.vp
| |
| glprogs/nv20_bumpAndLight.vp
| |
| glprogs/nv20_diffuseColor.vp
| |
| glprogs/nv20_specularColor.vp
| |
| glprogs/nv20_diffuseAndSpecularColor.vp
| |
| glprogs/environment.vfp
| |
| glprogs/environment.vfp
| |
| glprogs/test_direct.vfp
| |
| glprogs/test_direct.vfp
| |
| glprogs/interaction_direct.vfp
| |
| glprogs/interaction_direct.vfp
| |
| glprogs/soft_particle.vfp
| |
| glprogs/soft_particle.vfp
| |
| glprogs/cubic_light_point.vfp
| |
| glprogs/cubic_light_point.vfp
| |
| glprogs/cubic_light_proj.vfp
| |
| glprogs/cubic_light_proj.vfp
| |
| glprogs/test_cubic_light_point.vfp
| |
| glprogs/test_cubic_light_point.vfp
| |
| glprogs/test_cubic_light_proj.vfp
| |
| glprogs/test_cubic_light_proj.vfp
| |
| glprogs/ambient_cubic_light.vfp
| |
| glprogs/ambient_cubic_light.vfp
| |
| -------------------------------
| |
| using ARB_vertex_buffer_object memory
| |
| using ARB2 renderSystem
| |
| Font fonts/english/stone in size 12 not found, using size 24 instead.
| |
| gamex86 - Found DLL in EXE path with timestamp of 1485504986 - c:\games\darkmod
| |
| /gamex86.dll
| |
| gamex86 - Found DLL in pak file with timestamp of 1485504986 - c:\games\darkmod
| |
| \tdm_game01.pk4/gamex86.dll
| |
| gamex86 - DLL in EXE path is newer, ignoring DLL in pak file
| |
| Found Intel CPU with Hyper-Threading enabled, features: MMX SSE SSE2 SSE3 CMOV
| |
| game using MMX & SSE & SSE2 & SSE3 for SIMD processing.
| |
| enabled Flush-To-Zero mode
| |
| enabled Denormals-Are-Zero mode
| |
| --------- Initializing Game ----------
| |
| The Dark Mod 2.05, code revision 6757
| |
| Build date: Jan 15 2017
| |
| WARNING:file materials/gen_textures_different.mtr, line 82: material 'textures/
| |
| genetic/different/lichtschalter1_d.tga' previously defined at materials/gen_tex
| |
| tures_different.mtr:70
| |
| WARNING:file materials/gen_textures_floor.mtr, line 161: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 169: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 177: Expecting '{' but foun
| |
| d '-'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 281: Expecting '{' but foun
| |
| d 'copy_d.tga'
| |
| WARNING:file materials/gen_textures_floor.mtr, line 282: Missing decl name
| |
| WARNING:file materials/gen_textures_floor.mtr, line 377: material 'textures/gen
| |
| etic/floor/PAT0006_grey_blue_d.tga' previously defined at materials/gen_texture
| |
| s_floor.mtr:183
| |
| WARNING:file materials/tdm_epi_shader.mtr, line 425: material 'transformer_gaug
| |
| e' previously defined at materials/tdm_epi_shader.mtr:300
| |
| WARNING:file materials/tdm_epifire_furniture.mtr, line 35: material 'leather_ch
| |
| air_001' previously defined at materials/tdm_epi_shader.mtr:701
| |
| WARNING:file materials/tdm_stone_natural.mtr, line 2065: material 'textures/dar
| |
| kmod/stone/natural/rough_greyblue01' previously defined at materials/tdm_stone_
| |
| flat.mtr:2139
| |
| Initializing event system
| |
| ...833 event definitions
| |
| Initializing class hierarchy
| |
| ...170 classes, 409836 bytes for event callbacks
| |
| Initializing scripts
| |
| Compiled 'tdm_ai_lanternbot::startAlarmWhistle': 93.3 ms
| |
| ---------- Compile stats ----------
| |
|
| |
|
| Memory usage:
| | The file named <tt>darkmod.cfg</tt> should be located in the root directory of TDM installation. |
| Strings: 45, 5552 bytes
| | 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. |
| Statements: 20098, 401960 bytes
| | Let's assume for the rest of the article that root directory is <tt>C:\games\thedarkmod</tt> |
| Functions: 1251, 127656 bytes
| |
| Variables: 92436 bytes
| |
| Mem used: 1118756 bytes
| |
| Static data: 2277552 bytes
| |
| Allocated: 2825316 bytes
| |
| Thread size: 7068 bytes
| |
|
| |
|
| ...6 aas types | | This file stores the values of all switches and tweaks that player can change. |
| game initialized.
| | The game may work in completely different ways depending on these values, thus they are very important for reproducing the problem. |
| --------------------------------------
| | |
| Parsing material files
| | When reporting the problem on forums, you can do one of: |
| Found 0 new mission packages.
| | * 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. |
| Found 6 mods in the FM folder.
| | * 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. |
| WARNING:file c:\games\darkmod\fms\missions.tdminfo, line 3: Cannot find opening
| | |
| brace in file c:\games\darkmod\fms\missions.tdminfo:3.
| | When reporting on bugtracker, just attach the <tt>darkmod.cfg</tt> file to the issue. |
| WARNING:file c:\games\darkmod\fms\missions.tdminfo, line 86: Duplicate mission
| | |
| info declaration found: {
| | === condump === |
| Parsed 17 mission declarations.
| | |
| -------- Initializing Session --------
| | The term "condump" means all the text written to the game console. |
| Font fonts/english/mason_glow in size 12 not found, using size 48 instead.
| | You can usually open game console by pressing either Tilde(~) key or Ctrl+Alt+Tilde combo. |
| Font fonts/english/mason_glow in size 24 not found, using size 48 instead.
| | |
| Font fonts/english/mason in size 12 not found, using size 48 instead.
| | There are two ways to save the contents of game console into a file: |
| Font fonts/english/mason in size 24 not found, using size 48 instead.
| | |
| session initialized
| | :'''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). |
| --- Common Initialization Complete --- | | :Note: execute the command soon after the issue manifests itself. |
| ------------- Warnings --------------- | | |
| during The Dark Mod initialization...
| | :'''2) logfile.''' Open file <tt>darkmod.cfg</tt> in text editor. |
| WARNING:Couldn't load image: guis/assets/splash/launch
| | :Find or create new line containing: <tt>seta logFile "?"</tt> |
| WARNING:file c:\games\darkmod\fms\missions.tdminfo, line 3: Cannot find opening
| | :Instead of the question mark, set digit 2 if you experience a crash. Otherwise digit 1 is also OK. |
| brace in file c:\games\darkmod\fms\missions.tdminfo:3.
| | :Save the file, start TDM and reproduce the issue. |
| WARNING:file c:\games\darkmod\fms\missions.tdminfo, line 86: Duplicate mission
| | :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>. |
| info declaration found: {
| | |
| WARNING:file materials/gen_textures_different.mtr, line 82: material 'textures/
| | The first approach is better, but it is useless if TDM crashes or you cannot even get into game console. |
| genetic/different/lichtschalter1_d.tga' previously defined at materials/gen_tex
| | In any of these cases, use the second approach. |
| tures_different.mtr:70
| | |
| WARNING:file materials/gen_textures_floor.mtr, line 161: Expecting '{' but foun
| | When you have got the file, add it to your report just as you did with <tt>darkmod.cfg</tt>. |
| d '-'
| | |
| WARNING:file materials/gen_textures_floor.mtr, line 169: Expecting '{' but foun
| | === Screenshot === |
| d '-'
| | |
| WARNING:file materials/gen_textures_floor.mtr, line 177: Expecting '{' but foun
| | If something looks wrong for you, posting screenshot is a good thing to do. |
| d '-'
| | Otherwise, the guy who tries to reproduce your issue and fails will have hard time guessing if he sees the same picture as you. |
| WARNING:file materials/gen_textures_floor.mtr, line 281: Expecting '{' but foun
| | You can of course try to explain what you see with words, but it is vague and subjective. |
| d 'copy_d.tga'
| | |
| WARNING:file materials/gen_textures_floor.mtr, line 282: Missing decl name
| | There are two ways to get a screenshot: |
| WARNING:file materials/gen_textures_floor.mtr, line 377: material 'textures/gen
| | # Press a key in-game (F12 by default). Then find the screenshot in <tt>C:\games\thedarkmod\screenshots</tt> |
| etic/floor/PAT0006_grey_blue_d.tga' previously defined at materials/gen_texture
| | # 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. |
| s_floor.mtr:183
| | The first approach is preferred, but sometimes it fails to capture the glitch. |
| WARNING:file materials/tdm_epi_shader.mtr, line 425: material 'transformer_gaug
| | |
| e' previously defined at materials/tdm_epi_shader.mtr:300
| | When you want to share a picture on the forums, you can do one of: |
| WARNING:file materials/tdm_epifire_furniture.mtr, line 35: material 'leather_ch
| | * Add it as attachment to your forum post. |
| air_001' previously defined at materials/tdm_epi_shader.mtr:701
| | * 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) ! |
| WARNING:file materials/tdm_stone_natural.mtr, line 2065: material 'textures/dar
| | |
| kmod/stone/natural/rough_greyblue01' previously defined at materials/tdm_stone_
| | When reporting on bugtracker, simply attach the file to the issue and mention it somewhere in the text. |
| flat.mtr:2139
| | |
| WARNING:file skins/tdm_gen_metal.skin, line 596: skin 'iron_flat' previously de
| | === Coordinates === |
| fined at skins/tdm_gen_metal.skin:103
| | |
| WARNING:file sound/tdm_ai_commander.sndshd, line 1909: sound 'tdm_ai_commander_
| | Typically, a problem happens in-game on at least one of the released fan missions. In such case, please write the name of the FM and the world coordinates where the problem happens. |
| there_you_are' previously defined at sound/tdm_ai_commander.sndshd:1407
| | |
| 15 warnings
| | In order to find world coordinates, execute <tt>getviewpos</tt> in the game console. |
| execing autocommands.cfg
| | The coordinates will be printed in response: the first three are the coordinates, and the last three are the viewing angles. Copy them all to your report. |
| Dumped console text to mylog.txt.
| | Since you cannot copy text directly from the game console, use [[Reporting Problem#condump|one of the methods described above to get a condump]]. |
| </code>
| | In fact, it is a good idea to run <tt>getviewpos</tt> just before creating a condump. |
| | By the way, you can execute <tt>setviewpos</tt> with these six arguments to teleport yourself to this specific location, e.g. to ensure that you have copied coords correctly. |
| | |
| | Alternatively, you can set <tt>tdm_show_viewpos 1</tt> to display current coordinates on screen, so that they can be captured in screenshot. |
| | Or you can call command <tt>screenshot_viewpos</tt> to make a special screenshot with coordinates visible on it. |
| | |
| | == Advanced == |
| | |
| | Here are 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.<br> |
| | Like generating a filelist of the gamefolder.<br> |
| | <br> |
| | To create a filelisting of the TDM gamefolder, in windows 10<br> |
| | |
| | # Open file explorer, navigate to the tdm gamefolder. |
| | # click "file" (menu) > "open in powershell" and a blue window will appear. |
| | # Fill in the following command line in that window and hit the enter-key: dir /s > mytmdfolderandfiles.txt<br>This command generate a textfile in your gamefolder. |
| | # the content of this file mytmdfolderandfiles.txt you can give to people for research. |
| | After this, just run the TDM installer to download the original files. |
| | |
| | '''TODO''': write some simple way to get good textual representation of TDM installation directory. |
If TDM does not work properly for you, the best thing to do would be to report the problem.
You are welcome to post in Tech Support section of the forums, even if you suspect the problem is with your machine or you want to get some help/clarifications.
When there is clearly a problem with TDM itself, an issue is usually created in the bugtracker.
But since the bugtracker is a rather technical place, it is more advised to report problems in the forum.
Sooner or later someone will create the issue anyway if it is really needed.
This article describes some general information typically requested from everyone who reports a problem.
Baseline
This pieces of information are almost mandatory:
- Contents of darkmod.cfg.
- Contents of game console at some moment (known as "condump").
- In case of graphical issue, a screenshot showing the problem is often needed.
You can omit this information when writing a post on the forums: maybe your issue is trivial and someone will quickly explain what's wrong.
If it is not obvious, then you will soon be asked for it anyway =)
However, when creating an issue on the bugtracker, it is highly desirable to include all of these things, as well as the steps to reproduce.
darkmod.cfg
The file named darkmod.cfg 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 C:\games\thedarkmod
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 darkmod_cfg.txt, 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 darkmod.cfg 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: condump unwrap my_nasty_issue
- Then find file named my_nasty_issue.txt in C:\games\thedarkmod (root TDM directory).
- Note: execute the command soon after the issue manifests itself.
- 2) logfile. Open file darkmod.cfg in text editor.
- Find or create new line containing: seta logFile "?"
- 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 qconsole.log in the directory of the currently installed FM, for instance in C:\games\thedarkmod\fms\newjob.
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 darkmod.cfg.
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 C:\games\thedarkmod\screenshots
- 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.
Coordinates
Typically, a problem happens in-game on at least one of the released fan missions. In such case, please write the name of the FM and the world coordinates where the problem happens.
In order to find world coordinates, execute getviewpos in the game console.
The coordinates will be printed in response: the first three are the coordinates, and the last three are the viewing angles. Copy them all to your report.
Since you cannot copy text directly from the game console, use one of the methods described above to get a condump.
In fact, it is a good idea to run getviewpos just before creating a condump.
By the way, you can execute setviewpos with these six arguments to teleport yourself to this specific location, e.g. to ensure that you have copied coords correctly.
Alternatively, you can set tdm_show_viewpos 1 to display current coordinates on screen, so that they can be captured in screenshot.
Or you can call command screenshot_viewpos to make a special screenshot with coordinates visible on it.
Advanced
Here are 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.
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.
Like generating a filelist of the gamefolder.
To create a filelisting of the TDM gamefolder, in windows 10
- Open file explorer, navigate to the tdm gamefolder.
- click "file" (menu) > "open in powershell" and a blue window will appear.
- Fill in the following command line in that window and hit the enter-key: dir /s > mytmdfolderandfiles.txt
This command generate a textfile in your gamefolder.
- the content of this file mytmdfolderandfiles.txt you can give to people for research.
After this, just run the TDM installer to download the original files.
TODO: write some simple way to get good textual representation of TDM installation directory.