Search the Community

Ignoring is somewhat inadequate as you still see other members engaging in a discussion with the problematic user, and as Wellingtoncrab says such discussions displace all other content within that channel. Moderation is also imperfect as being unpleasant to engage with is not in itself banworthy, so there is nothing more to do if such people return to their old behaviour after a moderator had a talk with them, except live with it or move away. I'd be more willing to deal with it if it felt like there were more on-topic discussion, i.e. thoughts about recently played fan missions or mappers showcasing their progress, rather than a stream of consciousness about a meta topic that may or not have to do with TDM. I guess the forums already serve the desired purpose, or they just compartmentalise discussions better.

I didn't mean to give you PTSD from that one response, HMart. You're spot-on in your reply, though. I have no clue how to access the depth buffer, or what c file to modify to expose it or where and such. So, I gave up. In working on the FUEL shaders, it was a blackbox scenario. I had access to the shaders, but not the game engine code. So, I spent years learning shaders and getting creative with what was piped in, but my knowledge was capped by not being able to mess with the game code to implement more robust things. So, I mess with shaders, but get hesitant to jump into anything that involves digging into game code to expose or add things. I'll look into the places you pointed out to see if I can find something when I get a chance. I'm currently giving parallax occlusion mapping another shot, b/c it seems like all the pieces are there but it's just not looking decent. Gonna try to use another code source; might be easier for me to understand.

No. The Aeden's staff optional objective is the hardest of the game. To point out directions here, though, is getting into an area of heavy-duty spoilers ... so I'm constrained in my response just as I was constrained in my responses to the "endless keyhunt" complaints because to show the rather simple direction would be a huge spoiler. So I had to bite my tongue and take it. Aeden's staff is different, though - harder. I've never tried a no-KO ghost playthrough. Because I'm clumsy and have slow reflexes. I think it might be possible to do a stealth no-alerts playthrough. Are you allowed to KO? I think I've gotten the staff a few times in my playthroughs without alerting the builders in that room. The only switchable lights in the FM are table lamps. The cylindrical style wall lamps aren't extinguishable. The other fire and gas wall lamps are extinguished by water. In the Ox all waiters and commoners in the common room and outside are friendlies - except for the waitress in the upper lounge which is filled with enemies. You need water arrows. Moss arrows. Rope arrows. I've never used a gas arrow in a playthrough of the FM but one would make things easier, for sure. I'm going to replay the area and check through the locations that you mentioned - the loop etc. - then if it's OK with you I'll PM you with some info, tho' I'll ask you if you want the info first. So's not to spoil it for others who get that far in the game (few and far between!). I find it almost impossible not to click the "reveal spoiler" tags and read the info ... and, y'know, spoilers do spoil the real deal.

New version (see attached .zip) Uses texture diffuse color as fresnel highlight color for the fallback fresnel branch in interaction.ambient.fs. This helps fresnel blend into the surfaces and scene better, instead of looking like a monochromatic haze on everything. Also, in some missions I'm seeing a pink / red sky (eg: Lord Edgar's Bathhouse). I looked at screenshots of the mission, and it's supposed to be blue. Not sure if something in my shaders is doing that. I thought I had set something to .r *= 10 to highlight what the shader impacts. But, sifted through the shaders and I had all those parts commented out. It could be that the sky is using a branch of shading that I thought wasn't used any more, and I mucked up something. Not sure. That's the main problem I'm having.. I can't tell which textures are using which shaders. So, I can't tell which shaders are worth messing with, and which ones I messed with having adverse impact later. That's why I was hoping there was a project document that maps out what hooks to what. glprogs.stages.interaction.012.zip

Yeah, the behavior here is what we have seen since JC Denton's "HDR-Lite" shaders were introduced. Once the glancing angles amplify the light response above the rgb threshold for bloom, you get the blow-out. It looks realistic in some scenarios such as near a fireplace or torch but is not quite convincing with area lights or large bright lights whose light center is further away from the surface of the affected material. Example of the benefit of the effect ( ceiling fresnel effect ) : I guess the workaround is to darken the specular and diffuse a little further, maybe add a blend filter stage ( faked AO, etc), and maybe add an alpha channel to the specular to tone down the gloss response.

