Search the Community

Story: Build Time: Thanks: Download: In the in-game downloader, when it's back up* or at the following locations: Dropbox http://darkmod.taaaki.za.net/fms/lhl.pk4 http://fidcal.com/darkuser/missions/lhl.pk4 http://www.southquarter.com/tdm/fms/lhl.pk4 *right now the mission server is down, which means you will need to manually download and install this mission. Download the pk4 file from dropbox above, and place it in your folder called LhL inside your "fms" folder in your TDM install directory. Let me know if you run in to problems! Gallery: Hints, Tips, Walkthrough, Spoilers(!):

I wrote earlier that I owe this masterpiece a review, so... Here is my detailed review of this groundbreaking and seminal Mission Fan. SPOILERS ABOUND ! TDM PLAYER BEWARE, YOU'RE IN FOR SPOILERS AND MAYBE EVEN A SCARE ! This mission... subverted my expectations. Starting with the briefing video. Not since the days of Sergio Leone's Spaghetti Westerns have I seen such daring subversion right at the start. You're expecting one thing... then, bam ! I tried everything to infiltrate the mansion from the outside ! No luck ! Well and truly, expectations subverted ! NPC dialogue heard from the inside... stellar ! Brought a tear to my eye. Or was it just one of the raindrops that fell on my head ? What else brought a tear to my eye ? The senselessly slaughtered guard at the courtyard ! Clearly, a cautionary story that he who grabs a sword... and yet, forgets to dim his lantern, the fool... shall die by someone's sword or arrow. Figures ! That you hid the masterful sidequest of collecting the pennies-for-a-thought from the rather racy fountain, in order to later thoughtfully redistribute them to the poor and hungry street urchins of Bridgeport, is nothing short of design brilliance worthy of at least a two hours long, detailed GDC lecture. I'd watch such a lecture on a loop, 24 hours a day, twelve times a day. Brilliant stuff ! Ah, the side-yard, with steps and a basement entrance that looked and felt straight out of Thief II's opening mission, Running Interference... Could the cunning TDM homages to the classics get any better ?! Could they ? Well, soon enough, I discovered that, yes, they could get even better ! There was an even more amazing homage that I didn't expect ! Read on to find out what... The chefpick was... indescribably cool. I now yearn for it to be included in every single FM. The classic lockpicks feel completely passé. I knocked out both NPCs and... what is this unexpected social commentary ?! The knocked-out have names ?! I applaud your deeply incisive observation, worthy of a skilled chef with a kitchen knife, that the NPCs in games are not mere fictional constructs, but fictional beings with names, hearts and souls ! I confess, upon this moving revelation, I started shedding tears so uncontrollably, I nearly had to quit playing the mission. Yet, I pressed on, heartened and refreshed by such displays of humanity in a work of stealthy interactive fiction ! The commentary was no less subtle and stealthy, I tell you ! As subtle as the protagonist's gritty, grounded accent ! Two different entrances into the local vent system... I... I can't even... So many possible routes of entry. Truly, in the grand tradition of the TDM immersive sim design philosophy ! The choice of giving the intrepid protagonist a temporary rat companion, bribable by cheese, who fetches priceless hidden loot, was equal parts innovative and a hard-hitting social commentary on the abuse of animals for theft and burglary, and people "ratting out" their fellow tenants by revealing the hiding places of their priceless belongings ! I was deeply impressed ! I was thoroughly amazed ! You even had my 'stalgia sense tingling ! Why ? That minor element of your FM even reminded me of the old but gold Thief II FM campaign The Flying Age: The Abominable Flying Machines of Dr. Zeppelinger, where you escape a prison cell by giving a mouse a bit of cheese you've managed to find, and the mouse then provides you with a means of escape. I have scarcely ever seen such a wonderful duo of homages to other past LGS missions and fan missions ! Of course, the shocking revelation with the undead in the freezer was an even more biting commentary on the undead precariat of today, and their ruthless and dehumanizing exploitation by The Man, maaan, the snobby culinary establishment. Undeadkind merely want to roam their abandoned tombs and catacombs in peace (pieces ?) and get a bite or two out of a stray vagrant or drunk guard every now and then, no big deal. Society needs to be more charitable to undeadkind ! And you've even included a gas arrow up in the rafters ! You well and truly know your audience, as I'm an old, die-hard gas arrow collecting enthusiast. I am a sophisticated, yet simple man: I see a gas arrow in Thief or The Dark Mod, I immediately grab it, owing to its rarity. Thank you for such generous mission design. To cut a long story short, I have had a thorough, engrossing and moving cultural experience with this short-but-dazzling mission ! In the shadowed alleys of TDM fan mission sites, I have crossed paths with missions that were ruthlessly difficult and confounding, yet rewarding, but never have I played a mission this... authentic... avantgarde... thought-provoking... It even made me feel hungry ! Riveting, simply riveting. Like working on the skeleton of a 1930s Art Deco skyscraper. Ultimate verdict: 22 frommages out of 20, with a happy cheese-filled rat as the cherry on the top. (But what kind of frommage ? Cheddar ? Swiss cheese ? Gouda ?! I dunno. Don't have a cheesemaking degree.) In other words, I cannot rate this mission other than with the Chef Excellence Award for... Excellence ! *chef's kiss* Le Mission Légendaire Magnifique ! Roll over, Requiem ! Roll over, Crucible of Omens ! Roll over, Iris ! This, this... is the pinnacle TDM fan mission of all time.

