Search the Community

TDM Modpack v4.0 This new version of the Modpack is intended to be a long-term release. The Modpack is mature and stable enough to stay for some time how it is today, right where I want it to be: the foundation on which you build your favorite set of Mods for The Dark Mod. Good care was put to make sure the mods included in the Modpack stay true to TDM and neither the missions nor the gameplay are altered in any relevant way. Yes, we have more tools and skills at our disposal but it is up to you, the player, to make use of them or not. Play The Dark Mod your way. Compatible with 2.12 ONLY If you have previous versions of the Modpack I suggest you start fresh: disable and delete old mods. Use the mods included in version 4.0 from now on. TDM 2.12 introduces a great new feature and we can now have different mods from different sources running in parallel. Thanks @MirceaKitsune for pushing! Thanks @Dragofer for opening this door! What's more for 2.12 internal resources for mods have doubled and we can now load more mods than ever before and we are grateful for this! Thank you, @stgatilov! What's new in version 4.0? Starting with this release I am getting rid of the individual versioning and all mods are now at the same version (4.0 in this case). "TDM Modpack" is now the name of the project and the previous main "pack" has been split into two standalone mods: "Core Essentials" and the "Skill Upgrade". (The Skills are further split into their own packages and if you don't want a particular skill just look for the relevant pk4 and remove it). SHOULDERING BOOST - Decommissioned In TDM 2.12 we can now mantle while carrying bodies and the "Shouldering Boost" mod is no longer relevant and it has been decommissioned. In this new release of TDM we can also mantle while carrying objects therefore double thanks to @Daft Mugi for these quality of life improvements. Truly appreciated, thanks! SIMPLE SUBTITLES - New! Work on the subtitles is in progress and for the next version of TDM it is expected that players will be able to customize how subs are displayed on screen but until then, this new standalone mod offers an alternative for players looking for a rather simplistic presentation. Enable "Simple Subtitles", go to the audio settings and set the scope you prefer: Story [default]: Story only On: Story and general speech (Give it a try!) Off: Disable subtitles You can find more details of the mod in the opening post or in the readme included in the download. We must thank @Geep, @datiswous and @stgatilov (among other contributors) for the good work on the subtitles so far! Well done, guys! SMART OBJECTS - Present and Future Sometimes it is difficult to tell if an object is being held or not and the "Smart Objects" mod (now part of "Core Essentials") gets a little update and whenever you manipulate an object three dots [...] are displayed on screen: These three dots are a placeholder for real names, something I plan on addressing as a separate mod in the coming weeks... Here is the relevant topic: Nameless objects... a missed opportunity Stay tuned. INVENTORY MENU - Reworked The TDM user interface suffers from gigantism in some areas and the inventory menu has been re-worked and it is now delivered in a more compact format: The menu is 15% smaller and while the text has the same size as before item names are sometimes cut and I added a tip at the bottom to make sure the full name is always available. The updated menu is part of the "Core Essentials" mod. MINOR TWEAKS In each release of the Modpack I always tweak something and in for 4.0 I changed many things internally. You shouldn't notice any of the changes but it is worth giving the improved Whistle Skill a try... Here is the full changelog: • v4.0 New release - Major reorganization and global revision: Compatible with TDM 2.12. - All mods now share the same version (4.0 in this case). - Previous "Modpack" split into "Core Essentials" and the "Skill Upgrade". - Skill mods presented in their own, standalone pk4. - CORE ESSENTIALS: New, re-worked inventory menu. - CORE ESSENTIALS: New high mantle sound for our protagonist. - CORE ESSENTIALS - LOOT ANIMATIONS: Added scroll animation for paintings. - CORE ESSENTIALS - SMART OBJECTS: Display onscreen a subtle signal (...) when holding an item. - CORE ESSENTIALS - SHOULDERING BOOST: Mod decommissioned (alternative included in TDM 2.12) - SKILL UPGRADE - MANIPULATION: Improved script, smaller footprint. - SKILL UPGRADE - DISTRACTION: New approach (again). - HUNTER BOW: Increased radius of gas arrow effect. - BASIC SUBTITLES: Initial release. That's pretty much it for now. Thanks site admins, developers, mappers, modders and members of the community but more importantly, thank you taffer, for playing and supporting The Dark Mod. The download can be found in the opening post. Cheers!

We are proud to announce the release of: The Dark Mod 2.12 ! The 2.12 development cycle introduced many large code overhaul projects. Most of these were to lay the groundwork for future fixes and optimizations. The final release is yet another leap in performance over the already impressive 2.10 and 2.11 releases. A full changelog can be viewed here, but some highlights include: The Dark Mod 2.12 is a major step forward for mission designers! The culling system has been extensively overhauled to ensure that your CPU and GPU are not wasting resources rendering unseen geometry, lights, and shadows. Some of our best map optimization experts have achieved similar performance gains to what this new culling system does but it is a rare skill and we have even managed to improve performance on missions that were generally regarded as “well optimized”. Mission authors both new and old can follow standard mapping practices with no need to dive deep into sophisticated optimization techniques even for some pretty challenging scenarios such as wide open areas and long views. Players will immediately notice many missions that have made their system struggle with FPS now may be running much more smoothly! Smoother controls for players! Also during the 2.12 development cycle, work has been done to make controls more seamless and accessible. Frob can now use hold or click actions to use items. Once you get used to the mechanic, it will be hard to go back to using a separate “use key”. Mantling is now smoother, faster, and less prone to cause the player to clip through geometry. Leaning is now more subtle and less prone to cause motion sickness. To reduce the tedium of shuffling knocked out AI around to search for loot, you can now configure TDM to automatically loot any frobbed AI. A special thanks must go out to community member Geep! Over the course of 2.12 development, Geep has created subtitles for nearly all AI barks along with developing testing tools and procedures for this gargantuan task! You can see these changes in action by changing the Subtitles setting to “On” ( rather than “Story” ) on the Audio settings page. Geep also provided substantial feedback for our GUI and subtitle design process and edited font data to improve text quality overall. Datiswous has complimented the massive work by Geep to create AI bark subtitles by creating mission story subtitles for a large number of missions. Thank you! Turrets are now natively supported in The Dark Mod and can be paired with Security Cameras! Finally, the nasty 2.11 bug that caused AI to allow arrows to pass through them at certain angles was fixed by Joebarnin! Your assassin style play-throughs should be far less frustrating. See also, our 2.12 Feature discussions: To UPDATE, simply run the tdm_installer.exe file in your darkmod folder. Note that tdm_update.exe is no longer supported, but you can download the new installer from the Downloads page if you don’t have it yet. Please be aware that old saved games will not be compatible with 2.12, so finish any missions you might be in the middle of first! Also, some missions created prior to 2.12 may need to be updated so they will be playable in 2.12. Use the in-game mission downloader to check for updates.

I have just released a new utility, "refont", as an open-source, partial-successor of the traditional "q3font". For the whole story, see the new wiki page Refont. (I'm gonna post this in a few forum threads. Don't hate me for that.)

Thanks! I'll look at the portal design in that area. For a baseline, can you post details about your GPU, Driver, and Host OS

I upgraded from Windows 7 to Windows 10 for free. Does that not work anymore? If your objective is to keep running the same OS version for 15 years, I'm afraid you won't find Linux any better — as far as I know even Long Term Support releases don't go beyond 5 years unless you're a business who pays for extended support, and even that probably wouldn't give you more than 10 years. On the other hand, Linux upgrades are always free (assuming you're not using RHEL or another commercial distro), whereas Microsoft might require you to purchase an upgrade license.

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

