The DarkMod Wiki - User contributions [en]

https://wiki.thedarkmod.com/api.php?action=feedcontributions&feedformat=atom&user=Peter+spy The DarkMod Wiki - User contributions [en] 2026-04-29T06:24:41Z User contributions MediaWiki 1.45.3 https://wiki.thedarkmod.com/index.php?title=Alert_%26_Suspicion_Triggers&diff=33886 Alert & Suspicion Triggers 2025-03-13T17:13:42Z

<p>Peter spy: /* Controlling AI Reactions to Missing Objects */</p> <hr /> <div>TODO PLACEHOLDER<br /> <br /> AI will alert if they see or hear the player but alerts and suspicion (low alert) can be triggered by the AI noticing suspicious or missing objects and other situations. This article describes how to control this.<br /> <br /> ==Controlled Alerts==<br /> <br /> Alarms etc.<br /> <br /> For atdm:alarm_sound, alert_volume_mod ranges from -60 (no sounds at all) to positive 10.<br /> <br /> One thing I'd like to know is how to start AI off (at map start) at an elevated alert level rather than their default, casual state.<br /> <br /> alert_initial is the spawnarg you need. This is a floating point value.<br /> <br /> These are the thresholds.<br /> <br /> idle: 0 ... 1.5 <br /> observant: 1.5 ... 6<br /> suspicious: 6 ... 8<br /> searching: 8 ... 18<br /> agitated searching: 18 ... 23<br /> combat: >23 (but alert_initial doesn't work in this case, AI need an enemy to go into combat)<br /> <br /> ''edit: These were changed in 2.0 so that suspicious wasn't so tiny, but I forget the new values.''<br /> <br /> <br /> Which number is the one they go to after having spotted the player? The one where they go back to their regular patrols but keep their weapon out? <br /> <br /> This is still idle < 1.5. <br /> <br /> The code switches to a different AlertIdle state when the AI has encountered an enemy before. There's no difference in terms of the numbers.<br /> <br /> ==Suspicious Objects==<br /> TO DO<br /> noisemaker arrow on floor<br /> <br /> CHECK OUT <br /> AIUSE_<br /> STIM_VISUAL<br /> <br /> That's what is issued by STIM_VISUAL on arrows, doors and AI by default. The AI code reacts to those stims based on the AI_USE spawnarg.<br /> <br /> NOTES PASTED FOR REF TO REWRITE. SOME OF THIS MAY BE OBOSOLETE OR IRRELEVANT FOR THE MAPPER - I'VE GOT TO FIGURE IT OUT YET...<br /> <br /> script function for responding to STIM_VISUAL in ai_darkmod_base, and made some tweaks to the visibility tests in the dll (not in the pk4 yet). By adding a visual stim to the arrow and arrow result defs, I've got the AI reacting to arrows that it sees (only the first time it sees each one, using the ResponseIgnore script function.)<br /> <br /> However, I'd like to have the AI react differently to different sorts of objects.<br /> <br /> variable to classify the response to stim_visual:<br /> IMO, I think it's easier to just create different stims for these different cases, with the functionality in the response. E.g., stim_body, stim_suspicious_item, stim_missing_item, etc.<br /> <br /> Ok, I've implemented a bunch of .def variables that contain what I need. I have them all documented in a file that is intended to be included by scriptors that I will check in with the source.<br /> <br /> Here are the contents that I've added so far<br /> <br /> // This is the key name for the AIUse spawn arg<br /> #define AIUSE_KEY "AIUse"<br /> <br /> // And below are values in use<br /> <br /> #define AIUSE_WEAPON "AIUSE_WEAPON"<br /> <br /> #define AIUSE_LIGHTSOURCE "AIUSE_LIGHTSOURCE"<br /> <br /> #define AIUSE_BLOOD_EVIDENCE "AIUSE_BLOOD_EVIDENCE"<br /> <br /> #define AIUSE_SEAT "AIUSE_SEAT"<br /> <br /> #define AIUSE_COOK "AIUSE_COOK"<br /> <br /> #define AIUSE_EAT "AIUSE_EAT"<br /> <br /> #define AIUSE_PET "AIUSE_PET"<br /> <br /> #define AIUSE_CATTLE "AIUSE_CATTLE"<br /> <br /> #define AIUSE_PERSON "AIUSE_PERSON"<br /> <br /> #define AIUSE_PEST "AIUSE_PEST"<br /> <br /> #define AIUSE_DRINK "AIUSE_DRINK"<br /> <br /> //----------------------------------------------------------------------------------------<br /> <br /> All the FOLLOWING are in effect are strings. The AI scripts look to see what strings are attached as spawnargs under the specified keys, and use those to decide what "type" of entity it is. So if its a noble, they can adress it as a noble. If its a rat, they can address it as a pest.<br /> <br /> // The following strings define classes of person, these are used if AIUse is AIUSE_PERSON <br /> <br /> // This is the key value<br /> #define PERSONTYPE_KEY "personType"<br /> <br /> // And these are values in use, add to this list as needed<br /> #define PERSONTYPE_GENERIC "PERSONTYPE_GENERIC"<br /> #define PERSONTYPE_NOBLE "PERSONTYPE_NOBLE"<br /> #define PERSONTYPE_CITYWATCH "PERSONTYPE_CITYWATCH"<br /> #define PERSONTYPE_MERC_PROGUARD "PERSONTYPE_MERC_PROGUARD"<br /> #define PERSONTYPE_BUILDER "PERSONTYPE_BUILDER"<br /> #define PERSONTYPE_PAGAN "PERSONTYPE_PAGAN"<br /> <br /> //----------------------------------------------------------------------------------------<br /> // The following strings define genders of person, these are used if AIUse is AIUSE_PERSON <br /> // I don't want to get into the politics of gender identity here, this is just because the recorded<br /> // voices will likely be in gendered languages. As such, I'm just including the categories<br /> // that are involved in word gender selection in many languages.<br /> #define PERSONGENDER_KEY "personGender"<br /> <br /> #define PERSONGENDER_MALE "PERSONGENDER_MALE"<br /> #define PERSONGENDER_FEMALE "PERSONGENDER_FEMALE"<br /> #define PERSONGENDER_UNKNOWN "PERSONGENDER_UNKNOWN"<br /> <br /> //----------------------------------------------------------------------------------------<br /> // The following key and values are used for identifying types of lights<br /> #define AIUSE_LIGHTTYPE_KEY "lightType"<br /> #define AIUSE_LIGHTTYPE_TORCH "AIUSE_LIGHTTYPE_TORCH"<br /> #define AIUSE_LIGHTTYPE_GASLAMP "AIUSE_LIGHTTYPE_GASLAMP"<br /> #define AIUSE_LIGHTTYPE_ELECTRIC "AIUSE_LIGHTTYPE_ELECTRIC"<br /> #define AIUSE_LIGHTTYPE_MAGIC "AIUSE_LIGHTTYPE_MAGIC"<br /> <br /> //----------------------------------------------------------------------------------------<br /> // The following defines a key that should be non-0 if the device should be on<br /> #define AIUSE_SHOULDBEON_KEY "shouldBeOn"<br /> <br /> //----------------------------------------------------------------------------------------<br /> // The following defines a key that should be non-0 if the device should be closed<br /> #define AIUSE_SHOULDBECLOSED_KEY "shouldBeClosed"<br /> <br /> <br /> <br /> torch and candle flames turning on a visual stimulus if they are marked as supposed to be on and get doused. The stimulus turns off if it is relit.<br /> <br /> <br /> I'm adding the following spawn args. Note that they are spawn args, not variables, so they can't be changed other than in a .def file.<br /> <br /> "canLightTorches" : > 0.0 indicates the AI can light torches<br /> "canOperateSwitchLights" : > 0.0 indicates AI can turn on switched lights<br /> <br /> "chanceNoticeWeapon": 0.0 to 1.0, probability of noticing a seeable weapon not belonging to a friend<br /> "chanceNoticePerson": 0.0 to 1.0, probability of noticing (reacting to) a seeable person be it friend, foe or enemy. <br /> "chanceNoticeBlood": 0.0 to 1.0, probability of noticing a see-able patch of blood.<br /> "chanceNoticeLight": 0.0 to 1.0, probability of noticing a visible light source that is in the wrong state<br /> "chanceNoticeMissingItem": 0.0 to 1.0, probability of noticing a visible missing item<br /> "chanceNoticeDoor": 0.0 to 1.0, probability of noticing a visible open door that should be closed<br /> <br /> New values<br /> "AIUSE_MONSTER"<br /> "AIUSE_UNDEAD"<br /> "PERSONTYPE_THIEF"<br /> <br /> They are in the .def files. The defintions of the tags are in the AIUseValues.script file for inclusion in scripts.<br /> <br /> ==Suspicious Changes==<br /> <br /> TO DO<br /> <br /> Doors ajar, torches extinguished<br /> <br /> Q: If an AI is looking at a torch and the player shoots it out, will the AI react to it with more suspicion than just a general 'when did this go out?'?<br /> <br /> A: If the AI is close enough to catch some spray from the water arrow then he alerts but not otherwise.<br /> <br /> ==Missing or Moved Objects, Absence Markers==<br /> <br /> By default AI will take no notice if loot or other objects are missing or moved so it is up to the mapper to judge whether any prominent items ought to be noticed by their absence. The contents of a jewellery box or just a broom moved in a cupboard need not be a cause for attention whereas a guard protecting a precious artifact on a plinth in the middle of a hall should react if it is stolen or even moved off the pedestal onto the floor.<br /> <br /> ===Making AI Notice a Missing Object===<br /> <br /> To make AI notice, become suspicious or alert if an object is missing or moved add to any kind of moveable entity including loot, corpses, any moveable object you think the AI should notice is missing, the following property and values:<br /> <br /> '''''absence_noticeability'''''<br /> <br /> ...with a decimal fraction anywhere in the range from 0 to 1. The closer to 1 then the more likely the AI will notice. Examples:<br /> <br /> * 1 means the AI will always notice the object is missing 100% of the time<br /> * 0.5 means the AI will only notice the object is missing 50% of the time<br /> * 0 means the AI will never notice the object is missing (default)<br /> <br /> It works this way: If the object is moved or taken away then an absence marker is created at the original location (at the center of the bounds) which emits a visual stim. When the item is put back at its original location (within the original bounds of the entity), the absence marker is destroyed again.<br /> <br /> Currently the AI will notice at a range of 500 units. Check later if this is changed. It may even become a spawnarg you can adjust to AI do not alert too far away if a tiny ring is missing 25 metres away.<br /> <br /> IMPORTANT: The object must be illuminated well enough for the AI to see. If the AI do not notice then this is the first thing to check. It must also of course, not be obscured.<br /> <br /> The marker also may physically impede the player (in one instance, blocked jumping and forced crouching beneath).<br /> <br /> ===How Far Can the Object can be Moved Without Suspicion?===<br /> <br /> By default the player can move an object (with the ''absence_noticeability'' property) within the original boundaries of the entity's start position without arousing suspicion. So a crate that is only pushed a foot or so to one side will not arouse suspicion. If it is pushed further than half its own width then it will. But this can be controlled:<br /> <br /> You can add to the object the property:<br /> <br /> '''''absence_bounds_tolerance'''''<br /> <br /> ...with any value in doom units and this will be added to the boundaries of the entity's start position. So a crate sized 30 units cube even without this property can be pushed one foot and still clip its original boundaries and so not be noticed. But set this spawnarg to 100 and now it can be moved an extra 100 units in any direction without being noticed.<br /> <br /> If you want it to be moveable anywhere within a set area, eg, anywhere on a table top, then see next section....<br /> <br /> ===Moving within a Location or to a New Location Without Suspicion===<br /> <br /> What if you want the player to be able to move a vase anywhere on a table top or to a separate location completely - to another table or another room - without arousing suspicion? You can define the location: Do the following:<br /> <br /> * Create a brush entity to cover the table top and at least the height of the vase.<br /> * Texture the brush with clip texture, convert it to func_static, then give it a suitable name, eg 'vase_area'. <br /> * To the original vase add the property '''''absence_location_1''''' and give it the name of the brush, eg, 'vase_area'.<br /> <br /> So long as the vase is partly within that brush then the AI will not be concerned it has been moved about (eg, by a servant for cleaning.)<br /> <br /> And you can put the location brush elsewhere too so the vase can be given the property ''absence_bounds_tolerance'' (see above) to extend its coverage around its original location plus the new location brush might be placed on another table or in the kitchen sink if you want.<br /> <br /> It is planned to enable multiple alternate locations where it is OK for the object to be (eg, the cleaner put the vase on the next table.) Check at a later time if you can use absence_location_2, 3, etc.<br /> <br /> <br /> ==Restricting Alerts to one Type(team) of AI==<br /> <br /> Normally all AI will respond to an absence marker. If you only want one AI team to react then give the object the '''''team''''' property with the value of the team type (see [[AI Relations (Editing)#AI Types (Teams)|teams]].) Missing objects without this property may be noticed by all AI on all teams.<br /> <br /> <br /> ==Controlling AI Reactions to Missing Objects==<br /> <br /> The reaction of AI on noticing an object is missing can be controlled from slight suspicion up to full alert. Add this property to the object:<br /> <br /> '''''absence_alert_increase'''''<br /> <br /> And give it a value 0 to 23. This value will be added to the AI's current state in the range:<br /> <br /> * 0 to 1.5 = idle<br /> * 1.5 to 6 = observant<br /> * 6 to 8 = suspicious<br /> * 8 to 18 = searching<br /> * 18 to 23 = agitated searching<br /> <br /> So if the AI is already suspicious (say 7) then notices an object missing which had ''absence_alert_increase 4'' on it then the AI state will now be 11 and it will start searching.<br /> <br /> If this property is not set then the AI's alert level will be set to a default of just below agitated searching.<br /> <br /> <br /> <br /> [[Category:Editing]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Virtual_Darkness&diff=26788 Virtual Darkness 2020-12-11T07:39:36Z

