Search the Community

Relax @Näkki, it's great to hear you enjoyed the game. My personal expectations were just a bit different when I read the Steam page, although the various trailers should have been a warning that stealth maybe wasn't the biggest priority of the devs. From the Steam page: "Weird west legends meet eldritch horror in BLOOD WEST, an immersive stealth FPS." Also "Blood West is a stealth FPS inspired by the genre classics such as the Thief series (whose fans will be happy to hear the voice of Stephen Russell, the actor voicing the master-thief Garrett, returning here as the protagonist), S.T.A.L.K.E.R. games, or - from the contemporary catalog - Hunt: Showdown. The gameplay rewards the careful approach: scouting the area, stalking your enemies, and striking from the shadows. Can you figure out a way to clear a fort full of ghouls and monsters without raising an alarm?" From my personal experience I think the game is predominantly Hunt: Showdown, a bit of S.T.A.L.K.E.R. and a very small portion Thief. Stealth is very unforgiving and makes it almost impossible early game when there are various enemies around, but hey maybe I just suck at it. I don't see Deus Ex in it, unless the skill leveling is the Deus Ex part for you and then I have to disagree with you, as that seems like the trait system in Hunt: Showdown. Edit: What I also understood from the Steam forums is that the original VA was dropped close before the release of the full version and replaced by Russell with no real explanation from the devs why this was done.

I don't know if it's mentioned anywhere else on the Wiki, but it's worth mentioning that the first global keywords are for sound: // Use on of the predefined surface types like: // none, metal, stone, flesh, glass, wood stone And this: //surftype15 //description "carpet This is a carpet texture." I think this is sound as well, but I also think 'description' does other stuff, for example for using with vine arrows: stone description "vine_friendly" If someone has a list (or link to code) where all this is defined for TDM so mappers are aware, that would be useful. I would also move the 'special keywords' section up so it's before the obsolete stuff - that old stuff needs to be relegated to the very bottom. I would also change the title of that section from 'No ambient and frob -stages needed' to something like 'Deprecated stages' and say it's just there for historical reference.

This can be removed as well, you don't need to specify texture map slots you don't use. In some cases you even shouldn't.

Ambient atmospheres are in my opinion one of the best parts of the Dark Mod experience, not just for getting a mission to have the right feel but also for inspiration and to have them playing in the background when creating maps. The more the merrier, so here's a thread to collect all the links to ambient music and environmental sounds that could have a spot in TDM's setting. Ambients from the TDM forums Gast's Eerie Lullabies Magnanimous Merry's Miscellanea Orbweaver's Dark Ambients Spadey's Ambients Radioteque's Ambients Kyyrma's Composing Ambient Tracks for Dummies - Kyyrma shows how ambient soundtracks can be made from a set of sounds. Also contains some of his finished ambients. Request for more interior sounds - this thread is a very productive community session where members came up with a large and good selection of new ambients. Uncle Peti's Sound Den Dragofer's Ambients - post #6 in this thread SeriousToni's Ambients - posts #8, 12, 15 and 19 in this thread Ambients from the TTLG forums Custom resources list Gigagooga's Ambients 1 - possibly the largest pack of ambient musics and nature sounds, all of them high quality. Gigagooga's Ambients 2 - this pack puts more weight on shorter swells/hits/pads to be layered on top of a subtle ambient. Gigagooga's Ambients 3 Yandros' ambient loop Sephy's Ambients - a large collection of ambient pieces, including many shorter ones which will be valuable for anyone wanting to try a layered ambience approach like in the Thief OMs and Full Moon Fever. Internet databases www.freesound.org - some of the better composers in my opinion are ERH and BrandonNyte. www.purple-planet.com - a large selection of all kinds of ambient and musical soundtracks to be used freely. www.darkwinter.com - an internet label that publishes a lot of dark ambient music under a Creative Commons license. www.endlessascent.com - sister website of Darkwinter for non-dark ambients. Youtube Asatru Dark - also has very nice reference images for outdoor stone memorials, statue arrangements etc. #4 Void by Raffaele du Marteau & #6 Dreaming of Nowhere by Raffaele du Marteau - possibly the most forlorn pieces I've found on the internet. Alacazam - a prolific Creative Commons ambients composer . Cryo Chamber - for-profit label for dark ambient music with a large selection on offer. Going by their Youtube comments they're fine with people using their soundtracks for games etc., although you'd probably need to buy the soundtracks first. Dark Ambient Mixed Session - as much ambient as something to have in the background while mapping.

