Search the Community

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/

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.

This is an intereting discussion. So, could one of the mods please move this to a separate thread as to not derail the beta testing thread. As a developer, you spend about 80% of your time just reading code. So, optimizing for readability is very important. The more information you can gather just by reading without cluttering up the code (by needless comments) the better. Hungarian notation helps immensely to quickly prase the displayed code in your brain. Yes, your IDE will show the desired information as well, but a mechanical interaction with the code is required to show it (mouse over or similar). Also, often you are tasked to do code review on webpages that don't offer these nice crossreferencing features of your IDE. Some things are objectively bad, 'though, so the respective rules preventing those things should universally be followed. For instance, much legacy code is nested extremely because at some point in time, it must have been a rule that you only have one return-point in your function (probably a c-residual). Such code is exhausting to read ("what was the else-if-condition some 1000 lines ago leading to this else-case again?") and very likely contains tons of code duplication. Today, we have the rule to only use little nesting and short if-else-clauses, to make the code easy to read and debug. If I come accross such a nested legacy function, I refactor the shit out of that function while trying to understand it, just so the next person after me doesn't have to deal with that horrible mess again.

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)

I have gone outside station. So... I have 6 buttons to accelerate along 3 axes, mouselook to rotate around 2 axes and 2 buttons to rotate around third axis. And 1 button to remove velocity limit and 1 button combo to brake. I suppose this is a nod to Descent (which I also did not play). Quite surprised to see such complex controls in a modern game.

Yeah, I don't know what to say. Rev 10383 works fine and 10384 does not. It is always reproducible for me, meaning that every time I try to reproduce it, I can reproduce it. After some more testing, I found that r_multiSamples set at 2 or 4 has the glitch most often at that viewpos. When set to 8 or 16, it is still possible but less likely. Setting r_fboResolution 2 made no difference. If com_maxFPS is set to something lower, such as 30, the glitched frames display for a longer period of time. Yeah, I also wonder if it driver dependent or GPU dependent. I discovered the glitch while using graphics drivers Mesa 22.0.5, so I updated my OS and graphics drivers to Mesa 23.3.2 today as a test, and the problem is still there. It's strange that rev 10384 exposed this problem. My machine specs and settings: Linux, Ubuntu 22.04 AMD Ryzen 9 5900X AMD Radeon RX 6700 XT (Mesa 22.0.5 & Mesa 23.3.2 both exhibit the glitch) com_fixedTic 1 com_maxFPS 60 Anti-Aliasing 2x (r_multiSamples 2) The video I shared shows the viewpos. Even at the same viewpos, the glitched frame will pop in and out. I've only seen this glitch happen in this single room in Accountant 1. If I move around the room at that viewpos, I can find other view positions that also expose the glitch. Here's another viewpos for Anti-Aliasing 4x, 8x, and 16x. It requires moving the mouse slightly to get into the exact viewpos to expose the glitch. (1.7 -166.4 0.0) is not precise enough. -1460.29 1425.48 172.25 1.7 -166.4 0.0 Glitched frame (Shows the curtain texture, covering most of the frame. Also, a hint of the red carpet texture?): Good frame (Same viewpos and Anti-Aliasing settings, when the glitched frame disappeared for a moment.): (Before and after rev 10384) I wonder if this might also be related to: (Before and after rev 10384) Also, sometimes on the loading screen with Anti-Aliasing enabled, I get a glitched background, which does not show with Anti-Aliasing disabled. See left side of screenshot: I don't know if the last two examples (distorted first frame on launch & loading screen distorted background) are related, but I thought I'd mention them just in case it helps track down the issue.

I've been on DR 3.8 for a while, but today it started giving me an error with the title "Real Hard DarkRadiant Failure" and message "Could not acquire frame buffer lock", "Break into the debugger?". Regardless of whether I press Yes or No, the next message is "Unhandled exception", "An unhandled exception occurred. Press Abort to terminate etc.". If I press Abort or Retry on this message the top row of buttons (File, Edit, View etc.) flash rapidly and then DR shuts down. If I press Ignore I can continue using the program, but as soon as I interact with the UI the error message comes up again. So far I already tried to wipe my user settings in AppData/Roaming, but it made no difference.

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

