Search the Community

Aberconwy House, one of the best-preserved medieval houses in Wales, originating in the 14th century. Includes a house museum. If you happen to visit Wales, you can find it on 2 Castle Street in the town of Conwy. National Trust website for Aberconwy House Visit Wales website for Aberconwy House Geograph.co.uk entries for Aberconwy House Wikimedia Commons entries for Aberconwy House Conwy has several other preserved historical houses and buildings from earlier centuries. These include the later Tudor era Plas Mawr, which also has a house museum (and which I've already featured in this thread years earlier), and there's also the famous 'Smallest House in Great Britain' and plenty of preserved fortification monuments. Speaking of... The 'Smallest House in Great Britain', in Conwy, a tourist attraction that's more on the cheesy side due to its notoriety/record, but is still a nice example of a period house centuries old, that was built in the spirit of "How can our ingenuity provide us with a small house and lodgings even in a narrow, cramped part of the street ?" vernacular ingenuity. Official website for the Smallest House Visit Conwy website for the Smallest House Geograph.co.uk entries for the Smallest House Wikimedia Commons entries for the Smallest House Various narrow houses from around the world English Heritage website for the Medieval Merchant's House in Southampton Geograph.co.uk entries for the Medieval Merchant's House in Southampton Wikimedia Commons entries for the Medieval Merchant's House in Southampton Combine these photos with the medieval early modern housing and market hall photos from my previous post, and you'll have plenty of inspiration on how to furnish rural houses and townhouses in TDM's setting.

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

Ah, pity I wasn't reading the forums back in February. I'm fond of that game, along with Bugbear's other early title, Rally Trophy. I was never too good at FlatOut, but it was always a hoot to play.

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 revisited this issue and might have had a breakthrough. I noticed that when using the clipper my cursor wasn't changing, and afterwards when the cursor was no longer hidden when the dragging problem starts happening. If I take out the code that is supposed to change the mouse cursor when activating the clipper, the drag behavior remains correct during and after using the clipper tool. If I remember correctly from last time I went down this rabbit hole, Wayland has restrictions on pointer locking and I think it was only allowed while the pointer is hidden. I'm guessing something with changing the cursor is failing and then it doesn't get hidden before the pointer lock happens, causing Wayland to reject the pointer lock request. And when the pointer doesn't get locked, the math to calculate the drag amount goes all wonky. @MirceaKitsuneor others, if you'd like to try a quick and dirty workaround, find the void OrthoView::setCursorType(CursorType type) function and put a return statement on the first line so it doesn't actually change the cursor. I'll see if I can figure out what's actually going wrong when setting the cursors so we can make a proper fix.

In principle I like the idea of community campaign building. But the official campaign itself never really captured my imagination, not to mention it'd be hard for people to have an idea of where it's going, much less making it cohere. I scripted a Dark Mod campaign meant to introduce the districts, factions, and lore that does capture my imagination. But I'm not in any real position to ask people to build for it, and also there's still the problem that people may have different visions for it that may not cohere well. As for the "connecting mission", that might be interesting... But I'd reframe it a little, not that it has to be connecting per se, but you know, a hero or even another character from some FM in an adjacent setting alongside (or before or after) an existing FM, kind of like what Rozencranz and Guildenstern did for Hamlet, if you know about that. I think it's better to have it more open ended how an author wants to build off an existing FM than only connecting two FMs per se. That might be a really interesting theme to see play out.

I think we can use this script (mod) to extract all textures with specular maps, and if possible, create a map for testing. Unfortunately, I'm not yet familiar with the editor to help with this. I came here because I plan to work on textures more thoroughly, and I'm currently reading the wiki on texturing issues. In general, I'm interested in this topic. Maybe I'm not competent at all, but is it possible to make a texture have a constant reflection (yes/no) and a variable with a setting in the editor/accompanying document (?) that controls the intensity? For example, the same object/texture can behave differently on different maps.

Is there a reason why you post with white background and black letters? Because it is really hard on the eyes with a dark setting!

They are a riff on historic mushroom-style "linen smoothers", as this article sketches: http://www.oldandinteresting.com/antique-irons-smoothers-mangles.aspx The gold color hints at heavy brass. Bonus in the NSFW difficulty setting: One is also seen outside a laundry setting, for its *snort* suggestive shape.

Try the following: set the npcs' reaction to noise higher via the console by entering tdm_ai_sndvol 2 or 3. i recommend to use not higher than 3, cause if the value is too high, the npcs will hear you from much further away, which could brake the game. with this setting you need to move slowly more often and running around like a beheaded chick is no more. it somehow works for me. maybe u want it harder, then make the movement a bit slower with these settings. e.g: pm_mantle_fastMediumObstacleHeight 0 pm_fastLowObstacles 0 pm_creepmod 0.75 pm_runmod 2.00 pm_walkspeed 60 pm_mantle_push_msecs 1200 pm_mantle_hang_msecs 1125 pm_mantle_pushNonCrouched_msecs 825 hf

I found this file: mainmenu_settings_gameplay.gui It contains the following settings: choiceDef AIVision { rect SETTINGS_X_OFFSET, 0, 80, MM_LINE_H choices "#str_07323" // Nearly Blind;Forgiving;Challenging;Hardcore values "0;1;2;3" } Can you please help me find where the parameters choices and values are referenced? Edited: Maybe I shouldn't have rushed... I was able to register a new difficulty setting using english.lang But I still can’t find where they are addressed for difficulty levels(

I'm looking for the setting that controls the number of difficulty levels in the options menu. The current "hardcore" setting is not challenging enough for me, and I'd like to make it more difficult, like this one for thief. I can edit the Darkmod.cfg file and would like to know if I can create a separate *.pk4 file with this file, removing everything unnecessary except the parameters I need. Will the game load the default settings from the game root and the additional data from my file? Of course, it would be better if you could tell me how to create an additional difficulty setting. I've searched through all the archives and couldn't find what I need. Thank you for your help.

@snatcher I understand that when you feel your work doesn't live up to your goals that you don't want it out in the wild advertising your own perceived shortcomings but that leads to a troubling dilemma of authors who are never satisfied with their work offering fleeting access to their in-progress designs then rescinding them or allowing them to be lost. When I was a member of Doom3world forums, I would often see members do interesting experiments and sometimes that work would languish until someone new would examine it and pickup the torch. This seemed like a perfectly viable system until Doom3world was killed by spambots and countless projects and conceptual works were lost. I guess what I am trying to say is that mods don't need to be perfect to be valuable. If they contain some grain of a useable feature they might be adapted by mission authors in custom scenarios. They might offer instructive details that others trying to achieve the same results can examine. It would be great if known compelling works were kept somewhere safe other than via forum attachments and temporary file sharing sites. I suppose we used to collect such things in our internal SVN for safe keeping but even that isn't always viable. If folks would rather not post beta or incomplete mods to TDM's Moddb page, perhaps they would consider creating their own Moddb page or allow them to be added to my page for safe keeping. Please don't look at this as some sort of pressure campaign or anything. I fully understand anyone not willing to put their name next to something they aren't fully happy with. As a general proviso, ( if possible \ permitted ) I just want to prevent the loss of some valuable investigations and formative works. The end of Doom3world was a digital apocalypse similar to the death of photobucket. It is one of my greatest fears that TDM will become a digital memory with only the skeletons of old forum threads at the wayback archive site.

Yeah, that's two separate things going on. The Builders will eventually flip out if one of them is crushed by the elevator and they spot his corpse, but the other bug was legitimately a bug. The location separators between different areas have a sound loss associated with them so that a sound occurring on one side of a doorway is heard by AI at, say, 10 or 15 dB quieter. One of these was set to a negative sound loss, ie, it amplified the sound turning it into a huge megaphone that blasted noise all over the level. It wasn't just setting off the Builders but also all of the watchmen, the apartment landlord, and often the undead. To make it worse, the bug only had this effect on Windows. I'm a Linux user so it took me forever to figure out what was happening.

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

Sorry for digging this out, but, one thing I always wondered: Shouldn't a gamma value of 1 in Dark Mod give you the best experience when you're using a monitor with a gamma value close to 2.2 (which I think is the optimum in terms of realistic colour reproduction)? I have a monitor with very good out of the box colour reproduction, and almost ideal gamma. Yet I have to turn down the in-game gamma to about 0.9 to get a good result. I must say though that I prefer it darker than what the average player probably has, so, that might be the problem here. Still, I usually have very good result leaving the gamma on default setting in most games, which is probably calibrated towards monitors which display ideal gamma.

Looks very good, sounds very good and has a great atmosphere! Took me more than one hour to complete on Easy difficulty until I stumbled over the The last two scripted scenes were great and added perfectly to the LC setting. Good job!

Not to start a discussion on this but just for correctness, that is not true at all, unless you are using a really low polygon shadow mesh, if you see a pixelated shadow with stencil, then that is a shadow map or a mix of both stencil and shadow maps. Stencil shadows are crisp and well defined, they have no resolution setting or quality setting (besides turning off shadows), because they are literally geometry (triangles) being projected unto surfaces, while shadow maps are pixels (textures) so you can control how sharp they are. TDM has a mix shadow system, where some effects even in stencil shadow mode, will use shadow maps, for example volumetric lights shadows, are shadow maps. Stencil shadows Shadow maps

We are proud to announce the release of: The Dark Mod 2.12 ! The 2.12 development cycle introduced many large code overhaul projects. Most of these were to lay the groundwork for future fixes and optimizations. The final release is yet another leap in performance over the already impressive 2.10 and 2.11 releases. A full changelog can be viewed here, but some highlights include: The Dark Mod 2.12 is a major step forward for mission designers! The culling system has been extensively overhauled to ensure that your CPU and GPU are not wasting resources rendering unseen geometry, lights, and shadows. Some of our best map optimization experts have achieved similar performance gains to what this new culling system does but it is a rare skill and we have even managed to improve performance on missions that were generally regarded as “well optimized”. Mission authors both new and old can follow standard mapping practices with no need to dive deep into sophisticated optimization techniques even for some pretty challenging scenarios such as wide open areas and long views. Players will immediately notice many missions that have made their system struggle with FPS now may be running much more smoothly! Smoother controls for players! Also during the 2.12 development cycle, work has been done to make controls more seamless and accessible. Frob can now use hold or click actions to use items. Once you get used to the mechanic, it will be hard to go back to using a separate “use key”. Mantling is now smoother, faster, and less prone to cause the player to clip through geometry. Leaning is now more subtle and less prone to cause motion sickness. To reduce the tedium of shuffling knocked out AI around to search for loot, you can now configure TDM to automatically loot any frobbed AI. A special thanks must go out to community member Geep! Over the course of 2.12 development, Geep has created subtitles for nearly all AI barks along with developing testing tools and procedures for this gargantuan task! You can see these changes in action by changing the Subtitles setting to “On” ( rather than “Story” ) on the Audio settings page. Geep also provided substantial feedback for our GUI and subtitle design process and edited font data to improve text quality overall. Datiswous has complimented the massive work by Geep to create AI bark subtitles by creating mission story subtitles for a large number of missions. Thank you! Turrets are now natively supported in The Dark Mod and can be paired with Security Cameras! Finally, the nasty 2.11 bug that caused AI to allow arrows to pass through them at certain angles was fixed by Joebarnin! Your assassin style play-throughs should be far less frustrating. See also, our 2.12 Feature discussions: To UPDATE, simply run the tdm_installer.exe file in your darkmod folder. Note that tdm_update.exe is no longer supported, but you can download the new installer from the Downloads page if you don’t have it yet. Please be aware that old saved games will not be compatible with 2.12, so finish any missions you might be in the middle of first! Also, some missions created prior to 2.12 may need to be updated so they will be playable in 2.12. Use the in-game mission downloader to check for updates.

For peeps coming from Windows with no desire to invest a lot of time in learning Linux and the command line (you have to anyway to a certain extend) I would advise Linux mint if you want a fixed release or Manjaro if you want it rolling. Although @revelatorhad good experience with Solus. You can already start using it now in a multi-boot setting. So you are willing to invest time into figuring out some obscure way to get it working instead of invest time in a proper solution for the future. Why do you need to compile a Windows version, instead of a Linux version? I guess you could ask someone with Windows 10 to compile it for you?

One way to do that would be to link the map with the location system. A mapper can already make a system to do that with the location scripts. Basically when the player enters a location (or a set of locations), it can trigger a script that switches out the map for one with that location highlighted. That's how Thief used to do it, and I think it's still fitting with the setting. Having a literal dot moving around the map would be much harder. I'm not sure we could do that without source code support. But It also wouldn't be as fitting to the genre. I'd be happy to see some mappers having a highlighting-map though, just for some interesting variety.

When setting r_volumetricEnable to 0, I see some light disappear and FPS increases by maybe 2-3 FPS, but does not come close to the previous values. I run on a computer with 8 CPUs and none of them goes over 50%. I tried enabling the menu setting "Frontend Acceleration" and restarting, but that seemed to make no difference. For r_volumetricEnable set to 1, I tested the following: * beta 1: 33 FPS and 24 FPS * beta 2: 32 FPS and 24 FPS * beta 3: 33 FPS and 24 FPS * beta 4: 33 FPS and 24 FPS * beta 5: 17 FPS and 9 FPS

Can you double-check and see if the performance loss also impacts beta 5. I believe that a volumetric light was added to the skylight. You can also try setting r_volumetricEnable 0 and see if performance returns to normal.

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

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