-Do forgive the screenshots being a bit dark or vague in this post, I can only show so much without spoiling the second half of this FM that is best experienced firsthand.

"...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!

What do you mean by moving them around? You move them from the models folder into another folder? Models must be placed in the models folder. Otherwise, DM/DR cannot find them anymore causing the problems you mentioned in your post.

Alberic's Curse v3.11 is now out! It features: 1) A new script event related to the "Curse" 2) EFX Reverb 3) Volumetric Light effects 4) Different detail levels depending on LOD setting 5) A fix for a very old bug that caused stuttering in the basement, along with a long list of standard bug fixes 6) A few more surprises... Check for the mission update in the in-game downloader!

Here is another update to the English Stone font's DAT file used for subtitles and some readables: fontImage_24.dat This supercedes the Jan 30th update. As agreed, now all character spacings - as given by xSkip - are preserved (from this file in TDM 2.11). Exception: the Jan 30th repair of garbage metadata for "<" and ">" remains, including xSkip repair. ASCII Characters (lower 128). The earlier Jan 30th post summaries those ASCII characters that needed metadata changes to avoid adjoining stray marks. (The detail report below updates newer reversions and minor revisions.) ANSI Characters (upper 128). An analysis was also made of the status of the Stone 28 pt font's characters in the upper codepoint range of 128-255. This could be of interest if the subtitle system was some day expanded to include European languages, and continues to use the historic codepage method. The analysis also prompted some additional DAT tweaks now. Broadly, implementation of the upper-range characters (standard or TDM-specific, as defined in the TDM wiki's I18N - Character mapping I18N) is incomplete for Stone 24 pt. The status is: 43% (55 chars) Good as is. 9% (12 chars) Good enough after DAT tweak included in this update. 6% (7 chars) Missing and shown as hollow box. 30% (38 chars) Missing accent/diacritic. 7% (9 chars) Otherwise weird. But often suggestive of glyph work started but not completed. In addition, 7 chars within categories (3-5) were "improved", but are still not good. To really solve categories (3-5) requires DSS bitmap surgery (and corresponding DAT adjustments), which is beyond the scope of planned work. DAT tweaks of ANSI characters (like with ASCII) were careful to avoid changes to xSkip. Tweaks can be further grouped by problem solved.... In category (2): - (4 chars) Char is clipped, with stray mark from adjoining character on other side. - (7 chars) Stray mark, without char clipping. As improvements in categories (3-5): - (3 chars) Stray mark, without char clipping - (4 chars) Out of valid range on top edge A categorized itemization about treatment of specific problems and characters, with further details, is here: Information about methods, including new tools, to conduct this analysis and tweaking will be forthcoming, mostly after the 2.12 release.

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 think I found another case of bug 6480 and post in Talbot 2: Return to the City. 274.26 -1039.08 184.71 -15.8 24.9 0.0

@nbohr1more@Dragofer Update to the post quoted above: only missions with turrets are concerned, all others work fine.

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.

Just added a test as per your suggestion in my post above.

Of course, identifying struct via HN is useless. At work, we use HN when there are reasons for caution: u for unsigned to prevent unintentional implicit unsigned promotion (and overflow) Yes, I know, the compiler will issue a warning, but in some legacy projects, there are tons of warnings, so devs are going to miss that one new one. We are slowly working toward warning-free builds, but as long as we are not there yet, the u-prefix helps a lot. p for pointers to make the reader / dev aware that that variable could be NULL. m_ for members, obviously useful. Similarily, g_ and s_ for globals and statics respectively, although it is obviously discouraged to use those. Various prefixes for the different coordinate systems we use. I for interface, just for convenience b for boolean, this is basically just for convenience so you can directly see that this is the most basic type. This one, one could defintely argue against, but I personally like it.

That bothers me for way too long too..

New script for mappers: my flavour of a fog density fading script. To add this to your FM, add the line "thread FogIntensityLoop();" to your map's void main() function (see the example in fogfade.script) and set "fog_fade" "1" on each foglight to enable script control of it. Set "fog_intensity_multiplier" on each info_location entity to change how thick the fog is in that location (practically speaking it's a multiplier for visibility distance). Lastly, "fog_fade_speed" on each foglight determines how quickly it will change its density. The speed scales with the current value of shaderParm3, using shaderParm3 = 1000 as a baseline. So i.e. if shaderParm is currently at 1/10th of 1000, then fade speed will be 1/10th as fast. Differences to Obsttorte's script: https://forums.thedarkmod.com/index.php?/topic/14394-apples-and-peaches-obsttortes-mapping-and-scripting-thread/&do=findComment&comment=310436 my script uses fog lights you created, rather than creating one for you. Obsttorte's script will delete the foglight if entering a fogfree zone and recreate it later more than one fog light can be controlled (however, no per-fog-light level of control) adding this to the map requires adding a line to your void main() script, rather than adding an info_locations_settings entity with a custom scriptobject spawnarg in my script, mappers set a multiplier of fog visibility distance (shaderParm3), while in Obsttorte's script a "fog_density" spawnarg is used as an alternative to shaderParm3 smaller and less compactly written script fogfade.scriptfogfade.map