Shouldn't these (I cannot find them in DR) have a mirror effect applied, like models/darkmod/kitchen/tea_tray_silver2.ase ? I guess this is some brush with texture bc_teatray applied? Although this texture has the mirror effect applied.

I just recently became aware of this feature: https://wiki.thedarkmod.com/index.php?title=Particle_collisions_and_cutoff Unfortunately I completely missed it, as when I went to create weather effects in my FMs I just followed this (which doesn't mention it): https://wiki.thedarkmod.com/index.php?title=A_-_Z_Beginner_Full_Guide_Page_3#Rain_and_Snow The point of this thread is to a) make people aware of it and b) gather feedback from any mappers that have used it so we can get some mapper-focused documentation in the Wiki. The page above is great for background information about how it works, but as a mapper I really just want to know: What are the limitations of this (i.e. when should it be used and when shouldn't it be used)? Why isn't it the default behaviour? Why all this work to get it into the map? What built-in support for it exists (particle definitions, materials, etc). Do I need to create all this stuff myself? Texture layout vs. Linear layout: what's the difference in the end, pros/cons, why would I use one over the other... Why does it need a separate command (runParticle)? Can this just not be bundled in with dmap? A clear, step-by-step instruction on how to implement it in a map from beginning to end using a simple use case. Tagging some users who have relevant experience with this: @stgatilov @Goldwell @Amadeus

No warnings during dmap re: the patch, how do I check if a patch has a "[0..1] non-overlapping texcoords"? Is it correct in interpreting that to mean the texture has been fit to the patch? If so then yes. This is the patch copied from DR if that helps: <?xml version="1.0" encoding="utf-8"?> <map version="1" format="portable"> <layers> <layer id="0" name="Default" parentId="-1" active="true" hidden="false"/> </layers> <selectionGroups> <selectionGroup id="415" name=""/> <selectionGroup id="416" name=""/> <selectionGroup id="417" name=""/> <selectionGroup id="418" name=""/> <selectionGroup id="420" name=""/> <selectionGroup id="421" name=""/> <selectionGroup id="423" name=""/> <selectionGroup id="424" name=""/> </selectionGroups> <selectionSets/> <properties> <property key="EditTimeInSeconds" value="20837"/> <property key="LastCameraAngle" value="69 332.186 0"/> <property key="LastCameraPosition" value="20.0088 1653.64 531.677"/> <property key="LastShaderClipboardMaterial" value="textures/darkmod/nature/snow/snow_rough01"/> </properties> <entity number="0"> <primitives> <patch number="0" width="3" height="3" fixedSubdivisions="false"> <material name="textures/darkmod/weather/rain2_heavy2024mtr"/> <controlVertices> <controlVertex row="0" column="0" x="-448.000000" y="1712.000000" z="720.000000" u="0" v="0"/> <controlVertex row="1" column="0" x="-448.000000" y="1568.000000" z="720.000000" u="0" v="0.500000"/> <controlVertex row="2" column="0" x="-448.000000" y="1424.000000" z="720.000000" u="0" v="1.000000"/> <controlVertex row="0" column="1" x="-76.000000" y="1712.000000" z="720.000000" u="0.500000" v="0"/> <controlVertex row="1" column="1" x="-76.000000" y="1568.000000" z="720.000000" u="0.500000" v="0.500000"/> <controlVertex row="2" column="1" x="-76.000000" y="1424.000000" z="720.000000" u="0.500000" v="1.000000"/> <controlVertex row="0" column="2" x="296.000000" y="1712.000000" z="720.000000" u="1.000000" v="0"/> <controlVertex row="1" column="2" x="296.000000" y="1568.000000" z="720.000000" u="1.000000" v="0.500000"/> <controlVertex row="2" column="2" x="296.000000" y="1424.000000" z="720.000000" u="1.000000" v="1.000000"/> </controlVertices> <layers> <layer id="0"/> </layers> <selectionGroups/> <selectionSets/> </patch> </primitives> <keyValues> <keyValue key="classname" value="worldspawn"/> <keyValue key="difficulty0Name" value="easy"/> <keyValue key="difficulty1Name" value="medium"/> <keyValue key="difficulty2Name" value="hard"/> <keyValue key="shop_skip" value="1"/> </keyValues> <layers> <layer id="0"/> </layers> <selectionGroups/> <selectionSets/> </entity> </map>

