Search the Community

Stokesay Castle, one of the best-preserved fortified manor houses in England and the British Isles in general. Rather than remain an original castle or castle ruin, or completely converted into a mansion, manor house, chateau, or romantic folly, this older rural castle was converted into a traditional fortified manor house in the early modern era and hadn't really changed its nature throughout the centuries. I feel this is a very good inspiration for TDM, given the style of architecture in TDM's fictional universe. https://commons.wikimedia.org/wiki/Category:Stokesay_Castle https://commons.wikimedia.org/wiki/Category:Stokesay_Castle_(interior) https://www.geograph.org.uk/snippet/6359 https://www.geograph.org.uk/snippet/4859 Loads and loads of great photos behind these links, so don't think these are the only interesting ones I could share. There's a huge amount of interesting details in this fortified manor house.

No, it's a TDM asset called sparks.

TDM conveniently has a spawn_arg to add sound effects when an item breaks (snd_broken), but this causes the game to crash unfortunately, so I had to add the sound separately.

Hello Petike the Taffer (MMM ? how to implement this blue petike the taffer tableaux - so you get a message ?! ) nice to hear you´re back in town if you are still holding your hands on the TDM-Youtube Channel i´d like to ask you some questions about it : ( some ideas to give it a better appearance ) and about offering some vids I made of " Hazard-Pay " maybe by PM ( because of Musik i added and if it´s possible to implement them to the TDM-Youtube Channel

Yes, definitely needs to be distinguishable. Clear glass with light bulb visible would be the best way: You know that if you see clear glass and the bulb inside you can shoot it. The distinction isn't always possible to make without first trying it out though... paintings are the best example, you always need to get close to see if a painting can be looted. As for players learning about this, we should add those lights to the tutorial level where the basics of TDM are taught: In one of the hallways we'd have examples with the message "solid lights can't be shot, but ones with fragile glass and a lightbulb can be broken with broadhead arrows", the player is given arrows and can shoot at different lamps to compare. As for explosive barrels those would be cool to have too! In their case they should already be doable with a script, just that no one's ever done them: Remove the barrel, spawn the same explosion as the fire arrow or mine, and some temporary lasting physical debris if possible. Breakable lights would need support added to the builtin spawnfunc.

That's why last night I went with the idea of making new lamps with this mechanic: They should have transparent clear glass casing and show the light bulb inside, making it obvious they're different and can be shot. Something like this should make them easy to distinguish: Indeed I run into the painting problem myself: I always check every painting to see if it highlights and can be looted. Then again it's the same with doors in some FM's, which don't use a special door handle to make it clear that's a decorative door and not one you can go through.

Hello again I just want you guys to double check fms because i think files got mixed up Localization Packs: Vengeance for a Thief Part 1 its says it is for a pawn in the game localization pack String table English (iso-8859-1) for: Vengeance for a Thief Part 1: A Pawn in the Game But it is under VFAT1: The Angel's Tear download I have looked in my fm archieve and i foun fm named The Accountant: Part 1 - A Noble Home (prologue) It is not listed in download section. any idea about this one ?? is it a part of accountant campaign ? Is it obsolete ? or it is missed ? Also i came across Samhain Night on Bone Hill By PranQster Version: 0.9.7 Back again to version matter. Maybe it is not important to keep versions, maybe it is. For me it is important as i am updating my archive of fms so it is nice to just see version straight away than looking in every pk4 file for it. Also it would be very helpful just to add in download section beside released date, update date as well Maybe Sir You just like me. You look but you can not see TDM Fan Mission Lists: Released and Upcoming Thread https://wiki.thedarkmod.com/index.php?title=Fan_Missions_for_The_Dark_Mod

I couldn't help thinking of another realism related suggestion, don't know if it was discussed before but it seemed like an interesting idea. If this were to be changed on existing lights by default, it would have minor gameplay implications, but the sort that make missions easier in a fair way. So... electric lights: Like the real ones of the era, they're implied to use incandescent light bulbs... the kind that in reality will explore and shatter upon the smallest impact, and which like real lamps are encased in glass or paper. In any realistic scenario, shooting a broadhead arrow at a lamp or even throwing a rock at it would cause it to go through the glass and break the light bulb inside. Is it wrong to imagine TDM emulating this behavior as a gameplay mechanic? Just as you can shoot water arrows at flame based lights to put them out, you'd shoot broadhead arrows at electric lights to disable them... you must however hit the glass precisely, there's no room for error and it must be a perfect shot. As a way to compensate for the benefit, AI can treat this as suspicious and become alert if seeing or hearing a lamp break, or finding a broken lamp at any time if that's deemed to provide better balance. A technical look at implementing this: Just as broadhead arrows can go and stick through small soft objects such as books, they should do the same if you hit the glass material on a lamp, while of course still bouncing off if you hit metal: Lamp glass would need a special material flag that sends a signal to the entity upon collisions but allows arrows to go through, unlike glass in other parts of the world which is meant to act as solid and changing that everywhere would break a lot of things. When pierced by an arrow, the lamp should immediately turn itself off while playing a broken glass sound and spawning a few glass particles. The glass material should be hidden if the model is a transparent surface, or replaced with a broken glass texture in case the glass is painted on a lamp model without an interior... obviously this would be done by defining a broken skin for the entity to switch to. This does imply a few complexities which should be manageable: Existing lamps supporting this behavior will need new skins and in a few cases new textures, the def must include a new skin variable similar to the lit / unlit skins in this case a broken skin. Any electric light may be connected to a light switch, we don't want toggling the switch to bring the light bulb back to life... as such a flag to permanently disable triggering the light from that point on would be required. For special purposes such as scripted events to reset the world, we should allow an event to unbreak lamps, setting their state back to being lit / unlit while re-enabling trigger toggling. What do you think about this idea and who else wants it? Would it be worth the trouble to try and implement? If so should it only be done for new lights or as a separate entity definition of existing ones, or would the change be welcome retroactively for existing missions without players and FM authors alike feeling it makes them too easy?

I manually integrated and tested your PR. There is good news and bad news: The good news is that when running with the "GDK_BACKEND=x11" flag, using the clipper tool no longer breaks the window forcing me to restart DR afterward, the model / entity viewer no longer experiences the issue either. The bad news is that flag is still required, every viewport retains the problem if running Radiant in Wayland mode, we still have a big problem Linux users will increasingly run into as distros adopt it (KDE Plasma 6 now uses Wayland by default). So please integrate the PR if it doesn't break anything, it makes life much easier in the meantime! But this should remain open until either DR or WxWidgets or Wayland solve the core issue that exists when running in native mode.

I always loved the "connections" theme and I think it is very fitting to celebrate TDM. It's a shame we can't have 4 polls per thread because then my proposal would be to have free-for-all with a "connections"-rating added that evaluates how well the mission integrates into or expands upon the existing lore.

Oh my gosh, thank you for this! After reading what you just said, I realized I've in fact noticed the same thing in another program, but assumed it must be something completely unrelated: I've been working on creasing a CPU based voxel raytracing engine in Python, for which I settled with using PyGame. When the time came to implement first person camera control using the mouse, I noticed it did not work initially... however if I told my code to hide the mouse pointer first, locking it in the center of the window started working. It must be the same thing here in some form, Wayland likely has some very particular expectation on how the mouse pointer must be set in order to be locked. In fact just a few days ago, I tried a virtual worlds software called Vircadia / Overte again to see how it's been progressing. I activated mouse look mode and guess what happened: The exact same behavior of the view spinning endlessly as the cursor drifts away from the center due to lack of locking. So it's clearly happening to many things and not just GTK / WxWidgets related... but no all of them, most games (including TDM itself) work perfectly fine and mouse control never breaks. I'll try your solution later and mention the results, likely tomorrow as it's late now and I need to head off. If it works that would be incredible! At least as a workaround, we could simply not hide the cursor on Wayland, which will look ugly but at least allow using DR without needing hacks until they can solve whatever is happening on their end. Also Plasma 6 was just released, my distribution (Manjaro) will likely be getting it a couple of weeks or at most months from now. I'm curious how that will affect it: Hopefully it won't make the issue worse, but just in case I'd be happy to have a solution in Radiant before then.

the firts thing i think of ! in the wiki the " available TDM-Missions " list shows contest relations , but i think it´s not mentioned for every Mission that has partaken on a contest ( ?!?) if trudnicki has found another resource with full listing : please report ! P.S. !!! there´s the : Fan Mission Contests page on wiki

I've been feeling the itch to start mapping again, and I'd like to pick up my stalled WIP for the next FM building off my first one. If we end up with lighter contest requirements I'd run with this for the fun of participating. If my FM doesn't end up meeting contest criteria I'll still keep the October timeframe as a goal though. A mild requirement like "include a nod to a classic Thief/TDM map somewhere in your mission" sounds like a nice way to keep participation up without going full free-for-all.

Noticed all of these only because I played TDM by doing the opposite of stealth to practice swordfights. None of these bugs appeared as long as I played the game stealthily. Should also note that I used Snatcher's Core Essentials @snatcher on and off, but your mod does not alter the AI anyway, correct? Bugs happened both ways. 1) AI freezes in combat - https://bugs.thedarkmod.com/view.php?id=6371 It happens a lot with auto-parry disabled. It never happened with auto-parry enabled. It never happened with some guards, while it happened many times with specific guards. They unfreeze when player dies, or when AI is forced to re-equip the melee when player returned from a spot that usually causes them to throw rocks. Also experienced behavior of them only slowly walking towards me at the pace of "hunched sneakily searching mode", attacking once finally in proximity. 2) AI may collectively lose the ability to hear any of the players noise caused by footsteps / landing. Still unsure of what causes this, but Lockner Manor has a good layout to get to the result. Just follow the right-most path and repeat the process of winning sword-fights with City Watch, and then jump around the next guard to see if they can hear you. If they can not hear you, likely nobody can. If they still can, just combat them too and you will likely have deaf AI by the time you have dealt with the 3 Watch Guards outside. In my experience, when they hear the death scream well enough to run to its location or start searching - the deafening did not work. 3) Helmeted AI does not react to (nor hear) players overhead sword strikes made directly on helmet, stealthily from behind. Not sure if the same issue as deaf AI bug, but happened at least once while it was active. (Lockner Manor) 4) (Moor?) AI may lose the ability to hear AND see player after nearby swordfights and after two slashes to bloody their face. (I may have also Moss Arrowed them to face). Any sword strikes I make simply go through their model with no audio of impact. Collision still gets player detected. (A Good Neighbor) 5) Crash to desktop when archer puts bow away to take out melee (while I may have collided with them on staircase). (Lockner Manor) 6) Crash to desktop when I shot a shortsword-wielding charging Noble. Sound of a deflected arrow played (same that you hear when shooting a stone wall), when I expected a flesh-hitting sound. (A Good Neighbor) 7?) Sometimes AI says "Ow that hurt" merely because I block their strikes. - Is this an intended feature? Do they take actual damage too? Anyway, I didn't find mentions about many of these issues. Reporting aside, if you want me to experiment with something or find ways to replicate - I don't mind updating this thread, as I plan to mess around with sword-fights anyway. Just posted this initial version should anyone want to chime in with similar experiences, and I wanted to know if some of these bugs could be mission-, or mod-specific. Maybe caused by much or unfortunately timed quicksaving / loading?

I like proposal 2 because I have thought of doing that many times, but realistically, just allowing people to do whatever they want seems less restrictive, so more people might join in. Besides, if someone still wants to reinterpret a T1 or T3 mission, well, nobody is stopping them. Perhaps "include a nod to a classic Thief/TDM map somewhere in your mission" could be a milder requirement. Campaigns just take too much time to make.

Since I'm bored and haven't posted in a while and yet still finished Thief 4 a few times, I feel compelled to post. In response to a number of observations @Rio_Walker made: Seeing your hands and all the animations newGarrett would do was fun... at first. But given all the looting and environmental interactions the game has it really did slow things down a lot, especially when the game would occasionally realign the player just perfectly before playing an animation to open a drawer. If they had an option to disable these animations or speed them up significantly I'd have been happy. I've played using the Custom difficulty with the option to disable focus and the experience is kinda mixed. While it does make things a bit more traditional without the superpower ability to find loot more easily, it does seem like the game is designed very much for focus and disabling it can hide things you never even knew were present. If it weren't for the focus for example, I would never have noticed the "special" candles hidden around the city that talk when you light them. This game reminds me of a movie that has been reshot several times with footage from separate reshoots blended together with bad editing. It's painfully clear the story has been chopped and changed over the many years of its development and there's assets in the game that clearly had greater importance in a previous iteration but for which their plot points were cut. The most obvious example is the automatons. There's a dude who provides missions on obtaining pieces for one he's building, but apart from that there's also signs in other areas they had more importance (e.g. you see rooms full of them when going up an elevator, the Baron has disassembled ones on tables in his cutscene, etc.) Some plot elements just feel not fleshed out because they had to cobble together something to create this Frankenstein's monster of a game from so many elements. The ending sucks and is incredibly abrupt. Do we even know what the deal is with that half-built ship? Probably another abandoned plot point. With all of its problems, I still kinda like it in so far as its general gameplay. But it doesn't have the longevity of something like TDM or the classic Thief games especially with all the user missions available for them. Oh well, maybe I'm just pining for what it could have been in the hands of a better developer.

I intend to update the FM if any bugs/errors are found or updates to TDM necessitate it, but you're correct that I'm not updating it for content going forwards. The ambient tracks I used in this FM were a little bit busier than I normally would use, mostly because I knew this was going to be a very short FM going in and I had to deliver an atmosphere somewhat quickly. Rest assured that my next FM is going to be a bit less busy and more varied in terms of ambience. Don't worry, I don't view this as a major failing or anything. I don't really find Lovecraft's works "scary" in a traditional sense, if I wanted this to be overtly scary I likely would have gone way over the top and diverted too heavily from the source material. I've always enjoyed Lovecraft's works for their ominous tone, ambience, and mystery, which it seems from your feedback I more or less achieved. I'm glad you enjoyed my FM, Arrow, and thanks for the feedback!

Yes please: I've wanted something like this for a long time! One thing that always makes me sad in TDM is when a mission just... abruptly ends: Obviously every FM has an ending, but I never liked just transitioning to a stats screen as if nothing you did in the world mattered. I'd absolutely love a debriefing GUI just like the briefing one, where you can either have text or an image slideshow with music and voice-over which would be even better! Maybe some old FM's can be updated to use this too, I'd totally replay them just for that. One additional idea: Since FM's with multiple endings are something I always wished for and would love to do myself, support for multiple debriefing GUI's would be ideal, so the kinds of objectives you completed can execute a different one or skip / add certain passages. Absolutely hope the team can consider this, should be just a GUI execution hook to implement it so why not

On wikipage https://wiki.thedarkmod.com/index.php?title=Tdm_mapsequence.txt it states: and in the example code: It seems it's possible to define something like this: Mission 1: tunnel street prison Mission 2: lake warehouse1 Mission 3: warehouse2 ending where tunnel, street and prison are different map files and part of the first mission in a campaign of 3 missions. So since it's not fully supported, I wonder what is actually supported by tdm.

Collect them all in a testmap and then run an automation script that moves trough the map, making screenshots?

A visually breaking change is planned for 2.13 (6354). Environment mapping is used when material contains a stage like this: { blend add cubeMap env/gen3 texgen reflect } Historically, there are two separate shaders for this case: one if the material has bumpmapping, and one if it does not. Note that if the material has diffuse or specular stage, then bumpmap is added implicitly. The shader with bumpmap was apparently "tweaked" by someone in TDM and got several major differences: it has fresnel term output color is tonemapped to [0..1] range using X / (1 + X) the color multiplier is hardcoded to (0.4, 0.4, 0.4) I'd like to delete all of these differences and restore the same behavior as in non-bumpmapped case. It is also the same behavior which is used in both cases in Doom 3 BFG (and supposedly in Doom 3 too). Speaking of points 1 and 2, nobody will notice the difference except in rare corner cases. The point 3 however is serious. It is also the main reason behind the change. Right now nobody can tweak the intensity of environment mapping: if you try to set red/green/blue/rgb, these settings are simply ignored. Now the problem is that the intensity of most environment mapping materials will change. In core files I see text like this (stainglass_saint_01) : { blend add maskalpha cubeMap env/gen3 // tone down the reflection a bit //I see no evidence that these values do anything red Parm0 * 0.2 green Parm1 * 0.2 blue Parm2 * 0.2 texgen reflect } Since the default parameter was 0.4, after the change this material will get 2x less intensity. The situation is even worse if rgb multiplier is not specified, since then it will change from 0.4 to 1.0, i.e. envmapping will become 2.5 times brighter. I can probably collect the list of all materials using environment mapping, but I'm not sure I'll be able to check them all one by one. Perhaps I can delete existing rgb settings, blindly set "rgb 0.4" and hope for the best.

That would be another good method. The one I used was easier for me, given that I was also supporting a SFW difficulty level where she is already dressed before reaching the attic. Thanks. No animation available for that either, so all done with cut-scene fakery and video editing. Glad you enjoyed a bit of sparks with those. Although I can't take any credit for the idea of dress mannequins with human hands... you'll see them IRL at any mall. But the implementation in TDM... therein the magic: It's 11pm here, and I'm off. Thanks for chatting.

I played it twice. Maybe it's because I finished first Dishonored not long before playing for the second time, with clean hands, and sought another thrill of picking open a safe while Target is roaming the same room. The first time, I did run around killing guards, but eventually I couldn't get past a mission and quit. The second time, I just threw my hat in the wind and used WeMod. Once you're invisible to everything, ghosting isn't an issue =| Are there some cool tricks in this game? Yeah. I liked seeing my hands (a real kink at this point) fumble for a hidden switch, or smoothly yoink purses off guards. Focus was cheating, really, but I didn't hate it exactly. I just thought that this is Tomb Raider reboot/Arkham all over again. Hub? Nice, shame nothing we collect mean anything. Vendors out in the "open"? Hey, that feels like I'm actually in that world. What I hated was the ending. Or that Chase sequence. Loading screens masked as "cutscenes"? Ugh... The plot holes not helping either. But the worst thing are "Hidden" areas in the overworld. I think even with the guide, I haven't found all of them. But at least I finished it.

I don't know if it's related, but, I noticed since a few TDM versions that some text in readables in some missions is cut off. IIRC, also in the Training Mission. Also, the two books in JackFarmer's screenshots aren't the same height. The lower one is way shorter than the upper one.

Well some good news for those who have the 2080 ti and no money to upgrade to the 4000 series. Alan Wake 2 runs at > 70 fps with the FSR3 mod on it at high at 4K need to set "m_bLensDistortion": false, in AppData\Remedy\Renderer.ini to get rid of some ghosting effect on the main char when moving, but other than that it looks quite nice. the FSR3 mod is here -> https://www.nexusmods.com/site/mods/738 an alternative is this mod -> https://www.nexusmods.com/site/mods/757 which also supports intels xee models. there is also one for slightly older AMD cards but it is a paid mod and the author got himself into quite a shitstorm due to some rude behaviour so i wont link it here, look for LukeFZ if you really must. The other FSR3 mods require an RTX or Xee card so for nvidia everything from a 20 series and 30 series. The LukeFZ mod also supports the older GTX 10 series. One thing to note is that your card must be able to handle atleast 30 FPS minimum else it will look like crap and if movement is laggy without it it will still be laggy with framegen (this also applies to cards that support it natively like the 40 series).