I agree, and you might become happy in 2.13. My thinking was that you could select "Thief-Style" (new Daft-Mugi control scheme) or "TDM-Style" (old control scheme, but with long-frob shortcut for frob + use). No promises, however. The proposed change has to be accepted by more than one team member after all.

I'm thinking existing maps are kept as they are today, and keeps using the same assets as today. This so they can stay the same as today and won't deviate from how their author intended them to be. The existing missions won't be libre, but it is quite possible that the authors don't want them to be libre. If an author of a mission said "this mission itself is libre, but it relies on NC assets" then it would be possible to replace the NC assets to libre assets and the entire mission would be libre. Yes. If a mapper wanted to create a libre mission they would need to restrict themselves to only using libre assets. In this post, I suggest that Dark Radiant should allow mappers to search/filter media/gamedata by license (if DR does not already do this). Such a filter functionality would help facilitating the creation of a libre mission.

I'm not certain i understand the question, but it may be something similar to what I asked here (number 3): ...but it seems you've already found that post.

Anyone have a working link (or can create a link) to the modified version of ExportFontToDoom3 executable? This 2009 version was created by Crispy, to handle 256 chars instead of just 128. It was released in this forum post: the dark mode readables ttf fonts The following links to it are now dead: - crispy's original release: http://www.inventivedingo.com/stuff/exportfonttodoom3_modified.zip This is what's listed at the bottom of Font Conversion & Repair as as "Fixed version of ExportFontToDoom". - Hyeron's 2009 upload: http://www.4shared.com/file/151870191/d47d0e16/exportfonttodoom3_modified.html - tels 2011 mirror: http://bloodgate.com/mirrors/tdm/pub/exportfonttodoom3_modified.zip. No luck with wayback machine, github, sourceforge, either .exe or source. (Source & exe for unmodified version from Grant Davies is in hand.)