I don't recall a system for noise masking. It sounds like it'd be a good idea, but when you get into the details you realize it'd be complicated to implement. It's not only noise that that goes into it, I think. E.g., a high register can cut through even a loud but low register rumble. And it's not like the .wav file even has data on the register of what it's playing. So either you have to add meta-data (which is insane), or you have to have a system to literally check pitch on the .wav data and paramaterize it in time to know when it's going to cut through what other parameters from other sounds. For that matter, it doesn't even have the data on the loudness either, so you'd have to get that off the file too and time the peaks with the "simultaneous" moment at arbitrary places in every other sound file correctly. And then position is going to matter independently for each AI. So it's not like you can have one computation that works the same for all AI. You'd have to compute the masking level for each one, and then you get into the expense you're mentioning. I know there was a long discussion about it in the internal forums, and probably on the public subforums too, but it's been so long ago now I can't even remember the gist of them. Anyway the main issue is I don't know if you'll find a champion that wants to work on it. But if you're really curious to see how it might work, you could always try your hand at coding & implementing it. Nothing beats a good demo to test an idea in action. And there's no better way to learn how to code than a little project like that. I always encourage people to try to implement an idea they have, whether or not it may be a good idea, just because it shows the power of an open source game. We fans can try anything we want and see if it works!

We are proud to announce the release of: The Dark Mod 2.11 ! The Dark Mod 2.11 is primarily a bug-fix release. The majority of development time was dedicated to fixing or improving long-standing bugs or problem areas with the project rather than focusing on new features. That said, some of the improvements that were introduced to address these issues could very well be classified as new features in terms of the amount of changes required to bring them to life. A full changelog can be viewed here, but some highlights include: Major gameplay improvements! For players, Stealth Score and AI alert behavior has been improved to better detect tactile contact with AI and proximity. An older TDM release introduced a grace period feature that was overly broad and made some AI ignore players that were right in front of them. This has been substantially improved so stealth scoring and AI reactions should be a lot more consistent and logical. Players will also have a new Blackjack experience with better cues about whether a blackjack attack will succeed and improvements to the way that the blackjack attack is executed. Players can more smoothly transition from climbing as the player is now permitted to be crouched during the climb. There is a new multi-loot feature which allows you to pickup multiple loot pieces by holding down the frob button! Performance Improvements! The new volumetric light feature has been improved via a new blur phase. This means that you no longer need to increase the samples to reduce or remove banding and performance should be substantially improved. Before 2.10 ( dithering and low sample count): After 2.11 ( blurred and higher default sample count ) : Soft Shadows now utilize scissors and tile-based evaluation in stencil mode so that Anti-Aliasing no longer need be applied to the entire shadow buffer. Shadow Maps have improved mipmap, LOD and texel utilization. There should be fewer artifacts and better performance. Large models are now evaluated via a BVH structure so that they can be split for lighting and culling optimizations. AI think cycles have been optimized and perform less work per-frame. GLSL programs have been rewritten to have better performance on AMD graphic cards. Included mission improvements! Mission 1: A New Job now features subtitles! Mission 2: Tears of Saint Lucia has been improved with EFX reverb and a few bug fixes! Asset fixes and additions! Dragofer has fixed hundreds of assets that were missing setup definitions or other components that would cause the console to flood with errors on TDM launch or on the launch of missions. In addition, he has added hundreds of new and old assets from both TDM team members and members of the TDM community. Improvements for Mappers! The Engine now supports Obj model format Material Shaders no longer require you to add frob stages. Frob is now auto-generated. You can still add custom frob effects to materials if preferred Missions can now include decls that override those in the core TDM without using an override file to replace the entire core file. GUI scripting has been overhauled with better syntax and error reporting Dmap precision has been increased and Dmap T-junction performance has been optimized Please see our Moddb article for the full developer blog entry: https://www.moddb.com/mods/the-dark-mod/news/the-dark-mod-211-is-here 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.11, so finish any missions you might be in the middle of first!