<p>Peter spy: Deleted section on virtual ambient light as this is no longer relevant.</p> <hr /> <div>''written by Fidcal''<br /> <br /> '''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.<br /> <br /> This article here is just a general introduction into "ambient light settings".<br /> <br /> ==Introduction==<br /> <br /> 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.)<br /> <br /> Ambient light can be coloured to provide atmosphere and realism depending on the environment.<br /> <br /> <br /> == Brightness Standard ==<br /> <br /> 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.<br /> <br /> ==Ambient Light==<br /> <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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, the arg '''lightgem_adjust''' can be applied to any piece of '''worldspawn''' to offset the lightgem and bring balance back to the gameplay. For an '''ambient_world''' setting of 7, a lightgem_adjust setting 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. <br /> <br /> Other local ambient lights can be used to produce highlights, mood, or any purpose the mapper can imagine so can be any brightness.<br /> <br /> <br /> ==Enabling Virtual Ambient Light==<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == See also ==<br /> <br /> * The [[Location Settings]] article.<br /> <br /> {{tutorial-lighting}}<br /> <br /> [[Category:Ambient Light]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Virtual_Ambient_Light_Textures&diff=26787 Virtual Ambient Light Textures 2020-12-11T07:35:24Z

<p>Peter spy: </p> <hr /> <div>Edited by peter_spy, 2020<br><br><br /> As of TDM 2.08 none of the below is needed, as TDM uses ambient lights to calculate this instead of textures. The option to switch between this and legacy system is no longer in the menu, but you can type '''tdm_ambient_method 0''' in the game console to make sure you use the correct system.<br><br /> <br><br><br /> '''OLD VERSION:'''<br><br /> 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. Players can select between three methods for ambient rendering, so those with faster machines can use the true ambient light which gives better quality.<br /> <br /> '''So all textures should include these two stages:'''<br /> <br /> ''Please note that there is also a command for automatically converting all materials to fulfill the TDM 1.03 requirements called tdm_batchConvertMaterials (see [[TDM Material Batch Conversion]])''<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map textures/darkmod/yourname // Diffuse<br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> The first stage is for the simple ambient method, whereas the second one is for enhanced ambient rendering, which obviously also processes the normal- and specularmap of the material.<br /> <br /> If a material does not contain a specularmap, the fragmentMap parameter 3 in the enhanced ambient rendering stage has to be changed to _black, e.g. "textures/darkmod/yourname_s" becomes "_black". If on the contrary a material does not contain a normalmap, the proper replacement is "_flat", meaning a flat surface, e.g. "textures/darkmod/yourname_local" becomes "_flat".<br /> <br /> '''For [[DrVertexBlend (tutorial)|vertex-blended materials]], the ambient stages have to be altered in the following way:'''<br /> <pre><br /> // TDM Ambient Method Related <br /> { <br /> if (global5 == 1) <br /> blend add <br /> map textures/darkmod/materialA // Diffuse A<br /> scale 1, 1 <br /> red global2 <br /> green global3 <br /> blue global4 <br /> vertexColor <br /> } <br /> { <br /> if (global5 == 1) <br /> blend add <br /> map textures/darkmod/materialB // Diffuse B<br /> scale 1, 1 <br /> red global2 <br /> green global3 <br /> blue global4 <br /> inverseVertexColor <br /> } <br /> <br /> </pre><br /> <br /> AS OF TDM 2.0 the old Enhanced Ambient Stages:<br /> <br /> <pre><br /> <br /> { <br /> if (global5 == 2) <br /> blend add <br /> program ambientEnvVertexBlend.vfp <br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse A and Bump A resp. <br /> vertexParm 1 1, 1, 1, 1 // UV Scale for specular A and Diffuse B resp.<br /> vertexParm 2 1, 1, 1, 1 // UV Scale for Bump B and specular B resp. <br /> vertexParm 3 global2, global3, global4, 1 <br /> //----------- VertexColored ------------------- <br /> fragmentMap 0 cubeMap env/gen1 <br /> fragmentMap 1 textures/darkmod/materialA_local // Bump A <br /> fragmentMap 2 textures/darkmod/materialA // Diffuse A<br /> fragmentMap 3 textures/darkmod/materialA_s // Specular A <br /> //----------- InverseVertexColored ------------ <br /> fragmentMap 4 textures/darkmod/materialB_local // Bump B <br /> fragmentMap 5 textures/darkmod/materialB // Diffuse B <br /> fragmentMap 6 textures/darkmod/materialB_s // Specular B<br /> }<br /> <br /> </pre><br /> <br /> are '''no longer needed''' as the Ambient light now has it's own dedicated render path.<br /> <br /> [[Category:Textures]]<br /> [[Category:Ambient Light]]<br /> [[Category:Lighting]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Virtual_Ambient_Light_Textures&diff=26786 Virtual Ambient Light Textures 2020-12-11T07:31:16Z

<p>Peter spy: This is no longer needed.</p> <hr /> <div>As of TDM 2.08 none of the below is needed, as TDM uses ambient lights to calculate this instead of textures. The option to switch between this and legacy system is no longer in the menu, but you can type '''tdm_ambient_method 0''' in the game console to make sure you use the correct system.<br /> <br /> '''OLD VERSION:'''<br /> 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. Players can select between three methods for ambient rendering, so those with faster machines can use the true ambient light which gives better quality.<br /> <br /> '''So all textures should include these two stages:'''<br /> <br /> ''Please note that there is also a command for automatically converting all materials to fulfill the TDM 1.03 requirements called tdm_batchConvertMaterials (see [[TDM Material Batch Conversion]])''<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map textures/darkmod/yourname // Diffuse<br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> The first stage is for the simple ambient method, whereas the second one is for enhanced ambient rendering, which obviously also processes the normal- and specularmap of the material.<br /> <br /> If a material does not contain a specularmap, the fragmentMap parameter 3 in the enhanced ambient rendering stage has to be changed to _black, e.g. "textures/darkmod/yourname_s" becomes "_black". If on the contrary a material does not contain a normalmap, the proper replacement is "_flat", meaning a flat surface, e.g. "textures/darkmod/yourname_local" becomes "_flat".<br /> <br /> '''For [[DrVertexBlend (tutorial)|vertex-blended materials]], the ambient stages have to be altered in the following way:'''<br /> <pre><br /> // TDM Ambient Method Related <br /> { <br /> if (global5 == 1) <br /> blend add <br /> map textures/darkmod/materialA // Diffuse A<br /> scale 1, 1 <br /> red global2 <br /> green global3 <br /> blue global4 <br /> vertexColor <br /> } <br /> { <br /> if (global5 == 1) <br /> blend add <br /> map textures/darkmod/materialB // Diffuse B<br /> scale 1, 1 <br /> red global2 <br /> green global3 <br /> blue global4 <br /> inverseVertexColor <br /> } <br /> <br /> </pre><br /> <br /> AS OF TDM 2.0 the old Enhanced Ambient Stages:<br /> <br /> <pre><br /> <br /> { <br /> if (global5 == 2) <br /> blend add <br /> program ambientEnvVertexBlend.vfp <br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse A and Bump A resp. <br /> vertexParm 1 1, 1, 1, 1 // UV Scale for specular A and Diffuse B resp.<br /> vertexParm 2 1, 1, 1, 1 // UV Scale for Bump B and specular B resp. <br /> vertexParm 3 global2, global3, global4, 1 <br /> //----------- VertexColored ------------------- <br /> fragmentMap 0 cubeMap env/gen1 <br /> fragmentMap 1 textures/darkmod/materialA_local // Bump A <br /> fragmentMap 2 textures/darkmod/materialA // Diffuse A<br /> fragmentMap 3 textures/darkmod/materialA_s // Specular A <br /> //----------- InverseVertexColored ------------ <br /> fragmentMap 4 textures/darkmod/materialB_local // Bump B <br /> fragmentMap 5 textures/darkmod/materialB // Diffuse B <br /> fragmentMap 6 textures/darkmod/materialB_s // Specular B<br /> }<br /> <br /> </pre><br /> <br /> are '''no longer needed''' as the Ambient light now has it's own dedicated render path.<br /> <br /> [[Category:Textures]]<br /> [[Category:Ambient Light]]<br /> [[Category:Lighting]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=How_to_add_Textures_to_The_Dark_Mod&diff=26785 How to add Textures to The Dark Mod 2020-12-11T07:25:06Z

<p>Peter spy: /* Create your Shader Definition (Material) */ - removed the section about ambient textures</p> <hr /> <div>== Create your texture ==<br /> 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]].<br /> <br /> 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]]<br /> {{Things-To-Remember|<br /> * Use good source material<br /> * All image dimensions must be powers of two: 64, 128, 256, 512, 1024 (don't go beyond 1024).<br /> * Avoid lighting baked into the diffusemap<br /> * Keep your PSD/Gimp working version safe!}}<br /> == Save your Texture in the correct Format == <br /> 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).<br /> <br /> 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.<br /> <br /> 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>).<br /> {{Things-To-Remember|<br /> * Most textures don't need speculars<br /> * Create DDS for your diffusemap and specularmap.<br /> * Keep TGA version of your diffusemap and specularmap.<br /> * Create a TGA version of your normalmap (uncompressed, no RLE).<br /> * Create a JPG editor image (max. 256px)}}<br /> == Name your Texture ==<br /> 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.<br /> <br /> '''Some or all''' of the following may apply to any given material:<br /> <br /> # '''Object Type''' descriptor first (mostly for very specific-use textures) - it's a window, a door, a chest...<br /> # '''Material''' descriptor next - made from marble, wood, mud...<br /> # '''Size''' descriptor next - it is large, small...<br /> # '''Quality''' descriptors next - texture-wise, it is rough, new, cracked...<br /> # '''Color''' descriptors next - what color is it? red, green...<br /> # '''Number Increment''' next - which of the list is it? 001, 002...<br /> # '''Tiling''' and '''Image Type''' descriptors, if needed (file only, not material definition - see below)<br /> <br /> 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.<br /> <br /> <br /> '''Examples:'''<br /> <br /> 1. ''slate_large_cracked_grey_001''<br /> <br /> This name omits an '''Object Type''' descriptor, instead starting with the '''Material''' descriptor - it is a general, non-specialized texture.<br /> <br /> 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'.<br /> <br /> <br /> 2. ''door_wood_battered_005''<br /> <br /> This name omits a '''Size''' descriptor and a '''Color''' descriptor.<br /> <br /> 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'.<br /> <br /> <br /> 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).<br /> <br /> 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'''.<br /> <br /> 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.<br /> {{Things-To-Remember|<br /> * Choose descriptive names for your texture, while following TDM convention<br /> * Add the suffix '''tiling_1d'''/'''nontiling''' to the filename where appropriate<br /> * Diffusemap: '''mytexture.dds''' (note the '''lowercase''')<br /> * Normalmap: '''mytexture_local.tga'''<br /> * Editor image: '''mytexture_ed.jpg''' (max. 256 pixels in size)<br /> * (Optional) Specularmap: '''mytexture_s.dds'''}}<br /> <br /> == Move the Texture to the right Location ==<br /> 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.<br /> <br /> The .dds diffuse and specular go in the '''dds/textures/''' folder structure. The .tga normalmap goes in the '''textures/''' folder structure. Also, the texture may not render properly unless it's nested inside "../textures/darkmod/.." and for a custom texture (only for FM use) you should use "../textures/darkmod/your_texture_folder" in both the parent Darkmod folder (for mapping) and the same folder structure inside your pk4 (for release). <br /> <br /> Note: At one time, the Doom 3 engine and early TDM could not load DDS textures that were more than five folders deep. The deepest level allowed would be something along the lines of dds/textures/darkmod/door/metal/. This is no longer the case.<br /> {{Things-To-Remember|<br /> * Move the DDS textures into the '''dds/textures/...''' tree.<br /> * Move the TGA and JPG files into the '''textures/...''' tree.}}<br /> <br /> == Create your Shader Definition (Material) ==<br /> 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]].<br /> <br /> 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.)<br /> <br /> 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.)''<br /> {{Things-To-Remember|<br /> * Create your shader in the correct file (tdm_xxx_yyy.mtr) following the [[Material File Naming Convention]]<br /> * The shader name for tiling textures is the same as the diffusemap<br /> * Nontiling/tiling_1d textures go into a "virtual" subfolder nontiling/ or tiling_1d/<br /> * You don't need to specify file extensions (.dds/.tga/.jpg) to the material defs, this is automatically guessed by the engine.<br /> * You don't need the '''dds/''' folder prefix to reference the DDS textures.<br /> * Be sure to include the frob highlight code (see [[Basic Material File#Add_the_Frob_Highlight_Stage|Basic Material File]])<br /> <br /> == Upload the Textures == <br /> 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.<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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>'''.<br /> {{Things-To-Remember|<br /> * Upload the diffuse, normal, (specular,) and editor image to the regular darkmod SVN.<br /> * Upload the (RLE-compressed) TGA diffusemap and specularmap to the darkmod_hires SVN repository (into the '''tga_backup''' subfolder).<br /> * Upload the working source file (PSD/Gimp) to the '''texture_src''' repository.}}<br /> {{tutorial-textures}}<br /> __NOTOC__</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Textures&diff=26784 Textures 2020-12-11T07:23:51Z