You'll be surprised to hear but I don't quite get it either. Based on my understanding, there are a few confounding factors that make this a challenge. 1. We did a lot of work to ensure that the "included missions" were made part of the install so first time players would have a curated experience. Moving the missions back to the mission database might require undoing that work. 2. It is entirely possible to add the missions to the mission database while also being included in the installer but doing this will invite a few problems: 2a. What if the user updates the mission and then finds that their TDM install is somehow borked. They might run the installer to repair it and this will revert the mission version. If they fail to update their mission after this revert they might have incompatible save games that cause crashes and confusion 2b. What if a user starts downloading a mission update and at the same time starts a TDM upgrade ? 2c. Users opening bug tickets for a base TDM version due to problems seen in the included mission that are no longer present in the updated one, thus making it more tedious to narrow down duplicate bug submissions. 2d. Players seeing the missions on the TDM missions download page and downloading the package to install in the FMS directory then seeing duplicates in the mission list because the downloads page renames the packages with hashed filenames. All the above challenges revolve around potential user error and even though it should be obvious not to do these things, we have to compare the above to the vast swaths of folks who are begging to include TDM into Steam because unpacking a zip file and running an installer executable within a folder is "too difficult and confusing". One thing that we have the ability to do is change the file in the 2.12 installer repo so that if users run the updater it will apply the new mission. This change would not be visible to users so they would not get any alert about it. We would just have to announce it and hope that players watch for TDM announcements. I am doubtful anyone would want to work on it but I suppose that there could be some way to pass some sort of signal to the mission downloader when included missions have been changed on the installer side so they get a different update indicator. Still would be kludgy because you'd either be telling the player to exit TDM and run the installer or making TDM invoke the installer internally. So that is my take on "why" based on my own knowledge. Of course, part of my inability to "understand it" is due to my incredulity that we need to cater to players who are so below the bar in computer literacy that they would inflict these problems on themselves in the first place. None of this is an official stance just my own take on why the proposal to "let two updater processes control the same files in the same folder" has been rejected ( other than that such designs usually horrify programmers on a primordial gut level and if you mention that any program that does this you will see any programmer in vicinity instinctively reach for headache or stomach medicine ).

I remember I was surprised it couldn't run Invisible, Inc. properly. But I'll give it a try later.

Is it not possibly to just add a small script to these missions that only does this: #define ARROW_ZOOMDELAY 3 //VOLTA MOD Edit: I haven't installed the newest tdm version yet, so I guess this might be complete nonsense..

So what is the training mission for then? Apparently it's not showing standard tdm gameplay necessarily. Edit: Maybe it's not really worth it to keep discussing this. I mean I don't want to derail too much what the topic is actually for.

I totally agree that players usually don't care whether some non-customizable constant like bow shoot time is same as in core or not, as long as the mission plays well. This is a problem only for TDM development. But I don't know a proper way of solving this: mappers usually want to customize something "right now", and waiting for new release is rarely an option. And often customizations are not implemented until someone really wants them (or right away uses them), so that's also the chicken-and-egg problem here.

You are confusing how the core game is packaged with a "standard". The “standard” TDM experience imo would actually be however the mission author intended the mission to be played. There are lots of different types of missions which as experiences deviate from anything packaged in the core game. You are not owed a disclaimer.

@The Black Arrow That's a good analysis. I don't disagree but we're referring to different time periods with different quality aims: In the early days of 3D and low-res CRT screens when we had 256x256 textures, detail textures were used to make surfaces appear as if they have 1024x1024 textures... today in the age of 1080p monitors such texture can appear blurry from up close, we want to make 1024x1024 textures appear of 4096x4096 quality. Back then the goal was to get at least a little bit of perceived sharpness, today the goal is to see those microscopic details on every surface as if everything is real... while the concept of detail textures is old it scales to cover both aims. As you correctly pointed out, the ideal solution would be upgrading the actual textures themselves. Sadly there are two big problems with this that will likely never be possible to overcome: Someone must create or find identical textures to replace existing ones, which have to retroactively fit every old FM. That would be a huge effort for so many images, and will not look exactly the same way so people would complain how "this wall used to be made of small red bricks which are now larger and yellower which isn't what I intended and no longer line up". An advanced upscaling filter may be able to bump the resolution with good results, this would be a lot less effort and retain the exact appearance of textures. The even greater issue is storage and memory use would go through the roof. Imagine all our textures (from surfaces to entity skins) being 4096x4096 which would be the aim for decent quality today: TDM could take over 100 GB of drive space, you'd need at least 16 GB of RAM to run it, and the loading time of a FM will be 5 minutes. Detail textures are a magic solution for both problems: They're overlayed in realtime on top of the standard textures without changing their base appearance. This means you see pixels several times the scale of the image without requiring any image to actually be at that resolution, no vRAM or loading time increase. And if detail layers are disabled with distance you also don't lose FPS in per-pixels calculations when distant lights update.

I guess I could try to make it run on this: https://www.notebookcheck.nl/Fujitsu-Siemens-Lifebook-P1620.8269.0.html Not sure if an Intel GMA 950 will be enough..

Early TDM 15yr anniversary contest entry?

Why the sad face? Also, Kingsal would be better able to explain the changes, and he actually modified the script so that it is more TDM-friendly. This modified script is in Eye on the Prize and Moongate Ruckus

That is one reason. That is 2 more reasons. You'd like a script that, if you had to run it again, would "do the right thing". Unfortunately, that right thing is very hard to program, and needs IMHO to be both bidirectional and with a better method of string version control, to support both the FM author's updates and potentially multiple translators. Yes, another reason. Currently, it is my understanding that updating an FM (from the non-converted copy) and running the conversion script again causes mis-alignment of newly-generated #str values and previous .lang #str values. Another important cause of "nobody is making these language packs" is that Dark Radiant at best tolerates converted FMs. It offers no special translation support, as expressed in this code comment: "...we don't have any support for parsing the mod-specific translation data...." [from DR's DifficultySettingsManager.cpp]. That's where we are now. So officially give up on FM Western translations? Or improve the #str system to make it work for everyone? Or invent a new system? A new system. What would that look like to the FM author? To a non-author translator

Yet another breaking change, I'm afraid: 6346 Sounds have a bunch of parameters: minDistance maxDistance volume shakes soundClass The base value for each parameter is set in sound shader. However, it can be overridden with a different value in spawnargs (e.g. "s_volume" "-10") or in C++ engine code with SetSoundVolume (used extensively for footsteps). Unfortunately, Doom 3 engine has a special case: setting some parameter to zero means it will not override the base value. So there is no way to override sound volume with 0, because setting zero would mean "use value from sound shader", while setting 0.1 or -0.1 would mean "use volume = 0.1 or -0.1". This behavior causes confusion. It is especially bad when volume is set programmatically, because e.g. volume of player footsteps is computed as a sum of many modifiers (run, crouch, creep, in water, etc.) and it is hard to be sure you don't get zero sum in the end. The idea is to fix this mess and add a "don't override" special value in the system. Speaking of spawnargs, it would work like this: "s_volume" "13.4" = override with value 13.4 "s_volume" "0" or "s_volume" "0.0" = override with zero "s_volume" "" (empty string) = don't override Right now there are tons of zero values set in these spawnargs. It is not clear where the author intended to override with zero, and where he wanted to drop inherited override and use base value. I guess for compatibility reasons I'll have to replace spawnargs "s_volume" "0" with "s_volume" "" in all missions.

I wanted to internationalise The Hare in the Snare before I released it but I couldn't get the scripts to work and had some other questions as well. I posted about it Newbie Dark Radiant Questions and nobody replied, so I gave up. It being my first FM I didn't feel confident digging into it and just wanted to release the FM. I just got the impression that it wasn't a big deal and nobody cared about it. From memory, the script worked once but I needed to re-run it and just couldn't get it to work. It's also Perl which nobody really uses anymore. I think I recommended to a 'I want to help' person to convert it to Python, but that didn't go anywhere. I don't think you need the script though if you internationalise from the very beginning (i.e. create your own dictionaries). At the end of the day it's extra work for the mapper and if it adds too much overhead (i.e. is broken or is a PITA) then nobody is going to use it. https://wiki.thedarkmod.com/index.php?title=Internationalization

Ooohhhhhh, it's twitching in the build intenstine, as we say in Sweden (or do we? :D) I'm quite eager to create something. But they're releasing new skaven models for Age of Sigmar 4 this summer... And I have a 2 year old... And work... And a girlfriend... And too little time... I will try to create something at least. If I run out of time, I'll run out of time; then I at least have built something that can be released after the contest... Count me in, with the caveat that I may pull out before deadline...!

There's been talk over the years on how we could improve texture quality, often to no avail as it requires new high-resolution replacements that need to be created and will look different and add a strain on system resources. The sharpness post-process filter was supposed to improve that, but even with it you see ugly blurry pixels on any nearby surface. Yet there is a way, a highly efficient technique used by some engines in the 90's notably the first Unreal engine, and as it did wonders then it can still do so today: Detail textures. Base concept: You have a grayscale pattern for various surfaces, such as metal scratches or the waves of polished wood or the stucco of a rough rock, usually only a few highly generic patterns are needed. Each pattern is overlayed on top of corresponding textures several times, every iteration at a smaller... as with model LOD smaller iterations fade with camera distance as to not waste resources, the closer you get the more detail you see. This does wonders in making any texture look much sharper without changing the resolution of the original image, and because the final mixture is unique you don't perceive any repetitiveness! Here's a good resource from UE5 which seems to support them to this day: https://dev.epicgames.com/documentation/en-us/unreal-engine/adding-detail-textures-to-unreal-engine-materials Who else agrees this is something we can use and would greatly improve graphical fidelity? No one's ever going to replace every texture with a higher resolution version in vanilla TDM; Without this technique we'll always be stuck with early 2000's graphics, with it we have a magic way of making it look close to AAA games today! Imagine being able to see all those fine scratches on a guard's helmet as light shines on it, the thousands of little holes on a brick, the waves of wood as you lean into a table... all without even losing much performance nor a considerable increase in the size of game data. It's like the best deal one could hope for! The idTech 4 material system should already have what we need, namely the ability to mix any textures at independent sizes; Unlike the old days when only a diffuse texture was used, the pattern would now need to be applied to both albedo / specular / normal maps, to my knowledge there are shader keywords to combine each. Needless to say it would require editing every single material to specify its detail texture with a base scale and rotation: It would be painful but doable with a text injection script... I made a bash script to add cubemap reflections once, if it were worth it I could try adapting it to inject the base notation for details. A few changes will be needed of course: Details must be controlled by a main menu setting activating this system and specifying the level of detail, materials properties can't be controlled by cvars. Ultimately we may need to overlay them in realtime, rather than permanently modifying every material at load time which may have a bigger performance impact; We want each iteration to fade with distance and only appear a certain length from the camera, the effect will cause per-pixel lighting to have to render more detail per light - surface interaction so we'll need to control the pixel density.

Oh, some implementations might work a little differently from what I remember the term megatexture referring to. From what I used to know, it meant turning the entire level into a single model or set that uses a single enormous texture. While the concept may have its upsides, there are two major issues that negate any benefit in my view: The first is system resources, you don't benefit from any reuse as every pixel is unique, the only way to do it at scale is with a gigantic image thus a huge performance drop in pretty much every department. The second issue is that level design becomes far harder and more specialized... while here in TDM we only need to draw a bunch of brushes and place some modules to make a level, an engine based on megatextures would require level designers to sculpt and paint the entire world in software like Blender which is far more difficult and we likely wouldn't have even half of the FM creators we do today, even for those that know how to do it imagine the task of manually painting every brick on every home and so on.

Hello taffers, The campaign "Hidden Hands: Blood & Metal" consisting of five missions is now basically ready for beta testing (the briefing videos are missing and there are still some "real" speakers missing, at the moment there are tentative robot voices in these places, hope to replace them in the next two or three weeks). Unfortunately, the project has become somewhat more extensive than originally planned. It took me about two hours to test each mission. So you should allow at least12 hours for all five missions on the first run. Beta testing shall start at the beginning/middle of next week. The difficulty level is somewhere between "The Anomaly" and "The Lost Citadel". Some things are easier, others are not, but proper exploration and usage of the available resources/objects should always pave the way to success. Sign in here, if you are taff enough! Jack Testing thread:

Introduction A project is underway, led by Geep, to eventually provide English language subtitles (or if you prefer, "closed captions") for all the non-story phrases (e.g., barks) of the stock AI characters. The non-story phrases are identified by the "verbosity speech" subtitle tag. The hope is that these subtitles would be distributed as part of the future TDM 2.12 core and so available to all FMs, both old and new. Since there are 5-10K such phrases in total, this project will take a while. Let me know if you'd like to help. This forum thread can be used for project coordination, and to provide info about - What subtitle sets (e.g., for particular AI) are underway and completed Emerging tools or methods for bulk testing Style guidance for TDM subtitle authors. To support this project, a style guide will be developed as experience accumulates. While motivated by providing some consistency to English speech-tagged subtitles, it may be of some interest to FMers creating story-tagged subtitles, and those subtitling in other TDM-supported languages. Potential improvements to TDM's subtitling system - particularly those that would involve engine/GUI changes - can be discussed in this companion thread: Subtitles - Possibilities Beyond 2.11 Current Status - Subtitles for Barks All TDM vocal sets planned for TDM 2.12 have been delivered. New: Fixup Needed to Run These Under 2.12 Beta 3 The Thug - Update May 6, 2023 released as testSubtitlesThug2 FM. This takes advantage of new 2.12dev features and changes to style guidelines. The Lord - Update May 4, 2023 released as testSubtitlesLord2 FM The Wench - Two postponed April versions - Nov 25, 2023 released as testSubtitlesWenchOriginal and testSubtitlesWenchPatched FMs. Two versions because of Bugtracker 6284. IMPORTANT: See final version at end of this list, released Jan. 14, 2024. The Young Builder (Builder 4) - Update May 30, 2023 released (again) as testSubtitlesYoungBuilder FM. (Corrects error in briefing syntax of original May 17 release.) Average Jack - June 8, 2023 released as testSubtitlesJack FM. The Pro - June 23, 2023 released as testSubtitlesPro FM. The Maiden - July 8, 2023 released as testSubtitlesMaiden FM The Grumbler - July 24, 2023 released as testSubtitlesGrumbler FM The Mature Builder (Builder 3) - August 15, 2023, released as testSubtitlesMatureBuilder FM The Lady (aka Noblewoman) - Sept 9, 2023, released as testSubtitlesLady FM The Moor - Sept 14, 2023, released as testSubtitlesMoor FM The Commander - Sept 30, 2023, released as testSubtitlesCommander FM The Simpleton - Oct. 21, 2023, released as testSubtitlesSimpleton FM Builder 1 & 2 (shared vocal set) - Nov. 8, 2023, released as testSubtitlesBuilder1and2 FM The Critic - Nov. 25, 2023, released as testSubtitlesCritic_FM Manbeast - Dec. 10, 2023, released as testSubtitlesManbeast FM NEW! Lady02 - Dec 21, 2023, released as testSubtitlesLady02 FM. Assisted by datiswous. NEW! The Drunk - Jan 6, 2024, released as testSubtitlesDrunk FM. Assisted by MirceaKitsune. NEW! The Cynic - Jan. 13, 2024, released as testSubtitlesCynic FM. Incorporates early demo subtitles by Dragofer. NEW! The Wench, Final Revision - Jan. 14, 2024, released as testSubtitlesWenchFinal FM . Assisted by Dragofer. See also original May version (released in November) in the list above. All TDM vocal sets planned for TDM 2.12 have been delivered. Thanks, @nbohr1more, for integrating these into the release. All AI vocal sets, including additional ones for future consideration - perhaps as "verbosity effects" - are listed here. Current Status - Utilities buildSubtitleShader.exe - Latest release of April 10, 2023. This program fabricates a TDM sound shader file specifically for the testSubtitles... series of FMs used here. It does so by wrapping each sound file name in a directory into a sound shader with uniform incremental naming. While limited to a single directory, the latest release simplifies merging runs from multiple directories. @datiswous reports that this Windows console program also works under Linux/wine, where it is used with similar "testSubtitle..."-derived FMs for verbosity "story" subtitling. checkDurationsInSRT - May 6, 2023 Update (bug fix) This Win/console program scans a directory for .srt files, examines the subtitles, and warns about those phrases/messages that are potentially too short or too long in time, or that seem to require too high a reading rate, expressed in characters per second. It also looks for within-file subtitle messages that overlap in time. soundDurationsCSV.exe - March 7, 2023 Release This Windows console program scans a directory of sound files, reporting their names and (using pre-installed ffprobe) durations with millisecond resolution. The resulting .csv file can then be imported into a custom Excel spreadsheet for subtitle editing. For more, see also Feb 20th comments . findTooLongSubtitles.exe - Minor update, June 23, 2023 Release This Win/console program scans a directory for .subs and .srt files, checks the length in characters of each subtitle line, and reports those that exceed a specified maximum. analyzeFieldWidth of April 27, 2023 (release not scheduled; too idiosyncratic). Used to determine, for 12pt Carleton font, and a representative sampling of bark subtitles, how many characters might reasonably fit within a given gui field width. Later, parts of this code were used to build calcStringWidth.exe discussed next. calcStringWidth.exe - Oct. 11, 2023 Release. Calculates the display width of an input string, for 4 candidate subtitle fonts Carleton and Stone, uncompressed or 16:9 compressed. statsForSubtitles - June 25, 2023 Release. Starting with The Pro vocal set, this Windows console program automates the gathering and reporting of the basic statistics included with the announcement of every vocal set release in this forum thread. Current Status - Spreadsheets and Related Explanatory Documents, including Workflow and Templates Work by Geep on each vocal set starts with instantiation of a pre-configured Excel spreadsheet. This is used for subtitle editing and to do automatic calculations to help manage constraints and decision making. The announcement of each AI subtitle release here includes a link to the corresponding spreadsheet. At first, the spreadsheet's columns, formats, calculations, and highlighting (and its distillation into template form) would change quite a bit between each AI. As of June, 2023 and AverageJack, it has largely stabilized, and is now documented: June 10 Documents Explaining Workflow and Excel Spreadsheet/Template (for AverageJack) The v5 template was used for vocal sets from June's Average Jack to November's The Critic. Further clarifications are now available: Dec 7 Update of the "Explained" Doc for Spreadsheet Template v5 Subsequent vocal sets, through to 2024's The Cynic, use template v6: NEW! Jan. 10, 2024 "Explained" Doc for Spreadsheet Template v6 Current Status - Style Guide for Barks As of Sept 2, Subtitle Style Guide - Part 1 is now available. NEW! As of Jan 16, 2024: Subtitle Style Guide - Part 2 with more discussion and references. Current Status - Third-Party Tools For editing of "story" SRT files, datsiwous found "kdenlive" particularly helpful [to do: link to how-to below]. Geep has been working with the simpler, audio-only "Cadet" for barks.

It's a big project, so it's important to test everything thoroughly and run several tests. "The Lost Citadel" had a lot of bugs in the first release because I didn't test enough. I will not repeat this mistake. I have fixed all problems found during beta 2. Beta 3 shall include all subtitles and briefing videos. The problem is that I'm still missing some voices. This means we can't complete the game subtitles and produce the briefing videos. In the worst case, I'll have to do a new audition for this stuff, but currently I don't feel like it.

TDM 2.12 is ready for beta test This is how to get beta versions: Upgrade from any version (fast): 1 - Start tdm_installer in darkmod folder. 2 - On the first screen, check "Get custom version" and click "Next". Choose the first name in beta/2.12 list, should look like "beta212-NN". 3 - Click on "Refresh" button to ensure that it is not going to download too much stuff. 4 - Continue installing with "Next". Fresh install (slow): 1 - Create darkmod folder anywhere you like. 2 - Download the TDM Installer from downloads section of the website. Extract tdm_installer executable from the downloaded ZIP and place it into your darkmod folder. 3 - Start tdm_installer (in case of Linux, first edit file permissions to allow executing it). 4 - On the first screen, check "Get custom version" and click "Next". Choose the first name in beta/2.12 list, should look like "beta212-NN". 5 - Continue installing with "Next". In general, upgrade is recommended over fresh install. If you don't want to lose your current TDM installation, then you can copy the whole TDM directory and upgrade the copy. This way you can have both 2.12 beta and 2.11 at the same time. At the end of installation, tdm_installer resets your config by renaming darkmod.cfg to darkmod_{datatime}.cfg. This is a recommended procedure on upgrade, otherwise you are likely to have issues due to old config. If you need your old config for some reason, you can always find it in darkmod folder. 32-bit builds of TDM are deprecated, so they are not present in beta versions. They will be added at the very end of beta phase. Notes 1 - Please try to be specific when reporting a problem. What you were doing, where you were when the problem occurred, can you reproduce it, etc. This wiki article provides many suggestions for good bug reports. 2 - Make sure to check every mission for update just before playing it. We expect to apply small tweaks to missions during this beta phase. 3 - This effort is to find out if we broke anything in TDM with our 2.12 changes, if a new 2.12 feature isn't working correctly. We won't be trying to fix bugs that have been around for a long time. Instead, we will create an issue in bugtracker (if not yet present), to fix it after beta. 4 - If you find something wrong, it would be helpful if you report whether the issue happens in 2.11 too. By the way, you can easily get 2.11 version: just copy your darkmod folder and run tdm_installer on the copy, selecting "release211" on the custom version screen. Thank you for testing !

Well, let's explore this a bit. How can this be solved? Currently, creeping overrides running (like you said). Here are a couple issues or considerations: What about players who want to keep the fine control of toggling each one independently? Perhaps some players want to go from creeping to running. At the moment, the code is written in such a way (due to its Doom 3 history) that toggling creep can set the toggled run state, but toggling run cannot set the toggled creep state. The toggle creep key can set the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. Fixing this would require a lot of code rewriting. Brainstorming: It almost sounds like increase and decrease speed keys are desired. Run key to go from creep to walk and from walk to run. Creep key to go from run to walk and from walk to creep. If you're curious to give this a try, here's a Linux test build that matches beta212-05 (rev 16950-10635) with the following change: The toggle creep key sets the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. https://drive.google.com/file/d/1osTCQRf7LQ5wPvhGl2uRU4NcFnJPEu9_/view?usp=sharing