DarkRadiant 3.6.0 is ready for download. What's new: Feature: Selection Focus (Ctrl-F) Feature: Add Radiant.findEntityByName script method Feature: Media Browser shows a thumbnail preview when selecting folders Feature: Map is remembering layer visibilities between loads Fixed: ModelDefs are shown in T-pose Fixed: Patch vertices are the wrong colour Fixed: Shader Clipboard source gets cleared on 'copy shader' operation Fixed: Nodes of hidden layers are still visible after loading the map Fixed: Can't close properties window Fixed: Merge Action rendering is broken Fixed: After using ToggleMainControl_Camera, the center panel is grey after restart Fixed: When using ToggleMainControl_Camera, arrow keys cannot be used to move the viewer Fixed: Property Panel not remembering undocked/closed tabs Fixed: Texture Tool not updating during manipulation Fixed: Orthoview ignores filters for surfaces in models Fixed: Blue dot when selecting one face removed Tweak: Conversation Editor: double-click opens selected conversation Tweak: Preference option to disable drag select in camera view Tweak: ESC key should clear the resource tree view filter text Tweak: New layers function: tooltip popup getting in the way Feature: Selection Focus (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.6.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Have fun mapping!

I believe the plan was to first get better reflections working then move towards better surface shading and finally incorporate the probes into the ambient_world ( aka probe GI ). Hard to say but it may just be easier to examine what can be ported from RBDoom3BFG and add the full feature-set in one big change. If someone wanted to examine the shaders from that project and try to make them comply with our design requirements ( OpenGL GLSL 3.3 ) that would make it easier to begin such an evaluation. For non-team members, I think that only hmart, jonri, and totallytubular ( maybe Filizitas ?) have the skill-set to do this type of thing so it will probably wait until a team member has time to begin experimenting.

DarkRadiant 3.4.0 is ready for download. What's new: Feature: Allow Layers to be arranged into a Tree Fixed: Readable Editor displays "shader not found" in view Fixed: Undoing snap to grid with prefabs causes crash Fixed: Include doc in building instructions Fixed: Decal textures causes DR to crash - (textures/darkmod/decals/dirt/long_drip_pattern01) Fixed: Skin chooser: double click on materials list closes window Fixed: Selecting and deselecting a filtered child brush through layers leaves the brush selected Fixed: Material editor re-sorts stages on pasting image map resulting in wrong material stages list and wrong selected stage Fixed: Crash on start if engine path is choosen (Doom 3) Feature: Layers can now be arranged to form a hierarchy Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.4.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Have fun mapping!

DarkRadiant 3.5.0 is ready for download. What's new: Feature: More customisable layout, all windows and panes can be dragged and arranged Layouts like Embedded, Regular and Splitpane are superseded and have been removed Tweak: The LayerControlPanel's tooltip popup is now less annoying Tweak: Clarify distinction between Shadow render mode and other render modes Fixed: Show/hide Light Volumes for combined entities inconsistent Fixed: Currently applied particleDef not selected in Particle Selector Fixed: Layer visibility checkbox not reacting to double-clicks Fixed: Cannot toggle visibility of layers in Linux Fixed: Drag-and-dropping layers is not working in Linux Feature: Customisable Layout (click to see the videos) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.5.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Have fun mapping!

@stgatilov, you said, RE string comparisons: I'm unclear if you are referring just to changes you made in 2.11. I think equality testing of two strings (one of which is "text") was working and is a good and expected capability, and should be supported. Including against an empty string. I noticed in your bug activities that you did remove some comparisons with ... == "". I see you also removed string concatenation with "\". No problem, but does that mean multiline macros are no longer a thing? (If so, I'll need to change some examples) BTW, the series so far hasn't really tried to cover the 2.11 changes, since I figured it's a work in progress. But since you did a great deal of GUI work in July, perhaps it's stable enough to try to consider it. I see the logs listed in bugtracker, but don't have access to the private forum threads mentioned there: https://forums.thedarkmod.com/index.php?/topic/20526-gui-refactoring/&do=findComment&comment=477179 https://forums.thedarkmod.com/index.php?/topic/21535-order-of-evaluation-in-expressions-materials-and-gui/ (Nor do I have SVN currently set up on my newer machine, for changelogs from there.) Any place else I should look?

I'm using the version from kcghost. I just tested and I can't see any difference inside the inventory. On the stats itself it doesn't show the different loot types (still seen in the inventory), but instead gives more info on stealth score. Edit: I see Dragofer made an updated version of his script. I have to check that out. Edit2: That version works: https://forums.thedarkmod.com/applications/core/interface/file/attachment.php?id=21272&key=02755164a3bed10498683771fe9a0453

I looked but didn't see this video posted in these forums. It's pretty cool.

Announcing the Release of 'Requiem' for The Dark Mod! Download Download the latest version of the Dark Mod here: http://www.thedarkmo...wnload-the-mod/ Download the mission here: Mediafire: http://www.mediafire...u89/requiem.pk4 Southquarter: http://www.southquar...ons/requiem.pk4 Fidcal.com: http://www.fidcal.co...ons/requiem.pk4 Create a folder in your Dark Mod install with the path "darkmod/fms/requiem" and place the downloaded .pk4 file inside. When you load up The Dark Mod, the mission will appear on the "New Mission" page. Requiem can also be found directly using the in-game loader. Gameplay Notes While this mission is playable in TDM 1.8, for an optimal experience please download and play in TDM 2.0 (or higher). Most inventory items in the game can be dropped, so no need to carry them around after they are no longer of any use. Note that If you use noclip or other console commands while playing, there is a good chance that you will break the intended flow of gameplay. Credits Mapping and Readables: Gelo R. Fleisher Voice Acting: Goldwell Additional scripting: Obsttorte Additional textures and assets: Flanders, Sotha, Grayman, Springheel, Bikerdude, Obsttorte Additional map optimizations: Bikerdude Testers: Bikerdude, Obsttorte, Gnartsch, AluminumHaste, Baal, nbohr1more, PPoe Custom Soundtrack: Leonardo Badinella - http://leonardobadinella.com/ Additional Music: Lee Rosevere - http://freemusicarch...c/Lee_Rosevere/ Marianne Lihannah - http://www.funeralsinger.net/ Vox Vulgaris - http://www.last.fm/music/Vox+Vulgaris/ A note from the author Hi all. While I've been involved in indie game development for a while now, I'm first and foremost a writer. My most recent project has been a novella that tries to capture the visual feel and tone of the Thief series (you can find the link below). As I was writing, I found myself playing a lot of Thief and Dark Mod fan missions, and got to thinking that maybe I wanted to make one myself, as a companion piece to the book. When I finished up writing, I had a bit of down time and decided to take the plunge. Having never done any serious mapping before, my plan was to make a small mission that I could bang out in a month or two and call it a day. Well, as sometimes happens, the project got a little bit bigger than I had planned. Ten months, and lots of elbow grease later, Requiem is finally ready for you to play. I'd like to thank everyone who helped pitch in to help make Requiem come alive, from those who took the time to answer my many questions on the forums to those who actively contributed to the FM. I especially want to thank Bikerdude who served as my mapping mentor, and Obsttorte whose clever scripts really turned what was in my head into the game that you are playing. Above all, I want to thank you for downloading and playing Requiem; I hope you enjoy it. Links of Interest Author's Blog: http://gfleisher.blogspot.com/ Companion Novella (Amazon): http://www.amazon.co...k/dp/B00BYEW02M Companion Novella (Smashwords): http://www.smashword...oks/view/298956

It was not a bug, it was real-time shader compilation (PC-specific issue). They addressed it by pre-compiling shaders while you're in main menu.