@Geep Regarding 0.24 vs 0.25 font scale. I think there was purpose, though I can't say now which exactly. Maybe it was to ensure that all the text fits, maybe it was to make vertical padding symmetric. Anyway, why do you think 0.24 and 0.25 differ? I did not look in the code yet, but I think what engine does is 1) choose most suitable image, 2) render quad texture with it. Indeed, we can avoid some blurring if the pixel size of the quad exactly matches the image size. But I guess the engine counts font size in 640x480 virtual resolution. So even if the font size would be "12", it would later be stretched over whatever width you really have (if your aspect ratio is 16:9 then height would be stretched equally, but otherwise it would be stretched with different factor).

DarkRadiant 3.8.0 is ready for download. What's new: Feature: Support new frob-related material keywords Improvement: Mission selection list in Game setup is not alphabetically sorted Improvement: Better distinction between inherited and regular spawnargs Improvement: Silence sound shader button Improvement: Add Reload Definitions button to Model Chooser Fixed: Model Selector widgets are cut off and flicker constantly on Linux Fixed: DarkRadiant will not start without Dark Mod plugins Fixed: GenericEntityNode not calculating the direction correctly with "editor_rotatable" Fixed: RenderableArrow not drawing the tip correctly for arbitrary rotations Fixed: Light Inspector crashes on Linux Fixed: Models glitch out when filtering then showing them Fixed: Skin Editor: models not centered well in preview Fixed: "Copy Resource Path" includes top level folders Fixed: Skin Editor: internal test skins are shown if Material Editor was open previously Fixed: Changing Game/Project doesn't update loaded assets correctly Fixed: Model Chooser: initially hidden materials aren't revealed when enabling them Fixed: Choosing AI entity class 'atdm:townsfolk_commoner_update' causes crash Fixed: Sporadic assertion failure on shutdown due to LocalBitmapArtProvider destruction Fixed: Prefab Selector spams infinite error dialogs on Linux Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.8.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!

So, if I understand you, no Thief Gold FM does sound and text notifications of completed objectives? The missions in The Black Parade surely did. I'm completely confused now. I was sure that original Thief Gold had those objective complete notifications (at least the sound). Reading this thread suggests otherwise though: https://www.ttlg.com/forums/showthread.php?t=132977

I have a map, with a stone texture. I want to replace it with a new texture I made. However, there's 4,430 faces with this texture. I can use the find and replace to swap the textures, however, now the scale is wrong. How can I select all faces with the same texture? EDIT: Solved, check solution on next post

Greetings everyone! I recently got into TDM and am already having a lot of fun playing through and ghosting missions. However, coming from Thief, I am mostly relying on the rules and my experience with that game, while there are clearly differences in how TDM works. Right now, there is talk in the ghosting discussion thread on TTLG to amend the ruleset and include clarifications pertaining to TDM. So I wanted to drop by and ask: is there an active TDM ghosting community already and have any rules for this playstyle been developed? I would also like to ask someone to take a look at the draft of this addendum to see whether everything looks correct: https://www.ttlg.com/forums/showthread.php?t=148487&page=16&p=2473352&viewfull=1#post2473352 Thanks!

Make sure the gas lamp light is not set to no shadows. Same with the wall texture, make sure you didn't accidentally use _ns version of a texture

A Problem Arises I've paused subtitling of the Lady02 vocal set, because of a problem with the voice clips described here: https://forums.thedarkmod.com/index.php?/topic/21741-subtitles-possibilities-beyond-211/&do=findComment&comment=490151 While a way forward is being determined, I'll work on a different vocal set. Maybe manbeast, for which Kingsal just provided me the voice script.