I accidentally found a bug that's easy to miss but likely also to fix: Select an arrow, in my case I was using the water arrow. Hold down the fire button to charge your shot, wait until it's fully charged but before getting tired and having to abort it. Press esc to enter the main menu without letting go of the left mouse button, then press esc again to resume. If you look and move around, the position of the hand and bow will no longer update until you let go to fire, you can see your first person hands floating in mid-air from a distance till you release the mouse button which will fire and update the hands again.

Updated patch along with new test builds. Windows: https://drive.google.com/file/d/13lQig7Yzfc_jovU2zZklxLV1QOKAjkXe/view?usp=sharing Linux/Ubuntu: https://drive.google.com/file/d/1j7DoWBKuBAFdVH2Y-2LcYsgdtJNBabmn/view?usp=sharing @stgatilov Could you please update test-frob-daftmugi? Changes in update: Bodies can be dragged instantly by holding frob and moving the mouse. Food can be eaten the same way as extinguishing a candle. (Pending) Add menu setting "Hold Frob to Use", with options: Quick (200ms) - short delay before use Delayed (400ms) - long delay before use TDM original Current design: Frob Pick up body and shoulder it (carry it) / Drop body Pick up candle/lantern and carry it / Drop candle/lantern Pick up food and carry it / Drop food Pick up an item and carry it / Drop item Hold frob (for special action) Drag body or body limbs Pinch out candle (also, pinch out candle while carrying it) Toggle lantern off/on (also, toggle lantern while carrying it) Eat food (also, eat food while carrying it) Hold frob and move mouse to instantly drag body. Addressed concerns from initial design to current design: Changed the candle behavior to pick up on frob and extinguish on held frob. Added @AluminumHaste's suggestion to allow un-shouldering a body on frob. Added @nbohr1more's suggestion to allow extinguishing a candle while holding it. Added @Skaruts's suggestion to allow instant dragging of bodies on mouse move. Tried to address @snatcher's suggestion of making the extinguish candle delay 500ms instead of 200ms. There's a planned menu setting to set it to "Quick" (200ms) or "Delayed" (400ms). Also, I hope the "instant" body dragging will work well for you. I think this is finally in a good place. It's evolved quite a lot since its initial design. I've tried to address as many concerns and suggestions as I could. Thank you everyone who gave feedback! It's much appreciated!

Yeah it would be cool to see some more detailed statistics and it’s a shame they aren’t really captured. Since we are talking about fan mission platforms, where players also make the content for the game, I feel like the best thing we’ve got is you can look at the number of content releases for the games. Keep in mind the graph counts campaigns as single missions - so for example NHAT and TBP both count as 1 mission. A good year for TDM has has approaching maybe 50% - mostly we’re 25-30%. https://www.ttlg.com/forums/showthread.php?t=152494 You could also look at the number of ratings thief missions get on https://www.thiefguild.com/ vs TDM ones, but that is pretty iffy in that you could chalk that up to more awareness of the site in the thief community than TDM Out of curiosity is there a reason a thief player can’t be a new player? I kind of think a player is a player and new players would be ones who are playing the dark mod who weren't? Is there disagreement the base of players most likely to pick up the game are fans of the thief games? They are certainly the most fruitful place to find feedback on the game beyond the sphere of this forum that I have seen. When we were trying to finish up SLL there was a lot of discussion on the forums about how long it had been since there was a release for the game. I am thankful that the stats show at least some stability over the years in terms of releases for TDM, but the trend for all of the games is decline. Not doing anything is a valid response if that’s what the devs want to do - it is not possible to provide evidence that any effort will slow that inertia. As a player and content maker I would just prefer trying to find feedback where it is offered from players who were willing to try the game but ultimately could not engage with it and see if there is anything that can be done within reason to ease them into the game. The game has a lot to offer imo. All those players are potential contributors - contributions in turn attract players - it’d be nice to see the cycle go on as long as it can.

The Alchemist is a full-size city and mansion Dark Mod FM, the fourth in the Thief's Den series in which you play Farrell. It follows on from Heart of Lone Salvation so you should play that first. The main build of this FM was by Sotha who was unable to continue work on it. I (Fidcal) could see the potential so completed it, somewhat roughly and quickly, so it could be enjoyed rather than abandoned. Even so, it exceeded my original estimate! Read the notes below while you ... DOWNLOAD HERE. (27MB) Sam's death hit me hard and I've not been feeling so good. I'm worried I didn't get rid of the Heart of Lone Salvation quickly enough. I don't want to end my days like Martha Edridge. A health potion is too weak; I need something stronger. Only a holy healing potion will lift a curse so I need to find a good alchemist. But the city watch have been tipped off and the district is alive with guards searching for any intruder they find on the streets. I have no choice: I must get that potion... This FM needs Dark Mod Update 1.02 or later. TIP: You cannot drink the holy healing potion if you are perfectly fit! As said in the briefing, the city watch are already ALERT right from the start and much more likely to notice you in the dark. You'd better be ready to move! ALLOW 2 TO 4 HOURS PLAY FIRST TIME AROUND Players with low end machines will find this slow in some places especially when there is an alert. Hide. Let things calm down. Closing doors behind you may help. In Dark Mod some glass is breakable using any weapon. It may require several hits. But there is also toughened glass which cannot be broken. Only one way to find out which is which! Do not use Esc during the briefing or the cursor becomes invisible. (You can still select blind though looking for highlights.) You can skip the briefing with the left mouse button. If you miss anything you can use the back button to show it again. Above all, Enjoy! [EDIT] updated with debugged combination lock script 5 June 2010. If you had a previous version installed make sure it is totally removed first, ie, doom3/alchemist and darkmod/fms/alchemist. [EDIT] If you get strange crashes there is a known bug caused by the spiky balls. This is fixed in Dark Mod but I think not released until 1.03. Try my patch from http://www.fidcal.com/TEMP/alchemist_patch2.zip It makes the spiky balls passive - they don't do damage - but apart from that no difference. Close Dark Mod Unzip the patch into your game folder doom3\alchemist Start the FM afresh, don't use earlier gamesaves.

Greetings. First I would like to say a huge thanks for the continued support of this game and for TDM 2.10, it loads much MUCh faster now. However on Debian Linux I have an issue where the mouse occasionally just warps. It happens both in the game and in the menus, though obviously when it happens in the game it is quite disorienting. Anyone else experience this? I never saw it in 2.09... EDIT: Seems to have gone away when I switched window managers.

Here is version 6 of the script. What's new in v6? 1) Mouse wheel sensitivity (number of steps up or down) is no longer a thing. Just move the mouse wheel up one or more steps in a row to accelerate. Move the mouse wheel down one or more steps in a row to decelerate. 2) You can again navigate the inventory, turn pages, numbered dials and move objects you are holding back and forth by using Parry/Manipulate plus the mouse wheel. Please pay attention to the configuration. ------------------------------------ ADJUST PLAYER SPEED WITH THE MOUSE WHEEL v6.0 Credits: Obsttorte, snatcher. Description: Err... adjust player speed with mouse wheel? Topic: Adjust player speed with mouse wheel Installation and execution: Download AutoHotkey, install it, open Notepad, paste the below script inside, save it as TDM.ahk and double click on the file you just saved. The script will run in the background. To end the script, go to the Windows taskbar, look for a green icon with an "H", right click on it and select Exit. Configuration: Settings > Controls > Weapons: Remove mouse wheel bindings from Next Weapon and Previous Weapon (or from any other setting you may have set the mouse wheel to) Settings > Controls > General: Make sure Toggle Crouch is enabled and Always Run is disabled Settings > Controls > Movement: The Forward, Backwards, Left, Right, Run and Creep keys must match in both TDM and the script. Settings > Controls > Actions: The Parry/Manipulate key must match in both TDM and the script. Settings > Controls > Inventory: The Next Inv. Item and Prev Inv. Item must match in both TDM and the script. Recommended controls: Forward / Backward / Left / Right: W, S, A, D Run: Z Creep: C Parry/Manipulate: Right Mouse Button Next Inv. Item / Prev Inv. Item: Right Arrow, Left Arrow Known limitations and workarounds: You can move through the inventory, turn pages, numbered dials and move objects you are holding back and forth using Next / Prev Inv. Item or Parry/Manipulate + the mouse wheel. To prepare for a long jump from idle, move the mouse wheel up before executing your move. Remember the script will switch you automatically from running to walking after one second of inactivity. You cannot lean forward and switch speeds at the same time, for some reason... ; ===================================== ; Adjust player speed with mouse wheel ; ------------------------------------- ; An AutoHotkey script for The Dark Mod ; version 6.0 by Obsttorte & snatcher ; ===================================== ; ------------------------------------- ; Configure your keys below ; ------------------------------------- ; In-game movement keys key_left = a key_right = d key_forward = w key_backward = s ; In-game run and creep keys key_run = z key_creep = c ; In-game manipulate key (recommended right mouse button: RButton) key_manipulate = RButton ; In-game Next/Prev inventory keys key_next = Right key_prev = Left ; ------------------------------------- ; Do not edit anything past this point ; ------------------------------------- delay = 1000 ; delay in miliseconds between running > walking [default = 1000] speed = 0 ; init speed (-1 = creep | 0 = walk [default] | 1 = run) state = speed; counter for state switch #IfWinActive ahk_exe TheDarkModx64.exe ; run only when TDM is focused HotKey, *~%key_forward% up, keyForwardHandler return keyForwardHandler: if (speed == 1) ; we are running { sleep, delay if (!GetKeyState(key_forward) && !GetKeyState(key_backward) && !GetKeyState(key_right) && !GetKeyState(key_left)) { speed = 0 ; walk Send {%key_run% up} } } return *wheelup:: if (GetKeyState(key_manipulate)) { Send {%key_next%} } else { state += 1 if (speed == -1) ; we are creeping { speed = 0 ; walk Send {%key_creep% up} } else if (speed == 0) ; we are walking { speed = 1 ; run Send {%key_run% down} } state = 0 Sleep, 300 } return *wheeldown:: if (GetKeyState(key_manipulate)) { Send {%key_prev%} } else { state -= 1 if (speed == 0) ; we are walking { speed = -1 ; creep Send {%key_creep% down} } else if (speed == 1) ; we are running { speed = 0 ; walk Send {%key_run% up} } state = 0 Sleep, 300 } return Change-log: v6.0: You can now use as many mouse wheel steps as you like to switch speeds. You can navigate the inventory, turn pages, numbered dials and move objects you are holding back and forth by using Parry/Manipulate plus the mouse wheel. v5.0: To prevents sudden halts when running, a one-second delay has been added between the moment the player stops going forward and the script takes you automatically back to walking mode. To allow for a greater freedom of movement, the script requires to know now your backwards, right and left keys. v4.0: Altered so that when player is running and stops, you are back to walking mode. v3.0: The script only runs when TDM is in focus (tested in Win 10) v2.0: Second version by Obsttorte v1.0: First version by Obsttorte Cheers!

So, as everybody seems to have his own mapping thread, I thought about starting my own. I'm currently working on my map for the "unusual gameplay contest" and just set up a nice working elevator. I took a look one the multi-level elevator tutorial on the wiki and I think that my approach is much more easy to implement, so I thought I could describe it here. The elevator consists out of three parts: - a func_mover entity that will be our elevator-platform - the buttons that will control the elevator - a couple of waypoints, one for each floor what else do we need: a really short script, I'll go to explain further down The first step is to create an elevator-platform. This is your part . If your done with it change its classname to func mover (under entities/func/movers). Rename it to platform. (The names are for referance. Of course you can choose them as you like). The next step is to create some path_corner entities and place them, where you want your platform to stop. Be aware that the origin of the platform entity will move to the center of the bottom face of the pink block representing the path_corner. Let the platform target the path_corners. Make sure you start with "target0", then "target1" and so one. Start with the lowest path_corner and move upwards level by level. Create buttons for every floor on one of the levels. For the other you can just copy them around when we've set them up. On the buttons, you have to set three spawnargs. - target: let the buttons target the platform (so you have to insert its name here) - state_change_callback: set this to "movePlat". This is the name of the function we'll use to move the elevator - moveDir: set this to "0" for the lowest button, "1" for the next one and so one. This spawnarg controls which path_corner the platform should move to When you're done, copy the buttons to where else you'll need them. Ok, that's the setup in Dark Radiant. Now everything that's is needed is a script. And here it is. void movePlat(entity button,boolean bOpen,boolean bLocked,boolean bInterrupted) { entity mover = button.getEntityKey("target"); entity target = mover.getEntityKey("target"+button.getKey("moveDir")); mover.moveTo(target); } The "state_change_callback" is called everytime when the state of the specific object was changed, for example if a button is pressed. The function receives four arguments, of which we will only need the first one. The entity that we get here is the one who has called the script. In this case, the button we have pressed. Now what does the code do. The first line brings us the entity targeted by the button. This is our platform. We need to know this as we want to make it move The second line gives us the path_corner the platform should move to. Here you can see why you should start targeting them from 0 upwards and what the "moveDir" spawnarg is used for. An example: If you push a button whichs "moveDir" spawnarg is "1", than the platform targeted by the button will move to the path_corner targeted by the platform via the spawnarg "target1". The last line is quite self-explaining. It tells the platform to move to the designated path_corner. That's it. Pro's: - short code that is used for every elevator in the map (in fact you can use it for everything that translates) - fast setup Con's: - As I didn't tested it very much I don't know any if you find some please report here What is missing: - there are no sounds set up yet (will add them as soos as possible) - AI's should not yet be able to use the elevator (dido)

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

This looks better, but still to me shouldering should swap places with toggle-grabber. Or to make it consistent with loot and tools, the body could also appear as symbol in your inventory. It clearly is the one things that sticks out in this list...

Edit: in post 5 I discovered Whisper which does this task MUCH better. So don't use vosk. Some of the info till post 5 is still relevant for subtitle editing in Kdenlive in general. I previously posted about this in a status update. To make it a bit more in-view for the future I post the info also in this topic. I recently figured out how to make subtitles work for missions following this wiki guide: https://wiki.thedarkmod.com/index.php?title=Subtitles You can type in the subtitle-text manually either in the .subs or .srt files (in a text-editor) or use an video editor for that (recomended for .srt). What is also possible on some advanced editors including the free and open source multiplatform (Windows, Linux and Intel-Mac) Kdenlive editor is to auto generate the subtitle text for you from the audio or video file. You can then export to an .srt file that works directly in tdm. If you want to use the subs files for shorter sentences, you can just copy text from the .srt files. In Kdenlive you can install speech to text libraries from VOSK. For this to work you have to download and install Python. Info how to do the process of installation and usage can be seen in the following video (6.5 minutes): To sum it up: Configure first time: Install Python. (on Windows) During setup, you have to select Advanced Options and there mark Add Python to environment variables (super important!). In Kdenlive go to menu settings, click on configure Kdenlive. In that configure window, click in the left menu on Speech to text. There you click on the link to download speech models. On the website ( https://alphacephei.com/vosk/models ) you can click on a model download link, but keep the click pressed and move your mouse with the link to the configure Kdenlive window. Kdenlive then asks to install the model from url. vosk-model-en-us-0.22-lgraph is probably decent for most use cases. but you can install and test them all. To use it: First load an audio or video file into the view by dragging the file in one of the audio or video bars at the bottom (video: v1, v2 or audio: a1, a2). Click on menu Project > Subtitles > Edit Subtitle tool. You see an extra Subtitles bar on top. Now you select the audio or video file (it is sellected when it is outlined with an orange border) in the specific bar and then click on menu Project > Subtitles > Speech recognition. In the Speech recognition dialog, you select the correct language model and choose option Selected clip. After generation, you can preview the generated subtitles via the top right window. Make sure it is at starter position for playback. Using an audio file, you see a black background with the subtitles on top. Now you can tweek the position and edit the text directly in the Subtitles bar. This takes up the most time. Unfortunatelly the generation is not flawless, so you have to correct some words. Tweeking the subtitles for Requiem took me hours, becouse I wanted them to line up differently. Usually the subtitles are not generated as full senteces. This looks sloppy. If you want to add subtitles quickly without spending much time on it, it can be done this way. If you want to do it right, it still takes a lot of time in my experience. To export to .srt is shown in the following video: Although actually it's just one step: Click on menu Project > Subtitles > Export subtitle file. Alternativelly you can just save the kdenlive project and then the srt is exported as well. Every save will update the srt file. I might create a wiki article about it later. Kdenlive edit window:

I get that and full disclosure: I did not read the full thread, it's just too much! I was absent in recent months, so I missed all of this. That makes a lot of sense. Although, to solve this, one could communicate via audio cue ("uh uh") that no use-type-interaction is available for that entity. Anyway, there is an incredibly easy way to solve the inconsistency while staying true to the original control scheme and that is to simply swap shouldering and grabber. Entity type Short Press Long Press ...Release Button Junk Grabber Nothing Nothing Food Grabber Eat Nothing Loot Pick-up Nothing Nothing Bodies Grabber Shoulder Nothing Lights Grabber Exstinguish Nothing Tools Inventory Nothing Nothing This way, every interaction that was originally "frob + use" (shouldering, eat, exstinguish) will the become long-press-frob. So, the long-press simply becomes a shorthand for special action, nice and clean. While I do love the hold-type-grabber to death, I'd be willing to sacrifice it for a consistent control-scheme. (@stgatilov @Daft Mugi) Right now, we have this weird mixture of hold-type- and toggle-type-grabber that I guarantee you, will confuse new players (and streamers). I say, either fully embrace the lovely new hold-type-grabber (which I am still all for) or drop it completely.

The devs didn't title this thread, and @datiswous said they're attempting to mislead people by using Russell's name and a retro style to make it resemble Thief, which is cynical. I grew up on forums like I'm sure anyone who likes a game from '98 did. I actually left the Discord immediately after joining it because it was more off-topic doom-posting than anything relevant to the mod. I thought the forums might be better, but it's mostly just grown men yelling at clouds and telling strangers how mature they are, and a few brave souls actually developing anything. Depressing place, I'll just stick to enjoying new missions every 6 months without an account.

Here is an alternative way to simplify extinguishing candles and shouldering bodies. Player can double-press / double-click frob button to do a mixed frob + use action. The test build is available in tdm_installer as "test-frob-stgatilov". Attached the source code patch too: FrobUse_By_DoubleClick.patch The original TDM controls are left unchanged. The difference starts only when double-click is registered (which unfortunately can happen accidentally). Also, the double-click action always continues the single-click action. So when you grab a body/candle, the single-click action happens immediately: there is no need to delay it. The maximum time between double-clicks is controlled by cvar in_doubleClickDelay, default is 200 ms. In principle, you can set it to zero to return to the old behavior: then double-clicks won't be registered. Here is how it works internally. There is an utility class which tracks held buttons (which are called "impulses" --- Doom 3 has too few "buttons"). I have extended it to also register double-click. So whenever player clicks frob and this is registered as double-click, then: If there is nothing grabbed, then do ordinary "frob" to grab item (this allows to double-click on already grabbed item). If there is nothing grabbed now, then fall back to normal single-click frob (this happens for ungrabable stuff like doors). If there is something grabbed, then "use" it (that's the main part: it shoulders/extinguished/eats the thing). Unless we have a body shouldered, release currently grabbed item (we want to ungrab extinguished candle). And there is also a special case: If there is something equipped at the moment of double-click, the just "use" it instead of anything else (this allows to unshoulder body by double-click).

True, but, 1. this thread is called "Western stealth FPS with Stephen Russell", and, 2. nothing you said changes anything for me. The gameplay still doesn't look like something I'd enjoy. And, if you really think this forum is cynical, then you don't visit forums much. Actually, the majority of the users are are pretty mature, unlike in other forums.

The problem comes when the mouse leaves the window. For example, if you start dragging the 3D view to turn left and your mouse gets all the way to the left side of the window, you won't be able to keep turning left. In order to turn left infinitely, the mouse pointer has to get snapped back to give you room to keep moving the cursor left.

Thanks: Really sounds like that bug must be the case and what I'm experiencing. Question is if we can use any workarounds on DR's end, which like you said is itself very questionable. I think there would be one way actually: What if DR didn't require cursor wrapping at all? Just translate mouse movement as it happens and don't care where the mouse pointer is located! If the flag is available snap the pointer to the center of the windows / screen for sanity's sake, but if not let it go everywhere without translating the view based on it. At worst this could be done by comparing the mouse movement only between every two frames / ticks, instead of caring about the pointer's start position and expecting it to be in the center?