Search the Community

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

shows what the old quake engine was capable of even source had roots in the quake1 engine though the renderer got updated quite a lot with shaders etc. xash3d fwgs is an opensource interpretation of the old goldsource engine and plays pretty much all the older titles not only on PC but on phones and tablets as well, it can also be built natively on linux since it relies on SDL2. The original author uncle mike long since dropped the project but the fwgs guys have made some strides in enabling the missing renderers so now it runs in both opengl and software (no d3d yet). There also a modkit enabling a more modern renderer with shader effects (XashXt) but for most parts it cannot be used out of the box with the older games (only intended for those who want to create new mods). the engine itself is a strange mix of a C based renderer and C++ based client code, the funky thing is you can actually override the engines old renderer from the clientside with something quite a bit more modern. The old renderer got updated with a VBO engine part but it turned out to be buggy as hell and was later disabled (broken flashlight / geometry).

Complaint From Players The player must pick up candles before extinguishing them, and then the player must remember to drop the candle. The player must drag a body before shouldering it (picking it up), and the player must remember to frob again to stop dragging the body. The player finds this annoying or easy to make mistakes. For players who ghost, some of them have the goal of returning objects back to their original positions. With the current "pick up, use item, and drop" system, the item might not return easily or at all to its original position. For example, a candlestick might bounce off its holder. (See player quotes at the bottom.) Bug Tracker https://bugs.thedarkmod.com/view.php?id=6316 Problems to Solve How can the "pick up" step be eliminated so that the player can directly use or interact with the item where it is in the game world? How can so much key pressing and mouse clicking be eliminated when the player wants to directly use an item? How can candles be extinguished and lanterns toggled off/on without first picking them up? How can bodies be shouldered without first dragging them? Solution Design Goals Make TDM easier for new players while also improving it for longtime players. Reduce tedious steps for common frob interactions. Make it intuitive so that menu settings are unnecessary. Do not introduce bugs or break the game. Terms frob -- the frob button action happens instantly. hold frob -- the frob button is held for 200ms before the action happens. (This can be changed via cvar: 200ms by default.) Proposed Solution Note: Some issues have been struckthrough to show changes since the patch has been updated. Change how frobbing works for bodies, candles, and lanterns. For bodies: Frob to shoulder (pick up) a body. Second frob to drop shouldered body, while allowing frob on doors, switches, etc. Hold frob (key down) to start drag, continue to hold frob (key down) to drag body, and then release frob (key up) to stop dragging body. Also, a body can be dragged immediately by holding frob and moving the mouse. For candles/lanterns: Frob to extinguish candles and toggle off/on lanterns. Hold frob to pick it up, and then frob again to drop. Frob to pick it up, and then frob again to drop. Hold frob to extinguish candles and toggle off/on lanterns. For food: Frob to pick it up, and then frob again to drop. Hold frob to eat food. For other items: No change. New cvar "tdm_frobhold_delay", default:"200" The frob hold delay (in ms) before drag or extinguish. Set to 0 for TDM v2.11 (and prior) behavior. Solution Benefits Bodies: New players will have less to learn to get started moving knocked out guards. With TDM v2.11 and earlier, some players have played several missions before realizing that they could shoulder a body instead of dragging it long distances. Frob to shoulder body matches Thief, so longtime Thief players will find it familiar. Second frob drops a shouldered body. Players still have the ability to both shoulder and drag bodies. Compatible with the new auto-search bodies feature. Dragging feels more natural -- just grab, hold, and drop with a single button press. There is no longer the need to press the button twice. Also, it's no longer possible to walk away from a body while unintentionally dragging it. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Candles: New players will have less to learn to get started extinguishing candles. With TDM v2.11 and earlier, some players didn't know they could extinguish candles by picking them up and using them. Instead, they resorted to throwing them to extinguish them or hiding them. Hold frob to extinguish a candle feels like "pinching" it out. Once a candle is picked up, players still have the ability to manipulate and use them the same way they are used to in TDM v2.11 and earlier. For players who ghost and have the goal of putting objects back to their original positions, they'll have an easier time and not have to deal with candles popping off their holders when trying to place them back carefully. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Solution Issues Bodies: Frob does not drop a shouldered body, so that might be unexpected for new players. This is also different than Thief where a second frob will drop a body. "Use Inv. Item" or "Drop Inv. Item" drops the body. This is the same as TDM v2.11 and earlier. This is the price to pay for being able to frob (open/close) doors while shouldering a body. Patch was updated to drop body on second frob, while allowing frob on doors, switches, etc. Candles: Picking up a candle or lantern requires a slight delay, because the player must hold the frob button. The player might unintentionally extinguish a candle while moving it if they hold down frob. The player will need to learn that holding frob will extinguish the candle. The player can change the delay period via the "tdm_frobhold_delay" cvar. Also, when the cvar is set to a delay of 0, the behavior matches TDM v2.11 and earlier, meaning the player would have to first "Frob/Interact" to pick up the candle and then press "Use Inv. Item" to extinguish it. Some players might unintentionally extinguish a candle when they are trying to move it or pick it up. They need to make sure to hold frob to initiate moving the candle. When a candle is unlit, it will highlight but do nothing on frob. That might confuse players. However, the player will likely learn after extinguishing several candles that an unlit candle still highlights. It makes sense that an already-extinguished candle cannot be extinguished on frob. The official "Training Mission" might need to have its instructions updated to correctly guide the player through candle manipulation training. Updating the training mission to include the hold frob to extinguish would probably be helpful. Similar Solutions In Fallout 4, frob uses an item and long-press frob picks it up. Goldwell's mission, "Accountant 2: New In Town", has candles that extinguish on frob without the need of picking them up first. Snatcher's TDM Modpack includes a "Blow / Ignite" item that allows the player to blow out candles Wesp5's Unofficial Patch provides a way to directly extinguish movable candles by frobbing. Demonstration Videos Note: The last two videos don't quite demonstrate the latest patch anymore. But the gist is the same. This feature proposal is best experienced in game, but some demonstration videos are better than nothing. The following videos show either a clear improvement or that the player is not slowed down with the change in controls. For example, "long-press" sounds long, but it really isn't. Video: Body Shouldering and Dragging The purpose of this video is to show that frob to shoulder a body is fast and long-press frob to drag a body is fast enough and accurate. Video: Long-Press Frob to Pick Up Candle The purpose of this video is to show how the long-press frob to pick up a candle isn't really much slower than regular frob. Video: Frob to Extinguish The purpose of this video -- if a bit contrived -- is to show the efficiency and precision of this proposed feature. The task in the video was for the player to as quickly and accurately as possible extinguish candles and put them back in their original positions. On the left, TDM v2.11 is shown. The player has to highlight each candle, press "Frob/Interact" to pick up, press "Use Inv. Item" to extinguish, make sure the candle is back in place, and finally press "Frob/Interact" to drop the candle. The result shows mistakes and candles getting misplaced. On the right, the proposed feature is shown. The player frobs to extinguish the candles. The result shows no mistakes and candles are kept in their original positions. Special Thanks @Wellingtoncrab was instrumental in improving this feature during its early stages. We had many discussions covering varying scenarios, pros, and cons, and how it would affect the gameplay and player experience. Originally, I had a completely different solution that added a special "use modifier" keybinding. He suggested the frob to use and long-press frob to pick up mechanics. I coded it up, gave it a try, and found it to be too good. Without his feedback and patience, this feature wouldn't be as good as it is. Thank you, @Wellingtoncrab! And, of note, @Wellingtoncrab hasn't been able to try it in game yet, because I'm using Linux and can't compile a Windows build for him. So, if this feature isn't good, that's my fault. Code Patch I'll post the code patch in another post below this one so that folks who compile TDM themselves can give this proposal a try in game. And, if you do, I look forward to your feedback! Player Complaints TTLG (2023-01-10) Player 1: TDM Forums (2021-03-13) Player 2: Player 3: TDM Forums (2023-06-17) Player 4: TDM Discord (2021-05-18) Player 5: TDM Discord (2023-02-14) Player 6: Player 7: Player 8:

Just curious, based on this discussion: http://forums.thedarkmod.com/topic/19239-soft-r-gamma/?p=427350

Ever since I worked on "Chalice of Kings" with Bikerdude, I have wanted to get flame particles with new particle glares into the core mod. My reasoning was that the candles have glares and the un-glared torches look mismatched. This proposal was met with mixed reactions, so (knowing the history of TDM feature proposals...) I have created a technical demo. You may download it here: zzz_flameglare.pk4.txt (fixed) Just rename without the .txt extension at the end and place it in your Darkmod directory. Here are some screens. Using particles for this is probably the wrong way to go now that Duzenko has an emissive light feature in his branch: http://forums.thedarkmod.com/topic/19659-feature-request-emissive-materialsvolumetric-lights/

And btw I'm not against using both shadow systems, I just think that supporting two systems, is more work, but if the TDM engine team is okay with that, then go for it they have my full support, for what is worth. I just personally don't like that shadow maps are being pushed back is all. But you guys do what you want, this should be a mission makers decision, I'm just a "customer" I will have no choice but accept what you guys decide.

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

I know you didn't asked for non TDM mappers opinion but man this decision makes me really sad, imo after so many years, with both shadow systems and still deciding to hard limit shadow maps, to only stencil can do, is like cutting the wings of a bird. Has a player, I can't wait for the day you guys finally decide to remove stencil shadows from this engine. EDIT: Ups I didn't saw the poll at first so my comment was a tad precipitated sorry about that.

I think this will always be a divide. Engine coders will want a universal behavior that acts the same way across all missions. So if we want to offer the additional benefits of Shadow Maps, we will need to break lots of missions and then work to fix them. Mappers will probably want material or entity flags that force these behaviors so that they can force usage where they prefer. I think defaulting to consistent with Stencil rules is a good idea. Maybe this is a good case for using mission.cfg and have it force the cvars to enable the features?

I like how this has essentially become a Linux thread despite it not being the intended focus. I play around with Ubuntu MATE because I like Ubuntu and the MATE variant has an environment I prefer with a bunch of changes I like, a good compromise between old and new. That said, TDM behaves a bit oddly in Linux. For some reason in TDM it misses the occasional mouse click - if I happen to click fast enough there's a chance the event won't register. It seems to be something inherent to the Doom 3 engine in Linux - even in dhewm3, if I make a really fast click on the mouse it can sometimes ignore that mouse event and not fire the weapon. Generally you have to be really quick on the down/up event for it to happen, but it happens, it's reproducible and I can't just accept having to consciously be aware of my mouse behaviour and remembering to click long enough to guarantee the event is registered. I'm sure many won't notice this issue, but I'm pretty fussy about such things so it annoys me. This doesn't happen on anything else in Linux, just Doom3/TDM. Not surprisingly Windows doesn't have this issue, and it's a good example of the reasons why I don't bother moving entirely to Linux. I can't stand odd quirks like this and there's odd quirks EVERYWHERE in Linux. There's quirks aplenty in Windows too of course, but I'm used to them.

The real St. Alban was a pagan who became a celebrated religious personality, this All Saints Day 2010 The Dark Mod places its own spin on this mythical figure. Screenshots: Intro: "'Business' has been slow lately, even more so after most of my gear got snatched during a Watch raid... I've since been forced to hit the streets and pick pockets for a living. But my luck was about to change, last night I was approached by a red hooded figure with a proposition... As we sat down in a dark corner of a nearby inn, he told to me that the Builders of St. Alban's Cathedral in the Old Quarter had recently unearthed a discovery that might lead to the final resting place of some saint." " But before I do anything, I need to get my tools and stash from the evidence room at the local watch station." "with the hawks, doves will congregate they will drop honey from the cliffs wine will surge over the earth the sheep will wander harmlessly with the wolf then the wicked will rise, but to retribution" - 'scripture of St Alban' There is a new version out now, see the following thread St Albans Cathedral version 1.6 Build Time: about 2-3 months. Thanks:- Huge respect to the Dark Mod team for such a great mod and for all the hard work they put into it and continue to put into it. Special thanks to Fidcal, Serpentine and others for their help on the forums and to Testing:Ugoliant, Baddcog, Grayman, Lost soul, Bjorn and Baal (for doing all the Vp work in the town. Readables: Ungoliant and Mortemdesino for all awesome work on the readables. Resource: Fids, Grayman, Ungoliant - guis, models & images. Misc: Loren Schmidt - the author of the map I based the cathedral on. Info: # Like Thief2, some things are climable, pipes, wall vines etc.. You can also drop some of the keys, some door that are frobbabe mean there is another way inside - explore u taffer! # Due to TDM being a lot more of a resource hog than T2 I have been forced to limit the number of Ai in the mission, but they have better placement than my last mission. # On all difficulty levels the player starts with vertualy no tools/weapons, there are weapons to be found - read, read, read! # For the love of all that is holy, read the briefing otherwise you will problems completing the mission. Known issues:- # This mission will have less than optimal fps at a few points on the map, mid range DX9 card(X1900/GF7800) or higher required. # On low end PCs I recommend, V-sync is off, AA is off, Aniso is 4x or lower and that any and all background apps are closed.

A couple more: https://forums.thedarkmod.com/index.php?/topic/21739-resolved-allow-mantling-while-carrying-a-body/ https://forums.thedarkmod.com/index.php?/topic/22211-feature-proposal-new-lean-for-tdm-212/ https://forums.thedarkmod.com/index.php?/topic/22198-feature-proposal-frob-to-use-world-item/ https://forums.thedarkmod.com/index.php?/topic/22249-212-auto-search-bodies/

I feel that tweaking shaders visually does more harm than good in the end. Here is one example of what shader tweaking leads to, and where I'll do yet another visually-breaking change: 6354 Before that is was untweakable specular which also broke visuals: 5044 What a game engine needs is a universal model (preferably well-known) with several tweakable parameters. In fact, the very idea of PBR and why it wins today is that it models real physics, and thus it works more or less the same way in every engine and scenario. It is a well-known standard (with minor variations). We can't have PBR yet (and maybe forever), thus we stick close to Phong reflection model, which has been around for decades and is also quite standard. Artists should make assets that would result in a beautiful picture, not shaders. But they can't do it if we have some weird non-standard lighting model which changes every year. We should never tweak shaders based on how average missions becomes seemingly nicer to us! If someone decides to add normal mapping, it should behave as an approximation for how real high-resolution surface should behave in our model, not as some kind of "beautifier effect". If you want to add some effect which is outside the current model, it should be done in a way that: it does not change how the previous model works (and how current missions look) it can be tweaked by understandable parameters it is applied in all shaders and all lighting the same way I believe we already have fresnel and rim, but it is kinda hardcoded and not present in all shaders. Yet another result of someone tweaking shaders based on how it looks and not on how sound it is mathematically.

To cater to both audiences. I mentioned LibreGameWiki as one example. nbohr1more mentioned other uses. Explicitly allowing reuse and spread will help TDM reach a wider audience and would hopefully attract more volunteers. More volunteers which can help improve both TDM versions. There are several benefits for a project of being in the Debian repo. One is that TDM Debian-users can report defects on any package directly to Debian (no need to register on separate forums). Debian may then fix the issue themselves (in their "TDM-libre" package) and will offer the patch upstream to TDM, who can then choose to accept or reject the patch. I envision "TDM-libre" to have the same capability of downloading any mission as regular TDM. The only difference is that "TDM-libre" would come packaged with the regular engine (which is GPL+BSD) and an included mission that has libre media/gamedata. When I play TDM by myself, I want the unlimited-play and can accept commercial restrictions. But if I were to promote it somewhere, or charge for a stream when playing online, or make a video, I would want a version without commercial restrictions (and can temporarily accept limited-play) to make sure I don't violate anyone's copyright. Perhaps. That's what I'm trying to find out.

Author Note: This is a brand new mission and a new entry into the accountant series. There are some different than usual puzzles in this FM, so if you find yourself stuck try to think about your pathway forward in a logical manner. And if you're still having troubles then pop by this thread and ask (preferably with spoiler tags). This FM is brand new and serves as the first installment in The Accountant series, a few years back there was a small prologue style mission released however I felt that it did not represent The Accountant series so I decided to go back to the drawing board and do a whole new mission that's larger, has a better level design and has a story that lines up closer to what I plan to do with the accountant series. The mission is medium sized and you can expect between 30-90 minutes to complete it depending on your playstyle. Beta Testers Captain Cleveland Crowind Kingsal PukeyBee Skacky SquadaFroinx Voice Actors AndrosTheOxen Epifire Goldwell Stevenpfortune Yandros Custom assets Airship Ballet Bentraxx Bob Necro Dragofer DrKubiac Epifire Kingsal MalachiAD Sotha Springheel SquadaFroinx Available via in-game downloader File Size: 233 MB - Updated to v 1.1 (01.06.2018)

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.

I don't understand this bit, but then I know nothing about how sounds/audio are processed internally. Based on the audio alone (listening) I would say the engine knows how far I am from a sound source (or the other way around) and sets the volume accordingly. The engine also knows if I am behind a closed door or not. I don't know, it would seem all is there already.

As much as I'm a big fan of FOSS, it gets messy when it involves assets with a whole mix of licenses. The engine? Sure that'll work, but TDM is useless with just the engine. Even if you have a separate libre version with verified assets, you've now split the project into a full version and a libre-only version and for what? Some entry in a niche wiki and the Debian repo? Once people want actual full missions to play you begin to drift away from the restricted licenses imposed on the libre version and have to code and accommodate for that. If TDM was developed with the day-one intention of only allowed libre licensed assets then there'd be no problem, but it hasn't and what your asking is probably too much work and effort for little benefit.

The physics engine is open source (MIT licence) and it seems it was used on a AAA game already see here. https://github.com/jrouwe/JoltPhysics I can only dream that some day this may happen to some idtech4 based engine. So much cool physics based gameplay would be possible in that case. A small glimpse at what perhaps some TDM traps could look with a better physics engine, thou I do think some of the traps in the video bellow aren't suited for TDM and or are already possible with current TDM physics. https://www.moddb.com/games/shadwen/videos/video-2

@stgatilov, I've been looking into the stray marks associated with Stone 12 pt. Not much progress, because there's something strange going on. Any change I make to the metadata in fonts/english/stone/fontimage_12.dat (whether in the core or as an FM "/fonts/" override) is ignored. Whereas changes to the corresponding 24 pt .dat (whether in core or override) do show up in the nominally 12 pt subtitles (with either gui textscale of 0.24 or 0.25). Is there something in the engine code that is keeping this 12 pt .dat from being used? There are no warning about such at startup. Perhaps some engine hack left over from when there was a missing file?

Maybe they are referring to the GPL licensed parts of the engine. Maybe they are referring to the CC-BY-NC-SA license for the media/gamedata. As I understand it, the game engine is libre (GPL+BSD) so no change would be required there. I'm trying to see if there is a way of releasing a "TDM-libre"-version (not changing regular TDM) as I describe in my question (2). Or if the TDM Installer can qualify as libre software (1).

I did play Thief and FMs, but I don't play it any more, except for major things like Black Parade. The clunky movement and antiquated Dromed editor is what discouraged me from interacting with it over the years. I regularly play and sometimes make content for TDM, because it has much better movement model than Thief. I know that most missions don't use it well, but if you construct your geometry (gaps, ledges, distances) using power of two measurements, movement and mantling feels fast and snappy. There's no need for regression in that regard, in my opinion, there's a need for assets and missions made with the movement model in mind, to showcase its strengths properly. Even if TDM originally intended to "simulate the stealth gameplay of Thief, many things will be familiar to veteran Thief players" the actual mod history was a bit different. The team came up with a mission platform that has its own identity when it comes to mechanics. The way assets were made might have been a huge mistake, but that didn't prevent the platform from growing. Since you like anecdotal evidence, noone other Skacky once said that TDM movement model was super clunky, after playing The Painter's Wife. It was really hard to convince him that if a mapper places geometry this poorly, and isn't aware what spatial measurements play to the strengths of a movement model, no movement model will save his mission. And there is no fixing of this problem on the engine side, although it's not the first time when TDM team tries to address the asset problem with engine changes, which I suspect will ultimately lead to even more problems down the line. In game development, things like core mechanics and player tools are locked-down first, in one of the pre-production phases, because all the levels will be constructed around them. Making changes in core mechanics in a project this mature is very risky, I assume you don't plan on going through all playable spaces in all released TDM FMs to check for errors. Instead of making incremental changes in fundamental mechanics, I'd encourage you to create a fork, or some kind of major version bump candidate, like 3.0, where all things could be revamped: movement, player tools, UI, new frob mechanics, perhaps with UI contextual icons, new training map to incorporate all that, etc. Once all new elements fall into place and create something new, with a map or maps to back it up as relevant changes, it will be easier to convince existing player/author base that it was worth it. I assume the existing fanbase is already fragmented, as a result of all those heated discussions around the topic. But with multiple versions available for download, the transition to hypothetical "TDM 3.0" should be easier. It could be similar to UE2 and UE3, and you could also use this as an occasion to draw the line for backwards compatibility. I know there are old systems and variables kept in place just in order not to break existing missions. This way you could e.g. redo the LOD system, implement lights using math functions instead of textures, etc.

Hi, I'm trying to make some maps for dhewm3, but if I give the path where the game files resides it crashes. In my case the path is /usr/local/share/dhewm3/ This doesn't happen if I give it my working path but then I'm missing all definitions, models, materials etc.. ~/.local/share/dhewm3/ My system is Ubuntu 20.04, DarkRadiant 3.2.0 is installed from ppa This is the error: $ darkradiant SIGSEGV signal caught: 11 0: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZN6applog15SegFaultHandler14_handleSigSegvEi+0x474) [0x7f7b3f2ebef4] 1: /lib/x86_64-linux-gnu/libc.so.6(+0x43090) [0x7f7b524ce090] 2: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZN4decl23DeclarationFolderParser5parseERSiRKN3vfs8FileInfoERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x202) [0 x7f7b3f1abf32] 3: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZN6parser18ThreadedDeclParserIvE12processFilesEv+0x87b) [0x7f7b3f1b9f8b] 4: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZN6parser18ThreadedDeclParserIvE7doParseEv+0x20) [0x7f7b3f1bb140] 5: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZNSt17_Function_handlerIFSt10unique_ptrINSt13__future_base12_Result_baseENS2_8_DeleterEEvENS1_12_Task_setterIS0_INS1_7_Resu ltIvEES3_ENSt6thread8_InvokerISt5tupleIJZN6parser17ThreadedDefLoaderIvE19ensureLoaderStartedEvEUlvE_EEEEvEEE9_M_invokeERKSt9_Any_data+0x50) [0x7f7b3f1d1e20] 6: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZNSt13__future_base13_State_baseV29_M_do_setEPSt8functionIFSt10unique_ptrINS_12_Result_baseENS3_8_DeleterEEvEEPb+0x2d) [0x7 f7b3f1c6f2d] 7: /lib/x86_64-linux-gnu/libpthread.so.0(+0x114df) [0x7f7b5268e4df] 8: /usr/lib/x86_64-linux-gnu/darkradiant/modules/libradiantcore.so(_ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJZNSt13__future_base17_Async_state_implINS1_IS2_IJZN6parser17ThreadedDefLoad erIvE19ensureLoaderStartedEvEUlvE_EEEEvEC4EOSA_EUlvE_EEEEE6_M_runEv+0xfd) [0x7f7b3f1ca13d] 9: /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6de4) [0x7f7b528e2de4] 10: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f7b52685609] 11: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f7b525aa133]

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

Thanks! Looks like a map change rather than an engine issue. To verify further can you test beta 5 or newer with uncapped FPS set to max 300 in the advanced menu?