Particle collisions cannot be computed in realtime, particles are purely graphical effect which cannot interact with collisions. So the collisions have to be precomputed beforehand, just like dmap precomputes triangulations of brushes. Most of the nuances grow from here. It was possible in theory to run it automatically during dmap (just like e.g. you never have to run aas tool directly, because dmap calls it automatically), but I'm afraid it would annoy everyone because it may take quite a lot of time depending on settings. Now that some people have some practice with this, should we change it? Most importantly, collisions are precomputed statically. If you move the emitter, the collision information becomes wrong. All objects which seem dynamic are automatically excluded from precomputation, so the particles will still go straight through all the guards and moveables. What do you mean by "default" behavior? Default behavior of what? particles? Like make all particle emitters stop on collisions automatically? What about cases when mapper wanted particles to pierce walls? What about moving particle emitters? The goal was to reduce amount of work actually. As soon as you are able to set one huge particle emitter over the whole map, I think you don't have to mess with it any more, just remember to execute runParticle occasionally when you want up-to-date collisions. Before that, mapper had to split the rain patch into many patches and manually tweak every patch so that it stops at proper height. As far as I understand, it was very time-consuming and painful. As for areaLock, it does not restrict particles to single area. It only disables the whole system if renderer proves player does not see the specified area. As long as the door is open, you should still see rain falling indoors, no? Yeah, this is a tough question. Texture layout: Only works properly if particle evolves exactly the same way if emitted from the same location. Interacts with texturing: requires you to set non-overlapping texcoords in 0..1 range on the emitting surface. The only option in TDM 2.08. Ok for straight-falling rain, but snow is out of question. Linear layout: Only works for a periodic system, i.e. the whole system exactly repeats itself after some time. Precomputation might take a lot of time, especially if you insist on a large period. [problem for maintainers like me] If particle code is changed in TDM engine, the collisions must be recomputed. Was added in TDM 2.09. Supports pretty much any kind of particles, although snow was the main goal.

Of course, it is one of the reasons for the decline of online forums, since the advent of mobile phones. Forums on a mobile are a pain in the ass, but on the other hand, for certain things there are no real alternatives to forums, social networks cannot be with their sequential threads, where it is almost impossible to retrieve answers to a question that is asked. has done days ago. For devs for internal communication, the only thing offered is a collaborative app, such as System D (not to be confused with systemd). FOSS, free and anonymous registration, access further members only by invitation, full encrypted and private. https://www.system-d.org

Black Parade is released ! https://www.ttlg.com/forums/showthread.php?t=152429

Here's an example. For testing I created a room out of a bush and put the portal sky texture on the inner side. This is the portal sky texture in the background and it's just used to seal my playgorund. In the foregound you see a lever, which is supposed to open a secret door. The wall and secret door also have the portal sky texture. So I'm hoping to see my skybox on the wall, which you could then open and be in another room all of a sudden. This is what it looks like in DR: And here's an ingame screenshot. As you can see, instead of the skybox texture the wall is invisible. The player is supposed to see the sky instead. Also, I'm looking for a way to use multiple skyboxes. Since there's only one portal sky texture I don't see an elegant way to do this. I'd imagine that this would requrie naming the skyboxes and scripting the portal sky texture, in order route it to the currect skybox. But thats just me guessing on a potential solution, without having the actual technical skills yet.

Body awareness please. https://forums.thedarkmod.com/index.php?/topic/20013-are-you-gonna-add-this/

I loved it. Awesome game. I faceplanted at the people who asked for quest markers in the Steam forums there... Herr, lass Hirn regnen. The game is so great, and so true to the original, because it doesn't hold your hand. When is the new breed of gamers gonna learn.