<p>Peter spy: /* Material Files */ - deleted the info about virtual ambient textures as they're no longer needed.</p> <hr /> <div>{{index-page|category=Textures|topic=textures}}<br /> This page contains articles and links related to making/importing textures, editing .mtr files and others related to the mod.<br /> <br /> == Making Textures ==<br /> * [[Texture Creation - Basic Tutorial]]<br /> * [[DDS creation]]<br /> * '''[[How to add Textures to The Dark Mod]]''' ''-- (Overall Information and Guides)''<br /> * '''[[Texture Guidelines]]''' ''-- (Info on our hi-res repository, and what sizes to use for textures)''<br /> * '''[[Texture Folder Structure]]''' ''-- (Where to save new textures)''<br /> * Basic Texture Information: http://www.modwiki.net/wiki/Texturing<br /> * [[Common Texture Mistakes]]<br /> * [[Texture Sources]] ''-- (Good places to find source textures and photos)''<br /> * [[How to give Textures a nice Glow]]<br /> === Diffusemaps ===<br /> * [[Advanced Tips for Creating Diffusemaps]]<br /> * [[Remove Shadows in Source Images]]<br /> === Normalmaps ===<br /> * [[Normalmaps, How to Make Good Ones]]<br /> * [[No more Heightmaps]] ''-- (Basic info for turning a heightmap into a normalmap)''<br /> * [[Wall Texture Tutorial]] ''-- (How to make good normalmaps with Maya)''<br /> * [[Creating Textures with Normals out of Models]] ''-- (More info on using modeling software to make normalmaps)''<br /> * [[Inverse Normalmaps]] ''-- (A way to check if your normalmaps are correct)''<br /> * [[Inverting Normalmaps]] ''-- (How to fix them if they aren't correct)''<br /> <br /> == Material Files ==<br /> ''(Material files tell D3 what to do with your texture images. Without one, your texture will not work)''<br /> * [[Basic Material File]] ''-- (How to get a new texture in game)''<br /> * [[Surface Types]] ''-- (How to tell the engine whether your surface is stone, wood, grass, etc)''<br /> * [[Making Semi-transparent textures]]<br /> * [[Detail Textures]]<br /> * [[TDM Material Batch Conversion]] ''-- (Automatically convert materials to support the changes of TDM 1.03)''<br /> <br /> == Textures for Models ==<br /> * [[Creating Multiple Skins For A Model]] ''-- (How to swap different textures on the same model)''<br /> * [[DrVertexBlend (tutorial)]] ''-- (How to create smooth transitions between textures: Vertex Blending)''<br /> * [[Turning Shadows Off]] '' -- (How to turn shadows off to varying degrees)''<br /> <br /> == Other ==<br /> * [[Fast Re-Texturing of your Map]]<br /> * [[Grey Border Around Transparent GUI]] ''-- (sometimes transparent .tgas have an unwanted grey border)''<br /> * [[How To Make Your Own Visportal-texture]]<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26783 Material Files 2020-12-11T07:22:13Z

<p>Peter spy: /* Full example */ - typos</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> } <br /> }<br /> </pre><br /> <br /> <br /> As of TDM 2.08, none of the ambient stages are needed, so both this:<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> and this:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is redundant. Ambient rendering has its own dedicated function in the renderer now, and it doesn't use textures for it. The option is no longer in the game menu, but you can check it in the game console by typing '''tdm_ambient_method'''. It should be set to '''0'''.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26782 Material Files 2020-12-11T07:20:54Z

<p>Peter spy: /* Full example */</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> } <br /> }<br /> </pre><br /> <br /> <br /> As of TDM 2.08, none of the ambient stages are needed, so either this:<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> or this:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is redundant. Ambient rendering has it's own dedicated function in the renderer now, and it doesn't use textures for it. The option is no longer in the game menu, but you can check it in the game console by typing '''tdm_ambient_method'''. It should be set to '''0'''.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26781 Material Files 2020-12-11T07:17:36Z

<p>Peter spy: Removed the ambient stage section</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> } <br /> }<br /> </pre><br /> <br /> <br /> AS OF TDM 2.08, both this:<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> and this:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is '''no longer needed''' as ambient rendering has it's own dedicated function in the renderer now, and it doesn't use textures for it. The option is no longer in the game menu, but you can check it in the game console by typing '''tdm_ambient_method'''. It should be set to '''0'''.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26780 Material Files 2020-12-11T07:14:59Z

<p>Peter spy: /* Full example */ – removed the ambient stage and moved it to legacy section.</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Ambient Light Stage ==<br /> <br /> This block is no longer needed. By default, TDM uses ambient lights, not textures. The related option has been removed from the game menu in 2.08, but you can check it by typing '''tdm_ambient_method''' in the game console. It should be set to '''0'''.<br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> } <br /> }<br /> </pre><br /> <br /> <br /> AS OF TDM 2.08, both this:<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> and this:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is '''no longer needed''' as ambient rendering has it's own dedicated function in the renderer now, and it doesn't use textures for it. The option is no longer in the game menu, but you can check it in the game console by typing '''tdm_ambient_method'''. It should be set to '''0'''.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26779 Material Files 2020-12-11T07:08:15Z

<p>Peter spy: /* Add the Ambient Light Stage */ – changed to indicate this is no longer needed.</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Ambient Light Stage ==<br /> <br /> This block is no longer needed. By default, TDM uses ambient lights, not textures. The related option has been removed from the game menu in 2.08, but you can check it by typing '''tdm_ambient_method''' in the game console. It should be set to '''0'''.<br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> }<br /> <br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> }<br /> </pre><br /> <br /> <br /> AS OF TDM 2.0 the old Enhanced Ambient stage:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is '''no longer needed''' as ambient rendering has it's own dedicated function in the renderer now.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26778 Material Files 2020-12-11T06:44:20Z

<p>Peter spy: /* Add the Ambient Light Stage */ – deleted note on _black and _flat textures which seemed to be here by accident.</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Add the Ambient Light Stage ==<br /> <br /> This should go on all Dark Mod textures - see [[Virtual Ambient Light Textures]].<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> }<br /> <br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> }<br /> </pre><br /> <br /> <br /> AS OF TDM 2.0 the old Enhanced Ambient stage:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is '''no longer needed''' as ambient rendering has it's own dedicated function in the renderer now.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Material_Files&diff=26777 Material Files 2020-12-11T06:42:12Z

<p>Peter spy: /* Create a new Texture Definition */ – note on _black and _flat textures was misplaced.</p> <hr /> <div>{{Original_Reference|Fingernail & greebo|127}}<br /> <br /> <br /> <br /> == What the Heck is a Material File? ==<br /> The material files (.mtr) contain lists of 'material definitions' that tell the engine where to find the source files for the specified textures and what features it should have. All material files should be located in the '''darkmod/materials''' folder and have the extension '''.mtr'''. <br /> <br /> In fact, it's the material (=shader) which gets applied to surfaces of brushes, patches and models, not the actual TGA/DDS texture image. A TGA file cannot be applied to surfaces, it's the shader name which gets used.<br /> <br /> Polygons ==> Shader ==> Image(s) + Processing => Appearance<br /> <br /> Material definitions apply to a single 'texture', though it may be made up of multiple texture files blended together. A simple material definition looks like this:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/custom/redbrick_ed<br /> diffusemap textures/darkmod/custom/redbrick <br /> bumpmap textures/darkmod/custom/redbrick_local <br /> specularmap textures/darkmod/custom/redbrick_s <br /> }<br /> <br /> If you're using the ''material'' called '''textures/darkmod/stone/brick/redbrick_with_mortar''' in your map, Doom looks up the name in the material definition and loads the according image files (as specified by the [[Map Expressions]]). Note that you '''don't''' need to specify the file extension, the engine is automatically adding it (depending on your quality setting) and finds the according texture file. You also don't need to include the '''dds/''' prefix in the path, this is also added automatically.<br /> <br /> A single material file contains lots of material definitions. This is useful as textures that logically belong to each other are summarized in one material file (e.g. '''materials/tdm_stone_brick.mtr''')<br /> <br /> The .mtr files are read upon launching Doom 3 - changing your material file therefore requires either restarting Doom or typing '''reloadDecls''' in the console.<br /> <br /> == Create a new Texture Definition ==<br /> Provided you already saved your texture source file (the .tga or .dds) in the appropriate folder, you can go on and create your texture definition. You cannot use your textures without this step.<br /> <br /> Open up or create your personal material file with a text editor. There are existing guidelines for where texture definitions should go, for the sake of organization, but the engine doesn't care what the filename is as long as it's in the materials folder and has a .mtr extension. <br /> <br /> First, specify the name of your new material. If it is not a model texture, then the name should include the path to the texture files used. Example:<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> <br /> '''Note:''' Do not use special characters for your shader name or The Dark Mod parser might complain (e.g. no "&" (ampersand) or "-" (dash) characters, etc.)<br /> <br /> Then, open up a squiggly bracket ({), and start to fill in the texture paths as below, changing the paths and names for your texture.<br /> <br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed // editor image<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar // diffuse map<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local // normal map<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s // specular map<br /> }<br /> <br /> Close the definition with a close squiggly bracket (}).<br /> <br /> '''Note:''' If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.<br /> <br /> Save the file. Now you can load your new texture in [[DarkRadiant]] provided you did it all correctly.<br /> <br /> Alternatively you can also have a look a the existing material files and learn from them.<br /> <br /> == Add the Ambient Light Stage ==<br /> <br /> This should go on all Dark Mod textures - see [[Virtual Ambient Light Textures]].<br /> <br /> {{infobox|Note: If there is no specular map then substitute '''_black''', and if there is no bumpmap then use '''_flat''' instead.}}<br /> <br /> <pre><br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map <mappath/name><br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> </pre><br /> <br /> == Add the Frob Highlight Stage ==<br /> <br /> All materials need to have a conditional shader stage added to let the material highlight when the objects are frobbed. The technical details are of minor interest here, just copy and paste such a stage from other materials and adjust the diffusemap and bumpmap references.<br /> <br /> == Full example ==<br /> <br /> Here is the full example with the final material definition:<br /> <br /> <pre><br /> textures/darkmod/stone/brick/redbrick_with_mortar<br /> {<br /> // Use on of the predefined surface types like:<br /> // none, metal, stone, flesh, glass, wood<br /> stone<br /> <br /> // Or use "surftype15" and add the surface type as the first (or only) word of the description,<br /> // the following are possible:<br /> // tile, carpet, dirt, gravle, grass, rock, twigs, foliage, sand, mud, brokeglass, snow, ice, squeakboard,<br /> // puddle, moss, cloth, ceramic, slate, straw, armor_leath, armor_chain, armor_plate, climbable, paper, hardwood<br /> <br /> //surftype15<br /> //description "carpet This is a carpet texture."<br /> <br /> qer_editorimage textures/darkmod/stone/brick/redbrick_with_mortar_ed<br /> bumpmap textures/darkmod/stone/brick/redbrick_with_mortar_local<br /> diffusemap textures/darkmod/stone/brick/redbrick_with_mortar<br /> specularmap textures/darkmod/stone/brick/redbrick_with_mortar_s<br /> <br /> // This is the code required for frob highlighting this texture<br /> {<br /> if ( parm11 > 0 )<br /> blend gl_dst_color, gl_one<br /> map _white.tga<br /> rgb 0.40 * parm11<br /> }<br /> {<br /> if ( parm11 > 0 )<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> rgb 0.15 * parm11<br /> }<br /> <br /> // TDM Ambient Method Related<br /> {<br /> if (global5 == 1)<br /> blend add<br /> map textures/darkmod/stone/brick/redbrick_with_mortar<br /> scale 1, 1<br /> red global2<br /> green global3<br /> blue global4<br /> }<br /> <br /> }<br /> </pre><br /> <br /> <br /> AS OF TDM 2.0 the old Enhanced Ambient stage:<br /> <br /> <pre><br /> <br /> {<br /> if (global5 == 2)<br /> blend add<br /> program ambientEnvironment.vfp<br /> vertexParm 0 1, 1, 1, 1 // UV Scales for Diffuse and Bump<br /> vertexParm 1 1, 1, 1, 1 // (X,Y) UV Scale for specular<br /> vertexParm 2 global2, global3, global4, 1<br /> <br /> fragmentMap 0 cubeMap env/gen1<br /> fragmentMap 1 textures/darkmod/stone/brick/redbrick_with_mortar_local // Bump<br /> fragmentMap 2 textures/darkmod/stone/brick/redbrick_with_mortar // Diffuse<br /> fragmentMap 3 _black // Specular<br /> }<br /> <br /> </pre><br /> <br /> is '''no longer needed''' as ambient rendering has it's own dedicated function in the renderer now.<br /> <br /> == Special Keywords ==<br /> <br /> There are also some special keywords you can use:<br /> <br /> * noshadows - surface does not cast a shadow<br /> * noselfshadows - casts shadows, but not on itself<br /> * translucent - for things like glass<br /> * [[twosided]] - the surface will be duplicated and flipped, this causes it to be rendered twice. Useful for half-transparent things that should be visible from both sides. Normally surfaces are only visible from the front side (see note below)<br /> * noFog - do not render fog on this surface<br /> * Discrete - Dmap will not merge brushes with this material applied<br /> * NoFragment - Dmap will not split brushes with the material applied<br /> * nopicmip - The image_downsize settings will not affect this texture. Use sparingly, as low-end users need to use image_downsize to load larger maps.<br /> <br /> <br /> Note: <br /> <br /> http://www.iddevnet.com/doom3/materials.php<br /> <br /> twoSided Draw the front and back. '''Implies no-shadows''', because the shadow volume would be coplanar with the surface, giving depth fighting<br /> <br /> Use a nodraw surface with forceShadows to address this.<br /> <br /> == See also ==<br /> * [[Texture Guidelines]]<br /> * [[How to add Textures to The Dark Mod]]<br /> * [[Texture Creation - Basic Tutorial]]<br /> <br /> {{tutorial-textures|sort=Material}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=DDS_creation&diff=26627 DDS creation 2020-08-19T19:55:42Z

<p>Peter spy: /* Textures in TDM */</p> <hr /> <div>''AUGUST 2020 - REWRITE IN PROGRESS''<br /> ''All prior content here has been moved to new page [[DDS Creation with ATI Compressonator]].<br /> <br /> ==Introduction to DDS==<br /> <br /> DDS (Direct Draw Surface) is an image format often used in games due to its significant advantages over other file types:<br /> <br /> '''No need for conversion during load''': This is a target format in which textures are stored in your GPU memory. Other image types, like TGA, have to be converted during loading, and that makes the whole process longer.<br /> <br /> '''Better image quality with mipmapping''': Game engines use LOD systems to generate textures further away from the player, but (without mipmaps available) that results in blurred image and moire patterns. Mipmaps are scaled-down versions of your texture, stored within the same file as the full-scale texture. Mipmaps will improve image quality, the transition between LOD stages, and overall performance. More on mipmapping: https://en.wikipedia.org/wiki/Mipmap<br /> <br /> '''Very efficient compression''': Depending on the DDS compression format, a typical results is around 25% of the original uncompressed file. For example, a 2048x2048 px RGB texture saved as uncompressed TGA will be around 12 MB. Save it as DDS, and you'll go below 3 MB. Other formats like PNG or Zip compression will give you around 9 MB.<br /> <br /> ==Textures in TDM==<br /> <br /> TDM can handle textures in either TGA or DDS formats. For guidance in preparing compliant texture files, applicable to both formats, see:<br /> * [[How_to_add_Textures_to_The_Dark_Mod]]<br /> * [[Texture_Guidelines]]<br /> <br /> <br /> '''Folder structure in your FM'''<br /> <br /> While all TGA files go to:<br /> <br /> yourFmRootFolder/textures/''[optional subfolder(s)]''<br /> <br /> DDS files should go to:<br /> <br /> yourFmRootFolder/'''dds'''/textures/''[optional subfolder(s)]''<br /> <br /> In other words, you need to copy-paste your folder structure into the dds directory.<br /> <br /> '''Priority''': TDM gives DDS files higher priority than TGAs. If you have both for a given material, the engine will only load the DDS.<br /> <br /> '''Leave Normal Maps as TGA''': You can safely convert diffuse and specular textures to DDS. But normal (bump) maps are not images in the traditional sense; they're more like vector maps. Any lossy compression will always introduce some artifacts and otherwise damage that data. To be on the safe side, keep normal maps as TGAs.<br /> <br /> ==DDS Creation, In General ==<br /> <br /> '''Compression Formats''': DDS files can be compressed in different ways, depending on source image requirements. As a general rule, use -<br /> * DXT1 compression with RGB images<br /> * DXT5 for textures with alpha channel transparency<br /> More info on compression formats: http://wiki.polycount.com/wiki/DXT<br /> <br /> '''Mipmaping''': Mipmap generation is mandatory in TDM. Otherwise DDS textures won't show in game and you'll get console errors.<br /> <br /> TIP: You can improve texture quality - at no additional performance cost - by using the best mipmaps scaling filter available in the DDS file export settings. Usually they're ordered from faster/low-quality to slower/high-quality.<br /> <br /> ==DDS Creation with Specific Tools==<br /> * [[DDS Creation with GIMP]]<br /> * [[DDS Creation with ATI Compressonator]]<br /> <br /> ==General Workflow Tips==<br /> <br /> * Convert to DDS only after you have finalized textures that make up your material. There are at least two reasons for that:<br /> <br /> : '''DDS format isn't suited for fast iteration''': You have to restart the game and reload the map to see the any changes. With TGA files, you just need to use a refresh command to see your changes in an instant.<br /> <br /> : '''DDS compression is lossy''': While the compression ratio is pretty great, it slightly reduces image quality. You shouldn't work on DDS textures directly, as you'll decrease image quality with each save. Keep your source files and work on them instead, then export TGAs to DDS when you're happy with the final result.<br /> <br /> * Planning to revise and test your material's textures? Besides re-exporting the updated textures as TGA, be sure to delete its old DDS textures, that would have priority.<br /> <br /> ==Testing Your DDS Texture==<br /> Mipmapping is affected by in-game Anisotropic Filtering. Set it to x16 to ensure maximum image quality while testing your materials.<br /> <br /> ==See Also==<br /> * [http://wiki.polycount.com/wiki/DXT DDS compression formats]<br /> * [https://en.wikipedia.org/wiki/Mipmap Mipmaps]<br /> <br /> [[Category:Tutorial]]<br /> [[Category:Textures]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Cube_maps&diff=26340 Cube maps 2020-04-18T23:26:03Z

<p>Peter spy: </p> <hr /> <div>'''Note from peter_spy:'''<br /> ''This tutorial is largely outdated and needs substantial revision. E.g. you can add cubemap reflections to many more materials, from marble floors to metals. The shader code used here is also wrong as it doesn't use alpha stage for the cubemap. You will want to control the cubemap strength, typically via texture and alpha multiplier.''<br /> <br /> ''written by angua''<br /> <br /> <br /> How to create a cube map (also called environmental map) of your environment using the envshot command in TDM.<br /> <br /> Cube maps can be used to fake reflections e.g on water and highly reflective tiles, etc. The advantage is that rendering is faster. <br /> <br /> You can also find more inflormation on Cube maps in the modwiki: [https://modwiki.dhewm3.org/Cube_maps Cube Maps]<br /> <br /> ==Create your room==<br /> Create the room you want to have your pseudo-reflective water in. Add all the large parts, but you can leave small details (and of course the AI) out. Your room might for example look like this:<br /> <br /> [[Image:Cube map empty.jpg|320px|Example room]]<br /> <br /> ==Create your images==<br /> * Set the screen resolution of TDM to 640 x 480. If you don't, parts of your images will be cut off and they will not fit together any more. You will have to restart TDM or use console command vid_restart for the changes to take effect.<br /> <br /> * Open your map in TDM and get to the position of your water (at the center of the water source, about surface level, you can use noclip if you can't get there by walking).<br /> <br /> * In the console, type<br /> <br /> envshot [prefix] [size]<br /> <br /> [prefix] is how the images are going to be named. The size should be in powers of two. For example, your command could look like this:<br /> <br /> envshot water_pool 512<br /> <br /> Press enter, and you will see some flickering on the screen while your images are created, and a message in the console will appear saying <br /> <br /> Wrote env/water_pool_nz.tga,etc.<br /> <br /> You might want to make a few more envshots at slightly different positions, so that you don't have to repeat the whole procedure if your images are not appropriate. The direction at which you are facing during the shots is not important.<br /> <br /> * You should now see six new images in your /env folder:<br /> <br /> water_pool_nx.tga<br /> water_pool_ny.tga<br /> water_pool_nz.tga<br /> water_pool_px.tga<br /> water_pool_py.tga<br /> water_pool_pz.tga<br /> <br /> looking like this:<br /> <br /> [[Image:Cube map.jpg|320px|Cube map after shot]]<br /> <br /> You can of course also move them to a different folder if you want.<br /> <br /> ==Edit your images==<br /> :''This section won't be necessary in TDM 2.04. The images will be named and oriented correctly.''<br /> <br /> If you leave the images like this, they will not work ingame. You have to rename them and there is also some rotating and flipping required. (Note that this works for me if the reflecting surface is located at the bottom facing upwards, the required procedure might be different if the reflection is located at the walls or the ceiling).<br /> <br /> * Rename water_pool_nx to water_pool_back. Rotate it 90° counter clock wise and flip it horizontally. This is going to be located at the west.<br /> * Rename water_pool_ny to water_pool_right. Flip it horizontally. This is going to be located at the south.<br /> * Rename water_pool_nz to water_pool_down. You don't have to manipulate the direction here, since it is located at the bottom and will not be visible anyway.<br /> * Rename water_pool_px to water_pool_forward. Rotate it 90° clock wise and flip it horizontally. This is going to be located at the east.<br /> * Rename water_pool_py to water_pool_left. Rotate it 180° and flip it horizontally. This is going to be located at the north.<br /> * Rename water_pool_pz to water_pool_up. Flip it horizontally and rotate it 90° counter clock wise.<br /> <br /> *Rename water_pool_nz to water_pool_down. You don't have to manipulate the direction here, since it is located at the bottom and will not be visible anyway.<br /> <br /> You should now have six files in your /env folder (or wherever you moved them) called<br /> <br /> water_pool_back<br /> water_pool_right<br /> water_pool_down<br /> water_pool_forward<br /> water_pool_left<br /> water_pool_up<br /> <br /> looking like this:<br /> <br /> [[Image:Cube map processed.jpg|320px|Cube maps processed]]<br /> <br /> You can also add some blurryness if you want. That makes it less obvious that the reflection is faked by a static image.<br /> <br /> ==Write a material shader==<br /> Open an already existing material file or create a new one. Add the following shader:<br /> <br /> textures/env/water_pool<br /> {<br /> qer_editorimage env/water_pool_up.tga<br /> <br /> noFragment<br /> noshadows<br /> noimpact<br /> nooverlays<br /> forceOpaque<br /> nonsolid<br /> <br /> {<br /> forceHighQuality<br /> blend add<br /> cameraCubeMap env/water_pool<br /> texgen reflect<br /> }<br /> }<br /> <br /> If you have forceOpaque in your shader, the texture will be opaque and you will not be able to see the ground. If you leave it out, it will be semi-transparent and you can see the ground also.<br /> If you moved the images to a different folder, make sure that the correct paths are entered at the qer_editorimage and the cameraCubemap lines. (The path entered in the name of the shader (before the { ) is for the folder the texture will appear in Darkradiant. It can be different from the path the images are in.)<br /> <br /> ==Get your enviromental map ingame==<br /> <br /> * Open DarkRadiant (if you already have it open you might have to close and reopen it to be able to see the texture).<br /> * Draw a brush that is going to be your water. Texture it with common/nodraw.<br /> * Go to the media browser. You should find your texture in the /env folder. (If you wrote another path in the name of your shader, it will appear there.)<br /> [[Image:Cubemap1.jpg|300px]]<br /> <br /> * Apply it to the top face of the water brush. You should now see the water_pool_up image as editor image (that's what the qer_editorimage line in the shader was for). Scale and position of the texture is not important.<br /> <br /> [[Image:Cubemap2.jpg|300px]]<br /> * Convert the brush to a func_liquid. (You don't want to be able to walk on water, do you? That would happen if you didn't convert your brush.) For more detailed information on water creation, you can also look at the [[Swimmable Water]] tutorial.<br /> <br /> * you should now be able to see your water ingame. <br /> <br /> [[Image:Cubemap3.jpg|300px]]<br /> <br /> It will still look flat, like a mirror, and you will see that it is a static image (the torch is not flickering) so you might want to add a patch slightly above the water textured with, e.g. water_clear (or any other water texture that produces water waves).<br /> <br /> [[Image:Cubemap4.jpg|300px]]<br /> <br /> Here you can see the same pool textured with true reflective water for comparison:<br /> <br /> [[Image:Cubemap5.jpg|300px]]<br /> <br /> ==Notes==<br /> <br /> You have to take into consideration that in contrast to a true reflection, the cube map texture will not react to changes in the environment. So if you for example put the torch out, it will still be lit in the cube map.<br /> <br /> [[Image:Cubemap6.jpg|300px]]<br /> <br /> So it would be more practical to have non-extinguishable lights and no large moveables near the water.<br /> <br /> {{tutorial-editing}}<br /> [[Category:Skybox]]<br /> [[Category:Mapping Tutorials]]</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Talk:Texture_Sources&diff=26108 Talk:Texture Sources 2020-01-29T10:24:07Z

<p>Peter spy: </p> <hr /> <div>'''PeterSpy:''' I think we should avoid putting similar sites with free CC0 PBR materials just for the sake of it. Their actual behavior should be checked as well.<br /> For example, 3D Textures only has 1k textures and mixes lossy jpegs with pngs, Share Textures has annoying popup messages and lossy jpegs, etc.</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Talk:Texture_Sources&diff=26107 Talk:Texture Sources 2020-01-29T10:20:28Z

<p>Peter spy: A suggestion, what to avoid</p> <hr /> <div>I think we should avoid putting similar sites with free CC0 PBR materials just for the sake of it. Their actual behavior should be checked as well.<br /> For example, 3D Textures only has 1k textures and mixes lossy jpegs with pngs, Share Textures has annoying popup messages and lossy jpegs, etc.</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25389 Texture Sources 2019-05-15T15:50:40Z

<p>Peter spy: </p> <hr /> <div>Here is a list of sites where you can download some decent textures.<br />Note that most textures available these days are procedurally generated and made for PBR materials. TDM uses a non-PBR engine (idtech4), so these textures typically require some work to make them look good in game. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> * [https://quixel.com/megascans/library/free Quixel Megascans] – Textures and models, selected free assets. Signup required.<br /> <br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25388 Texture Sources 2019-05-15T15:45:18Z

<p>Peter spy: </p> <hr /> <div>Below is a list of sources from which good textures can be found. Note that most textures available these days are procedurally generated for PBR materials. TDM uses a non-PBR engine (idtech4), so these textures typically require some work to make them look good in game. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> * [https://quixel.com/megascans/library/free Quixel Megascans] – Textures and models, selected free assets. Signup required.<br /> <br /> <br /> Please add to this list.<br /> <br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25387 Texture Sources 2019-05-15T15:42:07Z

<p>Peter spy: </p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> * [https://quixel.com/megascans/library/free Quixel Megascans] – Textures and models, selected free assets. Signup required.<br /> <br /> <br /> Please add to this list.<br /> <br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25386 Texture Sources 2019-05-15T15:41:50Z

<p>Peter spy: </p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> * [https://quixel.com/megascans/library/free Quixel Megascans] – Textures and models, selected free assets. Signup required.<br /> <br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25385 Texture Sources 2019-05-15T15:39:59Z

<p>Peter spy: </p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> * [https://quixel.com/megascans/library/free Quixel Megascans] – Textures and models, selected free assets. Signup required.<br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25384 Texture Sources 2019-05-15T15:38:19Z

<p>Peter spy: /* Other sources */</p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Textures, brushes, models, and HDRI maps, usually for architectural rendering. Only some of those are free. Textures from 1k to 8k. Requires login credentials.<br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25383 Texture Sources 2019-05-15T15:34:51Z

<p>Peter spy: /* Free */</p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> * [https://texturehaven.com/textures/ Texture Haven] – 1k to 8k textures, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – 2k to 8k textures and Substance files, no registration required.<br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Some free content, requires login credentials.<br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25382 Texture Sources 2019-05-15T15:33:16Z

<p>Peter spy: /* Not completely free */</p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> <br /> * [https://texturehaven.com/textures/ Texture Haven] – All textures are free, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – Free textures only, no registration required.<br /> <br /> ===Other sources===<br /> * [https://www.poliigon.com/search?is_free=true Poliigon] – Some free content, requires login credentials.<br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy https://wiki.thedarkmod.com/index.php?title=Texture_Sources&diff=25381 Texture Sources 2019-05-15T15:31:43Z

<p>Peter spy: /* Free */</p> <hr /> <div>Below is a list of sources from which good textures can be found. These are not sites with ready built textures, there is some work to make them look good in TDM. See [[Textures]] for more information.<br /> <br /> ===Free===<br /> <br /> * [https://texturehaven.com/textures/ Texture Haven] – All textures are free, no signup required.<br /> * [https://cc0textures.com/ CC0 Textures] – Free textures only, no registration required.<br /> <br /> ===Not completely free===<br /> * [http://www.cgtextures.com/ CGTextures] - Good, well prepared.<br /> <br /> Please add to this list.<br /> <br /> {{textures}}</div>

Peter spy