Search the Community

You cheeky nandos. XD Have you not considered using the screen? She walks behind it, there is a shadow of her lifting her arms, the light flickers - POOF - model swap, she steps out clothed. Although, there had to be something preventing the player from walking behind the screen. I liked how you handled her undressing to begin with. What startled me earlier tho, along with creepy music while the Builder's priest sings in the background, is the dress mannequin... with human hands.

Yep... just what I was thinking of, except it's even worse than I remember now that I see it. Biggest limitation with stencil is you can't have alpha texture shadowing, so stuff like plants had to have their shadows turned off. I'd say this is the most important reason why enabling map-only effects was a good decision, followed by other improvements and potential future features like transparent / colorized (stained glass) shadows.

@snatcher I understand that when you feel your work doesn't live up to your goals that you don't want it out in the wild advertising your own perceived shortcomings but that leads to a troubling dilemma of authors who are never satisfied with their work offering fleeting access to their in-progress designs then rescinding them or allowing them to be lost. When I was a member of Doom3world forums, I would often see members do interesting experiments and sometimes that work would languish until someone new would examine it and pickup the torch. This seemed like a perfectly viable system until Doom3world was killed by spambots and countless projects and conceptual works were lost. I guess what I am trying to say is that mods don't need to be perfect to be valuable. If they contain some grain of a useable feature they might be adapted by mission authors in custom scenarios. They might offer instructive details that others trying to achieve the same results can examine. It would be great if known compelling works were kept somewhere safe other than via forum attachments and temporary file sharing sites. I suppose we used to collect such things in our internal SVN for safe keeping but even that isn't always viable. If folks would rather not post beta or incomplete mods to TDM's Moddb page, perhaps they would consider creating their own Moddb page or allow them to be added to my page for safe keeping. Please don't look at this as some sort of pressure campaign or anything. I fully understand anyone not willing to put their name next to something they aren't fully happy with. As a general proviso, ( if possible \ permitted ) I just want to prevent the loss of some valuable investigations and formative works. The end of Doom3world was a digital apocalypse similar to the death of photobucket. It is one of my greatest fears that TDM will become a digital memory with only the skeletons of old forum threads at the wayback archive site.

Congrats on the release! Remember to check ThiefGuild as well as the DarkFate forums (via Google Translate) for additional feedback.

I thought it would be convenient to collect in one place a list of all mods\addons\improvements created by the community for TDM. After surfing the entire forum I collected the following list of mods, and I present to you their list below. I will be glad if you correct me and provide any other links to mods that I may have missed. Graphic mods Fresnel Mod (MoDB link) Flame Glare Mod (MoDB link) ModPacks Unofficial Patch (MoDB link) TDM Modpack (MoDB link) (with the possibility of separate installation) Gameplay mods Augmentation Mod Wearable disguises Player Lamp (beta) Adjust player speed with mouse wheel Stealth Statistics Tool & Loot Stealth Stat (MoDB link) Textures TDM Texture Mod Small UI tweaks Reflections to all materials containing specular maps Sounds New Footstep sounds Collection of adjusted sounds by Anton Thiefier Sounds Blackjack Draw/Sheath SFX (MoDB link)

You can't make trees/grass cast proper shadows with stencil buffers, because they are rendered as bulky quads with alpha-tested texture. Imagine shadows falling on the surface of water, or on the glass. You will never see it with stencil shadows: the shadows are computed only on single solid surface closest to viewer at each pixel.

Both mean basically the same thing. Stencil is incapable of shading anything other than geometry so if you want textures that have transparent parts to cast shadows from the non-transparent part of the texture you need to accept that stencil mode will look different to maps mode. Likewise if you want shadows to render onto the semi-transparent part of textures.

Yes, but there are qualifiers to that statement. Stencil is more CPU bound ( and fillrate bound ) and Maps are more GPU memory bound and rely more on texture bandwidth. If lighting mechanisms were perfect the hybrid might not be so bad but both systems often overdraw and waste resources on unseen geometry so you end up with significant amounts of scene duplication. Maybe moving to a deferred model would reduce that duplication but then you end up with having to pack data into buffers and the inevitable quality loss and artifacts of compressing everything into a buffer. Trade offs in all directions.

The latch is just like any any other entity - you can use any model or func_static you like as long as the mechanism translates or rotates (or both).

Changelog of 2.13 development: dev17042-10732 * Restored ability to create cvars dynamically, fixing bow in missions (5600). * Fixed issue where .cfg files were saved every frame (5600). * Added sys.getcvarf script event for getting float value of cvar (6530). * Extracted most of constants from weapon scripts into cvars (6530). dev17035-10724 * Support passing information between game and briefing/debriefing GUI via persistent info. Also changed start map & location selection, added on_mission_complete script callback (6509 thread). * New bumpmapped environment mapping is now default (6354). * New behavior of zero sound spawnarg is not default (6346). * Added sound for "charge post" model (6527). * Major refactoring of cvars system to simplify future changes (5600). Known issues: * Bow does not shoot in some missions (only in this dev build): thread dev17026-10712 * Nested subviews (mirrors, remotes, sky, etc.) now work properly (6434). * Added GUI debriefing state on mission success (6509 thread). * Sound argument override with zero now works properly under cvar (6346 thread). * Environment mapping is same on bumpy and non-bumpy surfaces under cvar (6354 thread). * Default console font size reduced to 5, added lower bound depending on resolution. * Added high-quality versions of panel_carved_rectangles (6515). * Added proper normal map for stainglass_saint_03 (6521). * Fixed DestroyDelay warning when closing objectives. * Fixed the only remaining non-threadsafe cvar (5600). * Minor optimization of depth shader. * Added cm_allocator debug cvar (6505). * Fixed r_lockView when compass is enabled. dev17008-10685 * Enabled shadow features specific to maps implementation (poll). * Auto-detect number of parallel threads to use in jobs system (6503). * Improved parallel images loading, parallelized sounds loading, optimized EAS (6503). * Major improvements in mission loading progress bar (6503). * Core missions are now stored uncompressed in assets SVN (6498). * Deleted a lot of old rendering code under useNewRenderPasses + some cleanup (6271). dev16996-10665 * Environment mapping supports texcoord transforms on bumpmap (6500). * Fully disabled shadows on translucent objects (6490). * Fixed dmap making almost axis-aligned visportals buggy (6480). * com_maxFps no longer quantizes by milliseconds on Windows 8+. * Now Uncapped FPS and Vsync are ON by default. * Supported Vsync control on Linux. * Added set of prototype materials (thread). * Fixes to Stone font to remove stray pixels (post). * Loot candlestick no longer toggle the candle when taken. * Optimized volumetric lights and shadows in the new Training Mission (4352). * Fixed frob_light_holder_toggle_light on entities with both skin_lit and skin_unlit. * Now combination lock supports non-door entities by activating them. * Added low-poly version of hedge model (6481). * Added tiling version of distant_cityscape_01 texture (6487). * Added missing editor image for geometric02_red_end_HD (6492). * Added building_facades/city_district decal material. * Fixed rendering with "r_useScissor 0" (6349). * Added r_lockView debug rendering cvar (thread). * Fixed regression in polygon trace model (5887). * Added a set of lampion light entityDefs.

NHAT v4.3 is available in the mission database! Changes include: Story subtitles courtesy of Datiswous Volumetric Lighting effects Improved water shaders Some new performance optimizations and LOD detail settings Lots of bug fixes for both new and old visual glitches such as z-fighting and model\prefab missing surfaces More work done to prevent players from climbing out of the map into the void

Yes, if you change the internal path of a model you will need to update the map because the map only stores the model path as a string, it doesn't directly embed the model file. A .map file is just text so you could do this with search and replace in a text editor if you wanted.

I'd still be on XP if they hadn't dropped support. I didn't say anything to that effect. I just grew to hate having to keep switching OS due to their business model that keeps imposing that. Been doing that for nearly 30 years now. I don't expect Linux to be paradise. I just hope it's less infuriating than MS products. Either way, that's besides the point here.

wtf... the second cable was also the wrong type the third worked and the board runs again . corsair has some explaining to do i reckon since all my current PSU's are from them and the only indicator that the type is not for that PSU is a small badge printed on the connector that its either a type 3 or 4 (both fit on the modular types but only one will work) the models are a 750 watt cw and a 1000 watt hx. the hx was the one i swapped in and its a gold certified PSU with 10 years warranty. the cables despite the type number are also visually the same except the type 4 having 1 cable mounted differently and is the only one that fits the hx model appareantly. luckily the cable that is mounted differently has no connection inside the 1000 watt PSU so thats a plus as otherwise it would probably had incurred damage to either the board or the PSU but damn...

Welcome to the forums Ansome! And congrats on making it to beta phase!

"...to a robber whose soul is in his profession, there is a lure about a very old and feeble man who pays for his few necessities with Spanish gold." Good day, TDM community! I'm Ansome, a long-time forums lurker, and I'm here to recruit beta testers for my first FM: "The Terrible Old Man", based on H.P. Lovecraft's short story of the same name. This is a short (30-45 minute), story-driven FM with plenty of readables and a gloomy atmosphere. Do keep in mind that this is a more linear FM than you may be used to as it was deemed necessary for the purposes of the story's pacing. Regardless, the player does still have a degree of freedom in tackling challenges in the latter half of the FM. If this sounds interesting to you, please head over to the beta testing thread I will be posting shortly. Thank you!

It seems the unsnapped vertices were a bit of a red herring. The cause was simpler: the textures just don't align. When copying a shader from a receding/slanting surface to another one, the texture is tilted/rotated (like the side of an inclined wall made of bricks: it will "point" downwards) and this, I assume, happens to the patch too. If you "unrotate" it so the side of the bricks stays parallel to the ground, there's a seam as the textures are misaligned. It became obvious when using a tiling surface. I have managed to align the slanted surfaces at eye level, but the farther up or down you go, and the more sides you add to the object, the more misaligned they get. With a flat texture like plaster and some trimming, it could be hidden quite well I think. In case this is useful to someone, or for any future noob, here are a few pictures:

Update: @JackFarmer The root cause of the turret crash has been found. It seems that it was given the same physics code as the security camera but does not have handling for cases where no clip model exists. Removing the physics code fixes the issue. That said, I guess we may look into adding it back so that the turret follows the same destruction features as the camera?

Hi, I'm messing around with patches to see what can be done with them, and I have a couple of questions. None are critical issues, as a matter of fact, I doubt I'd notice them or cared if I were playing someone else's map, but as I'm learning, knowing what can't be done is sometimes as important as what can be done. Here's the thing: is it possible to bevel a surface not parallel to one of the orthogonal axes, in other words, a slanted bevel? To be more specific: I'm having problems with snapping it to the grid; it doesn't want to. I mean, I have done the bevel, and it looks nice from a distance, but the slanted surface refuses to snap to the grid, which causes a visible, although small, seam (or at least I assume that's the reason.) And projecting the texture is also a bit of pain. Let's see if I can attach a picture... OK... [a few/lots of minutes later] messing around with it one side now looks much better (almost imperceptible seam, tbh,) but the other side still looks off. I still can't snap to the grid the four corners (interestingly, it's the main brush, the frustum, the one that refuses, not the bevel, which is perfectly snapped). I can snap three of the four corners, but there is always one that shifts on its own will, even when using the smallest grid. See the next two pictures, where I have the main brush and the patch selected; the dots overlap except that one. And if I snap that one, another will shift (clockwise? I think.) I mean, that's like... what, 1/3 of 1/8 of a Doom Unit? 1mm? Not game-breaking, really, and nothing that can't be hidden with some trim or just in shadows, but I wonder if there's a technique for this or what I did wrong. [Hmmm, after some thinking, I wonder if my issue was creating the original cube on grid X and then cutting the triangular corner for the bevel on a different grid size so the corners were weirdly placed... I'd have to test that out] And speaking of seams, is it possible to make a smooth texture transition from the surface of a cylinder (or ring or whatever) to its cap? See the third picture, which is the rounded base of a column. If it's not (or it takes a lot of effort or editing), then it's no big deal, as there are more important things to worry about. But if there's a quick & easy way (natural projection hasn't worked for me in this instance), it would be good to know. Thanks!

I would only leave it as worldspawn if you need it to act like worldspawn. For example, if you have a nodrawsolid_wood brush covering a wonky wooden model and you want AI to be able to walk over it smoothly or it is to perform some sealing function. Other than that, just make a func_static so it gets filtered out in DR when you want to only look at sealing brushwork. So no harm in leaving it as worldspawn, but on the other hand you might get some benefit to making it a func_static.

Something I was thinking of: Even if some assets are non-commercial, are all assets at least accounted for to make sure they're credited accordingly and can be distributed? I ask following an issue in another great project I work with called Red Eclipse: They don't have NC assets but did have a few texture packages they had to remove because they later found out their clauses were incompatible with the project. If this hasn't happened in well over a decade it's very unlikely anyone would complain today and request removal for any reason, but if any resource had its license misunderstood that could destroy existing FM's unless perfect replacements were found. Obviously I presume the team never included any asset randomly found on the internet without verifying their explicit requirements in detail, but it doesn't hurt to check. I think the best that can be done otherwise would be to have a list of which assets are libre or have the NC clause: That way a map can choose to use those models and textures that are free if the author wants their FM to be fully libre, albeit this would handicap an author in what packages they can use. If core assets like character models or textures are also NC, the idea is likely pointless as you can't make a FM without those, at best you can skip a few texture packages... not sure about other things like core scripts or defs, since they're technically code I presume those are GPL?

TDM Latch Pack (Beta) By Frost_Salamander and wellingtoncrab with special thanks to Dragofer Tired of picking another lock or hunting for that missing key? Imagine The City is itself an elaborate lock, and you are the key. Embrace progression through careful exploration and navigation of the environment. Embrace the latch pill: Included is a new entity type and scripting for a door mounted toggle lock, or "latch", as well as new CC0 assets and prefabs. https://github.com/thedarkmodcommunity/test-latch/wiki Example Video Asset Pictures All models and textures in this pack are released under CC0 license and may be used freely without need of attribution. We waive copyright to the extent that possible, but aren’t lawyers. Latch Lock Features Supports single and double doors across all cardinal directions, as well as trap doors Uses the location system to handle context sensitive frob highlighting of the latch and the doors Automatically determines the correct latch state on map start based on the targeted door's "locked" spawnarg Options for rotate, translate, or both with unique sound slots for each Supports any model or func_static To get started head over and grab the latest release (available with or without demo content) and read the getting started guide. This is a beta release - so your feedback is appreciated!

At first I thought it was some wild precision bug but it looks like the skin might be nonsolid somehow and SteveL's change made the nonsolid attribute work? Either that or skin detection is somehow borked in this map. Feel free to edit the map, I'm no expert mapper but I might be able to perform some workaround by manipulating the entity. Edit: I fixed it with the following change: // entity 4 { "classname" "atdm:mover_door" "name" "atdm_mover_door_8" "lock_picktype" "-" "lock_pins" "0" "locked" "1" "solid" "1" "model" "atdm_mover_door_8" "origin" "710 -248 2050" "rotate" "0 90 0" "snd_close" "door_shut_06" "snd_open" "door_open_08" "used_by" "Balcony_door_keey" // "skin" "door_007_1" // primitive 0 Will upload the fix to the mission database. I don't see anything wrong with the door_007_1 skin but I would advise testing it in-game before using it going forward until this is fully sorted. Edit 2: The updated mission is now available in the mission database. Feel free to offer other fixes to this mission as long as they do not: Change visuals Change gameplay design ( Any purely bugged things that the mission author acknowledges "needs fixing" such as keys that are inaccessible or critical items that fall through surfaces when touched, etc can be fixed by any mapper and submitted for validation by the team. )

I was able to reproduce this in 2.12 beta as well as 2.11. Start mission setviewpos -5727 974 292 24 -57 0 Wait for new objective setviewpos 3795 5676 -3164 18 160 0 Wait for objective complete Shoulder body setviewpos -1643 3574 -1903 4 180 0 Drop body on elevator platform Press elevator button Setting "logFile 2", I was able to capture some console messages before the crash. "MISSION COMPLETED" displays twice instead of once. I haven't had a chance to look further into this. WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model MISSION COMPLETED MISSION COMPLETED ----- idRenderModelManagerLocal::EndLevelLoad ----- 0 models purged from previous level, 1031 models kept. --------------------------------------------------- Regenerated world, staticAllocCount = 0. Getting threadname failed, reason: No such file or directory (2) --------- Game Map Shutdown ---------- ModelGenerator memory: 133 LOD entries with 0 users using 2128 bytes. WARNING:idClipModel::FreeTraceModel: tried to free uncached trace model (index=0) --------- Game Map Shutdown done ----- Shutting down sound hardware idRenderSystem::Shutdown() ...shutting down QGL I18NLocal: Shutdown. ------------ Game Shutdown ----------- ModelGenerator memory: No LOD entries. Shutdown event system --------------------------------------

It's hard. I see what you are thinking about is a "bullet point" pattern, with or without a bullet point character. For that case, I suppose what we are trying to detect is: - the line starts with the bullet point pattern - a "J" character (say) with a shortened spacing, is somewhere in the line. - the line itself in the xd file is long enough to force a word wrap (let's just think about a single wrapping here) - the author assumed a particular word wrap point, and put in extra spaces in mid-line, immediately at the wrap point, so as to indent the latter part of the line, aligning with the indent of the first part. - the shortened-spacing J screws up the resulting alignment. Probably would need a script/program to winnow this down... ideally, that algorithm could also restrict attention to just Stone font. I'm OK with putting such an effort off for now, maybe revisiting it for 2.13.