Search the Community

Fair enough, Welli. From what I have seen in videos the primary frob in Dishonored is to acquire items bodies may have and the hold frob is reserved to shouldering. Thing is developers apparently kept the hold frob to shoulder bodies even when the body has nothing of value. Consistency, I think, and to prevent unintended actions perhaps? Anyway, they prioritized one action over the other, and each action remained in its own place. The material is, what would have done the devs of these games you mention if manipulating body limbs was a key mechanic along with shouldering? Right: Absolutely terrible, imho. No fun to be found there. I learned not to bother pretty quickly.

So giving it none of those tags, but making the AI invisible, silent, non-solid, and on a team neutral to everyone would not work? Oh well, it was a horrible inelegant idea anyway.

I notice now that the sitting pose of ai is like they're leaning, but in this case there's no back to lean on. I guess there's that shining mirror plate. If you don't want it to reflect, you could remove the reflection from the material?

Horror themed fan mission - exploration of seemingly deserted keep in the middle of swamps. Spiders, undead, darkness. ----------------------------------------------------------------------------------------------------------------------------- This is the story about the fate of my family. My uncle, Ralph Mac Roberts, is the baron of a keep nestled deep within the Rahenaen marshes. It was once an important outpost tasked with guarding one of the few Builder roads that cross the marsh, but after the Inventor`s Guild built a system of nearby dams that flooded the whole land, the road closed and there was no longer anything to watch over anymore. The keep itself needed reinforcement against the raising water level and the trade routes become almost impassable, not only for the carriages but for lone couriers as well. There hadn`t been any messages coming from the keep for over a year and my father was about to assemble a caravan so he could go on an expedition to the keep himself. However, in the middle of the night before he was set to leave, a carrier pigeon landed on his windowsill. My father received the letter and read the apologies from my uncle and his family, excusing their long absence. As a way to make reparations for their extended silence, my uncle invited me to the keep to stay there for a fortnight or so. My uncle had instructed me to leave my horse three leagues away from the keep by the nearest charcoal burning hut and hike the remainder of the road on foot, as the trek through the marsh is treacherous for horses. The weather will be awful this time of year, but my father insists that I should go anyways to ensure that our relatives are okay. These plains become dreadfully deserted - to the point where you more expect to meet the dead than the living. And by the way - I think I`m lost. ----------------------------------------------------------------------------------------------------------------------------- Download link: https://1drv.ms/u/s!Aj1DVS465udZgVkXteBbr6cUxdPH Thanks: to the TDM team for great tools, and all the contributors for their assets, to betatesters: Amadeus, Bienie, Boiler's_hiss, Dragofer, Filizitas, Judith, nbohr1more, s.urfer, again to Amadeus for proofreading and text tweaks, and to all the players for their time! Few screenshots: http://forums.thedarkmod.com/topic/10003-so-what-are-you-working-on-right-now/?p=434716 http://forums.thedarkmod.com/topic/10003-so-what-are-you-working-on-right-now/?p=429558 http://forums.thedarkmod.com/topic/19886-fm-marsh-of-rahena-beta-testing/?p=434507 Enjoy! Walk-through !major spoilers! Finding a way across the marsh area: Getting inside: Bed objective: Light sources: Maps: Enemies: Room objective: Hut objective: Sealed objective: Gold: Key: Bodies:

Good catch. I fixed the .gui name, and added afterwards this brief explanation: The value here is a path to a custom video material shader. It is set at runtime by the engine, based on information the FM author provided in mainmenu_custom_defs.gui as, e.g.: #define MM_BRIEFING_VIDEO_MATERIAL_1 "video/tdm_briefing_video" (In older FMs, the video was chopped into parts, in which case the engine updates the value just-in-time. See comments in mainmenu_custom_defs.gui for details.) FYI, there is a similar system for debriefing videos.

The diffuse maps works as expected, but the shader just ignores vertexColor (and inverseVertexColor) for the bump maps and they still get applied across the whole model. For example: in this material, the grass bump appears everywhere so my dirt path has a grass bump pattern visible in it, which does not look good. textures/darkmod/map_specific/grass4_dirt_01_blend { qer_editorimage textures/darkmod/nature/grass/grass4_ed surftype15 description "grass" { blend diffusemap map textures/darkmod/nature/grass/grass4 vertexColor } { blend bumpmap map textures/darkmod/nature/grass/grass4_local vertexColor } { blend diffusemap map textures/darkmod/nature/dirt/dry_earth_muddy inverseVertexColor } { blend bumpmap map textures/darkmod/nature/dirt/dry_earth_muddy_local inverseVertexColor } } I've tried other textures with the same result. Note that this shader was made using the built in material editor in DR 3.8.

With TDM 2.06 mappers and players can use OpenAL EFX system, which is basically an open-source software replacement for systems like EAX, which, at the time, was available only for dedicated hardware by Creative. This allows us to set reverb definitions for rooms, and in my opinion, it's a game-changer for TDM FMs. If you ever played old Thief games with EAX-enabled hardware, you know what I mean. Otherwise, try playing Kingsal's Volta and the Stone with EFX On and Off to see the difference. It's a new life for game environments. The EAX reference page in the Wiki can be quite intimidating though, there are many values to tinker with. I have some basic sound recording experience, but I'm not an audio guy. The purpose of this thread is to create clear guidelines for other non-audio guys. If you're an audio guy, these values will be familiar to you, because you can find similar parameters in Reverb plugins, e.g. for Adobe Audition. (Btw. feel free to correct me whenever I'm wrong about something.) First off, your map has to use location system. EFX system needs location names, and it will define reverb per location. It also needs location separators touching visportals to make proper transition between reverb for different locations. Create 'efxs' folder in your project root folder, create a text file map_name.efx, and open it. Now, first thing EFX system needs is a version number, so every .efx file needs start with Version 1 (I don't think any other number works). So, a typical .efx file with room definitions looks like this: Version 1 reverb "location1_name_here" { values here } reverb "location2_name_here" { values here }etc. And that's it. It seems like you don't need to include every parameter you see in the Wiki reference. Some variables don't do much or hardly do anything. Even if you delete something, the system will use the default value. You can have an empty set like above, and you won't break anything. You can also change the order of parameters, e.g. if you have your own workflow. Even then, making efx presets for all your locations manually can be really time-consuming. I bet a lot of mappers will want to make this as fast as possible, so they can move to more important things. That's where default presets come in handy. I prepared a set of general-purpose presets you can use in your locations. I tested them both on headphones and speakers, and they tend to sound quieter on speakers. If you think a preset is too quiet or too loud for your location, just put a "room" parameter in your definition, to change the volume. -1500 is the default value, and the volume range is from -5000 to 0 where 100 equals 1 db. Also, feel free to modify these presets as you wish: // Castle courtyard "environment diffusion" 0.6 "room hf" -1500 "room lf" -2000 "decay time" 2.13 "decay hf ratio" 0.61 "decay lf ratio" 0.23 "reflections" -500 "reflections delay" 0.16 "reverb delay" 0.36 "echo depth" 0.37 // Castle bathroom "environment size" 1.5 "environment diffusion" 0.75 "decay time" 1.8 "decay hf ratio" .5 "decay lf ratio" 2 "room hf" -4000 "reverb" 500 // Sewer pipe "environment diffusion" 0.8 "room hf" -1500 "room lf" 0 "decay time" 2.81 "decay hf ratio" 0.14 "reflections" 0 "reflections delay" 0.014 "reverb" 600 "reverb delay" 0.021 // Cave "environment size" 1.3 "environment diffusion" 0.75 "room hf" -200 "decay time" 3.5 "decay hf ratio" 1.5 "reflections" 400 "reflections delay" 0.015 "reverb" 1000 "reverb delay" 0.022 // Forest "room hf" -2000 "decay hf ratio" 0.54 "reflections" -1500 "reflections delay" 0.162 "reverb" -4300 "reverb delay" 0.088 "echo depth" 1 // Short stone corridor "environment diffusion" 0.6 "room hf" -400 "decay time" 1.2 "decay hf ratio" 0.75 "reflections" 400 "reflections delay" 0.004 "reverb" 1000 "reverb delay" 0.003 "echo time" 0.06 "hf reference" 5168.6 "lf reference" 139.5 // Small stone room "room hf" -400 "decay time" 1.15 "decay hf ratio" 0.75 "reflections" 0 "reflections delay" 0.006 "reverb" 600 "reverb delay" 0.005 "echo time" 0.06 "hf reference" 5168.6 "lf reference" 139.5 // Medium stone room "room hf" -400 "decay time" 1.5 "decay hf ratio" 0.75 "reflections" -1000 "reverb" 800 "echo time" 0.12 "hf reference" 5168.6 "lf reference" 139.5 // Large stone room "room hf" -400 "decay time" 2.2 "decay hf ratio" 0.75 "reflections" -2800 "reverb" 750 "reverb delay" 0.03 "hf reference" 5168.6 "lf reference" 139.5 // Short wood corridor "environment diffusion" 0.6 "room hf" -600 "room lf" -1600 "decay time" 1.75 "decay hf ratio" 0.5 "decay lf ratio" 0.87 "reflections" -650 "reflections delay" 0.012 "reverb" 200 "reverb delay" 0.024 "hf reference" 4705 "lf reference" 99.6 // Small wood room "room hf" -1200 "room lf" -800 "decay time" 0.79 "decay hf ratio" 0.32 "decay lf ratio" 0.87 "reflections" -500 "reflections delay" 0.032 "reverb" 0 "reverb delay" 0.029 "hf reference" 4705 "lf reference" 99.6 // Medium wood room "room hf" -1000 "room lf" -650 "decay time" 1.47 "decay hf ratio" 0.42 "decay lf ratio" 0.82 "reflections" -650 "reflections delay" 0.049 "reverb" 0 "reverb delay" 0.029 "hf reference" 4705 "lf reference" 99.6 // Large wood room "room hf" -600 "room lf" -650 "decay time" 2.65 "decay hf ratio" 0.33 "decay lf ratio" 0.82 "reflections" -650 "reflections delay" 0.066 "reverb" -400 "reverb delay" 0.049 "hf reference" 4705 "lf reference" 99.6 // Cathedral "environment diffusion" 0.87 "room hf" -1800 "room lf" -2400 "decay time" 9.48 "decay hf ratio" 0.19 "decay lf ratio" 0.1 "reflections" -500 "reflections delay" 0.09 "reverb" 0 "reverb delay" 0.042 "echo depth" 0.12 "hf reference" 2854.4 "lf reference" 20 // City streets "environment diffusion" 0.78 "room hf" -600 "room lf" -750 "decay time" 1.79 "decay hf ratio" 1.12 "decay lf ratio" 0.91 "reflections" -750 "reflections delay" 0.046 "reverb" -1000 "reverb delay" 0.028 "echo depth" 0.2 // City - abandoned "environment diffusion" 0.69 "room hf" -200 "room lf" -100 "decay time" 3.28 "decay hf ratio" 1.17 "decay lf ratio" 0.91 "reflections" -1200 "reflections delay" 0.044 "reverb" -1800 "reverb delay" 0.024 "echo depth" 0.2 "air absorption hf" -3.2 // Museum "room hf" -1800 "room lf" -1800 "decay time" 3.28 "decay hf ratio" 1.4 "decay lf ratio" 0.5 "reflections delay" 0.039 "reverb delay" 0.0034 "echo time" 0.13 "echo depth" 0.17 "hf reference" 2854.4 "lf reference" 107.5 (...) Now, if you're more interested in how the system works and how you can adjust values to get what you want, take a look at these values. Main values "room" Value Range: -10000 to 0 (-100 to 0 db) Master volume (gain) for both early reflections and reverb. Default value sits around -1500. Lower values actually decrease natural sound reverb. "reverb" Value Range: -10000 to 2000 (-100 to 20 db) Reverb gain parameter. Default value is 0. Higher values feel like you're in a medium or small room with reflective surfaces. Lower values actually decrease natural reverb of the sounds. "reflections" Value Range: -10000 to 0 (-100 to 0 db) Early reflections gain. The louder and less delayed these are, the more it feels like you're closer to the wall (inside a small empty room). "decay time" Value range: 0.1 to 20 (0.1 to 20 seconds) Time for the reverb to decay. Helps determine the size of a room. Average small rooms will have a reverb decay around 0.35 sec. A cathedral or a cavern will have 4-6 sec. Default value is 1.49. (...) Values for fine-tuning "reverb delay" Value range: 0.0 to 0.1 (0-100 ms) Creates delayed reverb effect. Default value is 0.011. "reflections delay" Value range: 0.0 to 0.3 (0-300 ms) Delays early reflections. Default value is 0.007. (...) Example workflow: 1. Use "reverb" to define how dead or live the room is. Add some delay with "reverb delay" if needed. 2. If the room is large (think cavern, canyon, or cathedral), use "decay time" to define bigger space. 3. Use "room" if you want to make "reverb" or "decay time" sound louder or quieter than the default (-1500). 4. Use "reflections" to tweak early sound reflections. (...) Notes / tips: 1. For volume / db parameters, don't bother with testing very low values. In real life, good self-noise characteristics for microphones and recorders is around -60 db. That means most people won't hear that noise. So, whenever you have ranges from -10000 to 0 or 2000, using values below -6000 probably won't do much. 2. If possible, use closed headphones for testing and tweaking, and then see how it holds up on your PC speakers. (...) As you see, this is work in progress, I will update this post with new information and useful things we come up with.

Don't think I do. The mission in questions has the short name vfat1, and the following content in its darkmod.txt: I eventually resorted to this walkthrough to get it done. This uses the name "Vengeance For A Thief 1 (Angel's Tear)". Curiously, I can't find anything mentioning Angel's Tear in the missions database you linked to, but there is a reference in this post. Oddly the description for vfat1 in the missions database appears to describe the "tear" as having already been stolen.

No, it does not. Caulk, shadowcaulk, or any other opaque material are the same for the sake of area/portal structure. All brushes with such textures are blockers of the same kind. The difference is that caulk is not rendered, is not lit, and does not cast shadows. Shadowcaulk is supposed to cast shadows (while still not being rendered and not lit).

There's a missing material in core (the dds file and the editor image itself are present). If I include it in the materials folder of Requiem the 2 missing textures show up in game. Material: textures/darkmod/window/simple_square01_lit { glass noselfshadow qer_editorimage textures/darkmod/window/simple_square01_lit_ed diffusemap _black { blend add map textures/darkmod/window/simple_square01_lit rgb 1 } } 2 options: Include the material back in core Include the material in Requiem materials folder

I think it's time to replace the frob material stages with a shader (probably add a param to the existing ambient shader) There is more than one angle to this issue but I am mainly concerned about too many stages in materials that are somewhat taxing in terms of performance. Imagine rendering of 3K surfaces interacting with 3 lights in average and using materials with 7 stages in average. The renderer loops through every stage for every surface making it ~ 20K checks per loop. It has to happen during the depth stage, then each light and then the ambient pass resulting in 100K checks. It makes sense to try to reduce this load, especially considering that the frob stage is relatively rarely invoked and the checks happen on the backend making it hard to parallelize the computation. I am thinking adding a top-level material keyword that would apply as frob color and get passed to the ambient shader when the surface is a part of a frobable entity. I would like to hear your thoughts from the mapper/designer POV.

Cool, I think this should help a lot. First off, there is an alpha channel in my vertex-blend texture, so I'll remake that without it. The "blend diffusemap" was from the DrVertexBlend tutorial, but I'll try using "blend add" instead. I had mistakenly thought the first line of the material file was referencing the vertex-blend image, so I should just be giving the material a name there? OK, I'll fix that too. Thanks!

The modules are comprised of models, they are completely ignored by the area-portal graph. And now they don't cast shadows if it is proved that light beams travelling though visportals don't touch them. If you use caulk to create areas, then there is nothing that would cast shadows: brushes don't cast shadows because they don't exist (caulk), and modules don't cast shadows because according to area-portal graph they are not hit by light to begin with. There is internal material called "shadowcaulk". As far as I understand, it is not drawn as ordinary surfaces, but it does cast shadows. I think in order to work properly with new optimization, shadowcaulk should be preferred to caulk for the brushes.

@MirceaKitsune try something other than caulk on that brush and see if it goes away. Make sure it's not a no shadows or transparent material.

I'm not having much success with vertex blending a cobblestone path with grass. I've applied it to an .ase model imported from Blender. I followed this tutorial: https://wiki.thedarkmod.com/index.php?title=DrVertexBlend_(tutorial)#Vertex_Painting_Each_Object In DR, my custom material file does show up in the material editor and it seems to be getting applied to the model but incorrectly - it's just a uniform green. In game, the model is greyscale - I think it's getting textured with my vertex-painting, instead of the grass and cobblestone. Here's the mtr file. Have I overlooked anything? textures/darkmod/map_specific/lawn_vertex_blend { surftype15 description "grass" qer_editorimage textures/darkmod/nature/grass/short_dry_grass_dark_ed.jpg { blend diffusemap map textures/darkmod/nature/grass/short_dry_grass_dark vertexColor } { blend bumpmap map textures/darkmod/nature/grass/short_dry_grass_local vertexColor } { if ( parm11 > 0 ) blend gl_dst_color, gl_one map _white rgb 0.40 * parm11 vertexColor } { if ( parm11 > 0 ) blend add map textures/darkmod/nature/grass/short_dry_grass_dark rgb 0.15 * parm11 vertexColor } { blend diffusemap map textures/darkmod/stone/cobblestones/cobblestones02_square_dark inverseVertexColor } { blend specularmap map textures/darkmod/stone/cobblestones/cobblestones02_square_dark_s inverseVertexColor } { blend bumpmap map textures/darkmod/stone/cobblestones/cobblestones02_square_dark_local inverseVertexColor } { if ( parm11 > 0 ) blend gl_dst_color, gl_one map _white rgb 0.40 * parm11 inverseVertexColor } { if ( parm11 > 0 ) blend add map textures/darkmod/stone/cobblestones/cobblestones02_square_dark rgb 0.15 * parm11 inverseVertexColor } } "lawn_vertex_blend" is the vertex-blended DDS image file exported from Blender and is also referenced in the .ase file.

@MirceaKitsuneSorry I admittedly cannot follow your statement. You do not need to modify an existing material to make a new material definition and all you need to apply it to an existing model is a skin definition. So there is no need to be concerned about altering the look of existing materials or trying to color match them (which would be as you mention very difficult using colorization given all the color variances in a typical texture) when you can just make a brand new material definition and skin definition for this without touching core definitions at all. That is material not texture so once you set it up I don’t see why a mapper would need to interact with an image editor, they would pick your new skin which references the new material and greyscale maps you have created and then will tweak the _color spawnarg just you are describing. Look at the light models in core which support the _color spawnarg - these usually have separate skins which denote they support custom _color or not. Same principle applies here.

Public release v1.7.6 (with Dark Mod support) is out. Improvements since the final beta 14 are: Fixed a few remaining bugs with zip/pk4 support. Game Versions window now properly displays TDM version. Import window no longer has a vestigial off-screen TDM field (because TDM doesn't need or support importing). Web search option is now disabled if an unknown/unsupported FM is selected. If an FM with an unknown or unsupported game type is selected, the messages in the tab area now no longer refer to Thief 3 ("Mod management is not supported for Thief: Deadly Shadows"). The full changelog can be viewed at the release link. The de facto official AngelLoader thread is here: https://www.ttlg.com/forums/showthread.php?t=149706 Bug reports, feature requests etc. are usually posted there. I'll continue following this thread though. Thanks everyone and enjoy!

Not so long ago I found what could make a pretty good profile picture and decided to try it out on these new forums. But I couldn't find a button anywhere that would let me change it. I asked on Discord and it seems Spooks also couldn't find anything anywhere. So I logged into an old alternative account and, lo and behold, that account has a button. This is on the first screen I get when I: 1) click on my account name in the top-right of the browser -> 2) click on 'profile'. Compared to my actual account: Are you also missing this button on your account? It'd be very much appreciated if that functionality could be restored to any of the affected accounts.

I finally got around to finishing this. It took me almost five hours but I managed to get all the loot and alert nobody. Some of the treasure I had to find on my way back because I'd missed it on the first try, but it did at least give me something to do on the return trip. Really nice mission, with lots of varied environments and (mostly) logical puzzles. The whole thing looked great too. St Wilbert's tomb was a highlight, as was the underwater base. Battlestar Galactica reference! I thought the tile floor spam in the Citadel itself made moving around more tedious than dangerous. Super cool mission. I'm looking forward to playing Anomaly, and then seeing what more you have in store for the HH series.

Thanks for the replies, gonna try those spoiler Tags again now for my short review (oh well it inserted one above my text now and I can't seem to delete it on mobile - this text editor is strange)

Just finished this mission and wow I gotta say in great honor to Grayman and of course the rest of the team picking it up, this was something I've never seen before in any other TDM mission, especially visually wise. I am so happy that grayson gave green light for other experienced mappers to finish his last mission. And what came out of this is really something special. I'll put my review in spoiler tags since I'm now referring to critical mission details. Edit - How do I put spoiler text here on mobile?? [spoiler] test [/spoiler][SPOILER] test [/SPOILER] [spoiler[spoiler [sfah

Good work! I enjoy short missions because things are nice and focused - you get in, you get out. Also I tend to do better with the loot amounts and I was able to get all the loot without too much trouble, which is rare for me. If I were to make a suggestion though - I found the intro briefing sequence a bit distracting because it was so obvious the narration was pitch-shifted to make a deeper voice. If you felt the original voice wasn't deep enough for your needs, I would either get someone on the forums to record it for you or just leave as is. That's my only real complaint and it's not even about the mission itself, so pretty good first start!

I confirmed that the noPortalFog material flag fixes this behavior: Modified delta1_fog material def: // legacy fog material fogs/delta1_fog { fogLight noShadows noPortalFog // prevents fog distance from closing portals { map _fog alpha 0.5 colored } } I'll look into added an entity flag because that's way more convenient than using override materials.

Okay, I had no idea, I have googled it up now and you are right, to my own surprise. Done, I´ve put some paragraphs which were previously not in spoiler tags into spoilers.

Thebigh is right. The pronunciation tripped me up too, but that is apparently how Leicester is pronounced. Also @TarhielI'm glad you are loving the FM but do you mind putting spoiler tags on your post please