https://postimages.org/ creates actual image urls to the file (a lot of image sharing sites share links to pages, but not to the actual file) optional: resize on upload optional: specify if you want them removed after a specific time. When you copy the url-list in a post and then after press enter, they get included as images into the post automatically. Example:

It's easy to imagine how #1 can be solved fairly: When the player or an enemy AI shoot an armed AI, the AI that was hit should be given a random destination near the attacker to run to. The further the player is from the target, the larger the radius around the player in which a random node may be picked; If you're far away the virtual sphere should be large, meaning AI may run to a room or passage near you but still in your general direction . This new behavior should be influenced by AI acuity and difficulty settings though I'm not sure which ones... also toggled by one, for those who prefer the old way and abusing clueless guards as they wonder what force of the universe must be hitting them. By the way, and I just realized this now: The problem doesn't only affect attacks, but also spotting the player before attacking. Think of the last time a guard standing outside spotted you on a balcony before you hid, enough to draw their swords and start searching but not attack you outright; The guard was alerted by something in a building, yet he draws his sword to search the area near him. If I'm standing outside and think I see a burglar in my house through the window, I'm going to go near my home if I plan to confront the possible intruder, not start looking around the road next to me and say "I know you're here somewhere" which would imply I have a serious problem Main reason I mention #2 is when I helped with transcribing the subtitles for the drunk voice, I noticed there are voice lines for AI returning with an ally. Two in fact: If the player is still there the AI has a voice line for telling the other person "that's the one let's get him", if the player hid there are lines such as "you were too slow now he got away". Those voices in particular are never played, or at least I don't remember ever hearing them in all those years: It occurred to me while I wrote this post that they're likely designed for a mechanic that was never implemented... or was but broke very long ago? Curious what its history is.