Builder Compound Pack will help you create better environments for your Builder-themed map sections! The aim of this experimental package is to provide high-quality models, materials, and other assets that don't put a big strain on the idtech4 engine. This early version is slightly more bare-bones than I wished for, as some modular sets (e.g. the roof) proved to be too complex and unfit for general use. Don't worry though, the set will be updated and expanded in future releases. Tweaks – Arch door and arch with hinges models have been removed. They were just static models, not actual door entities, and they weren't super useful, e.g. hey couldn't act as visportal closing entity due to gaps and transparent parts. – Detail texture stage added to selected materials (mostly those you can get very close to). As you approach a surface, you should see a slightly grainy layer that enhances the details. New content – Door01 and door01_frame have been added to both models and entities. This is a basic door for this corridor section. By default, it's locked (with easy lock) and AI will notice if it's left ajar. You may want to disable the latter (set ShouldBeClosed to 0) if you have a section with many AIs and doors, as it will probably disrupt AI patrolling too much. The frame will work with walls that are 16 units thick. Both door and the frame will work with grid of 8 and smaller. You can use the grid of 4 to change the door position within the frame. Look for grooves in the frame model. First of all, launch the map to see a simple section that was made with these assets. Use the menu or type map bc in the console to start the map. Noclip though the north wall, if you want to get to the staging area and see all pieces used to make this section. General info and tips: Make sure you have Rotate func_* entities around origin (Ctrl+R) enabled (Dark Radiant top icons) to use models efficiently. All models have custom pivot / origin point placement to make them snap to grid and geometry really fast. If you have keyboard shortcuts configured for RotateSelectionX/Y/Z and FloorSelection, placing these models around the map will be a breeze. I also recommend having shortcuts for SelectNudgeUp/Down/Left/Right, so you can move models in ortho views without using a mouse. DR detects models in a weird way, e.g. if your model is one-sided, or has some faces turned back to the camera in ortho view, selecting and moving it around will be difficult. Using keyboard is often more seamless and precise. You can select a model in perspective view, and then move it around in X/Y/Z plane using keyboard. Optimal scale for tileable materials is 0.125. This provides good pixel density vs repetition. Materials are optimized to be used both with and without post-processing, and the default gamma of 1.2. In some cases, specular hotspot might look slightly overblown with post-processing enabled. Correct look without post-processing was the first priority. Same principles apply to using lamp. The main idea behind this set is that you can use simple brushes for walls and floors, and wall panels have proper offset, so you don't need to use special surrounding BSP behind them. You can place panels right where your walls are, and there will be no z-fighting or clipping. Assumed basic measure for a corridor is 192 x 192 (length / width), but you can go lower if you don't plan to use arches and metal doors. The smallest wall panel piece is 24 units long. Use brushes to create basic space, then adjust it to what you can make with wall panels (combinations of 24, 48, 96, 192 etc.). DR's measurement tool is your friend. Default grid for placing most pieces is 8, but it goes down with smaller / more complex models and setups. One special case is matching metal doors to arch with hinges, this needs grid of 2. That's a mistake on my part. I didn't think of better pivot placement until it was too late. The example map contains a "staging area" where you'll find grouped arch, hinges, and doors, so you can use that as a template. As per The Dark Mod license, you may modify this pack's contents, although I'd advise against it. Most textures are compressed in lossy DDS format and compressing them again will result in loss of image quality. If you want to make changes, need alternative versions of a model or material contact me first. I'll see what I can do. Last but not least, I hope you'll find this pack useful and fun to work with, as I had plenty of fun while making it I already have a long list of models and features to include in subsequent releases, but I'm always open to feedback and suggestions. Thanks! Credits: Springheel, Obsttorte, Spooks, nbohr1more, STiFU, Destined and other TDM Forum members: guidance, encouragement, and fruitful discussions Epifire: asset feedback and critique The Black Arrow: inscription texts Plans for upcoming releases: Corridor: - Fixing the wall panel collision model, so strafing along it isn't wobbly Done. - Roof modular set Done. - Making metal door an entity with proper sounds and open/close times. Done, made proper door instead. - Floor switch model/entity for metal doors - Window set Done. Roadmap: All work is on hold for now. I'm working on a small FM that will use some of these assets plus many more. Some of existing assets will get reworked too. All links are taken down, and I have no release date yet, sorry.

I have quite a few assets from WIPs I'll probably never use elsewhere, so I thought I could share it here. Some of these are older and not necessarily matching the TDM lore, but I hope someone will find use for them. In terms of package format, I'll be creating 7zip packages with just model and/or texture files, so you can place them wherever you like in your project. I'll also include example material or def setup. I'll leave textures in .tga format, so you can make edits on uncompressed source and save as .dds later. So first up is a door/frame/key combo: Temp upload of all assets: https://we.tl/t-BOdrlNEXWJ See readme_notes for design / placement instructions.

So giving it none of those tags, but making the AI invisible, silent, non-solid, and on a team neutral to everyone would not work? Oh well, it was a horrible inelegant idea anyway.

Right, I forgot that's also a reason why TDM has every single texture from cgtextures listed in license.txt. But, according to current EULA, that might not be enough: