Leaderboard

Alright - managed to find the source the error - a single volumetric light had the spawnarg set of ".001/" The map is now fixed. Thanks all!

I think it will be "used" in very little sense, but it will be skipped and you won't see it. As far as I see, mainmenu_briefing_video.gui already includes subtitles code: //stgatilov #2454: display subtitles #define SUBTITLES_NAMEPREFIX BriefingVideo #include "guis/tdm_subtitles_common.gui" So just adding subtitles for your audio file would be enough. I guess sound from video file is also supported, just need to find the syntax on wiki.

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've spent a lot of time recently submitting patches to fix some bugs and working on a few things that I think would really improve the feel of TDM for 2.11. They are very small changes, and they are meant to polish what's already there without changing or breaking anything for anyone. (Available 2.11 beta 7) Added player "tdm_toggle_sheathe" cvar and "Toggle Sheathe" setting (6232) (thread). Renamed "New Missions" to "Missions List" in main menu (6230). @nbohr1more cleaned up my original patch. Originally, proposed by @snatcher (post). Fixed initial difficulty highlight on Objectives screen (6229). @stgatilov cleaned up my original patch. Fixed Objectives title slightly cut off on low text scale (6234). @stgatilov cleaned up my original patch. Made it possible for the player to change "pm_noclipspeed", so noclip speed can be set (6237). (Available in next beta) Make "tdm_toggle_creep" work like other toggle cvars, and add "Toggle Creep" to the settings menu (6242) (thread). (Not available) Make the inventory parchment background (dds file) separate from the "Missions List" parchment background (dds file). Without the patch, if you change the inventory background, it will also change the main menu. Patch submitted (6241) to decouple the inventory background from the main menu. This is meant for players who want to edit the inventory background (dds file) themselves (e.g. reduce its brightness without affecting the main menu). When you drop a long distance and land in a mantle, damage is shown after the mantle animation is complete. Partial fix submitted (6231). I think I'll need @stgatilov's help on this one. Bikerdude was very kind and provided a test map for this, which helped to expose an issue with my original patch. ("pm_mantle_while_shouldering" cvar available in 2.11 beta 7) It was requested by Bikerdude one year ago to allow mantling while carrying a body. Due to feedback, I've submitted three patches each with a different behavior, starting in August 2022 (5892) (thread) : (Patch v1) Always enable mantling while carrying a body. (Patch v2) Only enable mantling while carrying a body if "pm_mantle_while_shouldering" cvar is set. This is already available in 2.11 beta 7. (Patch v3) Restrict mantling at the waist. There is no agreement about how this should work yet. I've spent over 12 hours of work and testing on (v3) so far, so it would be incredibly discouraging if a final decision is not made between versions (v1), (v2), or (v3) for 2.11. Personally, I think patch (v1) always enable mantling while carry a body is best. This matches Thief 1 & 2 and does not require a cvar. If (v3) is chosen, the rules need to be decided. These are the final issues / bug trackers I have for 2.11. I hope they can make it into the final release of 2.11, because I think it would make TDM feel more polished and give a better first impression for newcomers. And, Thief players would have a better first time.

I mean, yes, obviously there is an internal forum where decisions are made regarding how to move forward with the game. That's how things work. And not just in our team, everywhere. Or do you see Apple discuss their business plans and new "innovations" in public? That being said, the team values all well though out ideas, feedback and suggestions, but even if everyone agrees that a certain feature would be nice to have, it doesn't automatically mean that it's going to happen, because there has to be a dev willing to do the work. You have to remember that we are all doing this for free on our free time. Every dev picks the task they are interested in the most. And that's precisely the reason why these excruciatingly long beta phases are so annoying: they prevent you from doing the stuff you really want to do. TDM is open-source and you can do with it whatever you like, but for something to be integrated officially into the game, the team has to agree on that. If you want to see a feature happen, implement it yourself and send in the patch, like Daft Mugi does. But be warned: Not everything listed in the bug tracker is a feature that has been fully agreed upon. It is always a safe bet to ask first, before doing the work. If you patch is not integrated into the core mod, you are of course free to offer it as a mod for TDM. Regarding the internal decision making process. It is rarely about personal preference, but more about: Is it in line with the existing vision / look & feel of TDM? Could it break anything? Number 2 especially applies to breaking FMs, which is a no-go because of the enormeous work mappers have put into their FMs.

As someone new to contributing, this has been an incredibly frustrating and stressful experience. I've felt like I'm racing towards an unknown deadline. I've lost track of how many hours I've put into TDM testing and code writing this month. One of the biggest sources of stress is not knowing the beta release schedule. TDM 2.10 was released March 2nd, 2022. So, my thinking was that these could get in this month (January), and then February would be mostly frozen. These are small changes compared to other patches I've seen made, and I don't consider them at risk of breaking the game. The "mantle while shouldering" code change is simple, but the hardest part is agreeing on its behavior. That changed behavior will affect both players and mappers. At least some players want that change, so I don't understand the hold up and big controversy. The main reason I saw against it was that an existing mission might have a mantle trap, so this change would break their mission. But no example was given of even a single case of this. The other source of frustration is not knowing what the internal dev communication is. I've been doing my work mostly in the dark. Also, sometimes I get surprised by a message like "the group has decided X" without a reason. And, from my point of view, my changes have been mostly bug fixes uncovered during beta testing. It would be a shame for players to have to wait an entire year for these bug fixes. And, I'm writing a TDM getting started guide for Thief players, incorporating these recent changes, because I know veteran Thief players would likely enjoy these changes. Again, not knowing the release schedule, I'm also racing to finish that guide against an unknown deadline. I wanted that guide's release to be the same day as TDM 2.11's release.

Like... who was that person who pushed the latest major mantling changes during beta?... UPDATE: Maybe things got mixed in my mind

To be honest, that can be said about 99% of changes to the game Yes, that's exactly what is happening I'm trying to filter all these changes depending on how scary they look to me. Out of what Daft Mugi has listed that is not in beta211-07 yet, I think only the fix for damage from fall + mantle is going to make it. The rest of the changes... I'd better not hurry. The general rule is that we do development before beta starts, not after. And especially not in the second half of beta.

I see your point, tho some of what's in the "Potential for translations" section is about current capabilities. But I can drop that separate section and fold the current-capabilities stuff into the "As for translations..." paragraph. I'll start a new forum topic, too. Maybe "Subtitles - Possibilities Beyond 2.11" would be general enough. Edit: wiki page edited, new forum threads started.

Thanks for fixing this @OrbWeaver

I think that the mainmenu_briefing.gui change is only needed for briefings that are accompanied by a voice-over like the ones in the included missions 1 and 2.

I added a few sentences to the Light Switches section of "Relighting Lights" about this workaround.

beta211-07 is available.