The DarkMod Wiki - User contributions [en]

IdTech4 Open Source

2011-12-30T17:48:26Z

New Horizon:

id Software has a long history making the code to their engines open source after a while. Even after being sold to Zenimax, this trend continued. The source code can be found [ftp://ftp.idsoftware.com/idstuff/source/ on the officiel FTP server] from id software.

So there is hope that idTech4 (the engine behind Doom 3 and Quake 4) will also be open sourced. For The Dark Mod this means that we can fix a long list of issues that are currently not possible.

Here is a small, incomplete list, in no particular order:

{|class="wikitable sortable" border=1 cellspacing=0 cellpadding=2 width=100%

|-
!bgcolor=#d0d0e0 width="10%"|Category
!bgcolor=#d0d0e0|Issue
!bgcolor=#d0d0e0|Possible outcome

|-
|Sound
|EAX does not work under Linux.
|Works there, too.

|-
|Sound
|Vis-portals do not diminish sound while opened.
|Open vis-portals would also diminish sound. Sound loss would scale with the size of the portal up to a certain size, where it would then be large enough to have not require sound loss.

|-
|Graphic
|The lightgem needs to render to a texture and transfer this texture back to the CPU via a complicated in-memory file scheme.
|Performance increase.

|-
|Graphic
|No instancing. Multiple instances of the same model are all rendered one by one, instead of uploading it once and then telling the graphic card to render them all in one go.
|Performance increase.

|-
|Graphic
|No access to the Z-Buffer. Without access to this data, any depth-based fragment shader effects like SSAO or Depth of Field require an extremely expensive z-pass render.
|Performance increase. More effect options.

|-
|Coding
|Single-threaded coding. It may be possible to divide the sub-systems into separate execution threads for processing on separate cores once the source code is available. The game Prey has implemented this type of change to Id Tech 4. On the extreme side of this concept, OpenCL could be used to perform AI path-finding, or physics calculations.
|Performance increase.

|-
|Graphic
|Shadow Volumes are calculated on the CPU. Moving to a GPU calculated Shadow Volume or a Shadow Mapping technique like Parallel Split Variance Shadow Maps would allow more on-screen geometry with active lighting applied. Soft shadows would also be MUCH less expensive than the current Z-Buffer render and Post-Process method.
|Performance increase. Higher poly-counts. More active lights. Soft shadows.

|-
|Graphic
|No access to Vertex positions. For vertex shader or geometry shader (DX10+ hardware) operations like R2VB, Vertex Texturing or Tessellation the correct Vertex locations will be needed. Fur shaders would also be possible...
|Performance increase, Fur shaders, Higher poly-counts.

|-
|Mapping
|Brushes cannot have Vertex Colors or Vertex Normals. Adding these attributes would give Brushes near feature parity with Models and allow for more seamless mixtures of the two construction methods. Brushes could have Patch style smoothing and curves yet could be properly scissored by a Visportal. Translucency could be applied to Brush-work prefabs.
|Performance. Ease of use for mappers.

|-
|Graphic
|Support for Light-Maps or Deluxe-Maps. While static lighting methods are not really an ideal usage for this engine, these features can have their utility. You could bake ambient bounced lights for areas that are predominantly statically lit. To make these methods more Doom 3 compatible, these could be implemented as an Ambient Light (3D texture support?) as a more robust extension of the Strombine method that is currently available (but very cumbersome). Maps made in other engines (without game specific assets) could be more easily migrated?
|Performance increase. Graphic enhancement. Migrated content?

|-
|Graphic
|LATC2 Normal Map compression support (AKA OpenGL 3Dc) See: http://www.opengl.org/registry/specs/EXT/texture_compression_latc.txt ... Reduced Normal Map memory requirements both on the storage volume and in graphic RAM.
|Performance increase. Graphic enhancement. Bigger maps for less RAM.

|-
|Graphic
|Local Cubemaps. (See HL2 env_cubemap.) Granting the ability to have reflective materials more accurately reflect their environment. It may be possible to setup scripted material fades (shaderparm?) to implement this with the current SDK framework but it would be yet another CPU dependent operation. The Skin changing in the LOD system could also be used perhaps? This one is definitely questionable about ''requiring'' Open Source, but is may be beneficial to set this up in the renderer.
|More accurate reflective materials. Gold loot (etc).

|-
|Animation
|GPU Skinning. Having the GPU stretch and transform the mesh would be tremendous performance enhancement for animations and would allow for extremely detailed facial animations like Team Fortress 2.
|Better animations. Performance Increase.

|-
|GUI
|Font rendering is buggy (only alpha map, [http://bugs.angua.at/view.php?id=2812 misses character 0xFF], no Unicode etc.).
|Better looking GUI and easier translations.

|-
|GUI
|The GUI is 4:3 (640x480), but covers always the entire screen and is thus [http://bugs.angua.at/view.php?id=2703 distorted on 16:9].
|GUI looks better on 16:9 and on multi-monitor setups.

|-
|GUI
|Language support (via ''''sys_lang'''') is limited to a fixed set of languages. Also the GUI refues to use non-ASCII strings for choices or values.
|Unicode support, better i18n support and UI translateable to more languages.

|-
|Sound
|Determine why "no_dups" doesn't always work and correct it. Remove the SDK workaround for this problem.
|Better sound randomization.

|-
|Entities
|Correct the occasional bad "trace" the engine performs.
|Eliminate spatial relationship problems.

|-
|Mapping
|Eliminate as many hard-coded limits as possible.
|Reduce mapper frustration.

|-
|Coding
|Grant the ability to create NEW material keywords
|Allow per-material effects that do not require every surface to include the keyword stage. Example: Fur Shaders, Anisotropic Material, etc.

|-
|Graphic
|Add the ability to have multiple dynamic LightFalloffImage stages
|Use ''Texture Sheets'' to render multiple light passes and maximize the work allocated to each light render. (Less waste.) Animated light texture effects can have all 3 axis of movement.

|-
|Graphic
|Add keywords for Cubemap light method and 3D texture light methods
|Extend the Doom 3 light method to more projection types without the need to replace or upgrade existing maps and assets.
|}

== See also ==

* [ftp://ftp.idsoftware.com/idstuff/source/ FTP Server from id software]
* [http://www.thedarkmod.com/downloads.php Download the source code for TDM]
* [http://www.doom3world.org/phpbb2/viewtopic.php?t=23491 Doom3world Wish List for Open Source Doom 3]
* [http://www.humus.name/index.php?page=3D&&start=0 Humus Demo's. Many useful graphic techniques that would require access to the renderer]

{{coding}}

What's new in TDM 1.06

2011-06-19T11:58:27Z

New Horizon: /* GUI */

See also the changelog on our bugtracker page: [http://bugs.angua.at/changelog_page.php?version_id=52 Changelog]
{{released|1.06|2011-06-19}}

== Changes / Features / Issues fixed ==

* [http://bugs.angua.at/view.php?id=541 #541]: AI should turn on lights while searching nearby (AI) (grayman)
* [http://bugs.angua.at/view.php?id=1623 #1623]: AI don't notice lights going out in front of them (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2133 #2133]: Add random tips to loading screen (GUI) (Springheel)
* [http://bugs.angua.at/view.php?id=2202 #2202]: Campaign Support (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2264 #2264]: Need a persistent data structure to store info between multiple maps (Coding) (greebo)
* [http://bugs.angua.at/view.php?id=2449 #2449]: Torch-carriers need pain modification (AI) (Springheel)
* [http://bugs.angua.at/view.php?id=2457 #2457]: Special search animations for torch-bearers (Animation) (Springheel)
* [http://bugs.angua.at/view.php?id=2518 #2518]: Mac OS X Support (Design/Coding) (greebo)
* [http://bugs.angua.at/view.php?id=2603 #2603]: AI do not play "notice_lights" bark (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2613 #2613]: Add more aspect ratios (Coding) (tels)
* [http://bugs.angua.at/view.php?id=2620 #2620]: Add alarm bark (Sound) (Springheel)
* [http://bugs.angua.at/view.php?id=2655 #2655]: Werebeast crawler can cause damage above his height (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2704 #2704]: model models/darkmod/loot/coins/coin_pile.lwo has too many verts for a poly (Models) (Springheel)
* [http://bugs.angua.at/view.php?id=2715 #2715]: Add option to switch off main menu background music (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2717 #2717]: An AI can think he's reached a goal that's on the floor above him (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2723 #2723]: tdm_update's differential updater leaves a corrupt tdm_game02.pk4 (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2728 #2728]: Rats interfering with AI movement (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2731 #2731]: AI playing default footsteps on straw mat? (Sound) (Springheel)
* [http://bugs.angua.at/view.php?id=2732 #2732]: AI leaves one of locked double doors unlocked (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2734 #2734]: Inaccurate AAS data can lead to a hang. (Coding) (grayman)
* [http://bugs.angua.at/view.php?id=2739 #2739]: Some stim/responses are being overwritten by others (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2740 #2740]: AI weapons sometimes cause bad pathfinding (AI) (grayman)
* [http://bugs.angua.at/view.php?id=2744 #2744]: Still getting "Cannot find attachment X to destroy" error (Coding) (greebo)
* [http://bugs.angua.at/view.php?id=2746 #2746]: "Wait until Ready" GUI to be displayed when the mission is ready to start (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2747 #2747]: Crashes after a "Doom 3 Blue Window" type of game shutdown (Coding) (greebo)
* [http://bugs.angua.at/view.php?id=2748 #2748]: Add lighting animations to female characters (AI) (Springheel)
* [http://bugs.angua.at/view.php?id=2750 #2750]: In-Game Downloader stops when switching pages (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2751 #2751]: Stale download progress info when requeing downloads (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2757 #2757]: Downloaded missions don't appear until full restart (GUI) (greebo)
* [http://bugs.angua.at/view.php?id=2762 #2762]: New path_corner type: "Follow this Actor" (AI) (greebo)
* [http://bugs.angua.at/view.php?id=2767 #2767]: Savegame Compression (Coding) (stgatilov)
* [http://bugs.angua.at/view.php?id=2768 #2768]: More portable lightgem - getting rid of named pipe / shared memory (Coding) (stgatilov & JC Denton)
* [http://bugs.angua.at/view.php?id=2774 #2774]: Restart Mission crashes after saving and dying when a weapon is drawn (Coding) (greebo)

== Campaign Support ==

* Maps can now be strung together to make multi-mission [[Setting_up_Campaigns | Campaigns]].

A number of new Campaign specific systems have be built.

* Multiple Briefings
* Multiple Briefing Videos
* De-Briefing Videos
* Conditional Objectives that span missions
* Inventory and Loot management for mult-mission setup

== OSX Support ==

* This will be the first Dark Mod release to officially ship with a Mac OSX binary.

{{clear}}

== Animations ==

* A dozen new animations added, including eat_carrot, sit_talk_gesture (x3), bang_door, walk_alert_torch, sit_turnpage, idle_ponder, and lift_skirt (Springheel)

== AI ==

* AI can now be made to notice whether specific lights have been extinguished or "switched off" and will now [[Relighting_Lights | RELIGHT]] them.
* AI can now be made to follow behind other (Leader) AI with an easier spawnarg method.

== GUI ==

* In fixing #2613 a new CVAR "r_fovRatio" was added (Tels), this defines the ratio between X and Y FOV and can be used setup arbitrary wide-screen or multi-monitor resolutions:

:[[Image:Fov_16_10.jpg|340px|FOV 16:10 on 1920x600]] [[Image:Fov_32_10.jpg|340px|FOV 32:10 on 1920x600 (TDM v1.06)]]

* The menu supports now a couple more resolutions ('''1360x768''', '''1600x900''', etc.) and two more aspect ratios ('''5:4''' and '''16:9 TV''') (Tels)

* The menu supports an optional bow aimer(Dram, New Horizon)

{{clear}}

== Savegames ==

* Savegames are now compressed on-the-fly, which reduces their size further by a factor of 2..4 depending on the mission. For example, saving at the start of "Heart" yielded '''85 Mbyte with v1.03''', '''11 Mbyte with v1.04''' and will yield '''2.5 Mbyte with v1.06'''. (stgatilov)

== Entities ==

* New character head (Springheel)
* New hanging wheel chandelier model (Springheel)
* New door handle model (Springheel)
* New AI characters: Builder Forger / Engineer/ BlackSmith (Springheel)
* New AI characters: Inventor Scientist / Gentleman scientist (Springheel)

== Textures ==

* New scattered paper decals x3 (Springheel)

{{whatsnew|sort=194}}

Virtual Darkness

2011-04-12T16:08:16Z

New Horizon: /* Ambient Light */

''written by Fidcal''

'''Note:''' The '''[[Location Settings]]''' article shows you an easy-to-use and general system to get different ambient light levels and colors for each location/zone the player is in. Since this system also covers different ambient sounds and script calls at zone boundaries, you should really use it.

This article here is just a general introduction into "ambient light settings".

==Introduction==

Being a stealth game system and as its name implies, most Dark Mod missions will take place at night and require darkness as cover. Generally, absolute blackness is unpopular in this type of game and is not recommended. It can make navigation difficult, uncomfortable, and gives an impoverished visual display. Instead, very low ambient light is used to represent blackness. We call this virtual darkness. This main ambient light should not be so dark that the player cannot make out some detail of nearby surfaces textures. Yet because it represents complete darkness it should not be so light that it seems strange that in-game characters cannot see you (see later.)

Ambient light can be coloured to provide atmosphere and realism depending on the environment.

== Brightness Standard ==

From Release 1, The Dark Mod includes a test map (may be included in a trainer mission.) for both players and mappers to standardise their gamma and brightness settings. I emphasise that this does '''not''' force all missions to be the exact same brightness. What it does is provide a standard setting so everyone can know what a particular mission is intended to look like. If a player then prefers to generally have their settings darker or brighter then at least they know. Likewise, if a mapper wants to produce a darker or brighter mission then they are free to do so but at least they will not do it without knowing. The advantages of all this is that in most cases players will not have to keep fiddling with the brightness setting for every individual mission.

==Ambient Light==

Unlike normal lights, ambient light does not by default fade to the edge of its radius but is the same constant brightness throughout. Rich variation of fading or patterning can be introduced with a light texture. For general use, ambientLightnfo is recommended as it has no patterning and so its brightness is consistent throughout its volume. Regard it as the one to use by default.

The main ambient light '''ambient_world''' illuminates the player like a regular light. If you're using the recommended '''low level of 6''', there should only be a negligible effect. The AI characters will not see the player too easily, the lightgem will provide a bonus for crouching, and thus complete darkness is simulated without blinding the player.

Mappers are not bound to an ambient_world of 6 though, higher settings are possible. Settings of 7 or 8 are not all that visually different from a setting of 6 to the player though, so a player might find that the AI are reacting too quickly, and spotting the player far too easily...even though it feels like they are lit the same as they were in the previous mission with a 6 ambient_world. In these cases, a '''lightgem_offset''' can be placed on a piece of '''worldspawn''' to offset the lightgem and bring balance back to the gameplay. For an '''ambient_world''' setting of 7, a lightgem_adjust seting of '''-1''' should be sufficient. For ambient_world of 8, a lightgem_adjust of '''-1.5'''. If a mapper wanted to go as high as an ambient_world of 9, a lightgem_adjust of -2 would be required. Ambient_world of 10 and above should not be offset as this is entering a realm where the brightness is not believable for hiding.

Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.

==Virtual Ambient Light==

All lights in Dark Mod are dynamic, real-time, having the potential to vary in-game and cast shadows. Naturally this affects performance and having too many lights close together is likely to reduce frame rates so care must be taken. This applies to the main ambient light too which naturally covers all surfaces.

To improve performance on some low-end systems, Dark Mod textures can simulate the main ambient light. This feature pre-calculates how much textures should be illuminated once only instead of continuously during gameplay. Players can select either method so those with faster machines can use the true ambient light which gives better quality.

==Enabling Virtual Ambient Light==

All that mappers need to do to allow players to select virtual ambient light is to name their main ambient light '''"ambient_world"'''. That's it. If the player selects this feature then Dark Mod takes the color/brightness values of that light and passes it to all the textures then switches off that ambient light. It is therefore important for mappers to do this to provide the best performance for players with slower machines.

Note: Some special materials have a background texture plus detail that is only visible with a real ambient light, for example, darkmod/stone/sculpted/corpse. The mapper can place normal lights or local ambient light for those surfaces where possible or leave them with their background texture.

== See also ==

* The [[Location Settings]] article.

{{tutorial-lighting}}

Virtual Darkness

2011-04-12T14:07:53Z

New Horizon: /* Ambient Light */

''written by Fidcal''

'''Note:''' The '''[[Location Settings]]''' article shows you an easy-to-use and general system to get different ambient light levels and colors for each location/zone the player is in. Since this system also covers different ambient sounds and script calls at zone boundaries, you should really use it.

This article here is just a general introduction into "ambient light settings".

==Introduction==

Being a stealth game system and as its name implies, most Dark Mod missions will take place at night and require darkness as cover. Generally, absolute blackness is unpopular in this type of game and is not recommended. It can make navigation difficult, uncomfortable, and gives an impoverished visual display. Instead, very low ambient light is used to represent blackness. We call this virtual darkness. This main ambient light should not be so dark that the player cannot make out some detail of nearby surfaces textures. Yet because it represents complete darkness it should not be so light that it seems strange that in-game characters cannot see you (see later.)

Ambient light can be coloured to provide atmosphere and realism depending on the environment.

== Brightness Standard ==

From Release 1, The Dark Mod includes a test map (may be included in a trainer mission.) for both players and mappers to standardise their gamma and brightness settings. I emphasise that this does '''not''' force all missions to be the exact same brightness. What it does is provide a standard setting so everyone can know what a particular mission is intended to look like. If a player then prefers to generally have their settings darker or brighter then at least they know. Likewise, if a mapper wants to produce a darker or brighter mission then they are free to do so but at least they will not do it without knowing. The advantages of all this is that in most cases players will not have to keep fiddling with the brightness setting for every individual mission.

==Ambient Light==

Unlike normal lights, ambient light does not by default fade to the edge of its radius but is the same constant brightness throughout. Rich variation of fading or patterning can be introduced with a light texture. For general use, ambientLightnfo is recommended as it has no patterning and so its brightness is consistent throughout its volume. Regard it as the one to use by default.

The main ambient light (ambient_world)illuminates the player like a regular light. If you're using the recommended low level of 6, there should only be a negligible effect. The AI characters should not see the player very easily, the lightgem should still provide a bonus for crouching, and thus complete darkness is simulated without blinding the player.

Mappers are not bound to an ambient_world of 6...higher settings are possible, but when using settings of 7, 8, or 9 a mapper might find that the AI are reacting too quickly, and spotting the player far too easily. In these cases, a lightgem_offset can be placed on a piece of worldspawn to offset the lightgem and balance the gameplay. For an ambient_world setting of 7, a lightgem_adjust seting of -1 should be sufficient. For ambient_world of 8, a lightgem_adjust of -1.5, and finally for ambient_world of 9, a lightgem_adjust of -2. Ambient_world of 10 and above should not be offset as this is entering a realm where the brightness is not believable.

Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.

==Virtual Ambient Light==

All lights in Dark Mod are dynamic, real-time, having the potential to vary in-game and cast shadows. Naturally this affects performance and having too many lights close together is likely to reduce frame rates so care must be taken. This applies to the main ambient light too which naturally covers all surfaces.

To improve performance on some low-end systems, Dark Mod textures can simulate the main ambient light. This feature pre-calculates how much textures should be illuminated once only instead of continuously during gameplay. Players can select either method so those with faster machines can use the true ambient light which gives better quality.

==Enabling Virtual Ambient Light==

All that mappers need to do to allow players to select virtual ambient light is to name their main ambient light '''"ambient_world"'''. That's it. If the player selects this feature then Dark Mod takes the color/brightness values of that light and passes it to all the textures then switches off that ambient light. It is therefore important for mappers to do this to provide the best performance for players with slower machines.

Note: Some special materials have a background texture plus detail that is only visible with a real ambient light, for example, darkmod/stone/sculpted/corpse. The mapper can place normal lights or local ambient light for those surfaces where possible or leave them with their background texture.

== See also ==

* The [[Location Settings]] article.

{{tutorial-lighting}}

Virtual Darkness

2011-04-11T21:36:55Z

New Horizon: /* Ambient Light */

''written by Fidcal''

'''Note:''' The '''[[Location Settings]]''' article shows you an easy-to-use and general system to get different ambient light levels and colors for each location/zone the player is in. Since this system also covers different ambient sounds and script calls at zone boundaries, you should really use it.

This article here is just a general introduction into "ambient light settings".

==Introduction==

Being a stealth game system and as its name implies, most Dark Mod missions will take place at night and require darkness as cover. Generally, absolute blackness is unpopular in this type of game and is not recommended. It can make navigation difficult, uncomfortable, and gives an impoverished visual display. Instead, very low ambient light is used to represent blackness. We call this virtual darkness. This main ambient light should not be so dark that the player cannot make out some detail of nearby surfaces textures. Yet because it represents complete darkness it should not be so light that it seems strange that in-game characters cannot see you (see later.)

Ambient light can be coloured to provide atmosphere and realism depending on the environment.

== Brightness Standard ==

From Release 1, The Dark Mod includes a test map (may be included in a trainer mission.) for both players and mappers to standardise their gamma and brightness settings. I emphasise that this does '''not''' force all missions to be the exact same brightness. What it does is provide a standard setting so everyone can know what a particular mission is intended to look like. If a player then prefers to generally have their settings darker or brighter then at least they know. Likewise, if a mapper wants to produce a darker or brighter mission then they are free to do so but at least they will not do it without knowing. The advantages of all this is that in most cases players will not have to keep fiddling with the brightness setting for every individual mission.

==Ambient Light==

The main ambient light does illuminate the player but if kept to the recommended low levels (5,6, 7, or 8) this should a negligible amount in which AI characters cannot see the player and thus represents complete darkness without blinding the player. If you find that an ambient_world level of 6 or 7 is causing higher alerts than you care for in your map, then set a lightgem_adjust on a piece of worldspawn to offset the ambient_world by a small amount. A seting of -1 should be sufficient.

Unlike normal lights, ambient light does not by default fade to the edge of its radius but is the same constant brightness throughout. Rich variation of fading or patterning can be introduced with a light texture. For general use, ambientLightnfo is recommended as it has no patterning and so its brightness is consistent throughout its volume. Regard it as the one to use by default.

Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.

==Virtual Ambient Light==

All lights in Dark Mod are dynamic, real-time, having the potential to vary in-game and cast shadows. Naturally this affects performance and having too many lights close together is likely to reduce frame rates so care must be taken. This applies to the main ambient light too which naturally covers all surfaces.

To improve performance on some low-end systems, Dark Mod textures can simulate the main ambient light. This feature pre-calculates how much textures should be illuminated once only instead of continuously during gameplay. Players can select either method so those with faster machines can use the true ambient light which gives better quality.

==Enabling Virtual Ambient Light==

All that mappers need to do to allow players to select virtual ambient light is to name their main ambient light '''"ambient_world"'''. That's it. If the player selects this feature then Dark Mod takes the color/brightness values of that light and passes it to all the textures then switches off that ambient light. It is therefore important for mappers to do this to provide the best performance for players with slower machines.

Note: Some special materials have a background texture plus detail that is only visible with a real ambient light, for example, darkmod/stone/sculpted/corpse. The mapper can place normal lights or local ambient light for those surfaces where possible or leave them with their background texture.

== See also ==

* The [[Location Settings]] article.

{{tutorial-lighting}}

What's new in TDM 1.03

2010-12-22T12:37:43Z

New Horizon: /* GUI */

See also the changelog on our bugtracker page: [http://bugs.angua.at/changelog_page.php?version_id=43 Changelog].

== Release Date ==
Version 1.03 of The Dark Mod has been released on December 22nd, 2010.

== Changes / Features / Issues fixed ==

* [http://bugs.angua.at/view.php?id=837 #837]: Arrows don't stick into attachments on living AI (Coding)
* [http://bugs.angua.at/view.php?id=1181 #1181]: When mantling onto a moving object the mantle process is stationary, often the object is long gone (Coding)
* [http://bugs.angua.at/view.php?id=1254 #1254]: Cannot see objectives or why failed after mission end (GUI)
* [http://bugs.angua.at/view.php?id=1421 #1421]: Arrows can stick in broken arrows (Physics)
* [http://bugs.angua.at/view.php?id=1422 #1422]: Arrows can stick in arrows sticking in AI (Physics)
* [http://bugs.angua.at/view.php?id=1697 #1697]: AI errors when alerted by melee damage (AI)
* [http://bugs.angua.at/view.php?id=1851 #1851]: Bug when "using" AI with "shoulderable" set to "0". (Coding)
* [http://bugs.angua.at/view.php?id=1960 #1960]: No error message when failing to install FM package (GUI)
* [http://bugs.angua.at/view.php?id=2065 #2065]: Discarding articles when sorting Missions in the "New Mission"-menu (GUI)
* [http://bugs.angua.at/view.php?id=2169 #2169]: Strange AI behaviour/death when underwater (Coding)
* [http://bugs.angua.at/view.php?id=2198 #2198]: Finish "reaction" soundshaders (Sound)
* [http://bugs.angua.at/view.php?id=2210 #2210]: Savegame trying to restore Doom3 objectiveSystem (Saving/Loading)
* [http://bugs.angua.at/view.php?id=2218 #2218]: "idle_animations_torso" causes crash (Coding)
* [http://bugs.angua.at/view.php?id=2225 #2225]: path_anim won't work without an "angle" property (Coding)
* [http://bugs.angua.at/view.php?id=2226 #2226]: Lanternbots turn invisible when slain (Coding)
* [http://bugs.angua.at/view.php?id=2229 #2229]: Conversations only playing once (Coding)
* [http://bugs.angua.at/view.php?id=2234 #2234]: Weapon scrolling broken (Coding)
* [http://bugs.angua.at/view.php?id=2236 #2236]: atdm:ai_townsfolk_commoner_armed def vocal set typo (Def / Setup)
* [http://bugs.angua.at/view.php?id=2237 #2237]: Need generic text guis for signs etc (Feature proposal)
* [http://bugs.angua.at/view.php?id=2241 #2241]: gameLocal.m_StimTimer is not cleared between maps (Coding)
* [http://bugs.angua.at/view.php?id=2242 #2242]: Stim/Response Code Cleanup (Coding)
* [http://bugs.angua.at/view.php?id=2243 #2243]: Crash in func_shooter entity when def_projectile is wrong (Coding)
* [http://bugs.angua.at/view.php?id=2244 #2244]: Invalid tokens in ASE files (errors in NAHT) (Script/Def)
* [http://bugs.angua.at/view.php?id=2255 #2255]: New Mission menu GUI improvements. (GUI)
* [http://bugs.angua.at/view.php?id=2257 #2257]: Curtain prefab and fabrics (Textures)
* [http://bugs.angua.at/view.php?id=2258 #2258]: Climbing chains sounds like rope (Coding)
* [http://bugs.angua.at/view.php?id=2260 #2260]: Easier override option for main menu music (GUI)
* [http://bugs.angua.at/view.php?id=2261 #2261]: in 16:9 aspect resolutions, 1280x720 and 1366x768 are reversed (GUI)
* [http://bugs.angua.at/view.php?id=2262 #2262]: Restart Game button for settings menu (GUI)
* [http://bugs.angua.at/view.php?id=2265 #2265]: Console commands to mark missions as played/completed (Coding)
* [http://bugs.angua.at/view.php?id=2268 #2268]: No need to extract startingmap.txt file from mission PK4 (Coding)
* [http://bugs.angua.at/view.php?id=2269 #2269]: Response Effect Knockout not working (Script/Def)
* [http://bugs.angua.at/view.php?id=2269 #2270]: Ambient music volume levels (Sound system)
* [http://bugs.angua.at/view.php?id=2280 #2280]: Mission version check is bound to fail on next major version (GUI)
* [http://bugs.angua.at/view.php?id=2281 #2281]: No physics for dropped pickpocketed objects (Physics)
* [http://bugs.angua.at/view.php?id=2287 #2287]: no_random_headturning Not Working (Animation)
* [http://bugs.angua.at/view.php?id=2308 #2308]: Mission Download Manager (Coding)
* [http://bugs.angua.at/view.php?id=2309 #2309]: Support for replace_anim_* spawnargs directly on AI (Coding)
* [http://bugs.angua.at/view.php?id=2319 #2319]: Bump tdm_lg_crouch_modifier to -2 (Coding)
* [http://bugs.angua.at/view.php?id=2324 #2324]: Water should decrease visibility: add Lightgem modifier (Coding)
* [http://bugs.angua.at/view.php?id=2326 #2326]: Location settings broken if player enters undefined area (Coding)
* [http://bugs.angua.at/view.php?id=2337 #2337]: Add a falloff to the dynamic ambient light (Coding)
* [http://bugs.angua.at/view.php?id=2342 #2341]: "No_dups" not working for vocal barks (Sound engine)
* [http://bugs.angua.at/view.php?id=2342 #2342]: idRotator reverses direction each time it is triggered (Coding)
* [http://bugs.angua.at/view.php?id=2343 #2343]: Split Action/Inventoy menu and add keybinds for Spyglass/Cycle Readables (GUI)
* [http://bugs.angua.at/view.php?id=2344 #2344]: Elevator button double firing (Def / Setup)
* [http://bugs.angua.at/view.php?id=2352 #2352]: Arrows stick into player head (Coding)
* [http://bugs.angua.at/view.php?id=2362 #2362]: Water texture/wobble is too fast (Coding)
* [http://bugs.angua.at/view.php?id=2369 #2369]: Horse - skins (Graphis)
* [http://bugs.angua.at/view.php?id=2377 #2377]: Add Sotha's skybox decals (Textures/Materials)
* [http://bugs.angua.at/view.php?id=2379 #2379]: New golden Ingots as loot items (Models)
* [http://bugs.angua.at/view.php?id=2380 #2380]: CObjectiveLocation doesn't recognize absence of deleted entities. (Design/Coding)
* [http://bugs.angua.at/view.php?id=2385 #2385]: AI playing cards: some sit_down_angles unusable (AI)
* [http://bugs.angua.at/view.php?id=2392 #2392]: Patrolling AI get up immediately after path_sleep (AI)
* [http://bugs.angua.at/view.php?id=2396 #2396]: Add the Bloom settings to the menu (GUI)
* [http://bugs.angua.at/view.php?id=2408 #2408]: Sleepers "seeing" bodies (AI)
* [http://bugs.angua.at/view.php?id=2414 #2414]: Problems caused by interleaved thinking (AI)
* [http://bugs.angua.at/view.php?id=2417 #2417]: Ambient sounds lost after loading (Coding)
* [http://bugs.angua.at/view.php?id=2424 #2424]: Click in menu causes game action (Coding/GUI)
* [http://bugs.angua.at/view.php?id=2426 #2426]: TDM Updater improvements (Coding)
* [http://bugs.angua.at/view.php?id=2430 #2430]: If shouldered entity is removed from game, stuck shouldering forever (Coding)
* [http://bugs.angua.at/view.php?id=2438 #2438]: Norman shield texture error (Textures)
* [http://bugs.angua.at/view.php?id=2440 #2440]: Unlit electric lights not switchable (stay dark) (Coding)
* [http://bugs.angua.at/view.php?id=2443 #2443]: Sconscript deprecation warnings (Design/Coding)
* [http://bugs.angua.at/view.php?id=2446 #2446]: Double check spider death animation (AI)
* [http://bugs.angua.at/view.php?id=2450 #2450]: Unknown Pause before Purchase Menu (GUI)
* [http://bugs.angua.at/view.php?id=2458 #2458]: Test female sleeping behaviour (Animation)
* [http://bugs.angua.at/view.php?id=2461 #2461]: Black wheelbarrow (Models)
* [http://bugs.angua.at/view.php?id=2465 #2465]: Wench eyes not closing when asleep (Animation)



== AI ==

* Spiders have been significantly upgraded: all-new animations (including death animation), new spider types, new behavior (ceiling hang) and quieter footsteps
* Three new female characters: noblewoman, wench, and rogue. [http://modetwo.net/darkmod/index.php?/topic/11535-new-female-characters/]
* New animations for female characters
* Lowered volume of zombie foot-drag (again)
* Implemented run animation for characters with weapons (so they don't stab their head while running)
* New "Werebeast" monster added
* several varied pain animations
* Horse AI

== GUI ==

* A "Restart game" button now in the "Settings menu" (Greebo)
* The "New mission" menu has been greatly improved and has new features like tracking which mission(s) you played before, how long it took etc. (Greebo)
* Built-in version check, so TDM can tell you when an update is available. (Greebo)
* The "Actions/Inventory" menu has been split into "Actions" and "Inventory" (Tels). This makes room for:
** It is now possible to bind keys for "Spyglass" and "Cycle Readables" from the menu (Tels)
* The "Video Settings" menu has been split into "General" and "Advanced" (New Horizon). This makes room for:
* Three ambient methods (New Horizon):
** '''Simple''' (our original texture based ambient)
** '''Normal''' (uses interaction shader to calculate ambient),
** '''Enhanced''' (JC's enhanced texture based ambient),

== Sounds ==
* <s>Added a new Builder vocal set -- the Strong Builder</s> -- Postponed -- (Mortem Desino)
* Added two new vocal sets: "Wench" and "Lady"
* AI no longer play the same vocal bark twice in a row, and play a wider range of vocals (you should notice quite a change!)
* several footstep sounds have been modified
* ambient sound will no longer be lost on reloading
* AI vocals have been adjusted to allow for better ability to determine direction of the sound

== Textures/Skins ==

* A new yellow skin for the lily model has been added (Tels)
* Yellow and brown skins for our grass, as well as a dense and a ''colored'' variant of these has been added (Tels)
* Grass skins can now be used on all bush models, turning them into grass or plants with long leaves.
* It is possible to set a list of skins, from which one will be chosen '''randomly''' at entity spawn time, see: [[random_skin]]
* A few building/tree skybox facade textures (Sotha)
* Copper clad roof texture and old oxidised copper texture, good for statue skins (Serpentine)
* Two higher res loose stone wall textures (Seperntine)
* The red-shingles-with-stripes texture has now twice the resolution and much better details (Arcturus)
* New ladder variants with sounds for chain, foliage (ivy) rope, metal, nosound (silent)

{|
|-
|[[Image:Three lilies.jpg|200px|Three lilies]]
|[[Image:grass_skins.jpg|200px|Grass variants]]
|}

== Models ==

* Aphrodite statue (Arcturus)
* New carrot stub/turnip stub (Baddcog) and moveables/eaten versions based on them
* Gold bar model with various sizes (Fidcal & Greebo)
* a few new [[LOD]] models, which are considerable simpler (and thus render faster) than their originals

{|
|-
|[[Image:Eaten.jpg|200px|Eaten carrot and turnip]]
|[[Image:Ingame side by side.jpg|200px|Left: LOD, Right: Original]]
|[[Image:Lily_after_colorcorrect.png|200px|Left: LOD, Right: Original]]
|}

== Physics ==

Formerly, mantling (jump, grab ledge, then pull yourself up) only worked for stationary or moving (translating) objects. Ishtvan now implemented mantling onto rotating objects, too. This [http://www.youtube.com/watch?v=EMyHMeuikc8 video] demonstrates nicely the effect and possibilities. Btw, the map is called [http://thedarkmod.com/fmdetails.php?id=33 Swing] and is a contest map that confines the player into a 1280x1280 (unlimited height) cube, and if you watch the video, you will see that the map certainly feels way bigger. A clever trick :)

== Code ==

'''id Software''' had the habit to add a small class for almost each feature needed, instead of combining the features into one class. This leads to situation where one entity can do X, the next can do Y, but none can do X and Y at the same time. Before we only added code to the code base, and fixed bugs. With v1.03 we also
started an effort on C++ code cleanup. That means:

* combining features into one spawnclass instead of distributing it over or duplicating it at several
* removing unnec. classes (idFuncRadioChatter, idDoor, idElevator, idTarget_EnableStamina, idAFEntity_ClawFourFingers, anything related to the PDA, idTarget_Tip etc.)
* adding small utility functions (like ToString() to the idBounds class)
* improving the performance of idlib classes (the idList class has seen improvements upon adding another list to it, f.i.)
* We also no longer include and use some AI scripts from the base,working towards our goal of a D3-free TDM

This is ongoing work, but it will contribute to making TDM better overall, in small steps.

{{whatsnew}}

Performance Tweaks

2010-10-06T12:31:11Z

New Horizon: /* The game is very slow! */

This article relates to performance issues ''for players''. For performance information ''for mappers'', see [[Performance: Essential Must-Knows]]

== Show FPS ==

First, you can check how many {{abbr|FPS|frames per second}} are achieved by opening the console with {{key|Ctrl}}+{{key|Alt}}+{{key|~}} (tilde, {{key|^}} on German keyboards) and type:

com_showFPS 1

== Optimizing the performance ==

=== Stop running programs in the background ===

Programs running in the background might either eat up memory that is needed for Doom3, and thus cause swapping to the hard disk, or they might consume CPU time or other resources. This can cause either general slowdowns or ''hickups'' during game play.

=== Run Doom3 in fullscreen ===

Running Doom3 in windowed mode might be quite a bit slower than fullscreen mode.

=== Reduce your resolution! ===

On older cards, Doom3's render engine is very expensive for every per pixel drawn, and reducing the resolution will help the most. For instance, at 1600x1200 the game needs to draw '''four times''' as many pixels as when running 800x600. The result with 800x600 will not look as bad as one might think – but the frame rate improvements might make it much more playable.

If you cannot set the resolution you want in the settings menu then enter it in doomconfig.cfg.

To edit doomconfig.cfg:

* Uninstall any current mission in the New Mission menu.
* Close Dark Mod
* Edit doomconfig.cfg in the darkmod folder
* Re-install the mission.
* Whenever you UNinstall and install another mission, these changes will migrate to those FMs as well.

(Alternatively, edit both the doomconfig in the darkmod folder AND the one in the current FM game folder, eg, doom3\chalice.)

Search down for these cvars first and replace them with the values shown:

seta r_mode "-1"
seta r_customHeight "640"
seta r_customWidth "480"

=== Set the ambient shading to "Faster" ===

(Not valid for '''Thief's Den demo''')

Inside the settings, change the ambient rendering method to "Faster".

=== Set the interaction.vfp to 'Standard' ===

(Not valid for '''Thief's Den''' demo.)
In the video settings menu, change the interaction shader to Standard. Ambient lighting will not look as good, but you may gain a few frames per second.

== The game is '''very''' slow! ==

If you get less than 10 FPS, or the game even stutters, please try this:

Look into your '''DoomConfig.cfg''' inside your <tt>saintlucia</tt> or <tt>thiefsden</tt> folder and check that the following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "1"
seta image_preload "1"
</pre>

=== Image downsizing ===

As a last resort, you may enable image downsizing: at the console, set '''image_downSize''' to '''1''' and then set a limit with '''image_downSizeLimit''', e.g., '''"image_downSizeLimit" "256"'''. This reduces texture memory requirements and may completely alleviate hard drive thrashing. There are similar cvars for bump and specular maps as well.
'''Note: This may result in very blurry briefing and menu screens.'''

===Drop in Frame Rates when Viewing Water===

Some players have reported a drastic drop in performance when an agitated water surface is in view. This on a Radeon card. Try entering this in the console. It disables the water visible surface effects but at least it might let you play normally...

set r_skipPostProcess "1"

==Blurry Briefing and Menu Screens==

If you get blurry briefing and menu screens then in DoomConfig.cfg make sure you do NOT have image_downSize 0. Instead set it to 1. But see also [[#Image downsizing]]

==Field of View Decrease==

'''Note''' that this setting might occasionally produce odd effects such as a grabbed object seems to move a little on release.

You can get a performance improvement if you decrease the field of view. By default this is 90 degrees but you might try entering in the console or in your doomconfig.cfg...

g_fov 85

In addition, if you are playing a mission that is too good to miss and reach a very low performance area which is almost unplayable on your machine, you might consider setting the field of view extremely low temporarily to get you through then restore to 90 later...

g_fov 50

Note from Fidcal: I have played comfortably on g_fov 75 and even think perhaps it makes nearby objects more realistically close so you can get right up to a table, etc. Not noticed any problem with restricted view.

== Player Shadow==

The player shadow slightly reduces performance. It has no game effect at all (not seen by AI for instance) apart from atmospheric effect so if you want to disable it enter in the console:

g_showplayershadow 0

Or, in doomconfig (see above) change the following line from "1" to "0":

seta g_showplayershadow "0"

== Player Lantern Shadow==

You may notice a drop in performance while using the player lantern.

Add "noshadows" "1" to entitydef light_lantern_moving in tdm_playertools_lantern.def and this stops the player lantern casting shadows. This helps improve performance slightly when using the lantern.

==Gameplay Performance Tips==

If you have done everything else you can and performance is still poor then one or two things you might do in game to help:

* Close all doors after you have passed through. Generally the game has to process both areas until you close the door if the doorway is still in sight.
* Kill or KO every AI you can. You might not like to play that way but generally, AI still hog resources even out of sight (depending on how set up in the game.)
* Avoid alerts. A dozen guards searching for you will really slow things down on a low-end machine.
* Try to look down at the ground when moving along. Gazing up at a grand vista will slow you down. Best to do your gazing while standing still.

== Last resort: Upgrade your hardware ==

Modern games need a lot of computing power, and while you don't need the absolutely newest hardware to play them, upgrading single components of your machine can help tremendously:

* If you got '''less than 2 GByte''' main memory, consider upgrading your memory. This really helps to reduce swapping, which introduces quite noticeable slowdowns.
* If you got a graphic card from NVidia older than the GF 7x00 series, consider upgrading it.

Upgrading your CPU will be quite complicated and the cost might be so sadly high that you could rather buy a new complete computer. Upgrading the hard disk will usually not help much with gaming, unless you are running out of free space.

== See also ==

See also the [[FAQ]].

{{installation}}

FAQ

2010-10-06T12:29:43Z

New Horizon: /* The game is very slow! */

{{important|headline=Important|text=This FAQ relates to the full TDM release version only. For players of the pre-release demos such as '''[[Thief's Den]]''' and '''[[Saint_Lucia|Tears of Saint Lucia]]''' please refer to the '''[[FAQ (Demo Releases)|Demo FAQ]]'''.'''}}

== What Doom versions are supported? ==

=== Can I use the Demo version of Doom 3? ===

No, sorry.

=== Does it run with the Steam version of Doom 3? ===

Yes :) You need to install the mod into the directory where Steam put Doom3, this might be under:

C:\Program Files\Steam\steamapps\common\doom 3

or a similiar folder.

'''Important:''' Create a shortcut on your desktop and set it to the following:

steam.exe -applaunch 9050 +set fs_game_base darkmod

This ensures that when you start Steam, it will launch TDM and not Doom 3 without TDM.

== Patching Doom 3 to verson 1.3.1.1304 ==

=== How can I check whether my Doom 3 is correctly patched? ===

Open Doom 3 and hit {{key|Ctrl}}+{{key|Alt}}+{{key|~}} (tilde, {{key|^}} on German keyboards) to open the console. You'll see the version printed in the lower left corner of the console. It should read '''1.3.1.1304'''. If your version is ending on 1302, you've got the wrong patch installed.

=== Where can I get the right patch? ===

We have the patch hosted on our FTP. See the [[Installation]] article to find a link to it.

If you have version 1.3.1.1302, you may need to uninstall and reinstall before patch 1.3.1.1304 will let you apply it.

=== What's that issue with the 1.3.1 patch? ===

When the 1.3.1 patch was released by Id, they released it a bit too early. Some download sites picked it up quite fast though and started to distribute it. The problem is, that Id replaced that patch with a different one, and, probably thinking that it hadn't spread yet, didn't bother to change the version number. However, you can still find "wrong" 1.3.1 patches and these will not work with the mod. That's why it is important to check the version number in the console to make sure that the right 1.3.1 patch is installed if the mod doesn't work. The link provided here on our own page points to the correct patch, so if you downloaded it from here you don't need to worry about it.

== Supported Operating Systems ==

=== Which Windows versions can I use? ===

The following versions of windows have been tested and are known to work : Windows 2000, Windows XP, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2003 in both 32bit and 64bit flavours.

=== Does it run in Linux? ===
Yes, Linux is supported.

=== Does it run in 64 Bit Linux? ===
Yes, Linux 64 bit is supported. In addition to the steps above, you need 32 bit compatibility libraries, since Doom3 is 32 bit only:
* On '''SuSE''', they should be included.
* On Ubuntu/Kubuntu, install the package '''ia32'''.

For TDM after 1.0, this step should be '''no''' longer neccessary:

* Since you cannot install 32 bit libraries on a 64 bit system with the normal package manager, you should use [http://ubuntuforums.org/showthread.php?t=474790 getlibs] to install '''libmng''' and the boost filesystem lib:
:<code>getlibs libmng.so.1</code>
:<code>getlibs -l libboost-filesystem1.34.1</code>

=== What about Gentoo? ===
Yes. It's not "officially" supported (the team doesn't test it specifically), however several users have reported success running TDM under Gentoo.

=== What about Ubuntu 8.10? ===
Yes. As of this writing you will need to install the '''libboost-filesystem''' package.

=== GLIBCXX_3.4.9 errors ===

If you receive an error about <tt>GLIBCXX_3.4.9</tt>, delete or rename the files <code>/usr/local/games/doom3/libstdc++.so.6</code> and <code>/usr/local/games/doom3/libgcc_s.so.1.</code>

If this doesn't resolve the error and you have an old version of GCC, then you may have to upgrade. It has been [http://modetwo.net/darkmod/index.php?/topic/9982-the-dark-mod-doom3-in-linux/ confirmed] that, at least under Gentoo, GCC 4.1 does not work with TDM but GCC 4.3 and GCC 4.4 are compatible.

=== Does it run on Mac OS X?===
No. Or at least not yet. The Doom 3 game itself does support Mac OS X, but The Dark Mod currently does not because we don't have any developers who use Macs. If you can help us getting it to run on OS X, please [http://modetwo.net/darkmod/index.php?showforum=11 let us know on the forum].

Since TDM works on Linux already, getting it working on OS X should not be too difficult for anyone with experience programming for that platform. In theory it's just a question of figuring out how to build the mod, sorting out dependencies, and writing a few pieces of platform-specific code.

== Graphics ==

=== Does TDM support widescreen resolutions? ===

Yes. Choose "16:9" or "16:10" in the in-game ''Settings'' menu, and select the appropriate resolution. Note that you need to restart the game to have the new setting in effect.

If the native resolution of your wide screen monitor is not listed, you can enter it into '''DoomConfig.cfg''' by changing the following entries like so:

set r_mode -1
set r_customwidth 1280
set r_customheight 800

Note that if you get performance problems, please consider using a lower resolution and taking a look at [[Performance Tweaks]].

== Troubleshooting ==

It is hard to answer question on why something fails, because wildly different systems cause wildy different symptoms. If the following section does not help you, please ask at out our [http://www.modetwo.net/darkmod forums].

=== Updater (tdm_update.exe) closes almost as soon as it's started ===

See the [[Tdm_update#Updater_closes_almost_as_soon_as_it.27s_started|main article on tdm_update]].

===FM won't install manually===

If you are running Dark Mod under Linux and have edited the file darkmod/currentfm.txt this might prevent the FM from installing. This may be fixed in an update but apparently editing using notepad under Wine works OK.

=== FMs downloaded but don't show in menu list===

You have download some FMs but they don't show on Dark Mod's New Missions list. Possible causes:

* You must not extract the pk4s or zip files but put them into the darkmod/fms folder (or alternatively you can create the FM folder in there eg, darkmod/fms/chalice for chalice.pk4 or chalice.zip.
* Early versions of Dark Mod cannot handle zip suffixes. Solution: rename to .pk4 or run tdm_update to get the latest version of Dark Mod.
* If you are running Linux then Doom 3 MUST be installed in a .doom3 folder. Note the dot before .doom3.

=== FM downloaded but won't play ===

If you have downloaded an FM you might see it in the New Missions List but can't get it to play. These are almost always an install problem. These are some of the causes and cures:

FMs (fan missions) are archives and in early versions of Dark Mod MUST be suffixed .pk4 not zip. Apparently Internet Explorer 8 may change it from pk4 to zip during download without telling you. You need to rename it back if running an early version of Dark Mod else run tdm_update to update and then zip files are OK.

You MUST use doom3\darkmod\tdmlauncher.exe to run Dark Mod in Windows and NOT Doom3.exe.

You do NOT need to extract the pk4 archives to install or play. Just download into or move the pk4 into the darkmod\fms folder. Optionally you can create a folder of the same name as the map and put it in there, eg, darkmod\fms\chalice but there is no need because Dark Mod will create that automatically. Just make sure your pk4 goes, unopened, into the fms folder then run tdmlauncher.exe

If you have done the above but see for example, a blank objectives screen and no briefing then it is still almost certainly an install error. I recommend you do a clean sweep if in doubt:
* Exit Dark Mod
* Delete doom3\darkmod\currentfm.txt (this just uninstalls any FM)
* Delete the map game folder (if any) This is NOT the folder in fms but the folder in doom3 of the same name as the FM, eg, doom3\chalice. Note: this has savegames and screenshots in so check and move them out if you want to preserve them. However, if you can't get the game to play it's likely you don't have any yet. If you can't see the folder don't worry. The folder name is normally the same as the pk4 but it might not be. Strictly speaking it must be the same as the name in startingmap.txt inside the pk4 archive. You might see this file in fms.
* Move the pk4 into the darkmod\fms folder if it is not already there.
* Delete the darkmod\fms\FMname folder if any, eg, darkmod\fms\chalice. Don't worry if there isn't one; it will be created automatically later.

So all that is left is the pk4 in the fms folder. Now run tdmlauncher.exe. The FM should be in the list in the New Missions menu. Re-install it and you should now be able to play it.

=== The game crashes on load ===
Make sure that:
* You installed [[#Patching_Doom_3_to_verson_1.3.1.1304|the correct version]] of the Doom 3 1.3.1 patch.
* Your system meets at least the minimum system specs.
* You have enough free main memory. Try closing a few running programs like Outlook, Anti-Virus or torrent clients.

==== Unknown event 'moveToCoverFrom'" ====
If you get a message like:

ERROR: Error: file script\doom_events.script, line 1038: Unknown event 'moveToCoverFrom'

or see this in the log:

found DLL in pak file: C:\Program Files\Doom 3\darkmod\tdm_game01.pk4/gamex86.dll
copy gamex86.dll to C:\Program Files\Doom 3\darkmod\gamex86.dll
could not create destination file

Try extracting that gamex86.dll manually from '''tdm_game01.pk4''' with Winzip or a similiar program into that folder.

The reason is very probably that you installed Doom3 into a folder with a space in it, and it seems Doom3 does not like that. Sorry.

=== Unknown event 'setEntityRelation' ===
The game is crashing to a small blue screen on startup:

[[Image:ErrorSetEntityRelation.jpg]]

The reason for this error is most likely an old version of gamex86.dll (or gamex86.so) lying around in your Doom 3 folder. Delete that file and try again.

=== Textures are missing, screen mostly black ===

[[Image:Tdm missing textures.jpg|right|240px|Black textures]]

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "0"
seta image_preload "1"
</pre>

=== Textures are missing, shadows are pitch black ===

Try disabling the AGP surface accelerator in DXDIAG

=== The briefing is very fuzzy ===

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the following settings are like shown below:

seta image_roundDown "1"
seta image_forceDownSize "0"
seta image_downSize "0"

=== The sky is corrupted ===

You either see black sky, or fragments of other textures. This seems only to happen on Geforce 6800 cards.

There are two fixes for this:

As a quick fix you can rename the following folder:

env/skyboxes/skybox_darkland_ne

to an different name. That will result in black sky.

Alternatively, edit the file <tt>materials/tdm_sky.mtr</tt> with '''Wordpad''' or a different editor and
find the sky material named '''textures/darkmod/nature/skybox/skybox_darkland_NE''':

<pre>
//Author: Dram
//skybox_ocean with ocean replaced with dark land
//Moon moved to north east by Fidcal
textures/darkmod/nature/skybox/skybox_darkland_NE
{
qer_editorimage env/skyboxes/skybox_ocean/ocean_ed
noFragment
noshadows
noimpact
nooverlays
forceOpaque
{
forceHighQuality
blend add
cameraCubeMap env/skyboxes/skybox_darkland_ne/darkland_NE
texgen skybox
texgen wobblesky .0 .0 .0
}
}
</pre>

In this declaration, comment out the line that reads '''forceHighQuality''' by adding <tt>//</tt> in front of it:

// forceHighQuality

That should fix the sky and make it render correctly.

=== The Sky rotates ===

If you see the sky spinning it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also gives better loading times and cures bloom problem.

=== Bloom problems ===

Bloom has been removed as a default option, if you wish to use it try using r_bloom 1/0; The reasoning behind the change is that it creates lighting situations which are unintended and result in over-bright lights or problems with water textures etc - It is strongly discouraged to use it and should be disabled if you are running an old build from when it was a default. If have a problem with bloom it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also gives better loading times and cures spinning sky problem.

===Underwater performance poor===

If you get very low framerates underwater then try turning off bloom.

===Upside-down screen===

If you get an upside-down screen, you can either turn off Catalyst AI if you have an ati card or try turning off bloom.

To turn off Catalyst AI, open your Catylist control panel, go to 'graphics' up the top left, select '3d' from the dropdown list and on the new menu below, select the 'AI'
Now select the 'Disable Catalyst A.I.' checkbox.

To turn off bloom, enter the console and type "set r_bloom 0" (remove quotes)
Then type "vid_restart" (remove quotes) to refresh the graphics.

=== The game is '''very''' slow! ===

If you get less than 10 FPS, or the game even stutters, please try this:

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the
following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "1"
seta image_preload "1"
</pre>

If that doesn't help, your system might run out of memory. Either upgrade to more than 1 Gbyte memory,
or try to close some other applications before playing.

Please see also the article about [[Performance Tweaks]] to improve the performance.

=== Slow loading times ===

If you find an FM is very slow to load it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also cures bloom and spinning sky problem.

Changing the following settings to 0 will also reduce loading time, but be warned...if you have a lower end system, poor graphics card, or low ram...you will likely notice a performance hit ingame since you will now be using uncompressed textures.
<pre style="max-width:35em">
seta image_useNormalCompression "0"
seta image_useCompression "0"
</pre>

===Game freezes for several seconds when opening doors===
The following problems :

A) "game freezes and loads some data from hard drive while opening doors"
B) "while loading mission you are returned to the menu and need to restart loading"

Are often resolved by disabling EAX 4.0 HD in Audio Settings menu.

===Game exits to menu after mission load, with renderpipe error in console===

'''Symptoms:''' Missions are installed properly and will load, but after they reach 100% you are returned to the main menu or objectives screen. If you open the console (Ctrl-Alt-~ on US keyboards), you see one/both of these errors:

ERROR: Failed to open \\.\pipe\dm_renderpipe

or

ERROR: idRenderSystemLocal::uncrop currentcrop <1

'''Solution:''' Some firewalls, notably ''Sunbelt Firewall'' (aka ''Kerio Firewall'') are known to interfere with TDM's lightgem, ''even when "disabled"''. To fix this problem, completely uninstall the firewall, and get a different one instead.

==="COULD NOT FIND TDMLAUNCHER" when installing an FM===

If you receive this error message you should check the start-arguments of DOOM3.exe / tdmlauncher.exe. Arguments are stored in darkmod/dmargs.txt and a faulty syntax e.g. a missing "+" before a "set"-command, will lead to this error message. Steam-users are advised to remove any launch-options from Doom.

===The sound lags behind the picture===

This seems to happen on Linux with certain ALSA drivers. You can try to disable "Dolby Surround" (switch to "Stereo") or just use OSS instead:

Put the following setting on your tdmlauncher.linux command line:

+set s_driver oss

and use "Stereo".

On some Ubuntu systems, applications using ALSA are re-directed to "pulseaudio" which causes a lack of syncrony between sound and image. Simply removing "pulseaudio" should get your sound back in syncrony:

sudo apt-get purge pulseaudio

=== Changing the screen resolution/aspect ratio does nothing!? ===

These changes require a restart of Doom to work.

=== Steam launches D3, not TDM ===

Whenever you start Steam and it does launch vanilla Doom instead of TDM, make sure you
follow this advice:

'''Important:''' Create a shortcut on your desktop and set it to the following:

steam.exe -applaunch 9050 +set fs_game_base darkmod

This ensures that when you start Steam, it will launch TDM and not Doom 3 without TDM.
== Known bugs ==
See article [[Known Bugs]].

[[Category:General]] [[Category:Installation]]

FAQ

2010-10-06T12:28:20Z

New Horizon: /* Slow loading times */

{{important|headline=Important|text=This FAQ relates to the full TDM release version only. For players of the pre-release demos such as '''[[Thief's Den]]''' and '''[[Saint_Lucia|Tears of Saint Lucia]]''' please refer to the '''[[FAQ (Demo Releases)|Demo FAQ]]'''.'''}}

== What Doom versions are supported? ==

=== Can I use the Demo version of Doom 3? ===

No, sorry.

=== Does it run with the Steam version of Doom 3? ===

Yes :) You need to install the mod into the directory where Steam put Doom3, this might be under:

C:\Program Files\Steam\steamapps\common\doom 3

or a similiar folder.

'''Important:''' Create a shortcut on your desktop and set it to the following:

steam.exe -applaunch 9050 +set fs_game_base darkmod

This ensures that when you start Steam, it will launch TDM and not Doom 3 without TDM.

== Patching Doom 3 to verson 1.3.1.1304 ==

=== How can I check whether my Doom 3 is correctly patched? ===

Open Doom 3 and hit {{key|Ctrl}}+{{key|Alt}}+{{key|~}} (tilde, {{key|^}} on German keyboards) to open the console. You'll see the version printed in the lower left corner of the console. It should read '''1.3.1.1304'''. If your version is ending on 1302, you've got the wrong patch installed.

=== Where can I get the right patch? ===

We have the patch hosted on our FTP. See the [[Installation]] article to find a link to it.

If you have version 1.3.1.1302, you may need to uninstall and reinstall before patch 1.3.1.1304 will let you apply it.

=== What's that issue with the 1.3.1 patch? ===

When the 1.3.1 patch was released by Id, they released it a bit too early. Some download sites picked it up quite fast though and started to distribute it. The problem is, that Id replaced that patch with a different one, and, probably thinking that it hadn't spread yet, didn't bother to change the version number. However, you can still find "wrong" 1.3.1 patches and these will not work with the mod. That's why it is important to check the version number in the console to make sure that the right 1.3.1 patch is installed if the mod doesn't work. The link provided here on our own page points to the correct patch, so if you downloaded it from here you don't need to worry about it.

== Supported Operating Systems ==

=== Which Windows versions can I use? ===

The following versions of windows have been tested and are known to work : Windows 2000, Windows XP, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2003 in both 32bit and 64bit flavours.

=== Does it run in Linux? ===
Yes, Linux is supported.

=== Does it run in 64 Bit Linux? ===
Yes, Linux 64 bit is supported. In addition to the steps above, you need 32 bit compatibility libraries, since Doom3 is 32 bit only:
* On '''SuSE''', they should be included.
* On Ubuntu/Kubuntu, install the package '''ia32'''.

For TDM after 1.0, this step should be '''no''' longer neccessary:

* Since you cannot install 32 bit libraries on a 64 bit system with the normal package manager, you should use [http://ubuntuforums.org/showthread.php?t=474790 getlibs] to install '''libmng''' and the boost filesystem lib:
:<code>getlibs libmng.so.1</code>
:<code>getlibs -l libboost-filesystem1.34.1</code>

=== What about Gentoo? ===
Yes. It's not "officially" supported (the team doesn't test it specifically), however several users have reported success running TDM under Gentoo.

=== What about Ubuntu 8.10? ===
Yes. As of this writing you will need to install the '''libboost-filesystem''' package.

=== GLIBCXX_3.4.9 errors ===

If you receive an error about <tt>GLIBCXX_3.4.9</tt>, delete or rename the files <code>/usr/local/games/doom3/libstdc++.so.6</code> and <code>/usr/local/games/doom3/libgcc_s.so.1.</code>

If this doesn't resolve the error and you have an old version of GCC, then you may have to upgrade. It has been [http://modetwo.net/darkmod/index.php?/topic/9982-the-dark-mod-doom3-in-linux/ confirmed] that, at least under Gentoo, GCC 4.1 does not work with TDM but GCC 4.3 and GCC 4.4 are compatible.

=== Does it run on Mac OS X?===
No. Or at least not yet. The Doom 3 game itself does support Mac OS X, but The Dark Mod currently does not because we don't have any developers who use Macs. If you can help us getting it to run on OS X, please [http://modetwo.net/darkmod/index.php?showforum=11 let us know on the forum].

Since TDM works on Linux already, getting it working on OS X should not be too difficult for anyone with experience programming for that platform. In theory it's just a question of figuring out how to build the mod, sorting out dependencies, and writing a few pieces of platform-specific code.

== Graphics ==

=== Does TDM support widescreen resolutions? ===

Yes. Choose "16:9" or "16:10" in the in-game ''Settings'' menu, and select the appropriate resolution. Note that you need to restart the game to have the new setting in effect.

If the native resolution of your wide screen monitor is not listed, you can enter it into '''DoomConfig.cfg''' by changing the following entries like so:

set r_mode -1
set r_customwidth 1280
set r_customheight 800

Note that if you get performance problems, please consider using a lower resolution and taking a look at [[Performance Tweaks]].

== Troubleshooting ==

It is hard to answer question on why something fails, because wildly different systems cause wildy different symptoms. If the following section does not help you, please ask at out our [http://www.modetwo.net/darkmod forums].

=== Updater (tdm_update.exe) closes almost as soon as it's started ===

See the [[Tdm_update#Updater_closes_almost_as_soon_as_it.27s_started|main article on tdm_update]].

===FM won't install manually===

If you are running Dark Mod under Linux and have edited the file darkmod/currentfm.txt this might prevent the FM from installing. This may be fixed in an update but apparently editing using notepad under Wine works OK.

=== FMs downloaded but don't show in menu list===

You have download some FMs but they don't show on Dark Mod's New Missions list. Possible causes:

* You must not extract the pk4s or zip files but put them into the darkmod/fms folder (or alternatively you can create the FM folder in there eg, darkmod/fms/chalice for chalice.pk4 or chalice.zip.
* Early versions of Dark Mod cannot handle zip suffixes. Solution: rename to .pk4 or run tdm_update to get the latest version of Dark Mod.
* If you are running Linux then Doom 3 MUST be installed in a .doom3 folder. Note the dot before .doom3.

=== FM downloaded but won't play ===

If you have downloaded an FM you might see it in the New Missions List but can't get it to play. These are almost always an install problem. These are some of the causes and cures:

FMs (fan missions) are archives and in early versions of Dark Mod MUST be suffixed .pk4 not zip. Apparently Internet Explorer 8 may change it from pk4 to zip during download without telling you. You need to rename it back if running an early version of Dark Mod else run tdm_update to update and then zip files are OK.

You MUST use doom3\darkmod\tdmlauncher.exe to run Dark Mod in Windows and NOT Doom3.exe.

You do NOT need to extract the pk4 archives to install or play. Just download into or move the pk4 into the darkmod\fms folder. Optionally you can create a folder of the same name as the map and put it in there, eg, darkmod\fms\chalice but there is no need because Dark Mod will create that automatically. Just make sure your pk4 goes, unopened, into the fms folder then run tdmlauncher.exe

If you have done the above but see for example, a blank objectives screen and no briefing then it is still almost certainly an install error. I recommend you do a clean sweep if in doubt:
* Exit Dark Mod
* Delete doom3\darkmod\currentfm.txt (this just uninstalls any FM)
* Delete the map game folder (if any) This is NOT the folder in fms but the folder in doom3 of the same name as the FM, eg, doom3\chalice. Note: this has savegames and screenshots in so check and move them out if you want to preserve them. However, if you can't get the game to play it's likely you don't have any yet. If you can't see the folder don't worry. The folder name is normally the same as the pk4 but it might not be. Strictly speaking it must be the same as the name in startingmap.txt inside the pk4 archive. You might see this file in fms.
* Move the pk4 into the darkmod\fms folder if it is not already there.
* Delete the darkmod\fms\FMname folder if any, eg, darkmod\fms\chalice. Don't worry if there isn't one; it will be created automatically later.

So all that is left is the pk4 in the fms folder. Now run tdmlauncher.exe. The FM should be in the list in the New Missions menu. Re-install it and you should now be able to play it.

=== The game crashes on load ===
Make sure that:
* You installed [[#Patching_Doom_3_to_verson_1.3.1.1304|the correct version]] of the Doom 3 1.3.1 patch.
* Your system meets at least the minimum system specs.
* You have enough free main memory. Try closing a few running programs like Outlook, Anti-Virus or torrent clients.

==== Unknown event 'moveToCoverFrom'" ====
If you get a message like:

ERROR: Error: file script\doom_events.script, line 1038: Unknown event 'moveToCoverFrom'

or see this in the log:

found DLL in pak file: C:\Program Files\Doom 3\darkmod\tdm_game01.pk4/gamex86.dll
copy gamex86.dll to C:\Program Files\Doom 3\darkmod\gamex86.dll
could not create destination file

Try extracting that gamex86.dll manually from '''tdm_game01.pk4''' with Winzip or a similiar program into that folder.

The reason is very probably that you installed Doom3 into a folder with a space in it, and it seems Doom3 does not like that. Sorry.

=== Unknown event 'setEntityRelation' ===
The game is crashing to a small blue screen on startup:

[[Image:ErrorSetEntityRelation.jpg]]

The reason for this error is most likely an old version of gamex86.dll (or gamex86.so) lying around in your Doom 3 folder. Delete that file and try again.

=== Textures are missing, screen mostly black ===

[[Image:Tdm missing textures.jpg|right|240px|Black textures]]

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "0"
seta image_preload "1"
</pre>

=== Textures are missing, shadows are pitch black ===

Try disabling the AGP surface accelerator in DXDIAG

=== The briefing is very fuzzy ===

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the following settings are like shown below:

seta image_roundDown "1"
seta image_forceDownSize "0"
seta image_downSize "0"

=== The sky is corrupted ===

You either see black sky, or fragments of other textures. This seems only to happen on Geforce 6800 cards.

There are two fixes for this:

As a quick fix you can rename the following folder:

env/skyboxes/skybox_darkland_ne

to an different name. That will result in black sky.

Alternatively, edit the file <tt>materials/tdm_sky.mtr</tt> with '''Wordpad''' or a different editor and
find the sky material named '''textures/darkmod/nature/skybox/skybox_darkland_NE''':

<pre>
//Author: Dram
//skybox_ocean with ocean replaced with dark land
//Moon moved to north east by Fidcal
textures/darkmod/nature/skybox/skybox_darkland_NE
{
qer_editorimage env/skyboxes/skybox_ocean/ocean_ed
noFragment
noshadows
noimpact
nooverlays
forceOpaque
{
forceHighQuality
blend add
cameraCubeMap env/skyboxes/skybox_darkland_ne/darkland_NE
texgen skybox
texgen wobblesky .0 .0 .0
}
}
</pre>

In this declaration, comment out the line that reads '''forceHighQuality''' by adding <tt>//</tt> in front of it:

// forceHighQuality

That should fix the sky and make it render correctly.

=== The Sky rotates ===

If you see the sky spinning it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also gives better loading times and cures bloom problem.

=== Bloom problems ===

Bloom has been removed as a default option, if you wish to use it try using r_bloom 1/0; The reasoning behind the change is that it creates lighting situations which are unintended and result in over-bright lights or problems with water textures etc - It is strongly discouraged to use it and should be disabled if you are running an old build from when it was a default. If have a problem with bloom it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also gives better loading times and cures spinning sky problem.

===Underwater performance poor===

If you get very low framerates underwater then try turning off bloom.

===Upside-down screen===

If you get an upside-down screen, you can either turn off Catalyst AI if you have an ati card or try turning off bloom.

To turn off Catalyst AI, open your Catylist control panel, go to 'graphics' up the top left, select '3d' from the dropdown list and on the new menu below, select the 'AI'
Now select the 'Disable Catalyst A.I.' checkbox.

To turn off bloom, enter the console and type "set r_bloom 0" (remove quotes)
Then type "vid_restart" (remove quotes) to refresh the graphics.

=== The game is '''very''' slow! ===

If you get loading times of 5 minutes or more, less than 10 FPS, or the game even stutters, please try this:

Look into your '''DoomConfig.cfg''' inside your <tt>darkmod</tt> folder and check that the
following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "1"
seta image_preload "1"
</pre>

If that doesn't help, your system might run out of memory. Either upgrade to more than 1 Gbyte memory,
or try to close some other applications before playing.

Please see also the article about [[Performance Tweaks]] to improve the performance.

=== Slow loading times ===

If you find an FM is very slow to load it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also cures bloom and spinning sky problem.

Changing the following settings to 0 will also reduce loading time, but be warned...if you have a lower end system, poor graphics card, or low ram...you will likely notice a performance hit ingame since you will now be using uncompressed textures.
<pre style="max-width:35em">
seta image_useNormalCompression "0"
seta image_useCompression "0"
</pre>

===Game freezes for several seconds when opening doors===
The following problems :

A) "game freezes and loads some data from hard drive while opening doors"
B) "while loading mission you are returned to the menu and need to restart loading"

Are often resolved by disabling EAX 4.0 HD in Audio Settings menu.

===Game exits to menu after mission load, with renderpipe error in console===

'''Symptoms:''' Missions are installed properly and will load, but after they reach 100% you are returned to the main menu or objectives screen. If you open the console (Ctrl-Alt-~ on US keyboards), you see one/both of these errors:

ERROR: Failed to open \\.\pipe\dm_renderpipe

or

ERROR: idRenderSystemLocal::uncrop currentcrop <1

'''Solution:''' Some firewalls, notably ''Sunbelt Firewall'' (aka ''Kerio Firewall'') are known to interfere with TDM's lightgem, ''even when "disabled"''. To fix this problem, completely uninstall the firewall, and get a different one instead.

==="COULD NOT FIND TDMLAUNCHER" when installing an FM===

If you receive this error message you should check the start-arguments of DOOM3.exe / tdmlauncher.exe. Arguments are stored in darkmod/dmargs.txt and a faulty syntax e.g. a missing "+" before a "set"-command, will lead to this error message. Steam-users are advised to remove any launch-options from Doom.

===The sound lags behind the picture===

This seems to happen on Linux with certain ALSA drivers. You can try to disable "Dolby Surround" (switch to "Stereo") or just use OSS instead:

Put the following setting on your tdmlauncher.linux command line:

+set s_driver oss

and use "Stereo".

On some Ubuntu systems, applications using ALSA are re-directed to "pulseaudio" which causes a lack of syncrony between sound and image. Simply removing "pulseaudio" should get your sound back in syncrony:

sudo apt-get purge pulseaudio

=== Changing the screen resolution/aspect ratio does nothing!? ===

These changes require a restart of Doom to work.

=== Steam launches D3, not TDM ===

Whenever you start Steam and it does launch vanilla Doom instead of TDM, make sure you
follow this advice:

'''Important:''' Create a shortcut on your desktop and set it to the following:

steam.exe -applaunch 9050 +set fs_game_base darkmod

This ensures that when you start Steam, it will launch TDM and not Doom 3 without TDM.
== Known bugs ==
See article [[Known Bugs]].

[[Category:General]] [[Category:Installation]]

Performance Tweaks

2010-08-22T23:30:08Z

New Horizon: /* Remove the custom interaction.vfp */

This article relates to performance issues ''for players''. For performance information ''for mappers'', see [[Performance: Essential Must-Knows]]

== Show FPS ==

First, you can check how many {{abbr|FPS|frames per second}} are achieved by opening the console with {{key|Ctrl}}+{{key|Alt}}+{{key|~}} (tilde, {{key|^}} on German keyboards) and type:

com_showFPS 1

== Optimizing the performance ==

=== Stop running programs in the background ===

Programs running in the background might either eat up memory that is needed for Doom3, and thus cause swapping to the hard disk, or they might consume CPU time or other resources. This can cause either general slowdowns or ''hickups'' during game play.

=== Run Doom3 in fullscreen ===

Running Doom3 in windowed mode might be quite a bit slower than fullscreen mode.

=== Reduce your resolution! ===

On older cards, Doom3's render engine is very expensive for every per pixel drawn, and reducing the resolution will help the most. For instance, at 1600x1200 the game needs to draw '''four times''' as many pixels as when running 800x600. The result with 800x600 will not look as bad as one might think – but the frame rate improvements might make it much more playable.

If you cannot set the resolution you want in the settings menu then enter it in doomconfig.cfg.

To edit doomconfig.cfg:

* Uninstall any current mission in the New Mission menu.
* Close Dark Mod
* Edit doomconfig.cfg in the darkmod folder
* Re-install the mission.
* Whenever you UNinstall and install another mission, these changes will migrate to those FMs as well.

(Alternatively, edit both the doomconfig in the darkmod folder AND the one in the current FM game folder, eg, doom3\chalice.)

Search down for these cvars first and replace them with the values shown:

seta r_mode "-1"
seta r_customHeight "640"
seta r_customWidth "480"

=== Set the ambient shading to "Faster" ===

(Not valid for '''Thief's Den demo''')

Inside the settings, change the ambient rendering method to "Faster".

=== Set the interaction.vfp to 'Standard' ===

(Not valid for '''Thief's Den''' demo.)
In the video settings menu, change the interaction shader to Standard. Ambient lighting will not look as good, but you may gain a few frames per second.

== The game is '''very''' slow! ==

If you get loading times of 5 minutes or more, less than 10 FPS, or the game even stutters, please try this:

Look into your '''DoomConfig.cfg''' inside your <tt>saintlucia</tt> or <tt>thiefsden</tt> folder and check that the following settings are like shown below:

<pre style="max-width:35em">
seta image_usePrecompressedTextures "1"
seta image_useNormalCompression "2"
seta image_useAllFormats "1"
seta image_useCompression "1"
seta image_preload "1"
</pre>

=== Image downsizing ===

As a last resort, you may enable image downsizing: at the console, set '''image_downSize''' to '''1''' and then set a limit with '''image_downSizeLimit''', e.g., '''"image_downSizeLimit" "256"'''. This reduces texture memory requirements and may completely alleviate hard drive thrashing. There are similar cvars for bump and specular maps as well.
'''Note: This may result in very blurry briefing and menu screens.'''

===Drop in Frame Rates when Viewing Water===

Some players have reported a drastic drop in performance when an agitated water surface is in view. This on a Radeon card. Try entering this in the console. It disables the water visible surface effects but at least it might let you play normally...

set r_skipPostProcess "1"

==Blurry Briefing and Menu Screens==

If you get blurry briefing and menu screens then in DoomConfig.cfg make sure you do NOT have image_downSize 0. Instead set it to 1. But see also [[#Image downsizing]]

==Field of View Decrease==

'''Note''' that this setting might occasionally produce odd effects such as a grabbed object seems to move a little on release.

You can get a performance improvement if you decrease the field of view. By default this is 90 degrees but you might try entering in the console or in your doomconfig.cfg...

g_fov 85

In addition, if you are playing a mission that is too good to miss and reach a very low performance area which is almost unplayable on your machine, you might consider setting the field of view extremely low temporarily to get you through then restore to 90 later...

g_fov 50

Note from Fidcal: I have played comfortably on g_fov 75 and even think perhaps it makes nearby objects more realistically close so you can get right up to a table, etc. Not noticed any problem with restricted view.

== Player Shadow==

The player shadow slightly reduces performance. It has no game effect at all (not seen by AI for instance) apart from atmospheric effect so if you want to disable it enter in the console:

g_showplayershadow 0

Or, in doomconfig (see above) change the following line from "1" to "0":

seta g_showplayershadow "0"

== Player Lantern Shadow==

You may notice a drop in performance while using the player lantern.

Add "noshadows" "1" to entitydef light_lantern_moving in tdm_playertools_lantern.def and this stops the player lantern casting shadows. This helps improve performance slightly when using the lantern.

==Gameplay Performance Tips==

If you have done everything else you can and performance is still poor then one or two things you might do in game to help:

* Close all doors after you have passed through. Generally the game has to process both areas until you close the door if the doorway is still in sight.
* Kill or KO every AI you can. You might not like to play that way but generally, AI still hog resources even out of sight (depending on how set up in the game.)
* Avoid alerts. A dozen guards searching for you will really slow things down on a low-end machine.
* Try to look down at the ground when moving along. Gazing up at a grand vista will slow you down. Best to do your gazing while standing still.

== Last resort: Upgrade your hardware ==

Modern games need a lot of computing power, and while you don't need the absolutely newest hardware to play them, upgrading single components of your machine can help tremendously:

* If you got '''less than 2 GByte''' main memory, consider upgrading your memory. This really helps to reduce swapping, which introduces quite noticeable slowdowns.
* If you got a graphic card from NVidia older than the GF 7x00 series, consider upgrading it.

Upgrading your CPU will be quite complicated and the cost might be so sadly high that you could rather buy a new complete computer. Upgrading the hard disk will usually not help much with gaming, unless you are running out of free space.

== See also ==

See also the [[FAQ]].

{{installation}}

How to add Textures to The Dark Mod

2010-03-24T14:43:35Z

New Horizon: Undo revision 9833 by New Horizon (Talk)

== Create your texture ==
This is mostly artwork. Be sure to start off with useful raw material with a reasonably high resolution. Where possible, work from photo-references. A basic guide can be found here: [[Texture Creation - Basic Tutorial]].

A few things to remember: Make sure your texture dimensions are a power of 2 (eg, 128, 256, 512, 1024, etc). Other common mistakes can be found here: [[Common Texture Mistakes]]
{{Things-To-Remember|
* Use good source material
* All image dimensions must be powers of two: 64, 128, 256, 512, 1024 (don't go beyond 1024).
* Avoid lighting baked into the diffusemap
* Keep your PSD/Gimp working version safe!}}
== Save your Texture in the correct Format ==
Save the diffusemap, the normalmap and an optional specularmap to a TGA file. The '''[[Texture Guidelines]]''' will help you choosing the correct resolution. A TGA version of your diffusemap is supposed to be uploaded to our hi-res repository for future reference (see below).

Once your TGA file is saved, you will have to create DDS files for the diffuse and specular (not the normalmap) as well. These are smaller in size and can be loaded faster by the engine. Follow the '''[[DDS creation]]''' guide to learn how to create the DDS files in the correct formats.

Also, create an editor image out of your diffusemap. The editor image dimension should be 256x256 pixels and the file should be saved in the JPG format. Add the '''_ed''' postfix to the filename name (like <code>mytexture_ed.jpg</code>).
{{Things-To-Remember|
* Most textures don't need speculars
* Create DDS for your diffusemap and specularmap.
* Keep TGA version of your diffusemap and specularmap.
* Create a TGA version of your normalmap (uncompressed, no RLE).
* Create a JPG editor image (max. 256px)}}
== Name your Texture ==
The following convention should be used for naming all new texture additions to TDM (many existing textures do not follow this convention, and over time effort will be made to update them). The goal is consistency among material names based on ordered characteristics.

'''Some or all''' of the following may apply to any given material:

# '''Object Type''' descriptor first (mostly for very specific-use textures) - it's a window, a door, a chest...
# '''Material''' descriptor next - made from marble, wood, mud...
# '''Size''' descriptor next - it is large, small...
# '''Quality''' descriptors next - texture-wise, it is rough, new, cracked...
# '''Color''' descriptors next - what color is it? red, green...
# '''Number Increment''' next - which of the list is it? 001, 002...
# '''Tiling''' and '''Image Type''' descriptors, if needed (file only, not material definition - see below)

If establishing precedent (creating a new '''Size''' descriptor, e.g., "huge"), try to avoid ambiguity and unnecessary overlapping with other descriptors (e.g., "enormous"), and set a good example others will follow.

'''Examples:'''

1. ''slate_large_cracked_grey_001''

This name omits an '''Object Type''' descriptor, instead starting with the '''Material''' descriptor - it is a general, non-specialized texture.

Why is this preferred? Some existing materials are named by quality descriptor first (e.g., 'cracked_slate...'). This is an inconvenience for the user, because they were looking for a 'slate', not a 'cracked'.

2. ''door_wood_battered_005''

This name omits a '''Size''' descriptor and a '''Color''' descriptor.

Why is this preferred? In the case of a model name (which this convention also covers), or a specific object type texture like the above, some existing assets are named by quality descriptor first (e.g., 'battered_wood...'). This is an inconvenience for the user, because they were looking for a 'door', not a 'battered'.

Be sure to rename all your DDS file extensions to a '''lowercase''' '''.dds''' (the Compressonator always creates files with uppercase extension, TDM requires them to be lowercase).

If your texture tiles only in one direction, include the phrase '''tiling_1d''' at the end of the name. If your texture does not tile (repeat) at all, add the phrase '''nontiling'''. So, a normalmap could be names as '''concrete_dirt01_tiling1d_local.tga'''.

Diffusemaps should have no extension to their name. Normalmaps should have a '''_local''' extension at the end of their name. Specular maps should have a '''_s''' extension, the editor images go with an '''_ed''' extension.
{{Things-To-Remember|
* Choose descriptive names for your texture, while following TDM convention
* Add the suffix '''tiling_1d'''/'''nontiling''' to the filename where appropriate
* Diffusemap: '''mytexture.dds''' (note the '''lowercase''')
* Normalmap: '''mytexture_local.tga'''
* Editor image: '''mytexture_ed.jpg''' (max. 256 pixels in size)
* (Optional) Specularmap: '''mytexture_s.dds'''}}

== Move the Texture to the right Location ==
When you upload textures, be sure to upload the files to the right spot. The '''[[Texture Folder Structure]]''' can help you finding the right folder for your texture.

The .dds diffuse and specular go in the '''dds/textures/''' folder structure. The .tga normalmap goes in the '''textures/''' folder structure. Note that there is a peculiarity of the Doom 3 engine not being able to load DDS textures that are more than five folders deep. The deepest level allowed would be something along the lines of dds/textures/darkmod/door/metal/. This is something to be watched out for.
{{Things-To-Remember|
* Move the DDS textures into the '''dds/textures/...''' tree.
* Move the TGA and JPG files into the '''textures/...''' tree.
* Don't save DDS files into folders more than 5 levels deep.}}
== Create your Shader Definition (Material) ==
Your material entry should be added to the .mtr file that has the same name as the folder your texture is saved in. For example, the material entry for a texture saved in '''textures/darkmod/wood/panels''' should be saved in the .mtr file, '''tdm_wood_panels.mtr'''. See also the [[Material File Naming Convention]].

You should name your material entry the same name as your diffuse texture, including the folder path structure (eg, "textures/darkmod/wood/panels/rectangle_oak_face"). (Do not add .tga or .dds to the end, and also skip the dds/ folder prefix.)

The only exception is when multiple shaders are using the same diffusemap, or when your texture doesn't tile (or tiles in only one direction). In the latter case, you would add '''/nontiling/''' or "/tiling_1d/''' to the end of the shader folder (a 'virtual' folder, essentially). ''(The textures used to be separated like that in the actual folder structure, but due to D3's inability to read .dds files five folders deep, they had to be moved.)''
{{Things-To-Remember|
* Create your shader in the correct file (tdm_xxx_yyy.mtr) following the [[Material File Naming Convention]]
* The shader name for tiling textures is the same as the diffusemap
* Nontiling/tiling_1d textures go into a "virtual" subfolder nontiling/ or tiling_1d/
* You don't need to specify file extensions (.dds/.tga/.jpg) to the material defs, this is automatically guessed by the engine.
* You don't need the '''dds/''' folder prefix to reference the DDS textures.
* Be sure to include the frob highlight code (see [[Basic Material File#Add_the_Frob_Highlight_Stage|Basic Material File]])
* You '''must''' include Dark Mod's ambient light stage (see [[Virtual Ambient Light Textures]])}}

== Upload the Textures ==
Once, you have checked your texture in-game (and are pleased with the results), you'll need to upload the files to our SVN repository. This requires that you have a valid username/password for SVN, which you can request from sparhawk.

The .tga of the diffuse and specular is needed as well in case we ever want to make modifications to the texture or new textures based on the old. Opening and resaving .dds files results in loss of detail, so all new versions of textures should be made from the .tga files. So, additional to the textures needed for the engine and editor (diffuse/normal/specular/editorimage) you're encouraged to upload the uncompressed textures to the hires repository.

The hires repository is located at '''<nowiki>https://<InsertDarkmodServerHere>/svn/darkmod_hires/trunk/tga_backup/</nowiki>'''. As only diffuse/speculars are compressed in DDS format, these are the only two that need to be uploaded in TGA format. The TGA files should be named just like the DDS versions and should be located in the analogous folder than they are in the main repository, but below the tga_backup/ folder. For instance tga_backup/textures/darkmod/stone/etc.

The hires TGA can be RLE-compressed to save some space, but this is not too important. Uncompressed TGAs are only important for the textures used by the engine itself.

As last part, it would be nice to have the actual working versions (Photoshop/Gimp source files) stored on the server too. This is of course a large upload, but having the source files is very valuable. For this purpose, there is another repository '''texture_src''' installed at '''<nowiki>https://<InsertDarkmodServerHere>/svn/texture_src/</nowiki>'''.
{{Things-To-Remember|
* Upload the diffuse, normal, (specular,) and editor image to the regular darkmod SVN.
* Upload the (RLE-compressed) TGA diffusemap and specularmap to the darkmod_hires SVN repository (into the '''tga_backup''' subfolder).
* Upload the working source file (PSD/Gimp) to the '''texture_src''' repository.}}
{{tutorial-textures}}
__NOTOC__

Texture Creation - Basic Tutorial

2010-03-24T14:42:23Z

New Horizon: Undo revision 9832 by New Horizon (Talk)

{{tutorial-textures}} {{Original_Reference|SneaksieDave|3814}}
A game like this needs a TON of textures. So I wanted to try to learn how to do this mysterious, wonderous, magick...

Erm, well, it's not magick. Far from it, in fact. This tutorial isn't for those of you who already know how to do this*, and already know it's not magick. This tutorial is for the rest of us, those who have been too scared or lazy to even bother asking "how do I?", like me. (It's the former, honest!)

== Prerequisites ==

You can use Gimp or Photoshop on Windows, for Linux you should use Gimp. So you'll need either of the two programs Gimp/Photoshop and the corresponding set of plugins:

=== Photoshop ===

* [http://developer.nvidia.com/object/photoshop_dds_plugins.html Nvidia normal map plugin]

=== Gimp ===

* [http://nifelheim.dyndns.org/~cocidius/normalmap/ GIMP normalmap plugin]
* [http://www.manucornet.net/Informatique/Texturize.php#download GIMP texturize plugin]
* [http://registry.gimp.org/plugin?id=4816 Gimp DDS plugin]

If you are using Kubuntu/Ubuntu, you can also install the <code>gimp-texturize</code> and <code>gimp-resynthesizer</code> packages.

To compile Gimp plugins from source, install the following packages and their dependecies:

* libgimp2.0-dev
* libgtk1.2-dev
* libglut3-dev (for the DDS plugin)

== Get your source picture ==

This could be anything from a photograph you took, to a free texture download from the internet (see [[Texture Sources]]), to a hand drawn picture, if you're one of those fortunate enough to possess that skill - though we generally prefer to work from photo-reference when possible.

If you do want to take photos, some tips:
* try to shoot on an overcast day; the diffuse light will remove most unwanted shadows
* try to take the photo as perfectly face-on to the surface as you can manage.
If your end result isn't perfect, don't worry, there are ways to fix it (transform->skew, to name one)
* Make sure that all parts of your photo you want to use as texture are in focus (e.g. sharp). Unsharp parts cannot be fixed later, at least not without a big quality loss!
* try to select an area that will be tile-able (if that's what you want)
* try to capture a large area such that you'll have enough to work with, but not so big that your resolution on the final product will suffer

== Create the diffuse map ==

The diffuse map is a tilable (usally) image which gives the color infomation, but does not contain lighting or height information for the texture. It is stored as dds with dxt1 or dxt3 compression for use in Doom 3 and as 24 bit TGA (with or without RLE) for the hires repository.

If your image has lighting baked in (shadows/highlights), you should remove it: [[Remove Shadows in Source Images]].

This is just a basic tutorial for creating textures. For further information about creating Diffusemaps, read [[Advanced Tips for Creating Diffusemaps]].

=== Photoshop ===

Inspect the source image. If you're going to tile it, try to find a regular repeating area. This is only to make your job easier. You can tile anything, really, but it depends on how much work you want to give yourself. If you don't know what I mean here, at the next step you will.

After you've chosen a rough tile-able area (from here forward I'm going to assume you are doing a tiled texture), crop that area out, and size your image to the desired size ratio. I wouldn't go lower than 1024 resolution at this stage of the work, or you'll start losing picture quality quickly. So set it to 2048X1024, or 1024X1024, etc. The reason we need to fix the size ratio (not the final size) at this stage is for the next step.

==== Set the offset ====

Go to Filter->Other->Offset. You want to set the horizontal and vertical to be exactly half of your cropped picture's width and height. That will make the opposite edges of the texture meet each other in the middle of the view, so you can make it really tile-able.

==== Make the seams disappear ====
See those seams running right down the middle of the pic, vertically and horizontally? You have to make them disappear. Get to know the clone tool. (Google...) There are many other ways to shuffle pixels too, but I'll leave the specifics up to you. This is usually the hardest, most time consuming step.

Once you've blended the lines away, run the Offset filter again to restore the correct layout of your pic, and save it out in a nice high quality (but not too big to manage) format. This is the "diffuse" image. We're using 24bit TGA for TDM.

=== Gimp ===

Use the <code>texturizer</code> or the <code>resynthezier</code> plugin - these are very easy to work with and make manual work almost needless.

== Create a normal map ==

The Normalmap tells the renderer in which direction a corresponding place on the diffusemap is facing, so that it can be shaded according to the present lightsources in the scene. It is stored as uncompressed 24 bit TGA (no RLE!) for use in Doom 3. You will learn the basics about creating Normalmaps here. For further information: [[Normalmaps, How to Make Good Ones]].

=== Photoshop ===

Now that the diffuse is done, using that same pic, open Filter->Nvidia Tools->NormalMapFilter. You'll probably have to play with the values for a while to get a feel for it, and to get a normal map you are happy with. This is a rough approximation method, by no means as accurate as actually modelling a texture (see [[Wall Texture Tutorial]] or [[Creating Textures with Normals out of Models]]), but it works pretty good in most cases. Basically, it will make light areas "high" and dark areas "low". Learn how to manipulate color levels in Photoshop, and you'll be making good normal maps with the Nvidia filter in no time. Generally, use values of 3 or 4 for simple things like woodgrain or nails. Values of 12 or higher can be used for more 3d effects.

If you think about it, there are countless ways to adjust the image (in fact, you're not even restricted to using the diffuse image as the base of the normal map...) to get desired results - inverting colors, brightness and contrast controls, painting over areas, gradients, etc. It's a "feel" thing, so you'll have to develop that for yourself. After creating your desired normal map (try not to make it too blurry, or too sharp, or too bumpy - yuck), save it out as you did with the diffuse image, with "_local" appended.

=== Gimp ===

This is a rough guide by a non-expert as I (fidcal) do it so at least there is something here. It assumes you have made a temporary greyscale image file saved as say nameGrey.tga with the brighter areas representing the high ground and darker means low as described elsewhere ready to make your make normal map. It assumes you've just downloaded Gimp and its Normalmap plugin (ESSENTIAL!), maybe configured it a bit so don't know much about it but just want a dumb list to follow.

* Open Gimp
* Gimp consists of separate floating windows with no main window so select the toolbar window > file menu > and open your greyscale image file.
* You can enlarge/maximize the window and zoom with the mouse wheel if you want.
* Menu > filters > map > normalmap
* On the normal map dialog, Click 3D map preview; it will make more sense then.
* On the normal map dialog, in the 'scale' box there is zero by default which is useless as a default as this seems to be the scale of depth. Enter 50 for a start.
* On the 3D preview dialog there is a window with a panel in it. Grab the panel with your left mouse button and drag it around. Now you should see a rough 3D impression of your image.
* If you have no idea what you're doing (like me) leave the scale at 50 as a reasonable value, otherwise adjust it according to your knowledge. Maybe come back here later if you feel your final result is not deep enough or too deep. Similarly leave the other controls or adjust if you know what you are doing.
* On the normal map dialog click OK.
* On Gimp's image window you should now see your greyscale image has been converted probably blue looking with depressions, eg inverted the heights; that's OK.
* Save as name_local.tga in the correct dark mod texture folder where your main texture is.
* A mini dialog pops up : RLE compression - set this UNchecked, and 'origin at bottom left' - leave this checked. Click OK.
* I had a lot of programs open including Doom so it seemed to hang a long time but eventually saved.
* You close Gimp by closing that toolbar window so I guess that's its nearest thing to a main window.

That's it.

== Create an editor image ==
As the diffusemap is very large it takes some time loading it into the editor, this is why DarkRadiant/DoomEd support the display of lowres editor images replacements. Just resize the diffusemap down to max. 256 pixels and save it in JPG format, but be sure to attach the '''_ed''' suffix.

== Add a specular map ==
The specularmap tells the renderer how shiny a corresponding place on the diffusemap is. It is stored as dds and its dimensions are typically scaled down to be half as big as those of the diffusemap.

If you want a specular map, the process is even more subjective. There are countless ways in Photoshop to adjust color and light level and even invert everything or parts or mask out areas. Specular maps work as such: Darker is rendered as dull, lighter is rendered as shiny. Get it? Think of the possibilities, and have fun with it. You can get some pretty amazing results with just minutes of work. Save that image out as you did the diffuse, '''with "_s" appended'''.

Note that most surface types don't need a specular map. Only shiny surfaces, like metal or wet stone, really need one, while wood, cobbles, canvas, leaves, dirt etc. should not have a specular map.

== Create your material file ==

Create a material for the texture. In the materials folder, locate the material file where you texture fits in best. Then add the following:

textures/your_desired_editor_texture_folder/your_texture_name
{
// Use one of the predefined surface types like stone, glass, wood
stone
// or use this:
// surfaceType 15
// and make the first word in the description below your texture type,
// like so:
// description "foliage" (This is a grass texture)

description "Add here a little description of your texture"
qer_editorimage textures/your_file_folder/your_texture_name_ed

bumpmap textures/your_file_folder/your_texture_name_local
diffusemap textures/your_file_folder/your_texture_name
specularmap textures/your_file_folder/your_texture_name_s

// This is the code required for frob highlighting this texture
{
if ( parm11 > 0 )
blend gl_dst_color, gl_one
map _white.tga
rgb 0.40 * parm11
}
{
if ( parm11 > 0 )
blend add
map textures/your_file_folder/your_texture_name
rgb 0.15 * parm11
}
}

Oh, and on Windows, use Wordpad, not Notepad. That's it. Your new texture should appear in both the editor and in-game.

== Summary ==
So you see, it's really quite simple:
* Crop the desired area
* Make it tileable if necessary
* Generate a normal map
* Generate an editor image
* Create a specular map if you want one
* Include it in a material file
* DONE

The most important thing though, is to obey the [[Texture Guidelines]].

== Further Information ==

* [[Common Texture Mistakes]]
* [[How to add Textures to The Dark Mod]]
* [[Texture Folder Structure]]
* [[Basic Material File]]

== Links ==

=== Photoshop ===

* [http://developer.nvidia.com/object/photoshop_dds_plugins.html nVidia Normal Map PlugIn]

=== Gimp ===

* [http://nifelheim.dyndns.org/~cocidius/normalmap/ GIMP normalmap plugin]
* [http://www.manucornet.net/Informatique/Texturize.php#download GIMP texturize plugin *THIS IS AMAZING*]
* [http://registry.gimp.org/plugin?id=4816 Gimp DDS plugin]

=== Assorted tutorials ===

* [http://www.doom3world.org/phpbb2/viewtopic.php?t=11893 Doom3World texture tutorials]
* [http://www.quake3bits.com/htm/tutorials/creating_bumpmaps_from_images.htm Kat's normal-map making tutorial]
* [http://www.gimp.org/tutorials/Tileable_Textures/ Quick GIMP tutorial for tileable textures]
* [http://www.stormvision.net/index.cfm/act/tutorials/tutorial_ID/1 Another tileable texture tutorial]

How to add Textures to The Dark Mod

2010-03-24T13:21:01Z

New Horizon: /* Save your Texture in the correct Format */

== Create your texture ==
This is mostly artwork. Be sure to start off with useful raw material with a reasonably high resolution. Where possible, work from photo-references. A basic guide can be found here: [[Texture Creation - Basic Tutorial]].

A few things to remember: Make sure your texture dimensions are a power of 2 (eg, 128, 256, 512, 1024, etc). Other common mistakes can be found here: [[Common Texture Mistakes]]
{{Things-To-Remember|
* Use good source material
* All image dimensions must be powers of two: 64, 128, 256, 512, 1024 (don't go beyond 1024).
* Avoid lighting baked into the diffusemap
* Keep your PSD/Gimp working version safe!}}
== Save your Texture in the correct Format ==
Save the diffusemap, the normalmap and an optional specularmap to a TGA file. The '''[[Texture Guidelines]]''' will help you choosing the correct resolution. A TGA version of your diffusemap is supposed to be uploaded to our hi-res repository for future reference (see below).

Once your TGA file is saved, you will have to create DDS files for the diffuse and specular (not the normalmap) as well. These are smaller in size and can be loaded faster by the engine. Follow the '''[[DDS creation]]''' guide to learn how to create the DDS files in the correct formats.

Also, create an editor image out of your diffusemap. The editor image dimension should be 256x256 pixels and the file should be saved in the JPG format. Add the '''_ed''' postfix to the filename name (like <code>mytexture_ed.jpg</code>).
{{Things-To-Remember|
* Most textures don't need speculars
* Create DDS for your diffusemap and specularmap.
* Keep TGA version of your diffusemap and specularmap(uncompressed, no RLE).
* Create a TGA version of your normalmap (uncompressed, no RLE).
* Create a JPG editor image (max. 256px)}}

== Name your Texture ==
The following convention should be used for naming all new texture additions to TDM (many existing textures do not follow this convention, and over time effort will be made to update them). The goal is consistency among material names based on ordered characteristics.

'''Some or all''' of the following may apply to any given material:

# '''Object Type''' descriptor first (mostly for very specific-use textures) - it's a window, a door, a chest...
# '''Material''' descriptor next - made from marble, wood, mud...
# '''Size''' descriptor next - it is large, small...
# '''Quality''' descriptors next - texture-wise, it is rough, new, cracked...
# '''Color''' descriptors next - what color is it? red, green...
# '''Number Increment''' next - which of the list is it? 001, 002...
# '''Tiling''' and '''Image Type''' descriptors, if needed (file only, not material definition - see below)

If establishing precedent (creating a new '''Size''' descriptor, e.g., "huge"), try to avoid ambiguity and unnecessary overlapping with other descriptors (e.g., "enormous"), and set a good example others will follow.

'''Examples:'''

1. ''slate_large_cracked_grey_001''

This name omits an '''Object Type''' descriptor, instead starting with the '''Material''' descriptor - it is a general, non-specialized texture.

Why is this preferred? Some existing materials are named by quality descriptor first (e.g., 'cracked_slate...'). This is an inconvenience for the user, because they were looking for a 'slate', not a 'cracked'.

2. ''door_wood_battered_005''

This name omits a '''Size''' descriptor and a '''Color''' descriptor.

Why is this preferred? In the case of a model name (which this convention also covers), or a specific object type texture like the above, some existing assets are named by quality descriptor first (e.g., 'battered_wood...'). This is an inconvenience for the user, because they were looking for a 'door', not a 'battered'.

Be sure to rename all your DDS file extensions to a '''lowercase''' '''.dds''' (the Compressonator always creates files with uppercase extension, TDM requires them to be lowercase).

If your texture tiles only in one direction, include the phrase '''tiling_1d''' at the end of the name. If your texture does not tile (repeat) at all, add the phrase '''nontiling'''. So, a normalmap could be names as '''concrete_dirt01_tiling1d_local.tga'''.

Diffusemaps should have no extension to their name. Normalmaps should have a '''_local''' extension at the end of their name. Specular maps should have a '''_s''' extension, the editor images go with an '''_ed''' extension.
{{Things-To-Remember|
* Choose descriptive names for your texture, while following TDM convention
* Add the suffix '''tiling_1d'''/'''nontiling''' to the filename where appropriate
* Diffusemap: '''mytexture.dds''' (note the '''lowercase''')
* Normalmap: '''mytexture_local.tga'''
* Editor image: '''mytexture_ed.jpg''' (max. 256 pixels in size)
* (Optional) Specularmap: '''mytexture_s.dds'''}}

== Move the Texture to the right Location ==
When you upload textures, be sure to upload the files to the right spot. The '''[[Texture Folder Structure]]''' can help you finding the right folder for your texture.

The .dds diffuse and specular go in the '''dds/textures/''' folder structure. The .tga normalmap goes in the '''textures/''' folder structure. Note that there is a peculiarity of the Doom 3 engine not being able to load DDS textures that are more than five folders deep. The deepest level allowed would be something along the lines of dds/textures/darkmod/door/metal/. This is something to be watched out for.
{{Things-To-Remember|
* Move the DDS textures into the '''dds/textures/...''' tree.
* Move the TGA and JPG files into the '''textures/...''' tree.
* Don't save DDS files into folders more than 5 levels deep.}}
== Create your Shader Definition (Material) ==
Your material entry should be added to the .mtr file that has the same name as the folder your texture is saved in. For example, the material entry for a texture saved in '''textures/darkmod/wood/panels''' should be saved in the .mtr file, '''tdm_wood_panels.mtr'''. See also the [[Material File Naming Convention]].

You should name your material entry the same name as your diffuse texture, including the folder path structure (eg, "textures/darkmod/wood/panels/rectangle_oak_face"). (Do not add .tga or .dds to the end, and also skip the dds/ folder prefix.)

The only exception is when multiple shaders are using the same diffusemap, or when your texture doesn't tile (or tiles in only one direction). In the latter case, you would add '''/nontiling/''' or "/tiling_1d/''' to the end of the shader folder (a 'virtual' folder, essentially). ''(The textures used to be separated like that in the actual folder structure, but due to D3's inability to read .dds files five folders deep, they had to be moved.)''
{{Things-To-Remember|
* Create your shader in the correct file (tdm_xxx_yyy.mtr) following the [[Material File Naming Convention]]
* The shader name for tiling textures is the same as the diffusemap
* Nontiling/tiling_1d textures go into a "virtual" subfolder nontiling/ or tiling_1d/
* You don't need to specify file extensions (.dds/.tga/.jpg) to the material defs, this is automatically guessed by the engine.
* You don't need the '''dds/''' folder prefix to reference the DDS textures.
* Be sure to include the frob highlight code (see [[Basic Material File#Add_the_Frob_Highlight_Stage|Basic Material File]])
* You '''must''' include Dark Mod's ambient light stage (see [[Virtual Ambient Light Textures]])}}

== Upload the Textures ==
Once, you have checked your texture in-game (and are pleased with the results), you'll need to upload the files to our SVN repository. This requires that you have a valid username/password for SVN, which you can request from sparhawk.

The .tga of the diffuse and specular is needed as well in case we ever want to make modifications to the texture or new textures based on the old. Opening and resaving .dds files results in loss of detail, so all new versions of textures should be made from the .tga files. So, additional to the textures needed for the engine and editor (diffuse/normal/specular/editorimage) you're encouraged to upload the uncompressed textures to the hires repository.

The hires repository is located at '''<nowiki>https://<InsertDarkmodServerHere>/svn/darkmod_hires/trunk/tga_backup/</nowiki>'''. As only diffuse/speculars are compressed in DDS format, these are the only two that need to be uploaded in TGA format. The TGA files should be named just like the DDS versions and should be located in the analogous folder than they are in the main repository, but below the tga_backup/ folder. For instance tga_backup/textures/darkmod/stone/etc.

The hires TGA can be RLE-compressed to save some space, but this is not too important. Uncompressed TGAs are only important for the textures used by the engine itself.

As last part, it would be nice to have the actual working versions (Photoshop/Gimp source files) stored on the server too. This is of course a large upload, but having the source files is very valuable. For this purpose, there is another repository '''texture_src''' installed at '''<nowiki>https://<InsertDarkmodServerHere>/svn/texture_src/</nowiki>'''.
{{Things-To-Remember|
* Upload the diffuse, normal, (specular,) and editor image to the regular darkmod SVN.
* Upload the (RLE-compressed) TGA diffusemap and specularmap to the darkmod_hires SVN repository (into the '''tga_backup''' subfolder).
* Upload the working source file (PSD/Gimp) to the '''texture_src''' repository.}}
{{tutorial-textures}}
__NOTOC__

Texture Creation - Basic Tutorial

2010-03-24T13:18:53Z

New Horizon: /* Create the diffuse map */

{{tutorial-textures}} {{Original_Reference|SneaksieDave|3814}}
A game like this needs a TON of textures. So I wanted to try to learn how to do this mysterious, wonderous, magick...

Erm, well, it's not magick. Far from it, in fact. This tutorial isn't for those of you who already know how to do this*, and already know it's not magick. This tutorial is for the rest of us, those who have been too scared or lazy to even bother asking "how do I?", like me. (It's the former, honest!)

== Prerequisites ==

You can use Gimp or Photoshop on Windows, for Linux you should use Gimp. So you'll need either of the two programs Gimp/Photoshop and the corresponding set of plugins:

=== Photoshop ===

* [http://developer.nvidia.com/object/photoshop_dds_plugins.html Nvidia normal map plugin]

=== Gimp ===

* [http://nifelheim.dyndns.org/~cocidius/normalmap/ GIMP normalmap plugin]
* [http://www.manucornet.net/Informatique/Texturize.php#download GIMP texturize plugin]
* [http://registry.gimp.org/plugin?id=4816 Gimp DDS plugin]

If you are using Kubuntu/Ubuntu, you can also install the <code>gimp-texturize</code> and <code>gimp-resynthesizer</code> packages.

To compile Gimp plugins from source, install the following packages and their dependecies:

* libgimp2.0-dev
* libgtk1.2-dev
* libglut3-dev (for the DDS plugin)

== Get your source picture ==

This could be anything from a photograph you took, to a free texture download from the internet (see [[Texture Sources]]), to a hand drawn picture, if you're one of those fortunate enough to possess that skill - though we generally prefer to work from photo-reference when possible.

If you do want to take photos, some tips:
* try to shoot on an overcast day; the diffuse light will remove most unwanted shadows
* try to take the photo as perfectly face-on to the surface as you can manage.
If your end result isn't perfect, don't worry, there are ways to fix it (transform->skew, to name one)
* Make sure that all parts of your photo you want to use as texture are in focus (e.g. sharp). Unsharp parts cannot be fixed later, at least not without a big quality loss!
* try to select an area that will be tile-able (if that's what you want)
* try to capture a large area such that you'll have enough to work with, but not so big that your resolution on the final product will suffer

== Create the diffuse map ==

The diffuse map is a tilable (usally) image which gives the color infomation, but does not contain lighting or height information for the texture. It is stored as dds with dxt1 or dxt3 compression for use in Doom 3 and as 24 bit TGA (without RLE) for the hires repository.

If your image has lighting baked in (shadows/highlights), you should remove it: [[Remove Shadows in Source Images]].

This is just a basic tutorial for creating textures. For further information about creating Diffusemaps, read [[Advanced Tips for Creating Diffusemaps]].

=== Photoshop ===

Inspect the source image. If you're going to tile it, try to find a regular repeating area. This is only to make your job easier. You can tile anything, really, but it depends on how much work you want to give yourself. If you don't know what I mean here, at the next step you will.

After you've chosen a rough tile-able area (from here forward I'm going to assume you are doing a tiled texture), crop that area out, and size your image to the desired size ratio. I wouldn't go lower than 1024 resolution at this stage of the work, or you'll start losing picture quality quickly. So set it to 2048X1024, or 1024X1024, etc. The reason we need to fix the size ratio (not the final size) at this stage is for the next step.

==== Set the offset ====

Go to Filter->Other->Offset. You want to set the horizontal and vertical to be exactly half of your cropped picture's width and height. That will make the opposite edges of the texture meet each other in the middle of the view, so you can make it really tile-able.

==== Make the seams disappear ====
See those seams running right down the middle of the pic, vertically and horizontally? You have to make them disappear. Get to know the clone tool. (Google...) There are many other ways to shuffle pixels too, but I'll leave the specifics up to you. This is usually the hardest, most time consuming step.

Once you've blended the lines away, run the Offset filter again to restore the correct layout of your pic, and save it out in a nice high quality (but not too big to manage) format. This is the "diffuse" image. We're using 24bit TGA for TDM.

=== Gimp ===

Use the <code>texturizer</code> or the <code>resynthezier</code> plugin - these are very easy to work with and make manual work almost needless.

== Create a normal map ==

The Normalmap tells the renderer in which direction a corresponding place on the diffusemap is facing, so that it can be shaded according to the present lightsources in the scene. It is stored as uncompressed 24 bit TGA (no RLE!) for use in Doom 3. You will learn the basics about creating Normalmaps here. For further information: [[Normalmaps, How to Make Good Ones]].

=== Photoshop ===

Now that the diffuse is done, using that same pic, open Filter->Nvidia Tools->NormalMapFilter. You'll probably have to play with the values for a while to get a feel for it, and to get a normal map you are happy with. This is a rough approximation method, by no means as accurate as actually modelling a texture (see [[Wall Texture Tutorial]] or [[Creating Textures with Normals out of Models]]), but it works pretty good in most cases. Basically, it will make light areas "high" and dark areas "low". Learn how to manipulate color levels in Photoshop, and you'll be making good normal maps with the Nvidia filter in no time. Generally, use values of 3 or 4 for simple things like woodgrain or nails. Values of 12 or higher can be used for more 3d effects.

If you think about it, there are countless ways to adjust the image (in fact, you're not even restricted to using the diffuse image as the base of the normal map...) to get desired results - inverting colors, brightness and contrast controls, painting over areas, gradients, etc. It's a "feel" thing, so you'll have to develop that for yourself. After creating your desired normal map (try not to make it too blurry, or too sharp, or too bumpy - yuck), save it out as you did with the diffuse image, with "_local" appended.

=== Gimp ===

This is a rough guide by a non-expert as I (fidcal) do it so at least there is something here. It assumes you have made a temporary greyscale image file saved as say nameGrey.tga with the brighter areas representing the high ground and darker means low as described elsewhere ready to make your make normal map. It assumes you've just downloaded Gimp and its Normalmap plugin (ESSENTIAL!), maybe configured it a bit so don't know much about it but just want a dumb list to follow.

* Open Gimp
* Gimp consists of separate floating windows with no main window so select the toolbar window > file menu > and open your greyscale image file.
* You can enlarge/maximize the window and zoom with the mouse wheel if you want.
* Menu > filters > map > normalmap
* On the normal map dialog, Click 3D map preview; it will make more sense then.
* On the normal map dialog, in the 'scale' box there is zero by default which is useless as a default as this seems to be the scale of depth. Enter 50 for a start.
* On the 3D preview dialog there is a window with a panel in it. Grab the panel with your left mouse button and drag it around. Now you should see a rough 3D impression of your image.
* If you have no idea what you're doing (like me) leave the scale at 50 as a reasonable value, otherwise adjust it according to your knowledge. Maybe come back here later if you feel your final result is not deep enough or too deep. Similarly leave the other controls or adjust if you know what you are doing.
* On the normal map dialog click OK.
* On Gimp's image window you should now see your greyscale image has been converted probably blue looking with depressions, eg inverted the heights; that's OK.
* Save as name_local.tga in the correct dark mod texture folder where your main texture is.
* A mini dialog pops up : RLE compression - set this UNchecked, and 'origin at bottom left' - leave this checked. Click OK.
* I had a lot of programs open including Doom so it seemed to hang a long time but eventually saved.
* You close Gimp by closing that toolbar window so I guess that's its nearest thing to a main window.

That's it.

== Create an editor image ==
As the diffusemap is very large it takes some time loading it into the editor, this is why DarkRadiant/DoomEd support the display of lowres editor images replacements. Just resize the diffusemap down to max. 256 pixels and save it in JPG format, but be sure to attach the '''_ed''' suffix.

== Add a specular map ==
The specularmap tells the renderer how shiny a corresponding place on the diffusemap is. It is stored as dds and its dimensions are typically scaled down to be half as big as those of the diffusemap.

If you want a specular map, the process is even more subjective. There are countless ways in Photoshop to adjust color and light level and even invert everything or parts or mask out areas. Specular maps work as such: Darker is rendered as dull, lighter is rendered as shiny. Get it? Think of the possibilities, and have fun with it. You can get some pretty amazing results with just minutes of work. Save that image out as you did the diffuse, '''with "_s" appended'''.

Note that most surface types don't need a specular map. Only shiny surfaces, like metal or wet stone, really need one, while wood, cobbles, canvas, leaves, dirt etc. should not have a specular map.

== Create your material file ==

Create a material for the texture. In the materials folder, locate the material file where you texture fits in best. Then add the following:

textures/your_desired_editor_texture_folder/your_texture_name
{
// Use one of the predefined surface types like stone, glass, wood
stone
// or use this:
// surfaceType 15
// and make the first word in the description below your texture type,
// like so:
// description "foliage" (This is a grass texture)

description "Add here a little description of your texture"
qer_editorimage textures/your_file_folder/your_texture_name_ed

bumpmap textures/your_file_folder/your_texture_name_local
diffusemap textures/your_file_folder/your_texture_name
specularmap textures/your_file_folder/your_texture_name_s

// This is the code required for frob highlighting this texture
{
if ( parm11 > 0 )
blend gl_dst_color, gl_one
map _white.tga
rgb 0.40 * parm11
}
{
if ( parm11 > 0 )
blend add
map textures/your_file_folder/your_texture_name
rgb 0.15 * parm11
}
}

Oh, and on Windows, use Wordpad, not Notepad. That's it. Your new texture should appear in both the editor and in-game.

== Summary ==
So you see, it's really quite simple:
* Crop the desired area
* Make it tileable if necessary
* Generate a normal map
* Generate an editor image
* Create a specular map if you want one
* Include it in a material file
* DONE

The most important thing though, is to obey the [[Texture Guidelines]].

== Further Information ==

* [[Common Texture Mistakes]]
* [[How to add Textures to The Dark Mod]]
* [[Texture Folder Structure]]
* [[Basic Material File]]

== Links ==

=== Photoshop ===

* [http://developer.nvidia.com/object/photoshop_dds_plugins.html nVidia Normal Map PlugIn]

=== Gimp ===

* [http://nifelheim.dyndns.org/~cocidius/normalmap/ GIMP normalmap plugin]
* [http://www.manucornet.net/Informatique/Texturize.php#download GIMP texturize plugin *THIS IS AMAZING*]
* [http://registry.gimp.org/plugin?id=4816 Gimp DDS plugin]

=== Assorted tutorials ===

* [http://www.doom3world.org/phpbb2/viewtopic.php?t=11893 Doom3World texture tutorials]
* [http://www.quake3bits.com/htm/tutorials/creating_bumpmaps_from_images.htm Kat's normal-map making tutorial]
* [http://www.gimp.org/tutorials/Tileable_Textures/ Quick GIMP tutorial for tileable textures]
* [http://www.stormvision.net/index.cfm/act/tutorials/tutorial_ID/1 Another tileable texture tutorial]

What's new in TDM 1.01

2010-02-22T23:54:24Z

New Horizon: /* Sounds */

This article is a work-in-progress and can change before the final release. There are '''no promises''' here. Features may be postponed or removed even if they appear on this list, and regressions may re-introduce bugs after they've been fixed internally. See also the changelog on our bugtracker page: [http://bugs.angua.at/changelog_page.php?project_id=2 Changelog].

== Bugs fixed ==
* [http://bugs.angua.at/view.php?id=1921 #1921]: HUD Font reverts to Doom 3 font after fresh gamesave load.
* [http://bugs.angua.at/view.php?id=1963 #1963]: Double doors sometimes highlight at a distance.
* [http://bugs.angua.at/view.php?id=1968 #1968] Blackjack no longer makes metallic clang when hitting world
* [http://bugs.angua.at/view.php?id=1970 #1970]: Chests went non-solid when frobbed
* [http://bugs.angua.at/view.php?id=1976 #1976]: Shop items get duplicated on "Restart" after dying
* [http://bugs.angua.at/view.php?id=1990 #1990]: No SOUND on TDM after installing a mission, added CVAR (tdm_fm_restart_delay) to issue a delay request to tdmlauncher.
* [http://bugs.angua.at/view.php?id=1996 #1996]: Fixed bug that made shouldered bodies undroppable
* [http://bugs.angua.at/view.php?id=2007 #2007]: Fixed: Location settings did igore the "music volume" slider
* [http://bugs.angua.at/view.php?id=2013 #2013]: AI vertical FOV too high (they could see you through the top of their helmet)
* [http://bugs.angua.at/view.php?id=2067 #2067]: Fixed bug when using shop_skip 1 in FMs.
* [http://bugs.angua.at/view.php?id=2072 #2072]: Rats (and other small animals) could be shouldered
* [http://bugs.angua.at/view.php?id=2075 #2075]: AI were alerted when they took falling damage
* [http://bugs.angua.at/view.php?id=2083 #2083]: Small items like candles, candle holders, rocks etc floated on water instead of sinking
* [http://bugs.angua.at/view.php?id=2093 #2093]: Fireplace_arch was missing its texture
* [http://bugs.angua.at/view.php?id=2117 #2117]: frob_peer hilite does not sync.
* [http://bugs.angua.at/view.php?id=2119 #2119]: Player's run footfall sounds are played while shouldering a body
* [http://bugs.angua.at/view.php?id=2120 #2120]: Arrows stuck in AI head can collide with ragdoll causing midair suspension
* [http://bugs.angua.at/view.php?id=2122 #2122]: Ragdoll AI not getting pushed back by impact with plate armor
* [http://bugs.angua.at/view.php?id=2125 #2125]: Dead AI play failed KO speech and twitch when hit by blackjack
* [http://bugs.angua.at/view.php?id=2128 #2128]: atdm:moveable_holder_tall_plus_candle3_unlit model alignment error
* [http://bugs.angua.at/view.php?id=2114 #2114]: Running when aiming results in footstep frequency being too fast
* Fixed savegames getting to huge sizes, leading to out-of-memory or crashes
* Fixed a few crashes and memory errors
* Fixed: Crash with ATI cards when viewing certain models (like the marble column)
* Fixed: Location settings did not work with "fast" ambient method
* Melee controls now more responsive
* Fixed blackjack bug where player could hit low ceilings
* Fixed archer bows blocking blackjack attempts
* Fixed bug where some close-range melee attacks neglected armor
* Altered sword thrust collision physics to match up better with visible sword model
* Minor fixes to models and textures (e.g. inverted normals)
* Added a bunch of missing editor images for models (STiFU).
* AI will not be able to see as high without actually tilting their head up.
* AI now have individual FOVs, so a one-eyed guard actually won't see you on their bad side, and hooded AI can't see you through their hood.

== Features added ==
* [http://bugs.angua.at/view.php?id=2123 #2123]: In-game objectives display
* A lot new skins for: dirty fireplaces, unlit lamps etc.
* New script events for: get/setDroppable, isEntityHidden, Melee etc.
* Support for "skin_unlit" and "skin_lit" on light entities
* New "unbindOnAlertIndex" spawnarg on attached entities, to make AI drop them when alerted
* Crouch indicator: Lightgem "wings" squash down slightly when crouch mode is on (helpful when climbing)
* AI have a combat skill level now: novice, trained, skilled
* added Difficulty Slider for combat in menu
* [http://bugs.angua.at/view.php?id=2024 AI can be set to drop attached objects on alert]
* greater flexibility added to absence markers
* [http://bugs.angua.at/view.php?id=2012 #2012]: GC's movetype-specific metal footstep sounds are in-game
* [http://bugs.angua.at/view.php?id=2015 #2015]: Added console commands to control logging to darkmod.log
* [http://bugs.angua.at/view.php?id=2002 #2002]: FM Installer Code checks required version of Mission to be installed, information can be added to darkmod.txt in the FM package.
* [http://bugs.angua.at/view.php?id=1977 #1977]: FM Installer Code considers ZIP files as well as PK4s now
* [http://bugs.angua.at/view.php?id=1984 #1984]: FM Installer Code needs to replace dashes with underscores on creating the fms subfolder
* [http://bugs.angua.at/view.php?id=2080 #2080]: Doors have a larger sound radius now.

== AI added ==

* added two zombie types with various skins, as well as "sleeping" behaviour
* added spiders and spider children
* added new elite guard character
* added elite guard helmet (immune to KOs)
* added skeleton AI
* added revenant character
* added male beggar character
* added male pagan character

== Entities added ==

* A lot of new [[combo entities]] have been added:
** fireplaces,
** static torches,
** statues with torch in hand,
** campfires, bucket and bonfires,
** electric streetlights,
** wall-mounted lamps and torches,
** geodes with pulsating light,
** bottles+candle,
** skulls+candle etc.
* new colored torch flames: blue, green, orange
* new fireflames: white and black smoking, smouldering ones, large and huge bonfires, bucketfire
* a few new model props (eg, saw, wall-light)
* climbable ragdoll chains
* [http://bugs.angua.at/view.php?id=2110 Bug #2110] [[Loot paintings]]

== Sounds ==

* changed AI footsteps to mono (so the direction of sound is accurate)
* reduced volume of player footsteps
* increased sound radius of doors
* changed sound of arrow equip/un-equip
* changed sound of bow draw
* changed player submersion in water bubble sound

Added Dario D's ambient sound contributions.

* Environmental Sound Shaders added
** animal_crickets_birds01, animal_crickets04, animal_crickets05, animal_dog03, animal_frog03, animal_night_bird01, animal_owl04, animal_owl05, animal_owl06
** machine_sparks01
** music_harp01, music_harp02, music_bum_bum01, music_bum_bum02
** weather_thunder04, weather_thunder05
* Ambient Sound Shaders added
** drone01, drone02, drone03a, drone03b, drone05a, drone05b
** hit01a, hit02b, hit03a, hit03b
** hum01, hum01b, hum02, hum03, hum04, hum05_loop, hum05_loop_b, hum06_loop, hum06_loop_b, hum07_loop, hum07_loop_b, hum08

== Textures ==
Added STiFU's, Renzatic's and Baddcog's textures, including the following shaders:
STiFU:
* textures/darkmod/door/wood/board_brown_nails_hinge
* textures/darkmod/metal/detailed/threadplate_large_dirty
* textures/darkmod/roof/slate_cracked_large_greyblue
* textures/darkmod/roof/slate_cracked_large_greyblue_shiny
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey_wet
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey_wet
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_even
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_rough
* textures/darkmod/stone/flat/tiles_ceramic_large_ornate_old_blue
* textures/darkmod/stone/flat/tiles_large_dirty_cracked
* textures/darkmod/stone/flat/tiles_large_dirty_cracked_greasy
* textures/darkmod/stone/natural/rock_large_rough_grey
* textures/darkmod/stone/natural/rock_large_rough_grey_greasy
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old_greasy
* textures/darkmod/wood/boards/polished_shiny_large_red
* textures/darkmod/wood/boards/rough_wood_large_brown
* textures/darkmod/wood/boards/rough_wood_large_brown_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark_glossy
* textures/darkmod/wood/boards/roof_framework_boards_large_old_brown
* textures/darkmod/wood/boards/roof_framework_boards_large_old_green
* textures/darkmod/roof/shingles_blue
* textures/darkmod/roof/shingles_blue_shiny
* textures/darkmod/roof/shingles_red_shiny
* Improved: textures/darkmod/roof/shingles_red
* textures/darkmod/nature/bones/skull_panels_dirty
* textures/darkmod/nature/bones/bone_wall
* textures/darkmod/nature/bones/tiling_1d/trim_bones
Baddcog:
* textures/darkmod/roof/rooftiles_ceramic_blue
* textures/darkmod/roof/rooftiles_ceramic_brown
* textures/darkmod/roof/rooftiles_ceramic_red
Renzatic:
* textures/darkmod/plaster/tiling_1d/plaster_rot01
* textures/darkmod/nature/dirt/dirt_packed_grey
* textures/darkmod/stone/brick/bricks_ind_grey
* textures/darkmod/stone/brick/bricks_mossy01
* textures/darkmod/stone/brick/stone_rough_segmented
* textures/darkmod/stone/cobblestones/cobblestone_vert_grey
* textures/darkmod/stone/sculpted/tiling_1d/concrete_trim01
* textures/darkmod/wood/boards/wood_rot_planks01
* textures/darkmod/wood/boards/wood_rot_planks02
* textures/darkmod/wood/panels/tiling_1d/wood_old_trim01
* textures/darkmod/wood/panels/tiling_1d/wood_rot_trim01

== See also ==

* [http://thedarkmod.com/downloads.php Download TDM]

Installation

2009-11-05T12:48:00Z

New Horizon: /* Installing and Running Fan Missions */

{{important|headline=Important|text=This article tells you how to install the full version of [[The Dark Mod]]. If you are installing one of the demos: ''Thief's Den'' or ''Saint Lucia'', then you can ignore this page. Instead, follow the instructions here: [[Thief%27s_Den#Installation|Thief's Den Installation]] or [[Saint_Lucia|Saint Lucia Installation]].}}

__TOC__

{{important|headline=Important|text=You'll need to install the [http://www.dramthethief.com/darkmod/files/DOOM3-1.3.1.exe Doom 3 patch 1.3.1] ([http://72.8.59.188/TheDarkMod/Files/DOOM3-1.3.1.exe mirror]) otherwise the Mod won't run.}}

== Prerequisites ==
=== System Requirements ===
At a minimum, you'll need a machine which is capable of running the Doom 3 game. The team recommends adding more RAM and a bit more CPU to the basic requirements, however, otherwise running the larger maps will be difficult.

Supported operating systems are Windows (2000/XP/Vista/Win7) or Linux. Doom 3 currently supports Macs, but The Dark Mod has not been ported to that platform.

=== Install Doom 3 Patch 1.3.1 ===
In order to install The Dark Mod, you need to have the v1.3.1 patch for Doom 3 installed. See the [[#Weblinks|download section below]] for links.

Linux users: make sure that the install path for Doom 3 is all lowercase (e.g. <code>/usr/local/lib/doom3</code>).

=== Space Requirements ===
This is only an estimation of the space requirements needed to play TDM missions. Keep in mind that development on TDM is going to continue over time and new stuff will be added all the time.

* For the D3 installation you roughly need 1.5 GB.
* For the base TDM 1.00 package you need another 1.6 GB.
* Plus a variable amount of space you need for downloaded FM packages.
* Plus a variable amount of space for screenshots, savegames, etc.

'''So the minimum can be estimated to be slightly above 3 GB.'''

It's difficult to give numbers about FM package size, as this depends on the amount of custom content the FM author is packing in. Usually FMs are very small, if they're using the stock TDM content (1 to 10 MB). Note: FMs are in PK4 (i.e. ZIP) format, so textures and mission files are shipped in compressed form.

Savegames are of varying size, they can be up to 10-20 MB per save depending on the size of the FM you're playing, plus a small 700 kB screenshot generated per savegame.

Screenshots depend on the screen resolution you're using (~2 MB per shot).

=== References ===
See the article [[Known System Configurations]] for a (hopefully growing) collection of system configurations and the corresponding user feedback.

== Installing The Dark Mod ==

===Install on Windows===
You need a working and patched Doom 3 installation on your hard drive. These steps will assume that you installed Doom 3 in the folder <tt>C:\Games\Doom3</tt>.
# Create a '''darkmod''' folder in your Doom 3 directory, like this: '''C:\Games\Doom3\darkmod'''
# Download the [http://www.bloodgate.com/mirrors/tdm/pub/pk4/tdm_update_win.zip TDM Updater] from one of our mirrors.
# Extract the '''tdm_update.exe''' from the downloaded ZIP and copy it into your '''C:\Games\Doom3\darkmod''' directory.
# Run tdm_update.exe. The installer will connect to our download mirrors and start the download process.
# Be patient and wait. The download weighs about '''1.4 GB''' will take a while.
# If you see error messages about corrupt files, please try to run the updater again, these massive downloads are sometimes failing.
# After installation, you'll find an executable <tt>tdmlauncher.exe</tt> in your darkmod folder, i.e. <tt>C:\Games\Doom3\darkmod\tdmlauncher.exe</tt>. Use this to start The Dark Mod.

===Install on Linux===

# You need the native version of Doom 3 installed and patched to v1.3.1, [[#Weblinks|see below]] for download links and install instructions.
# Since there is no 64 bit version of either Doom 3 or The DarkMod, on 64 bit systems you also need the 32 bit compatibility libraries installed. On some distributions like SuSE, these are included in the default installation, but on Kubuntu/Ubuntu you need to install the package called <code>ia32-lib</code> and all its dependencies. Otherwise, even the installer for Doom 3 will fail to run.
# Create a folder <tt>~/.doom3/darkmod</tt> in your home directory. Mind the dot in the path.
# Download the Linux version of the [http://www.bloodgate.com/mirrors/tdm/pub/pk4/tdm_update_linux.zip TDM Updater] and save it to <tt>~/.doom3/darkmod/</tt>
# Extract ''tdm_update.linux'': <tt>unzip tdm_update_linux.zip</tt>
# Make ''tdm_update.linux'' executable: <tt>chmod +x tdm_update.linux</tt>
# Run the updater: <tt>./tdm_update.linux</tt> It will connect to our mirrors and download the packages for you.
If you get an error about GLIBCXX_3.4.9, delete or rename the files <tt>/usr/local/games/doom3/libstdc++.so.6</tt> and <tt>/usr/local/games/doom3/libgcc_s.so.1</tt>.

=== Alternative download methods ===

If you have troubles running tdm_update, you can see if [[tdm_update|this page]] helps you. Otherwise, you can
also use other download methods to get a initial copy of the mod. Visit [[http://www.mindplaces.com/darkmod/downloads.php]].

== Launching The Dark Mod ==
Use the '''tdmlauncher''' application to run The Dark Mod. This small application will take care of launching the Doom 3 process with the correct command line arguments. TDM Launcher is available for both Windows and Linux.

* '''Windows:''' <tt>C:\Games\Doom3\darkmod\tdmlauncher.exe</tt>
* '''Linux:''' <tt>~/.doom3/darkmod/tdmlauncher.linux</tt>
** Before it can be run the first time, you must make '''tdmlauncher.linux''' executable: <br /><tt>chmod +x ~/.doom3/darkmod/tdmlauncher.linux</tt>

Note: The tdmlauncher application will also be used by the game itself when installing/re-installing/uninstalling FM packages, so don't ever think about deleting that file.
* See also [[Creating Desktop Shortcuts for TDM]].
* See also [[tdmlauncher in Gentoo Linux]]

=== Passing custom command line arguments ===
Some people like to have custom command line arguments to the game, which is supported by tdmlauncher. Open the <tt>dmargs.txt</tt> in your darkmod folder and add any arguments you'd like TDM Launcher to pass to the Doom3 command line.
* See also [[Doom3 command line arguments]].

=== Troubleshooting TDM Launcher ===
The tdmlauncher executable will generate a small logfile <tt>tdmlauncher.log</tt> each time it is invoked. The log file is located right next to the executable and might give some useful insight if the game fails to load.

== First Startup ==
* Please take your time to read through [[The Dark Mod Gameplay]] article to get familiar with the game.
* TDM ships with a Training Mission which is designed to introduce you to TDM gameplay. You should start this mission first even if you've played stealth games before.
* Adjust the settings in the menus, like screen resolution and gameplay settings.
* See also the [[Performance Tweaks]] article to make TDM run a little bit faster if you're on a lower end machine.

== Installing and Running Fan Missions ==
Go to www.thedarkmod.com to get hold of mission packages available for The Dark Mod. Each FM is contained in a PK4 file, which contains all the files necessary to run the mission.
# Download the mission PK4 - (IE7 renames PK4s to Zip. Do not unzip. Rename the FM zip to PK4)
# Drop the file into the fms/ folder, e.g. <tt>C:\Games\doom3\darkmod\fms\</tt>
# Launch The Dark Mod
# The mission should now be listed in your ''New Mission'' menu.
# Highlight the mission and hit ''Install'' to install. TDM will automatically restart.
# Hit ''New Mission'' and then ''Start this Mission'' on the upper left.
See the full article [[Installing and Running Fan Missions]] for a detailed explanation.

== Weblinks ==

* Doom [http://72.8.59.188/TheDarkMod/Files/DOOM3-1.3.1.exe v1.3.1 patch for Windows] ([http://www.dramthethief.com/darkmod/files/DOOM3-1.3.1.exe mirror])
* Doom v1.3.1 for Linux: [ftp://ftp.idsoftware.com/idstuff/doom3/ FTP] [http://zerowing.idsoftware.com:6969/ BitTorrent]

==DoomConfig.cfg Howto==

Game configuration settings are stored in the file DoomConfig.cfg but there is one in every FM folder as well as base and darkmod folders. Normally you just use the Settings menu but if you want to manually change or add any settings you should read [[DoomConfig.cfg]] to see how they all integrate together or you may lose some settings if you edit the wrong way.

== See also ==

* [[tdm_update]] - if you have troubles with running the installer/updater
* [[FAQ]] - Frequently Asked Questions and their answers

{{installation}}

FAQ

2009-10-19T17:36:41Z

New Horizon: /* Textures are missing, screen mostly black */

Virtual Darkness

2009-10-11T21:41:20Z

New Horizon: /* Ambient Light */

''written by Fidcal''

'''Note:''' The '''[[Location Settings]]''' article shows you an easy-to-use and general system to get different ambient light levels and colors for each location/zone the player is in. Since this system also covers different ambient sounds and script calls at zone boundaries, you should really use it.

This article here is just a general introduction into "ambient light settings".

==Introduction==

Being a stealth game system and as its name implies, most Dark Mod missions will take place at night and require darkness as cover. Generally, absolute blackness is unpopular in this type of game and is not recommended. It can make navigation difficult, uncomfortable, and gives an impoverished visual display. Instead, very low ambient light is used to represent blackness. We call this virtual darkness. This main ambient light should not be so dark that the player cannot make out some detail of nearby surfaces textures. Yet because it represents complete darkness it should not be so light that it seems strange that in-game characters cannot see you (see later.)

Ambient light can be coloured to provide atmosphere and realism depending on the environment.

== Brightness Standard ==

From Release 1, The Dark Mod includes a test map (may be included in a trainer mission.) for both players and mappers to standardise their gamma and brightness settings. I emphasise that this does '''not''' force all missions to be the exact same brightness. What it does is provide a standard setting so everyone can know what a particular mission is intended to look like. If a player then prefers to generally have their settings darker or brighter then at least they know. Likewise, if a mapper wants to produce a darker or brighter mission then they are free to do so but at least they will not do it without knowing. The advantages of all this is that in most cases players will not have to keep fiddling with the brightness setting for every individual mission.

==Ambient Light==

The main ambient light does illuminate the player but if kept to the recommended low levels (6, 7, or 8) this is a negligible amount in which AI characters cannot see the player and thus represents complete darkness without blinding the player.

Unlike normal lights, ambient light does not by default fade to the edge of its radius but is the same constant brightness throughout. Rich variation of fading or patterning can be introduced with a light texture. For general use, ambientLightnfo is recommended as it has no patterning and so its brightness is consistent throughout its volume. Regard it as the one to use by default.

Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.

==Virtual Ambient Light==

All lights in Dark Mod are dynamic, real-time, having the potential to vary in-game and cast shadows. Naturally this affects performance and having too many lights close together is likely to reduce frame rates so care must be taken. This applies to the main ambient light too which naturally covers all surfaces.

To improve performance on some low-end systems, Dark Mod textures can simulate the main ambient light. This feature pre-calculates how much textures should be illuminated once only instead of continuously during gameplay. Players can select either method so those with faster machines can use the true ambient light which gives better quality.

==Enabling Virtual Ambient Light==

All that mappers need to do to allow players to select virtual ambient light is to name their main ambient light '''"ambient_world"'''. That's it. If the player selects this feature then Dark Mod takes the color/brightness values of that light and passes it to all the textures then switches off that ambient light. It is therefore important for mappers to do this to provide the best performance for players with slower machines.

Note: Some special materials have a background texture plus detail that is only visible with a real ambient light, for example, darkmod/stone/sculpted/corpse. The mapper can place normal lights or local ambient light for those surfaces where possible or leave them with their background texture.

== See also ==

* The [[Location Settings]] article.

{{tutorial-lighting}}

Virtual Darkness

2009-10-02T22:24:43Z

New Horizon: /* Ambient Light */

''written by Fidcal''

'''Note:''' The '''[[Location Settings]]''' article shows you an easy-to-use and general system to get different ambient light levels and colors for each location/zone the player is in. Since this system also covers different ambient sounds and script calls at zone boundaries, you should really use it.

This article here is just a general introduction into "ambient light settings".

==Introduction==

Being a stealth game system and as its name implies, most Dark Mod missions will take place at night and require darkness as cover. Generally, absolute blackness is unpopular in this type of game and is not recommended. It can make navigation difficult, uncomfortable, and gives an impoverished visual display. Instead, very low ambient light is used to represent blackness. We call this virtual darkness. This main ambient light should not be so dark that the player cannot make out some detail of nearby surfaces textures. Yet because it represents complete darkness it should not be so light that it seems strange that in-game characters cannot see you (see later.)

Ambient light can be coloured to provide atmosphere and realism depending on the environment.

== Brightness Standard ==

From Release 1, The Dark Mod includes a test map (may be included in a trainer mission.) for both players and mappers to standardise their gamma and brightness settings. I emphasise that this does '''not''' force all missions to be the exact same brightness. What it does is provide a standard setting so everyone can know what a particular mission is intended to look like. If a player then prefers to generally have their settings darker or brighter then at least they know. Likewise, if a mapper wants to produce a darker or brighter mission then they are free to do so but at least they will not do it without knowing. The advantages of all this is that in most cases players will not have to keep fiddling with the brightness setting for every individual mission.

==Ambient Light==

The main ambient light does illuminate the player but if kept to the recommended low level this is a negligible amount in which AI characters cannot see the player and thus represents complete darkness without blinding the player. Sometimes it may be necessary to use more ambient than another level and in turn brighten the lightgem more than it should in what is supposed to be total darkness. In this case adjust your light gem with tdm_lg_adjust in the console, try small increments of -.05, or -.04...just until the lightgem is barely lit while standing. Once you've settled on your lightgem setting for total darkness, add lightgem_adjust to the worldspawn entity in your map.

Unlike normal lights, ambient light does not by default fade to the edge of its radius but is the same constant brightness throughout. Rich variation of fading or patterning can be introduced with a light texture. For general use, ambientLightnfo is recommended as it has no patterning and so its brightness is consistent throughout its volume. Regard it as the one to use by default.

Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.

==Virtual Ambient Light==

All lights in Dark Mod are dynamic, real-time, having the potential to vary in-game and cast shadows. Naturally this affects performance and having too many lights close together is likely to reduce frame rates so care must be taken. This applies to the main ambient light too which naturally covers all surfaces.

To improve performance on some low-end systems, Dark Mod textures can simulate the main ambient light. This feature pre-calculates how much textures should be illuminated once only instead of continuously during gameplay. Players can select either method so those with faster machines can use the true ambient light which gives better quality.

==Enabling Virtual Ambient Light==

All that mappers need to do to allow players to select virtual ambient light is to name their main ambient light '''"ambient_world"'''. That's it. If the player selects this feature then Dark Mod takes the color/brightness values of that light and passes it to all the textures then switches off that ambient light. It is therefore important for mappers to do this to provide the best performance for players with slower machines.

Note: Some special materials have a background texture plus detail that is only visible with a real ambient light, for example, darkmod/stone/sculpted/corpse. The mapper can place normal lights or local ambient light for those surfaces where possible or leave them with their background texture.

== See also ==

* The [[Location Settings]] article.

{{tutorial-lighting}}

Doom 3 Editor Modes

2008-03-09T17:12:20Z

New Horizon: /* One more. You can guess what this does... */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:12:08Z

New Horizon: /* For the Darkmod Particle editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:11:55Z

New Horizon: /* For the Darkmod Light editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:11:44Z

New Horizon: /* For the Darkmod articulated figures editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:11:24Z

New Horizon: /* For the Darkmod sound editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:11:05Z

New Horizon: /* For the Darkmod declaration and script editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:10:54Z

New Horizon: /* For the DarkMod GUI editor in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:10:35Z

New Horizon: /* For the Dark Mod map editor (Doom3 Radiant) in desktop mode */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Doom 3 Editor Modes

2008-03-09T17:10:05Z

New Horizon: /* Using Doom3 Radiant with Dark Mod */

{{Original_Reference|jay_pettit|315}}

== Fixing Full Screen Mode ==
The game starts in a small window after using the editor because the shortcut for the editor should contain a command to start the editor in desktop mode. (trying to use the editor full screen at 640x480 or 800x600 is a no fun)

Find the shortcut you use for the game (not the editor) right click and select properties. In the Target: box add set r_fullscreen 1 on the end. It should look something like this...
d:\games\doom3\doom3.exe set r_fullscreen 1
That reverses the command passed by the editor shorcut. If you are already passing a command with the short cut, ie set fs_game DarkMod then you'll also need to put a '+' in there, like this:
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1
That will start The Dark Mod (not doom3, you'll have to select doom3 in the Mods menu to play the original) in full screen mode.

== Using Doom3 Radiant with Dark Mod ==
Also worth doing is setting up the editor shortcut so that it loads DarkMod content along side the original Doom3 content when it starts. Right click on your editor short cut and add +set fs_game DarkMod on the end of the Target: ie.
d:\games\doom3\doom3.exe +set com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod

== Spaces and install paths ==
As a general rule of thumb: '''no spaces or capital letters in the paths.'''

Having spaces in your Doom3 install path should not affect your ability to play Doom3 or The Dark Mod. It will adversly affect your ability to edit the DarkMod with some of the editing tools. Seeing as we are developers you know what you have to do...

C:\Program Files\Doom 3

...is no use. There is a space in Program Files and in Doom 3

c:\doom3

is fine. So is:

d:\games\doom3

All clear? Good

== Starting Doom 3, The Dark Mod and the Editors from Shortcuts ==
Change the Target: field in the Shortcut properties dialogue box to...

=== For Doom3 in full screen mode ===
d:\games\doom3\doom3.exe set r_fullscreen 1

=== For The Dark Mod ===
d:\games\doom3\doom3.exe set fs_game DarkMod

=== For The Dark Mod in full screen mode ===
d:\games\doom3\doom3.exe set fs_game DarkMod +set r_fullscreen 1

=== For the Dark Mod map editor (Doom3 Radiant) in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editor +set fs_game DarkMod
(or type editor in the Doom3 console)

=== For the DarkMod GUI editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editGUIs +set fs_game DarkMod
(or type editGUIs in the Doom3 console)

=== For the Darkmod sound editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editSounds +set fs_game DarkMod
(or type editSounds in the Doom3 console)

=== For the Darkmod declaration and script editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editDecls +set fs_game DarkMod
(or type editDecls in the Doom3 console)

=== For the Darkmod articulated figures editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editAFs +set fs_game DarkMod
(or type editAFs in the Doom3 console)

=== For the Darkmod Light editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editLights +set fs_game DarkMod
(or type editLights in the Doom3 console or press j in radiant)

=== For the Darkmod Particle editor in desktop mode ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editParticles +set fs_game DarkMod
(or type editParticles in the Doom3 console)

=== One more. You can guess what this does... ===
d:\games\doom3\doom3.exe com_allowConsole 1 +set r_fullscreen 0 +editPDAs +set fs_game DarkMod

Obviously you'll need to adjust the path to something more appropriate if you installed Doom3 somewhere other than d:\games\doom3

[[Category:Editing]]

Thief's Den

2008-01-21T00:36:06Z

New Horizon: /* Download */

[[Image:Thiefs den splash.jpg|right]] Welcome to this short mission demo of [[The Dark Mod]]. Thief's Den is just a few rooms but it is a complete, fully playable mission, and includes a good selection of the main Dark Mod features. Keep in mind that The Dark Mod is still a work in progress and this is reflected in the demo. Voices are temporary placeholders, for example, and AI behaviour is not yet fully developed. You will certainly find bugs and glitches but we hope that doesn't spoil your enjoyment too much.

Any flaws or failings in this demo do not necessarily indicate limitations in The Dark Mod's potential but just this particular demo — which was originally begun as a very rough accompaniment to a mission development tutorial. It was never intended for release as a playable mission but was modified into a workable game so everyone could see the current state of progress and have some fun.

{{Important|headline=Important|text=We recommend you start the download then please read through this page and especially [[Thief's Den Gameplay]] while downloading. You cannot complete the mission without being aware of new features described on that page.}}

__TOC__
== Download ==
Choose a download mirror below. The download is about 200 Mbyte and works for both Windows and Linux. It's a self-extracting 7-zip archive, not a fully-fledged installer.

{{Important|headline=Important|text=
<br>
When the downloaded file does report errors during extraction, your download got corrupted, and you '''MUST''' download the file again. A package extracted only half or with errors will '''NOT''' run properly.

If you are unsure whether you got the right file, either use the torrent (it checks the file to be correct), or compare the [http://en.wikipedia.org/wiki/md5sum md5sum] of the download to <code>d162dfdb7b1c9f9a9d0aaac915a75099</code>.}}

'''Mirrors:'''
* [http://208.49.149.118/TheDarkMod/release/thiefs_den_v1.0.exe Darkmod FTP] (might be slow)
* [http://www.shadowdarkkeep.com/missions/thiefs_den_v1.0.exe Shadowdark Keep] (thanks to Komag!)
* [http://www.southquarter.com/fms/data/thiefs_den_v1.0.exe Southquarter] (thanks to Brethren!)
* [http://bloodgate.com/mirrors/tdm/ bloodgate.com] (North America, thanks to Tels)
* [http://www.thirdfilms.com/thiefs_den_v1.0.exe Third Films] (Thanks to Godismygoldfish)

* '''Torrent:''' [http://bloodgate.com/mirrors/tdm/pub/thiefs_den_v1.0.exe.torrent thiefs_den_v1.0.exe.torrent] (thanks to everybody helping to distribute)

== Installation ==
{{important|headline=Summary:|text=Don't be put off - all you need is Doom 3 installed with patch, extract our download into the Doom folder, then make/modify a desktop shortcut and you're playing!}}

You'll need the following to play the Thief's Den:
# Windows or Linux
# About '''500 Mbytes''' free disk space
# At least '''512 Mbyte''' system memory, better are '''1024 Mbyte''' or more
# A grafic card with at least '''64 Mbyte''' video memory, better are '''128 Mbyte''' or more
# A working Doom 3 installation
# Doom 3 must be patched to 1.3.1. You can download the correct patch (20 Mbyte) here:
#* '''Windows''': Doom [http://208.49.149.118/TheDarkMod/Files/DOOM3-1.3.1.exe v1.3.1 patch for Windows]
#* '''Linux''': Doom v1.3.1 for Linux: [ftp://ftp.idsoftware.com/idstuff/doom3/ FTP] [http://zerowing.idsoftware.com:6969/ BitTorrent]

Already patched Doom 3 before reading this? Make sure you have the correct version of the 1.3.1 patch. See the [[#FAQ|FAQ]] below.

=== Windows ===

Now proceed with the following steps. Substitute your own Doom 3 path for <tt>C:\games\doom3</tt>.

# [[#Download|Download]] thiefs_den.exe and copy it to <tt>C:\games\doom3</tt>.
# Run thiefs_den.exe. A thiefs_den folder will be created.
# In <tt>C:\games\doom3\thiefs_den</tt> is a file called <tt>DevIL.dll</tt>. You MUST copy this into your <tt>C:\games\doom3</tt> folder OR your <tt>C:\WINDOWS\system32</tt> folder (where it can be shared by other applications. If there is already one there then use the newest date.)
# Now you'll need to create a shortcut to the Thief's Den demo:
## Copy the existing Doom 3 shortcut on your desktop. Rename the copy "Thief's Den".
## Right-click, choose Properties and edit the command line. It should read
C:\games\doom3\DOOM3.exe +set fs_game thiefs_den

You're done! All you need to do is double-click the shortcut to run the demo. But before you do, '''please take a minute to read [[Thief's Den Gameplay]] for information on how to actually play The Dark Mod''' (many features will be familiar to Thief players, but there are important differences).

=== Linux ===

* [[#Download|Download]] thiefs_den.exe and copy it to the <code>.doom3</code> folder in your home directory. This directory might not be visible if you use a file manager like Konqueror, so use a console, Midnight Commander, or type ".doom3" into the location bar in Konqueror to navigate there.
* ''Either:''
*# Right-click on <tt>thiefs_den.exe</tt> and select "Open with Wine Windows Emulator" from the menu. Click OK and wait for the package to extract.
* ''Or:''
*# Install the package '''p7zip'''
*# In a console, type:
*# <tt>cd ~/.doom3</tt>
*# <tt>7z x thiefs_den.exe</tt>
* Copy the existing Doom 3 shortcut on your desktop to a new one and rename it to "Thief's Den".
* Right-click, open the properties of that shortcut, go to the "Application" or "Launcher" tab and edit the command line. It should read:
/usr/local/games/doom3/doom.x86 +seta com_allowConsole 1 +set fs_game thiefs_den
* Double-click the shortcut to run the game.
** If it doesn't start, use your package manager to install '''libdevil1'''
* Open the Doom 3 console using the key below the Escape key ({{key|~}}) on US keyboards), and compile the map by typing: <tt>dmap thiefs_den</tt>
* Click "Start Mission" to start the game.

== Playing Thief's Den, Settings ==

For information on changing settings, and on unique features of The Dark Mod and stealth gaming in general, see [[Thief's Den Gameplay]].

Note that you shouldn't expect The Dark Mod to run at the same settings as Doom3. TDM does far more processing, and uses higher resolution graphics, than Doom3 did. If your computer is close to the minimum specs to play Doom3, you will unfortunately have a laggy experience (or will have to turn your video settings down) with the demo.

== The Mission, Objectives, Loot Count ==

You play a thief who has been double-crossed by another! Can you retrieve your ill-gotten gains and incriminate your adversary to divert the attention from you of the ruthless city watch? Full briefing and objectives are shown at the start of the mission.

You can play stealthily or use the weapons at your disposal to make it easier. There are no difficulty levels yet but as an extra challenge this mission can be ghosted without using any weapons including rope arrows.

End of mission statistics are not implemented yet. Total loot count for Thief's Den is 904. Good luck!

== Feedback ==
Of course we're anxious to hear your impressions about our Thief's Den Pre-Beta Release. There is a public feedback & discussion thread open in our forums: [http://modetwo.net/darkmod/index.php?showtopic=7082 Pre-Beta Discussion]. Please drop by and let us know what you think.
{{Important|headline=That being said,|text=don't rush into the forums and spend an hour writing up detailed bug lists of what's working and what you think needs fixing. It's very likely that we are already aware of these problems. The list below is only a small sampling of things we have yet to address.}}
Crashes and installation help requests are of course something different, feel free to contact us, but be sure to check the FAQ on this page first.

== Known Issues and Bugs ==

'''Please read before posting feedback!'''

The Dark Mod is not slated for a beta-release until the end of 2008, so this demo has plenty of incomplete features and known issues/bugs. In addition, many values (like mantling height, walking speed, volume of sounds, visual acuity of AI, etc) are not necessarily at their final settings. Here are a few of the more common issues you may encounter:

'''AI WIP issues:''' The vocalizations for the AI are placeholders, so don't expect much. Many of the animations (like the walk animation) are also placeholders, and many animations are not yet included. The Thug model has some imperfections that are known issues. The Thief model has a field of view that is oriented improperly, meaning he can sometimes see things at angles he shouldn't be able to.

AI intelligence is far from perfect. They still have problems pathfinding sometimes, and may get stuck on doors and KO'd bodies. They are also missing a ‘searching’ animation, so they will sometimes walk, run, and then walk again while looking around.

AI do not react to some environmental factors (like getting a crate thrown at them or hearing an elevator) that they should.

'''AI Weapons Float:''' It is a known issue that AI weapons don’t always stay attached to the AI’s hands when attacking.

'''AI Shadow:''' The shadows of AI occasionally get cut-off, usually at the head, making the shadow look weird. This is particularly noticeable with characters carrying or standing near a lightsource.

'''Sounds:''' Some sound effects are placeholders. Collision sounds (where things bump into other things) are especially poor. It is a known issue that the player’s footsteps are somewhat irregular.

'''Bow Aiming:''' The lack of a bow-sight is intentional. However, the bow currently is offset slightly—the arrow actually goes up a bit from where you are aiming, as if you were ‘lobbing’ your shot. This is a known (minor) issue that needs to be fixed, but it shouldn't cause too many problems in the meantime.

'''Subtle Highlighting:''' The "froblight" effect that highlights an object is occasionally difficult to see, especially on bright-coloured objects. This needs to be tweaked individually, eventually.

'''Objects Not Moving:''' Not really a mod issue, but in the map there are objects that look like they should probably move if you bump them (like the boots or the wine-bottles), but they don't. Many objects have intentionally been left as static for this map.

'''Particle effects cut off:''' Sometimes particle effects (like splashes from water arrows or gas clouds) are cut off or flicker when they occur at particular angles to the player. This is a purely cosmetic issue we have yet to track down.

'''Menu issues:''' Changing certain graphic settings, like the resolution, requires a restart of Doom 3. However, there is not yet a message that tells you to do so.

More importantly, occasionally navigation breaks down and you might get 'trapped' in a blank menu background. Rather than delay launch further we had to leave that unfixed. If this happens to you then Alt+F4 will exit the program (in Windows.)

'''Saved Game issues:''' Loading saved games works well during a single play session. If you quit Doom3 and then run the game later, however, you may experience some strangeness when attempting to load saved games. The Thiefs Den map can be completed in less than half-an-hour, so try to complete it in one sitting for best results.

'''Keyboard mappings:''' They default mapping of keys is for American/English keyboards. This means that some keys are inaccessible when you use a different keyboard layout. For instance "[" cannot be reached on a German keyboard as the required pressing of {{key|ALT GR}}+{{key|8}} will toggle crouch instead due to Doom not making a difference between the two {{key|ALT}}-keys.

The used fonts do not contain any special characters beyond ASCII. This means if you for instance have a German keybord and bind the key "ü" to a function, it will show up empty in the settings menu. The key will still work in game, though.

''' Missing Texture: ''' The logs in the pot near the fireplace are black because a skin file was left out of the package at the last minute (oops!).

== Troubleshooting ==

'''If''' (and only if) you're experiencing problems, here are some things to try:

# Make sure Doom 3 is patched correctly. You need the correct version of the 1.3.1 patch. See the [[#FAQ|FAQ]] below.
# Make sure that the install path for Doom 3:
#* does not contain any blanks (e.g. <code>C:/doom3</code> is ok, <code>C:/Program files/Doom3</code> is not)
#* is in all lowercase (e.g. <code>/usr/local/lib/doom3</code> is ok, <code>/home/username/MyDoom</code> is not). This is especially important for Linux.

== FAQ ==
; Can I use the Demo version of Doom 3?
: Almost certainly not.

; How can I check whether my Doom 3 is correctly patched?
: Open Doom 3 and hit {{key|Ctrl}}+{{key|Alt}}+{{key|~}} (tilde, {{key|^}} on German keyboards) to open the console. You'll see the version printed in the lower left corner of the console. It should read '''1.3.1.1304'''. If your version is ending on 1302, you've got the wrong patch installed.

; Where can I get the right patch?
: We have the patch hosted on our FTP. See [[#Installation|above]] to find a link to it.
:
: If you have version 1.3.1.1302, you may need to uninstall and reinstall before patch 1.3.1.1304 will let you apply it.

; What's that issue with the 1.3.1 patch?
: When the 1.3.1 patch was released by Id, they released it a bit too early. Some download sites picked it up quite fast though and started to distribute it. The problem is, that Id replaced that patch with a different one, and, probably thinking that it hadn't spread yet, didn't bother to change the version number. However, you can still find "wrong" 1.3.1 patches and these will not work with the mod. That's why it is important to check the version number in the console to make sure that the right 1.3.1 patch is installed if the mod doesn't work. The link provided here on our own page points to the correct patch, so if you downloaded it from here you don't need to worry about it.

; Does it run in Linux?
: Yes, Linux is supported. You may need:
* the package '''libdevil1''',
* either Wine or p7zip to extract the contents from the EXE file
* recompile the map via the console, or the pathfinding of the AI is broken

; Does it run in MacOS?
: No. Or at least not yet. The Doom 3 game itself is supporting MacOS, but The Dark Mod is not - mainly because we don't have anyone developing on Macs. If you can help us getting it to run on MacOS, please [http://modetwo.net/darkmod/index.php?showtopic=7082 apply at the forum].

; Changing the screen resolution/aspect ratio does nothing!?
: These changes require a restart of Doom to work. Currently, our GUI does not warn you about this.

; I've finished all objectives except for the last one (leaving), and I can't find this "front door". Where is it?
: Look at your map (default: {{key|M}}). The front door is inside the main building (on the far side from where you enter). You came in through the back door.

== Ok, I've finished the mission. Now what? ==
It's probably occurred to some of you eager mappers out there that with Thief's Den and [[Dark Radiant]] (our Dark Mod editor), it is possible to start mapping for The Dark Mod. You're right. Although we stripped a number of unnecessary files out of the demo release, it does have a number of models, textures, and code (not to mention the great tutorial on the wiki that explains how much of the map was made) that can be used as a starting point for mapping.

Feel free to start experimenting now. Although there is no promise that maps made using the demo assets will be 100% compatible with the mod when it is released (as many things will no doubt be added/updated by then), you certainly can get a good start. It's also an excellent way to earn a spot as a beta-mapper with the team, which gives you access to the full mod.

{{installation}}
[[Category:Thief's Den]]

Gameplay

2008-01-14T19:30:57Z

New Horizon: /* Mantling */

Since The Dark Mod is designed to simulate the stealth gameplay of Thief, many things will be very familiar to Thief players. There are some features that work differently, however, and several features are still only partially working. The following guide will explain how things work (and what doesn't work yet) in The Dark Mod.

== Adjusting your Settings ==

# Select "Settings" from the Main Menu
# Select the type of setting you wish to adjust: Audio, Video, Controls, or Gameplay (note that many gameplay options are not yet implemented, and default D3 ones are still present in the list).
# The demo ships with controls set to defaults familiar to Thief players. However, there are a few new keys/features, so it is worth looking over the Controls screen to see what they are.

'''Note:''' Changes to many Video settings will not take effect until you reload D3 (currently there is no warning message about this).

== Starting the Mission ==
# Select “Start Mission” from the Main Menu.
# Read the Mission Briefing screen, then select “Objectives”
# Read your objectives, then select “Start Mission”
# The Mission Loading screen should appear.

== Stealth Gameplay ==

'''Note:''' If you are familiar with stealth gameplay already (ie, you have played Thief before), then you can skip this section.
# You are a Thief, not a Warrior. Your best path to success is to avoid being seen by your opponents. While you might be able to survive one toe-to-toe fight with a guard, you’re not likely to survive two.
# Noise can give away your position: crouching, moving slowly, and walking on soft surfaces (such as moss from moss arrows), all help to reduce noise.
# Staying in shadows helps to hide you from the enemy. The light gem at the bottom centre of the screen shows how well lit you are. The darker the gem, the more difficult you are to see.
# If you are spotted but get away, the AI will eventually stop searching for you.
# You can pickpocket items visible on other characters.
# Rope arrows can be climbed but they only stick in solid wood (not metal or thin plaster boards). It does not matter whether the surface is a fixed surface or an object, even moveable, such as a door or crate, so long as it is a suitable material.
# Water arrows can be used to extinguish flames to make an area darker.
# You can lean forward to look down and lean around corners to see if anyone is coming.
# There are two climbing controls - if you jump while in front of a ledge or furniture then you will climb (mantle) from the top of the jump. There is also a separate mantle-only control so if the mantle fails you do not drop back and make a noise. You need to be in the correct position to mantle so adjust if it fails. In particular, note that the mantle is view-sensitive. This means you should look at the edge you want to climb, eg, to climb on a chair, look down at the seat then press the mantle control. By this means you can clamber over relatively low but awkward obstructions and even select one ledge above/below another.
# To manipulate the world around you, you usually center the object in your view. This will cause it to ‘highlight’. If you click your Frob key, you interact with that object (called ‘frobbing’). For many objects, that means picking them up. It also flips switches and opens doors.

== The Dark Mod Gameplay ==
Below are descriptions of gameplay and WIP (Work In Progress) issues that you should be aware of. Some things work differently in The Dark Mod than Thief, and some things just don’t work at all because we’re not finished them yet.

(In particular, there is an objective in Thief's Den which requires you to drop an inventory item, so make sure you read the last paragraph in the section Holding Junk Objects.)

== Objectives ==

Your objectives are displayed after the Mission Briefing. When you complete an objective, a chime will sound and “Objective Completed” will be displayed at the top of the screen. To check the status of your objectives during the game, hit the Esc key to go to the Main Menu, and select Objectives. Hitting Esc again will return you to the game.

When you have completed all objectives, the map will close and a “Mission Succeeded” screen will appear. Likewise, if you fail an objective or are killed, a “Failed Mission” screen will appear. You can restart the map by selecting the "Restart" option or via the Main Menu.

== HUD Display ==

The lightgem at the bottom of the screen indicates how easy you are to see. This is primarily due to how much light is hitting you, but also includes things like whether you are crouched, moving, or have a weapon drawn.

When you are injured, a small red healthbar appears below the lightgem. It will remain visible until you are healed (which cannot be done in this demo).

Your currently selected weapon is displayed in the bottom left corner of the screen. Your currently selected inventory object (or your loot totals) is displayed in the bottom right.

Weapon hotkeys are different than in Thief, since the key underneath Esc ({{key|~}} on US keyboards) is reserved for use by the console:
* {{key|1}} Put away weapons
* {{key|2}} Blackjack
* {{key|3}} Short Sword
* {{key|4}} Broadheads
* {{key|5}} Water Arrows
* {{key|6}} Fire Arrows
* {{key|7}} Rope Arrows
* {{key|8}} Gas Arrows
* {{key|9}} Noise Arrows
* {{key|0}} Moss Arrows

== Inventory Objects ==
Cycle through your inventory using the Inventory Prev/Next keys (default: {{key|[}} or {{key|TAB}} for next item and {{key|]}} for prev item). Inventory objects are stored in groups, so all keys will be stored together, all readables, etc.

To ‘use’ an inventory object, select it and then hit the Use key (default: {{key|U}}). This will drink potions, throw mines, activate the spyglass, etc.

You can drop inventory items by hitting the inventory drop key (default: {{key|R}}). See the section "Holding Junk Objects" for more information. Note that mappers may designate some important inventory items as undroppable.

You can clear the inventory selection by hitting the backspace key {{key|BACKSPACE}}.

=== Inventory Object: Spyglass ===

A good Thief likes to scout ahead. To use the spyglass, select it in inventory and hit Use. You can use the next/prev weapon keys to zoom in and out. You cannot use weapons or frob objects while using the spyglass.

=== Inventory Object: Player Lantern ===

Light is usually the bane of thieves everywhere, but there are times when you need just a little to make your way around. To this end, some thieves carry a covered lantern with a hood that can be closed to block out the light. To use the lantern, select it in inventory and hit Use. This will lift the cover if the lantern is currently off, or close the cover if it is currently lit. There is also a hotkey for using the lantern; by default this is {{key|L}}.

=== Inventory Objects: Maps and Readables ===

In The Dark Mod, both maps and readables (books, scrolls, etc) are inventory items. To read them, you scroll to the object in your inventory and then hit the Use key. The map or readable will be displayed on screen. Note that '''this does not pause the game'''. Unlike Thief, events continue to unfold around you, and you can be attacked while reading if not careful. You can see your environment around the edges of the map/readable, but the best suggestion is to find a safe place to read. Hitting Use again will put the readable away.

The Map key (default: {{key|M}}) will also automatically bring up your map.

=== Inventory Objects: Keys ===
Some doors or chests require keys to open. To open a locked object, select the key by scrolling to it in your inventory and hit the Use key (NOT the frob key) while highlighting the object.

== Blackjacking (WIP Issues) ==

Blackjacking is functional, but still requires some work before it is smooth and easy-to-use. At the moment, blackjacking requires you to get quite close to your opponent (it is currently tricky to get close enough without actually bumping into the AI). You '''must''' center your opponent’s head in your screen (usually forcing you to look up) in order to hit them properly. AI with helmets must be unalert and hit from behind. AI without helmets can be hit from any direction if unalert, but must be hit from behind if alert.

== Combat (WIP issues) ==

Melee combat is still in the early stages of development. At the moment, you can do little but slash at your opponent. Blocking does not work, and there is only one form of attack.

AI will kill you after approximately five hits, depending on their weapon. It currently takes you about the same to kill them. If an AI has armour, it will deflect your weapon or limit the damage it does. AI take more damage if hit in vital areas (head and chest) than they do in the arms and legs.

== Holding Junk Objects ==
This is one area that works quite differently from the Thief series. “Junk” objects (anything that you can carry that doesn’t go into inventory, like chairs, candles, or bodies) are held out in front of you when frobbed. Unlike in Thief, they take up physical space, and can be used to push or manipulate other objects. They can also bump into other objects, making noise (or being knocked out of your hands), so be careful.

To grab a junk object, frob it as normal. The object will stop highlighting, and any weapons you have selected will lower. At this point, you can use the next/prev weapon keys (default: mousewheel up/down) to move the object closer/further away from you, and moving your mouse around will move the object (so that it stays basically in the center of your screen). If you try to move an object in a direction it can’t go (because there is something in the way) it will fall out of your hands and make noise. This can sometimes make it tricky to pick up an object if other objects are in the way. It can take a while to get used to this.

The heavier the object, the slower it moves, so you may notice a ‘lag’ if you turn quickly with heavy objects.

To drop an object, hit the {{key|R}} key. You can also throw a held object by hitting the Attack key. Tapping the Attack key throws the object a short distance; holding the Attack key down and releasing it will throw it further.

To rotate a held object, hold down the {{key|Z}} key or middle mouse button, and move your mouse. This can be useful for replacing objects that have been knocked over, or for placing moveable objects in creative ways (like putting a plank over a gap, or stacking chairs).

It is possible to “drop” inventory items into your hands, where they can be manipulated as if they were junk objects. Select the object in your inventory, and hit the Drop key {{key|R}}. The object will appear in front of you like a junk object, and you can rotate it, set it down, etc. To put it back into your inventory, you must "use" the item again ({{key|U}}) or scroll to the next inventory item ({{key|TAB}} or {{key|[}}/{{key|]}}).

Note—held objects can be used to block projectiles.

== Moving Bodies (WIP Issues) ==

Currently, ‘shouldering’ bodies is planned but not implemented. To remove bodies from sight in the demo, you must drag them. This requires you to ‘frob’ the body, and then move away. The body will drag along with you until you frob it again or the body gets stuck on something.

Currently, this is difficult to do. Bodies frequently catch on world geometry, or moveable objects (like a dropped weapon), and get ‘pulled’ out of your hands. Some AI seem to be particularly difficult to move for some reason (there may be issues with mass and friction to resolve). There are many issues to iron out here.

Note that AI will notice and get suspicious if a friend’s weapon is just lying around, so you’ll need to hide that as well.

== Doors and Lockpicking ==
Although lockpicking is mostly working in TDM, it still needs some tweaking and it was not included in this map.

Locked doors will make a sound when you try to open them without the proper key. If a door does not highlight, then it is for decorative purposes only.

== Mantling ==
There are two different ways to mantle in The Dark Mod. One is by using the Jump key, which Thief players will be familiar with. There is also a key specifically for mantling (default: {{key|
C}}), so that failing to mantle will not result in jumping and making noise. You cannot mantle while carrying a junk object. A successful mantle is more likely if you are looking directly at the edge of the object you wish to climb.

== Rising Code ==
To avoid trapping the player when 'clipping' into surfaces, the D3 code automatically gently pushes the player upwards to release from such situations. While this shouldn’t happen, it occasionally does - it is preferable to being permanently trapped.

----
* ''[[Thief's Den|Back to main instructions]]''

[[Category:Installation]]
[[Category:Thief's Den]]

Gameplay

2008-01-14T19:30:38Z

New Horizon: /* Mantling */

Since The Dark Mod is designed to simulate the stealth gameplay of Thief, many things will be very familiar to Thief players. There are some features that work differently, however, and several features are still only partially working. The following guide will explain how things work (and what doesn't work yet) in The Dark Mod.

== Adjusting your Settings ==

# Select "Settings" from the Main Menu
# Select the type of setting you wish to adjust: Audio, Video, Controls, or Gameplay (note that many gameplay options are not yet implemented, and default D3 ones are still present in the list).
# The demo ships with controls set to defaults familiar to Thief players. However, there are a few new keys/features, so it is worth looking over the Controls screen to see what they are.

'''Note:''' Changes to many Video settings will not take effect until you reload D3 (currently there is no warning message about this).

== Starting the Mission ==
# Select “Start Mission” from the Main Menu.
# Read the Mission Briefing screen, then select “Objectives”
# Read your objectives, then select “Start Mission”
# The Mission Loading screen should appear.

== Stealth Gameplay ==

'''Note:''' If you are familiar with stealth gameplay already (ie, you have played Thief before), then you can skip this section.
# You are a Thief, not a Warrior. Your best path to success is to avoid being seen by your opponents. While you might be able to survive one toe-to-toe fight with a guard, you’re not likely to survive two.
# Noise can give away your position: crouching, moving slowly, and walking on soft surfaces (such as moss from moss arrows), all help to reduce noise.
# Staying in shadows helps to hide you from the enemy. The light gem at the bottom centre of the screen shows how well lit you are. The darker the gem, the more difficult you are to see.
# If you are spotted but get away, the AI will eventually stop searching for you.
# You can pickpocket items visible on other characters.
# Rope arrows can be climbed but they only stick in solid wood (not metal or thin plaster boards). It does not matter whether the surface is a fixed surface or an object, even moveable, such as a door or crate, so long as it is a suitable material.
# Water arrows can be used to extinguish flames to make an area darker.
# You can lean forward to look down and lean around corners to see if anyone is coming.
# There are two climbing controls - if you jump while in front of a ledge or furniture then you will climb (mantle) from the top of the jump. There is also a separate mantle-only control so if the mantle fails you do not drop back and make a noise. You need to be in the correct position to mantle so adjust if it fails. In particular, note that the mantle is view-sensitive. This means you should look at the edge you want to climb, eg, to climb on a chair, look down at the seat then press the mantle control. By this means you can clamber over relatively low but awkward obstructions and even select one ledge above/below another.
# To manipulate the world around you, you usually center the object in your view. This will cause it to ‘highlight’. If you click your Frob key, you interact with that object (called ‘frobbing’). For many objects, that means picking them up. It also flips switches and opens doors.

== The Dark Mod Gameplay ==
Below are descriptions of gameplay and WIP (Work In Progress) issues that you should be aware of. Some things work differently in The Dark Mod than Thief, and some things just don’t work at all because we’re not finished them yet.

(In particular, there is an objective in Thief's Den which requires you to drop an inventory item, so make sure you read the last paragraph in the section Holding Junk Objects.)

== Objectives ==

Your objectives are displayed after the Mission Briefing. When you complete an objective, a chime will sound and “Objective Completed” will be displayed at the top of the screen. To check the status of your objectives during the game, hit the Esc key to go to the Main Menu, and select Objectives. Hitting Esc again will return you to the game.

When you have completed all objectives, the map will close and a “Mission Succeeded” screen will appear. Likewise, if you fail an objective or are killed, a “Failed Mission” screen will appear. You can restart the map by selecting the "Restart" option or via the Main Menu.

== HUD Display ==

The lightgem at the bottom of the screen indicates how easy you are to see. This is primarily due to how much light is hitting you, but also includes things like whether you are crouched, moving, or have a weapon drawn.

When you are injured, a small red healthbar appears below the lightgem. It will remain visible until you are healed (which cannot be done in this demo).

Your currently selected weapon is displayed in the bottom left corner of the screen. Your currently selected inventory object (or your loot totals) is displayed in the bottom right.

Weapon hotkeys are different than in Thief, since the key underneath Esc ({{key|~}} on US keyboards) is reserved for use by the console:
* {{key|1}} Put away weapons
* {{key|2}} Blackjack
* {{key|3}} Short Sword
* {{key|4}} Broadheads
* {{key|5}} Water Arrows
* {{key|6}} Fire Arrows
* {{key|7}} Rope Arrows
* {{key|8}} Gas Arrows
* {{key|9}} Noise Arrows
* {{key|0}} Moss Arrows

== Inventory Objects ==
Cycle through your inventory using the Inventory Prev/Next keys (default: {{key|[}} or {{key|TAB}} for next item and {{key|]}} for prev item). Inventory objects are stored in groups, so all keys will be stored together, all readables, etc.

To ‘use’ an inventory object, select it and then hit the Use key (default: {{key|U}}). This will drink potions, throw mines, activate the spyglass, etc.

You can drop inventory items by hitting the inventory drop key (default: {{key|R}}). See the section "Holding Junk Objects" for more information. Note that mappers may designate some important inventory items as undroppable.

You can clear the inventory selection by hitting the backspace key {{key|BACKSPACE}}.

=== Inventory Object: Spyglass ===

A good Thief likes to scout ahead. To use the spyglass, select it in inventory and hit Use. You can use the next/prev weapon keys to zoom in and out. You cannot use weapons or frob objects while using the spyglass.

=== Inventory Object: Player Lantern ===

Light is usually the bane of thieves everywhere, but there are times when you need just a little to make your way around. To this end, some thieves carry a covered lantern with a hood that can be closed to block out the light. To use the lantern, select it in inventory and hit Use. This will lift the cover if the lantern is currently off, or close the cover if it is currently lit. There is also a hotkey for using the lantern; by default this is {{key|L}}.

=== Inventory Objects: Maps and Readables ===

In The Dark Mod, both maps and readables (books, scrolls, etc) are inventory items. To read them, you scroll to the object in your inventory and then hit the Use key. The map or readable will be displayed on screen. Note that '''this does not pause the game'''. Unlike Thief, events continue to unfold around you, and you can be attacked while reading if not careful. You can see your environment around the edges of the map/readable, but the best suggestion is to find a safe place to read. Hitting Use again will put the readable away.

The Map key (default: {{key|M}}) will also automatically bring up your map.

=== Inventory Objects: Keys ===
Some doors or chests require keys to open. To open a locked object, select the key by scrolling to it in your inventory and hit the Use key (NOT the frob key) while highlighting the object.

== Blackjacking (WIP Issues) ==

Blackjacking is functional, but still requires some work before it is smooth and easy-to-use. At the moment, blackjacking requires you to get quite close to your opponent (it is currently tricky to get close enough without actually bumping into the AI). You '''must''' center your opponent’s head in your screen (usually forcing you to look up) in order to hit them properly. AI with helmets must be unalert and hit from behind. AI without helmets can be hit from any direction if unalert, but must be hit from behind if alert.

== Combat (WIP issues) ==

Melee combat is still in the early stages of development. At the moment, you can do little but slash at your opponent. Blocking does not work, and there is only one form of attack.

AI will kill you after approximately five hits, depending on their weapon. It currently takes you about the same to kill them. If an AI has armour, it will deflect your weapon or limit the damage it does. AI take more damage if hit in vital areas (head and chest) than they do in the arms and legs.

== Holding Junk Objects ==
This is one area that works quite differently from the Thief series. “Junk” objects (anything that you can carry that doesn’t go into inventory, like chairs, candles, or bodies) are held out in front of you when frobbed. Unlike in Thief, they take up physical space, and can be used to push or manipulate other objects. They can also bump into other objects, making noise (or being knocked out of your hands), so be careful.

To grab a junk object, frob it as normal. The object will stop highlighting, and any weapons you have selected will lower. At this point, you can use the next/prev weapon keys (default: mousewheel up/down) to move the object closer/further away from you, and moving your mouse around will move the object (so that it stays basically in the center of your screen). If you try to move an object in a direction it can’t go (because there is something in the way) it will fall out of your hands and make noise. This can sometimes make it tricky to pick up an object if other objects are in the way. It can take a while to get used to this.

The heavier the object, the slower it moves, so you may notice a ‘lag’ if you turn quickly with heavy objects.

To drop an object, hit the {{key|R}} key. You can also throw a held object by hitting the Attack key. Tapping the Attack key throws the object a short distance; holding the Attack key down and releasing it will throw it further.

To rotate a held object, hold down the {{key|Z}} key or middle mouse button, and move your mouse. This can be useful for replacing objects that have been knocked over, or for placing moveable objects in creative ways (like putting a plank over a gap, or stacking chairs).

It is possible to “drop” inventory items into your hands, where they can be manipulated as if they were junk objects. Select the object in your inventory, and hit the Drop key {{key|R}}. The object will appear in front of you like a junk object, and you can rotate it, set it down, etc. To put it back into your inventory, you must "use" the item again ({{key|U}}) or scroll to the next inventory item ({{key|TAB}} or {{key|[}}/{{key|]}}).

Note—held objects can be used to block projectiles.

== Moving Bodies (WIP Issues) ==

Currently, ‘shouldering’ bodies is planned but not implemented. To remove bodies from sight in the demo, you must drag them. This requires you to ‘frob’ the body, and then move away. The body will drag along with you until you frob it again or the body gets stuck on something.

Currently, this is difficult to do. Bodies frequently catch on world geometry, or moveable objects (like a dropped weapon), and get ‘pulled’ out of your hands. Some AI seem to be particularly difficult to move for some reason (there may be issues with mass and friction to resolve). There are many issues to iron out here.

Note that AI will notice and get suspicious if a friend’s weapon is just lying around, so you’ll need to hide that as well.

== Doors and Lockpicking ==
Although lockpicking is mostly working in TDM, it still needs some tweaking and it was not included in this map.

Locked doors will make a sound when you try to open them without the proper key. If a door does not highlight, then it is for decorative purposes only.

== Mantling ==
There are two different ways to mantle in The Dark Mod. One is by using the Jump key, which Thief players will be familiar with. There is also a key specifically for mantling (default: {{key|
c}}), so that failing to mantle will not result in jumping and making noise. You cannot mantle while carrying a junk object. A successful mantle is more likely if you are looking directly at the edge of the object you wish to climb.

== Rising Code ==
To avoid trapping the player when 'clipping' into surfaces, the D3 code automatically gently pushes the player upwards to release from such situations. While this shouldn’t happen, it occasionally does - it is preferable to being permanently trapped.

----
* ''[[Thief's Den|Back to main instructions]]''

[[Category:Installation]]
[[Category:Thief's Den]]

Gameplay

2008-01-14T19:29:45Z

New Horizon: /* Inventory Objects: Maps and Readables */

Since The Dark Mod is designed to simulate the stealth gameplay of Thief, many things will be very familiar to Thief players. There are some features that work differently, however, and several features are still only partially working. The following guide will explain how things work (and what doesn't work yet) in The Dark Mod.

== Adjusting your Settings ==

# Select "Settings" from the Main Menu
# Select the type of setting you wish to adjust: Audio, Video, Controls, or Gameplay (note that many gameplay options are not yet implemented, and default D3 ones are still present in the list).
# The demo ships with controls set to defaults familiar to Thief players. However, there are a few new keys/features, so it is worth looking over the Controls screen to see what they are.

'''Note:''' Changes to many Video settings will not take effect until you reload D3 (currently there is no warning message about this).

== Starting the Mission ==
# Select “Start Mission” from the Main Menu.
# Read the Mission Briefing screen, then select “Objectives”
# Read your objectives, then select “Start Mission”
# The Mission Loading screen should appear.

== Stealth Gameplay ==

'''Note:''' If you are familiar with stealth gameplay already (ie, you have played Thief before), then you can skip this section.
# You are a Thief, not a Warrior. Your best path to success is to avoid being seen by your opponents. While you might be able to survive one toe-to-toe fight with a guard, you’re not likely to survive two.
# Noise can give away your position: crouching, moving slowly, and walking on soft surfaces (such as moss from moss arrows), all help to reduce noise.
# Staying in shadows helps to hide you from the enemy. The light gem at the bottom centre of the screen shows how well lit you are. The darker the gem, the more difficult you are to see.
# If you are spotted but get away, the AI will eventually stop searching for you.
# You can pickpocket items visible on other characters.
# Rope arrows can be climbed but they only stick in solid wood (not metal or thin plaster boards). It does not matter whether the surface is a fixed surface or an object, even moveable, such as a door or crate, so long as it is a suitable material.
# Water arrows can be used to extinguish flames to make an area darker.
# You can lean forward to look down and lean around corners to see if anyone is coming.
# There are two climbing controls - if you jump while in front of a ledge or furniture then you will climb (mantle) from the top of the jump. There is also a separate mantle-only control so if the mantle fails you do not drop back and make a noise. You need to be in the correct position to mantle so adjust if it fails. In particular, note that the mantle is view-sensitive. This means you should look at the edge you want to climb, eg, to climb on a chair, look down at the seat then press the mantle control. By this means you can clamber over relatively low but awkward obstructions and even select one ledge above/below another.
# To manipulate the world around you, you usually center the object in your view. This will cause it to ‘highlight’. If you click your Frob key, you interact with that object (called ‘frobbing’). For many objects, that means picking them up. It also flips switches and opens doors.

== The Dark Mod Gameplay ==
Below are descriptions of gameplay and WIP (Work In Progress) issues that you should be aware of. Some things work differently in The Dark Mod than Thief, and some things just don’t work at all because we’re not finished them yet.

(In particular, there is an objective in Thief's Den which requires you to drop an inventory item, so make sure you read the last paragraph in the section Holding Junk Objects.)

== Objectives ==

Your objectives are displayed after the Mission Briefing. When you complete an objective, a chime will sound and “Objective Completed” will be displayed at the top of the screen. To check the status of your objectives during the game, hit the Esc key to go to the Main Menu, and select Objectives. Hitting Esc again will return you to the game.

When you have completed all objectives, the map will close and a “Mission Succeeded” screen will appear. Likewise, if you fail an objective or are killed, a “Failed Mission” screen will appear. You can restart the map by selecting the "Restart" option or via the Main Menu.

== HUD Display ==

The lightgem at the bottom of the screen indicates how easy you are to see. This is primarily due to how much light is hitting you, but also includes things like whether you are crouched, moving, or have a weapon drawn.

When you are injured, a small red healthbar appears below the lightgem. It will remain visible until you are healed (which cannot be done in this demo).

Your currently selected weapon is displayed in the bottom left corner of the screen. Your currently selected inventory object (or your loot totals) is displayed in the bottom right.

Weapon hotkeys are different than in Thief, since the key underneath Esc ({{key|~}} on US keyboards) is reserved for use by the console:
* {{key|1}} Put away weapons
* {{key|2}} Blackjack
* {{key|3}} Short Sword
* {{key|4}} Broadheads
* {{key|5}} Water Arrows
* {{key|6}} Fire Arrows
* {{key|7}} Rope Arrows
* {{key|8}} Gas Arrows
* {{key|9}} Noise Arrows
* {{key|0}} Moss Arrows

== Inventory Objects ==
Cycle through your inventory using the Inventory Prev/Next keys (default: {{key|[}} or {{key|TAB}} for next item and {{key|]}} for prev item). Inventory objects are stored in groups, so all keys will be stored together, all readables, etc.

To ‘use’ an inventory object, select it and then hit the Use key (default: {{key|U}}). This will drink potions, throw mines, activate the spyglass, etc.

You can drop inventory items by hitting the inventory drop key (default: {{key|R}}). See the section "Holding Junk Objects" for more information. Note that mappers may designate some important inventory items as undroppable.

You can clear the inventory selection by hitting the backspace key {{key|BACKSPACE}}.

=== Inventory Object: Spyglass ===

A good Thief likes to scout ahead. To use the spyglass, select it in inventory and hit Use. You can use the next/prev weapon keys to zoom in and out. You cannot use weapons or frob objects while using the spyglass.

=== Inventory Object: Player Lantern ===

Light is usually the bane of thieves everywhere, but there are times when you need just a little to make your way around. To this end, some thieves carry a covered lantern with a hood that can be closed to block out the light. To use the lantern, select it in inventory and hit Use. This will lift the cover if the lantern is currently off, or close the cover if it is currently lit. There is also a hotkey for using the lantern; by default this is {{key|L}}.

=== Inventory Objects: Maps and Readables ===

In The Dark Mod, both maps and readables (books, scrolls, etc) are inventory items. To read them, you scroll to the object in your inventory and then hit the Use key. The map or readable will be displayed on screen. Note that '''this does not pause the game'''. Unlike Thief, events continue to unfold around you, and you can be attacked while reading if not careful. You can see your environment around the edges of the map/readable, but the best suggestion is to find a safe place to read. Hitting Use again will put the readable away.

The Map key (default: {{key|M}}) will also automatically bring up your map.

=== Inventory Objects: Keys ===
Some doors or chests require keys to open. To open a locked object, select the key by scrolling to it in your inventory and hit the Use key (NOT the frob key) while highlighting the object.

== Blackjacking (WIP Issues) ==

Blackjacking is functional, but still requires some work before it is smooth and easy-to-use. At the moment, blackjacking requires you to get quite close to your opponent (it is currently tricky to get close enough without actually bumping into the AI). You '''must''' center your opponent’s head in your screen (usually forcing you to look up) in order to hit them properly. AI with helmets must be unalert and hit from behind. AI without helmets can be hit from any direction if unalert, but must be hit from behind if alert.

== Combat (WIP issues) ==

Melee combat is still in the early stages of development. At the moment, you can do little but slash at your opponent. Blocking does not work, and there is only one form of attack.

AI will kill you after approximately five hits, depending on their weapon. It currently takes you about the same to kill them. If an AI has armour, it will deflect your weapon or limit the damage it does. AI take more damage if hit in vital areas (head and chest) than they do in the arms and legs.

== Holding Junk Objects ==
This is one area that works quite differently from the Thief series. “Junk” objects (anything that you can carry that doesn’t go into inventory, like chairs, candles, or bodies) are held out in front of you when frobbed. Unlike in Thief, they take up physical space, and can be used to push or manipulate other objects. They can also bump into other objects, making noise (or being knocked out of your hands), so be careful.

To grab a junk object, frob it as normal. The object will stop highlighting, and any weapons you have selected will lower. At this point, you can use the next/prev weapon keys (default: mousewheel up/down) to move the object closer/further away from you, and moving your mouse around will move the object (so that it stays basically in the center of your screen). If you try to move an object in a direction it can’t go (because there is something in the way) it will fall out of your hands and make noise. This can sometimes make it tricky to pick up an object if other objects are in the way. It can take a while to get used to this.

The heavier the object, the slower it moves, so you may notice a ‘lag’ if you turn quickly with heavy objects.

To drop an object, hit the {{key|R}} key. You can also throw a held object by hitting the Attack key. Tapping the Attack key throws the object a short distance; holding the Attack key down and releasing it will throw it further.

To rotate a held object, hold down the {{key|Z}} key or middle mouse button, and move your mouse. This can be useful for replacing objects that have been knocked over, or for placing moveable objects in creative ways (like putting a plank over a gap, or stacking chairs).

It is possible to “drop” inventory items into your hands, where they can be manipulated as if they were junk objects. Select the object in your inventory, and hit the Drop key {{key|R}}. The object will appear in front of you like a junk object, and you can rotate it, set it down, etc. To put it back into your inventory, you must "use" the item again ({{key|U}}) or scroll to the next inventory item ({{key|TAB}} or {{key|[}}/{{key|]}}).

Note—held objects can be used to block projectiles.

== Moving Bodies (WIP Issues) ==

Currently, ‘shouldering’ bodies is planned but not implemented. To remove bodies from sight in the demo, you must drag them. This requires you to ‘frob’ the body, and then move away. The body will drag along with you until you frob it again or the body gets stuck on something.

Currently, this is difficult to do. Bodies frequently catch on world geometry, or moveable objects (like a dropped weapon), and get ‘pulled’ out of your hands. Some AI seem to be particularly difficult to move for some reason (there may be issues with mass and friction to resolve). There are many issues to iron out here.

Note that AI will notice and get suspicious if a friend’s weapon is just lying around, so you’ll need to hide that as well.

== Doors and Lockpicking ==
Although lockpicking is mostly working in TDM, it still needs some tweaking and it was not included in this map.

Locked doors will make a sound when you try to open them without the proper key. If a door does not highlight, then it is for decorative purposes only.

== Mantling ==
There are two different ways to mantle in The Dark Mod. One is by using the Jump key, which Thief players will be familiar with. There is also a key specifically for mantling (default: {{key|M}}), so that failing to mantle will not result in jumping and making noise. You cannot mantle while carrying a junk object. A successful mantle is more likely if you are looking directly at the edge of the object you wish to climb.

== Rising Code ==
To avoid trapping the player when 'clipping' into surfaces, the D3 code automatically gently pushes the player upwards to release from such situations. While this shouldn’t happen, it occasionally does - it is preferable to being permanently trapped.

----
* ''[[Thief's Den|Back to main instructions]]''

[[Category:Installation]]
[[Category:Thief's Den]]

Gameplay

2008-01-14T19:29:24Z

New Horizon: /* Inventory Object: Player Lantern */

Since The Dark Mod is designed to simulate the stealth gameplay of Thief, many things will be very familiar to Thief players. There are some features that work differently, however, and several features are still only partially working. The following guide will explain how things work (and what doesn't work yet) in The Dark Mod.

== Adjusting your Settings ==

# Select "Settings" from the Main Menu
# Select the type of setting you wish to adjust: Audio, Video, Controls, or Gameplay (note that many gameplay options are not yet implemented, and default D3 ones are still present in the list).
# The demo ships with controls set to defaults familiar to Thief players. However, there are a few new keys/features, so it is worth looking over the Controls screen to see what they are.

'''Note:''' Changes to many Video settings will not take effect until you reload D3 (currently there is no warning message about this).

== Starting the Mission ==
# Select “Start Mission” from the Main Menu.
# Read the Mission Briefing screen, then select “Objectives”
# Read your objectives, then select “Start Mission”
# The Mission Loading screen should appear.

== Stealth Gameplay ==

'''Note:''' If you are familiar with stealth gameplay already (ie, you have played Thief before), then you can skip this section.
# You are a Thief, not a Warrior. Your best path to success is to avoid being seen by your opponents. While you might be able to survive one toe-to-toe fight with a guard, you’re not likely to survive two.
# Noise can give away your position: crouching, moving slowly, and walking on soft surfaces (such as moss from moss arrows), all help to reduce noise.
# Staying in shadows helps to hide you from the enemy. The light gem at the bottom centre of the screen shows how well lit you are. The darker the gem, the more difficult you are to see.
# If you are spotted but get away, the AI will eventually stop searching for you.
# You can pickpocket items visible on other characters.
# Rope arrows can be climbed but they only stick in solid wood (not metal or thin plaster boards). It does not matter whether the surface is a fixed surface or an object, even moveable, such as a door or crate, so long as it is a suitable material.
# Water arrows can be used to extinguish flames to make an area darker.
# You can lean forward to look down and lean around corners to see if anyone is coming.
# There are two climbing controls - if you jump while in front of a ledge or furniture then you will climb (mantle) from the top of the jump. There is also a separate mantle-only control so if the mantle fails you do not drop back and make a noise. You need to be in the correct position to mantle so adjust if it fails. In particular, note that the mantle is view-sensitive. This means you should look at the edge you want to climb, eg, to climb on a chair, look down at the seat then press the mantle control. By this means you can clamber over relatively low but awkward obstructions and even select one ledge above/below another.
# To manipulate the world around you, you usually center the object in your view. This will cause it to ‘highlight’. If you click your Frob key, you interact with that object (called ‘frobbing’). For many objects, that means picking them up. It also flips switches and opens doors.

== The Dark Mod Gameplay ==
Below are descriptions of gameplay and WIP (Work In Progress) issues that you should be aware of. Some things work differently in The Dark Mod than Thief, and some things just don’t work at all because we’re not finished them yet.

(In particular, there is an objective in Thief's Den which requires you to drop an inventory item, so make sure you read the last paragraph in the section Holding Junk Objects.)

== Objectives ==

Your objectives are displayed after the Mission Briefing. When you complete an objective, a chime will sound and “Objective Completed” will be displayed at the top of the screen. To check the status of your objectives during the game, hit the Esc key to go to the Main Menu, and select Objectives. Hitting Esc again will return you to the game.

When you have completed all objectives, the map will close and a “Mission Succeeded” screen will appear. Likewise, if you fail an objective or are killed, a “Failed Mission” screen will appear. You can restart the map by selecting the "Restart" option or via the Main Menu.

== HUD Display ==

The lightgem at the bottom of the screen indicates how easy you are to see. This is primarily due to how much light is hitting you, but also includes things like whether you are crouched, moving, or have a weapon drawn.

When you are injured, a small red healthbar appears below the lightgem. It will remain visible until you are healed (which cannot be done in this demo).

Your currently selected weapon is displayed in the bottom left corner of the screen. Your currently selected inventory object (or your loot totals) is displayed in the bottom right.

Weapon hotkeys are different than in Thief, since the key underneath Esc ({{key|~}} on US keyboards) is reserved for use by the console:
* {{key|1}} Put away weapons
* {{key|2}} Blackjack
* {{key|3}} Short Sword
* {{key|4}} Broadheads
* {{key|5}} Water Arrows
* {{key|6}} Fire Arrows
* {{key|7}} Rope Arrows
* {{key|8}} Gas Arrows
* {{key|9}} Noise Arrows
* {{key|0}} Moss Arrows

== Inventory Objects ==
Cycle through your inventory using the Inventory Prev/Next keys (default: {{key|[}} or {{key|TAB}} for next item and {{key|]}} for prev item). Inventory objects are stored in groups, so all keys will be stored together, all readables, etc.

To ‘use’ an inventory object, select it and then hit the Use key (default: {{key|U}}). This will drink potions, throw mines, activate the spyglass, etc.

You can drop inventory items by hitting the inventory drop key (default: {{key|R}}). See the section "Holding Junk Objects" for more information. Note that mappers may designate some important inventory items as undroppable.

You can clear the inventory selection by hitting the backspace key {{key|BACKSPACE}}.

=== Inventory Object: Spyglass ===

A good Thief likes to scout ahead. To use the spyglass, select it in inventory and hit Use. You can use the next/prev weapon keys to zoom in and out. You cannot use weapons or frob objects while using the spyglass.

=== Inventory Object: Player Lantern ===

Light is usually the bane of thieves everywhere, but there are times when you need just a little to make your way around. To this end, some thieves carry a covered lantern with a hood that can be closed to block out the light. To use the lantern, select it in inventory and hit Use. This will lift the cover if the lantern is currently off, or close the cover if it is currently lit. There is also a hotkey for using the lantern; by default this is {{key|L}}.

=== Inventory Objects: Maps and Readables ===

In The Dark Mod, both maps and readables (books, scrolls, etc) are inventory items. To read them, you scroll to the object in your inventory and then hit the Use key. The map or readable will be displayed on screen. Note that '''this does not pause the game'''. Unlike Thief, events continue to unfold around you, and you can be attacked while reading if not careful. You can see your environment around the edges of the map/readable, but the best suggestion is to find a safe place to read. Hitting Use again will put the readable away.

The Map key (default: {{key|O}}) will also automatically bring up your map.

=== Inventory Objects: Keys ===
Some doors or chests require keys to open. To open a locked object, select the key by scrolling to it in your inventory and hit the Use key (NOT the frob key) while highlighting the object.

== Blackjacking (WIP Issues) ==

Blackjacking is functional, but still requires some work before it is smooth and easy-to-use. At the moment, blackjacking requires you to get quite close to your opponent (it is currently tricky to get close enough without actually bumping into the AI). You '''must''' center your opponent’s head in your screen (usually forcing you to look up) in order to hit them properly. AI with helmets must be unalert and hit from behind. AI without helmets can be hit from any direction if unalert, but must be hit from behind if alert.

== Combat (WIP issues) ==

Melee combat is still in the early stages of development. At the moment, you can do little but slash at your opponent. Blocking does not work, and there is only one form of attack.

AI will kill you after approximately five hits, depending on their weapon. It currently takes you about the same to kill them. If an AI has armour, it will deflect your weapon or limit the damage it does. AI take more damage if hit in vital areas (head and chest) than they do in the arms and legs.

== Holding Junk Objects ==
This is one area that works quite differently from the Thief series. “Junk” objects (anything that you can carry that doesn’t go into inventory, like chairs, candles, or bodies) are held out in front of you when frobbed. Unlike in Thief, they take up physical space, and can be used to push or manipulate other objects. They can also bump into other objects, making noise (or being knocked out of your hands), so be careful.

To grab a junk object, frob it as normal. The object will stop highlighting, and any weapons you have selected will lower. At this point, you can use the next/prev weapon keys (default: mousewheel up/down) to move the object closer/further away from you, and moving your mouse around will move the object (so that it stays basically in the center of your screen). If you try to move an object in a direction it can’t go (because there is something in the way) it will fall out of your hands and make noise. This can sometimes make it tricky to pick up an object if other objects are in the way. It can take a while to get used to this.

The heavier the object, the slower it moves, so you may notice a ‘lag’ if you turn quickly with heavy objects.

To drop an object, hit the {{key|R}} key. You can also throw a held object by hitting the Attack key. Tapping the Attack key throws the object a short distance; holding the Attack key down and releasing it will throw it further.

To rotate a held object, hold down the {{key|Z}} key or middle mouse button, and move your mouse. This can be useful for replacing objects that have been knocked over, or for placing moveable objects in creative ways (like putting a plank over a gap, or stacking chairs).

It is possible to “drop” inventory items into your hands, where they can be manipulated as if they were junk objects. Select the object in your inventory, and hit the Drop key {{key|R}}. The object will appear in front of you like a junk object, and you can rotate it, set it down, etc. To put it back into your inventory, you must "use" the item again ({{key|U}}) or scroll to the next inventory item ({{key|TAB}} or {{key|[}}/{{key|]}}).

Note—held objects can be used to block projectiles.

== Moving Bodies (WIP Issues) ==

Currently, ‘shouldering’ bodies is planned but not implemented. To remove bodies from sight in the demo, you must drag them. This requires you to ‘frob’ the body, and then move away. The body will drag along with you until you frob it again or the body gets stuck on something.

Currently, this is difficult to do. Bodies frequently catch on world geometry, or moveable objects (like a dropped weapon), and get ‘pulled’ out of your hands. Some AI seem to be particularly difficult to move for some reason (there may be issues with mass and friction to resolve). There are many issues to iron out here.

Note that AI will notice and get suspicious if a friend’s weapon is just lying around, so you’ll need to hide that as well.

== Doors and Lockpicking ==
Although lockpicking is mostly working in TDM, it still needs some tweaking and it was not included in this map.

Locked doors will make a sound when you try to open them without the proper key. If a door does not highlight, then it is for decorative purposes only.

== Mantling ==
There are two different ways to mantle in The Dark Mod. One is by using the Jump key, which Thief players will be familiar with. There is also a key specifically for mantling (default: {{key|M}}), so that failing to mantle will not result in jumping and making noise. You cannot mantle while carrying a junk object. A successful mantle is more likely if you are looking directly at the edge of the object you wish to climb.

== Rising Code ==
To avoid trapping the player when 'clipping' into surfaces, the D3 code automatically gently pushes the player upwards to release from such situations. While this shouldn’t happen, it occasionally does - it is preferable to being permanently trapped.

----
* ''[[Thief's Den|Back to main instructions]]''

[[Category:Installation]]
[[Category:Thief's Den]]

Texture Guidelines

2006-06-22T02:56:26Z

New Horizon:

'''Q: What is the darkmod_hires CVS directory for?'''

A: To help us maintain our high and low res textures, we have had to setup a darkmod_hires repository on CVS. It will contain map, object and character hi_res textures that will later be released as a self installing upgrade package.

'''Q: When do I upload to the darkmod_hires repository?'''

A: Anytime you create a new texture.

'''Q: I have uploaded my hires textures, now what?'''

A: Switch back to the regular 'darkmod' mod directory and upload the low res textures.

'''Q: How do I download the hires textures?'''

A: In the same way you download the rest of the mod. The only exception is that you have to change the file path while using the darkmod_hires directory.

'''Q: What is the reason for having these texture guidelines?'''

A: There are several.

'''1. To make downloading the mod easier for our members who are on dialup.'''

'''2. To prevent the mod from ballooning into a huge monster. Uncompressed TGA's add up quickly.'''

'''3. To make the mod accessible to members and eventually players who will not have high end computers that are capable of handling the textures.'''

Here is the basic setup for uploading and downloading from this repository.

http://208.49.149.118/TheDarkMod/screenshots/hires.jpg

== TEXTURE GUIDELINES: ==

Texture groups should attempt to stay within the following standards.

'''''Format: DDS Compression.'''''

With this formula,the largest DDS textures (1024x1024) weigh in at roughly 1 to 1.5 megs, mip maps included.

'''Do keep a backup of the ultra hi-res versions of your work. Try not to forget that you must upload a high res and low res version to their respective repositories.'''

'''Tiled textures- Walls, Floors, Ceiling, Doors...ect -'''

Diffuse: [ Min/Max: 1024 x 1024]

Normal: [ Min: 512 x 512 / Max: 1024 x 1024]

Specular: [ Min: 256 x 256 / Max: 512 x 512]

'''Large objects- Beds, barrels, chairs, bookshelves-'''

Diffuse: [ Min/Max: 1024 x 1024]

Normal: [ Min: 512 x 512 / Max: 1024 x 1024]

Specular: [ Min: 256 x 256 / Max: 512 x 512]

'''Small objects- Keys, books, goblets, utensils-'''

Diffuse: [ Min/Max: 256 x 256]

Normal: [ Min: 256 x 256 / Max: 512 x 512]

Specular: [ Min: 128 x 128 / Max: 256 x 256]

'''AI: All characters-'''

Diffuse: [ Min/Max: 1024 x 1024]

Normal: [ Min: 512 x 512 / Max: 1024 x 1024]

Other: [ Min: 256 x 256 / Max: 512 x 512]

By following this formula, you will reduce your final file size while retaining high quality presentation.

Coming soon: DDS creation.

Texture Guidelines

2006-06-22T02:55:39Z

New Horizon:

Model/Texture Guidelines

2006-02-24T03:28:43Z

New Horizon:

There is really nothing complicated about how the models are setup. To simplify the process we decide reorganized the system in the following manner.

1. A '''Model''' resides in its own folder. In this example ''models/props/furniture/armoire''

2. All '''Textures''' are stored in ''models/darkmod/props/textures''

3. Material files should look like this.

http://208.49.149.118/TheDarkMod/screenshots/materialfiles.jpg

'''Model software.'''

Each model should have this path. I'm not sure if all modeling software handles the texture paths the same, but this is how it looks in lightwave.

Take note that the _d is not needed at the end of the path. I saw a few models in my journey that came through like that. It causes the model to look fullbright all the time.

http://208.49.149.118/TheDarkMod/screenshots/lightwavesetup.jpg

That's it.

Sound

2005-12-05T20:45:25Z

New Horizon:

A page about sound fx and ambients, how to include them in your map, and suchlike.

[[Voice Set Guidelines]]

Sound

2005-12-05T20:45:13Z

New Horizon:

A page about sound fx and ambients, how to include them in your map, and suchlike.
[[Voice Set Guidelines]]

Textures

2005-12-05T20:42:46Z

New Horizon:

This page contains articles and links related to making/importing textures, editing .mtr files and others related to the mod.

[[Texture Guidelines]]

Main Page

2005-12-05T18:56:03Z

New Horizon:

<p style="margin:2em 0 0 0; text-align:center; font-size:200%;">Welcome to the Dark Wiki</p>
<p style="margin:0 0 3em 0; text-align:center; font-size:94%">A wiki documenting the Dark Mod for Doom 3</p>

<table align="center" width="90%" cellspacing="10"><tr>
<td style="width:50%; vertical-align:top; padding:2em; border:1px solid #e1e1e1; background-color:#f9f9f9">

'''New to the site?'''

This wiki is focused on documenting the various aspects involved with developing, and mapping, for The Dark Mod. Please visit the about page or talk to some of our editors in #darkmod on irc.starchat.net if you want to learn more about this project.

'''Want to help?'''

As the modwiki is a community project, feel free to register and join us on this great endeavour! Please check out the style guide first and follow these guidelines. Visit open tasks to find out which pages need help. You can also visit the sandbox to experiment with the wiki markup language.

'''High quality links:'''

Other interesting Dark Mod related links:

<dl>
<dt>[http://www.thedarkmod.com www.thedarkmod.com]</dt>
<dd>The project website</dd>

<dt>[http://www.modetwo.net/darkmod www.modetwo.net/darkmod]</dt>
<dd>The project forum</dd>
</dl>

</td><td style="vertical-align:top; padding:2em; border:1px solid #e1e1e1; background-color:#f9f9f9">

<h2>Editing Categories:</h2>

<dl>
<dt>[[Installation]]</dt>
<dd>Information how to get The Dark Mod running</dd>

<dt>[[Universe]]</dt>
<dd>Information about The Dark Mod universe and setting</dd>

<dt>[[Editing]]</dt>
<dd>Information about level design and the tools</dd>

<dt>[[Textures]]</dt>
<dd>Explanation of material shaders and image files</dd>

<dt>[[Modeling]]</dt>
<dd>Modeling and file format information</dd>

<dt>[[Sound]]</dt>
<dd>Soundeffects, ambients and how to get them ingame</dd>

<dt>[[Coding]]</dt>
<dd>Source code modification, level and GUI scripting</dd>

<dt>[[Release]]</dt>
<dd>How to pack a mission, and get it tested and released!</dd>
</dl>

</td></tr></table>
<p style="margin:2em 0 2em 0; text-align:center; font-size:94%">(Create a new page by making a link to it, then click it. Or you can just go to www.evilarmyfilms.com/darkwiki/yourpagename)</p>

Model/Texture Guidelines

2005-12-05T17:29:07Z

New Horizon:

There is really nothing complicated about how the models are setup. To simplify the process we decide reorganized the system in the following manner.

1. A '''Model''' resides in its own folder. In this example ''models/props/furniture/armoire''

2. All '''Textures''' are stored in ''models/props/textures''

3. Material files should look like this.

http://208.49.149.118/TheDarkMod/screenshots/materialfiles.jpg

'''Model software.'''

Each model should have this path. I'm not sure if all modeling software handles the texture paths the same, but this is how it looks in lightwave.

Take note that the _d is not needed at the end of the path. I saw a few models in my journey that came through like that. It causes the model to look fullbright all the time.

http://208.49.149.118/TheDarkMod/screenshots/lightwavesetup.jpg

That's it.

Model/Texture Guidelines

2005-12-05T17:28:28Z

New Horizon:

There is really nothing complicated about how the models are setup. To simplify the process we decide reorganized the system in the following manner.

1. A '''Model''' resides in its own folder. In this example ''models/props/furniture/armoire''

2. All '''Textures''' are stored in ''models/props/textures''

3. Material files should look like this.

http://208.49.149.118/TheDarkMod/screenshots/materialfiles.jpg

Model software.

Each model should have this path. I'm not sure if all modeling software handles the texture paths the same, but this is how it looks in lightwave.

Take note that the _d is not needed at the end of the path. I saw a few models in my journey that came through like that. It causes the model to look fullbright all the time.

http://208.49.149.118/TheDarkMod/screenshots/lightwavesetup.jpg

That's it.

Model/Texture Guidelines

2005-12-05T17:26:51Z

New Horizon:

Modeling

2005-12-05T17:26:37Z

New Horizon:

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

[[Model/Texture Guidelines]]

Modeling

2005-12-05T17:25:31Z

New Horizon:

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

== [[Model/Texture Guidelines]] ==

There is really nothing complicated about how the models are setup. To simplify the process we decide reorganized the system in the following manner.

1. A '''Model''' resides in its own folder. In this example ''models/props/furniture/armoire''

2. All '''Textures''' are stored in ''models/props/textures''

3. Material files should look like this.

Modeling

2005-12-05T17:21:57Z

New Horizon:

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

== [[Model/Texture Guidelines]] ==

Okay, there is really nothing too complicated about how the models are now setup. I tried to simplify the process so that if we decide to reorganize the models in the future, it won't require moving all the skins too.

1. Model resides in its own folder. In this case models/props/furniture/armoire

2. Textures are stored in models/props/textures

3. Material files should look like this.

Modeling

2005-12-05T17:21:48Z

New Horizon:

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

== [[Model/Texture Guidelines]] ==
'''How to avoid black models'''

Okay, there is really nothing too complicated about how the models are now setup. I tried to simplify the process so that if we decide to reorganize the models in the future, it won't require moving all the skins too.

1. Model resides in its own folder. In this case models/props/furniture/armoire

2. Textures are stored in models/props/textures

3. Material files should look like this.

Modeling

2005-12-05T17:21:33Z

New Horizon: /* Model/Texture Guidelines */

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

== [[Model/Texture Guidelines]] ==
'''How to avoid black models.'''

Okay, there is really nothing too complicated about how the models are now setup. I tried to simplify the process so that if we decide to reorganize the models in the future, it won't require moving all the skins too.

1. Model resides in its own folder. In this case models/props/furniture/armoire

2. Textures are stored in models/props/textures

3. Material files should look like this.

Modeling

2005-12-05T17:20:53Z

New Horizon:

This page will detail and link to other pages talking about making, importing etc. various formats of 3D Model.

== [[Model/Texture Guidelines]] ==
'''How to avoid black models.'''

Texture Guidelines

2005-12-05T17:15:32Z

New Horizon:

'''Q: What is the darkmod_hires CVS directory for?'''

A: To help us maintain our high and low res textures, we have had to setup a darkmod_hires repository on CVS. It will contain map, object and character hi_res textures that will later be released as a self installing upgrade package.

'''Q: When do I upload to the darkmod_hires repository?'''

A: Anytime an original texture exceeds the texture specifications listed below.

'''Q: What if the texture does not exceed the texture specifications?'''

A: Then upload directly to the regular 'darkmod' directory. No hires copy is needed.

'''Q: I have uploaded my hires textures, now what?'''

A: Switch back to the regular 'darkmod' mod directory and upload the low res textures.

'''Q: How do I download the hires textures?'''

A: In the same way you download the rest of the mod. The only exception is that you have to change the file path while using the darkmod_hires directory.

'''Q: What is the reason for having these texture guidelines?'''

A: There are several.

'''1. To make downloading the mod easier for our members who are on dialup.'''

'''2. To prevent the mod from ballooning into a huge monster. Uncompressed TGA's add up quickly.'''

'''3. To make the mod accessible to members and eventually players who will not have high end computers that are capable of handling the textures.'''

Here is the basic setup for uploading and downloading from this repository.

http://208.49.149.118/TheDarkMod/screenshots/hires.jpg

== TEXTURE GUIDELINES: ==

Texture groups should attempt to stay within the following standards.

'''''Format: TGA with RLE 24 bit Lossless Compression.'''''

With this formula,the largest TGA textures (512x512) weigh in at roughly 700 kb with 24 Bit, RLE lossless compression.

'''Do keep a backup of the ultra hi-res versions of your work. Try not to forget that you must upload a high res and low res version to their respective repositories.'''

'''Tiled textures- Walls, Floors, Ceiling, Doors...ect -'''

Diffuse: [ Min/Max: 512 x 512]

Normal: [ Min/Max: 512 x 512]

Specular: [ Min/Max: 256 x 256]

'''Large objects- Beds, barrels, chairs, bookshelves-'''

Diffuse: [ Min/Max: 512 x 512]

Normal: [ Min/Max: 256x256]

Specular: [ Min/Max: 128 x 128]

'''Small objects- Keys, books, goblets, utensils-'''

Diffuse: [ Min/Max: 256 x 256]

Normal: [ Min/Max: 128 x 128]

Specular: [ Min/Max: 128x128]

'''AI: All characters-'''

Diffuse: [ Min/Max: 512 x 512]

Normal: [ Min/Max: 512 x 512]

Other: [ Min/Max: 256x256]

By following this formula, you will reduce your final file size while retaining high quality looks, but at a slightly reduced resolution.