Search the Community

I just found this thread on ttlg listing Immersive Sims: https://www.ttlg.com/forums/showthread.php?t=151176

I've been wanting to post this topic for many months now. It's a continuation to ideas I posted a while back, regarding my wish to create a total conversion for TDM, adding a cyberpunk theme alongside the original steampunk world. The reason for making a new thread is that I have a plan laid out by now, but will need help from the community with it. I wish to know how many people would be willing to help out, so that I may know whether I should start laying out the foundation of this project. I will explain exactly what I plan to do in the form of a FAQ below, so that I can easily cover every aspect. This is going to be long, so make sure you have some time before diving into it! If you want to go straight to the points about what I require and skip the rest, read the titles in red which cover the essential paragraphs. What is this all about?The idea is in part inspired by one of the favorite games in my childhood, DeusEx - The Conspiracy. I used to spend weeks playing through it every few months, drawn by its adventurous story and its dark yet appealing environments. Since the last few years, it's been a dream of mine to create a FOSS cyberpunk stealth game with RPG elements, that would be entirely unique (similarly to how TDM is unique from Thief) yet have the same feel and atmosphere I loved about it (once again like TDM has the same atmosphere as Thief). My earliest thoughts were on trying to achieve this in Xonotic, which is a GPL licensed arena-type shooter I've been a long time contributor to. Of course I eventually abandoned the idea... mostly given that Xonotic has no features for single-player mechanics, such as saving / loading or any kind of AI except bots treated as real players. Then more than two years ago, I finally discovered The Dark Mod. After playing it for some time, I quickly realized it's by far my best option to making such a project come true. Why The Dark Mod, instead of building the game from scratch? It was designed to be a steampunk stealth game after all!The first reason why I want to use TDM as a basis is that it already has every crucial mechanic I need, in terms of AI and interaction and world programming. It does of course lack a lot of the features I ultimately hope to include, although most are optional and I could attempt scripting them at a later stage... for now little to no game code chances would be required. The most significant features are the AI (very advanced and intelligent), carefully balanced gameplay plus other common ideas, as well as the mapping system with its intelligent area portals. It should also be considered that while I'm usually a competent contributor, I'm terrible when it comes to programming something from the ground up, so there's no other way this could happen as a FOSS project unless I hire an entire team. The project aims to be a stealth game that works the same way after all, so why not? To exemplify what I mean: You can open DarkRadiant and build a medieval town with a tavern, then add a guard patrolling the tavern with a bow and a sword. In the conversion, you'll be able to build a futuristic city with a club, and have a guard patrol that club with a knife and a rifle. In both cases, the AI will do exactly the same things with equally correct results: The guards take the same patrol routes, chase after the player the same way, vocally alert one another in the same fashion, and search rooms and hiding spots as efficiently once the player disappears from view. There is no "medieval patrol style" versus "futuristic patrol style", the choices and decisions are exactly the same! The only considerable difference will be the assets and animations and settings. The second reason is that I'm a fan of the idTech engines as well as gtkRadiant based editors. idTech 4 is in fact one of my favorite engines in the line, due to how intuitively it was designed at its core and how much it pulled off during its day. Its only problem is that it hasn't had as many developers forking and modernizing it, unlike idTech 3 with say Daemon engine (for Unvanquished)... that is of course not its fault, and in part due to being open-sourced much more recently in comparison. How exactly would the mod work? Are you thinking of creating your own TDM fork?I don't plan to create an actual fork of TDM, which would be impossible to maintain on my own and only divide the community and its efforts. My plan is to create a mod that will run on top of vanilla TDM, adding new content without affecting any of the existing functionality. The mod would be distributed as one or many pk4 files, which are simply dropped into the main directory next to the stock pk4's! Its assets will be grouped under the mod's own name, so that they're always distinguishable from the normal ones... just like every default component is listed in a "thedarkmod" directory inside DarkRadiant, they would be listed in a "howeverthiswillbecalled" group. Once you have the pk4(s) of the mod inside your TDM installation, normally download any mission using them it in order to play it! So missions will be able to use entities and assets from both stock TDM and this mod?My plan is to allow that, and nothing should prevent maps with mixed assets. Keep in mind however that I ultimately want the mod to be independent, and encourage relevant missions to only use textures and entities included with it rather than a mix! If you take out every single stock TDM asset (excluding md5anim's which will be reused) the mod will be expected to work on its own. Will the new assets also be non-commercial?Unlike vanilla TDM, I don't wish to include any CC-*-NC and CC-*-ND assets with the mod. That's primarily because I find them limiting, and feel that they ruin the openness of the project. Is there a name for the mod yet?I've been thinking about it but haven't fully decided so far. I want it to be something familiar and related to TDM; Initially I wanted to call it The Dark Modern, but that sounds rather silly. The name I'm considering now is The Dark Machina, which retains familiarity with TDM and is also more theme relevant... further suggestions are appreciated. What is the benefit for the community? Why should anyone put any effort into this?The project is targeted to everyone in the TDM community who alongside a steampunk stealth game, would enjoy a cyberpunk stealth game of equal or greater visual fidelity... with exactly the same base gameplay and core functionality, but an entirely different world and atmosphere. The project will be publicly available on a Git repository of its own (most likely Gitlab), and anyone will be able to easily install it on top of vanilla TDM. Simply put: If you help and things go according to plan, you'll have a triple-A scifi game inspired by the look and feel of the DeusEx series, just as you currently have a triple-A game victorian game inspired by the look and feel of Thief. What do you need help with exactly? What would others have to do?Obviously I'm not asking others to do the work for me. But at the same time, it's not something I can just go ahead and do on my own either! For this reason I've come up with a plan, which would allow contributions to happen gradually whenever someone willing to dedicate their time to helping adds something new. This is mainly a call to existing TDM developers, who know best how to export and define new assets. If the project takes off, based on the answers I get in this thread, the starter plan is as follows: I will be creating two Git repositories. One will be the official repository of the mod, which will contain assets in working format and condition... the other will contain images, sounds, blend files, and other resources in their native format. This will include freely licensed assets I find on the internet, which I will hand pick and tweak to make sure they're in the readiest state possible, then sort them in a way that's easy to work with. Most will be taken from http://opengameart.org and http://www.blendswap.com and I'll likely use a few things from Xonotic altogether! The assets included in this repository are to be exported and / or converted to TDM compatible formats, then included in the real mod repository. A list will be maintained in order to keep track of which assets have already been ported. Every ported asset can be issued as a pull request, or sent to me personally in case the contributor doesn't have access to the Git service that will be used. The rigging, exporting, and conversion processes are what I require the community's help with! As far as models textures and sounds go, no new content will need to be created... I plan to use freely licensed resources which are already available and plenty, enough to create a full mod out of. Obviously I'll be doing some of the exporting and definition writing myself, but since there will be so much new content I can't do it all on my own... unless I dedicate every waking hour of my life to it for over an year, which would be more than I can handle TLDR: I'll be compiling a repository of game-ready assets, such as textures and models and sounds. Anyone who wishes to help is only asked to pick them up, adjust the TDM specific necessities (exporting to md5, creating material definitions, etc) and publicize the results for inclusion. So no new content is going to be needed?For the most part, no. There is only one exception to this rule: Voices. As they're something TDM specific, they have to be created to match the world and what's happening in it. They are however not a priority, and can happen at a later stage in the project. Until then we can live with a few cyborg troops saying things like "in the name of the Lord Builder, you shall go to the gallows, you heretic" Other than that, I will eventually want to add new functionality. Including a Minecraft type inventory system, computer chips the player can install into their suit or body in order to gain enhancements (modules / augmentations / whatever), and most importantly a re-implementation of the interactive touchscreens in Doom 3. Those are however even more distant needs in comparison, and not what this thread will focus on at this point... I plan to look into such once I'm sure there are enough contributors to be certain this is happening altogether. What do you need done for each type of asset explicitly?Here is a list of every new asset type the mod is going to introduce, and the steps I estimate to be required for each: Characters: I will be offering the blend files of all characters scheduled for inclusion. They will contain the mesh, textures, as well as the rig that the character comes with (if available). Steps to be taken include: Rigging the character to the TDM animation skeleton after using the original rig for initial posing (including face rigging), generating the shadow mesh, making sure polygon count is within acceptable limits, and finally exporting to md5. Lastly, generating and tweaking the character definitions (stats, team, social status, voice, etc) and the material definitions for the character's textures, which should be all that's needed for the model to become a working character. Notice: I'll be preparing a blend file containing the simplified / optimized TDM rig in order to ease the process, including the face rig which I remember had to be extracted from existing characters. Models: A similar process would be needed with static models and simple entities: They will be distributed as blend files which include the model and texture, and need to be exported to ase / lwo, with entity and material definitions in place. Textures: Most will likely be distributed as jpg and png, and will need to be converted to dds and tga. The material definitions will need to be created as usual. Sounds: Will be distributed as wav or ogg, which normally don't need to be converted. Sound definitions need to be created however.As far as specific TDM functions go, this is how I intend the modifications to work per component: Weapons: The plan is to keep each weapon the same in terms of purpose and functionality, and mainly modify the models animations and sounds. The same core code will therefore be used by each, but new entity definitions should be made in order to not affect maps using the existing items while the mod is installed. Menu: When a mission intended for the mod is installed, the main menu will use different textures and a different background song... no modifications to the entries or functionality will be made otherwise. I'm uncertain as to how this can be achieved, although it is lower on the priority list.What will be the modern equivalent of existing TDM items, as well as new content?Like I said, I plan to keep the functionality and purpose roughly the same, at least for a while. Therefore items will serve the same goals, and work almost exactly like the existing ones in TDM... it will be basically the names and appearances that change. The important replacements I currently have planned include: Weapons: Blackjack becomes Police Baton or Taser. Sword becomes Knife. Bow becomes Crossbow or Sniper (arrow types and behaviors unchanged). Items: Lantern becomes Flashlight or Keychain Light. Telescope becomes Binoculars. Compass remains Compass. Snake and Triangle lockpicks become Physical and Electronic lockpick (mechanical doors are unlocked with the first, electronic doors with the later). Potions become Medkits, Syringes, or special types of enhancements.As far as completely new content goes in regard to items and entities, here is a rough list so far: Books & Notes: Alongside the existing books and notes, laptops / smartphones / tablets will be added. They are unrelated to future plans for interactive screens, and simply refer to new types of visuals for readable items found throughout the world. Lighting: The replacement to existing candles and torches will mostly consist of desk lamps, particularly neon and LED based ones. Characters: A similar structure of factions will be followed, compared to the existing guards + thieves + civilians + beggars + nobles. In this case the main categories will be: Police (ideally different suits for various units), gang members (once again different clothing for each gang), with modern looking civilians of various classes. There will also be entirely new outfits covering jobs existent in modern times, such as scientists or industrial workers. Robots: The existing code behind the Steambot will be used to implement multiple kinds of security drones patrolling an area. Especially in early stages before new scripts are considered, they can have the same function of only sounding an alarm when the enemy is spotted. Props: There will be various modern props added throughout the world, depending on what content I find. This will include: Flaming barrels for poorer areas, futuristic cars and bikes parked on the sidewalks, televisions that play videos (in case itTech 4 allows video textures), and the list goes on.Closing thoughts:First of all, thank you for reading this enormous post, regardless of whether you wish to support the project or not. This is something I've dreamed of creating for a while now, and I really hope at least a few artists out there are willing to support it! Please leave your thoughts if you want, as well as voting on the pool so I can more easily estimate the help I may expect.

Recently revisiting the forums after a longer period of time I wanted to check the unread content. I don't know if I am doing this wrong since.. ever... but on mobile (visiting the unread content page on my smartphone) you have to click on that tiny speech bubble to go to the most recent post in a thread. If you don't click correctly you'll hit the headline and end up at post 1 in the beginning of the thread. It's terrible on mobile, since not only the speech bubble is really small and was to miss. But also the thread headline is just millimeters away from it so you go right to the first post that was ever made instead of the most recent ones. Am I doing it wrong? I just want to go through u read content a d the to the newest post from that topic.

A@datiswous Ah yeah, well sorry, I was quiet busy and only visiting discord. First time here on the forums since months now I think.. Thank you for the subtitles. I encourage everyone who is interested in using them to download it from here as I'm not sure when I'll be able to implement them myself into the mission. Again, thank you for your work.

I think it is a good idea! Our ingame mission downloader and mission view has long been subject of multiple improvement suggestions. Due to the sheer mass of missions that have been released in the last 15 years, things got really cluttered and especially newcomers will have a hard time finding what they want. However, improving the ingame guis is quite a task, so a web-based application might really suit this scenario well. Maybe we could even add a linke to it from our ingame menus, so user can access it quicker. Some more things to think about Would users be able to add custom tags and downvote / upvote certain tags, much like the system of Steam? This would also allow to add tags like "beautiful", or "difficult". Actually, the more users can contribute to this system, the better, because it will be automatically maintained then. The browser should also contain a flag for whether the FM belongs to a connected series of FMs or not and have the capability to go to the previous or next FM in that series. There should also be a flag for fully fledges campaigns. Some might like a flag whether or not an FM is "ghostable".

DarkRadiant 3.7.0 is ready for download. What's new: Feature: Skin Editor Improvement: Script Window usability improvements Fixed: Hitting escape while autosaving crashes to desktop Fixed: Def parsing problem in tdm_playertools_lockpicks.def Fixed: DR hangs if selecting a lot of entities with entity list open Fixed: Float Property Editor's entry box is sticking around after selecting a float key Fixed: Spline entities without model spawnarg are unselectable Fixed: Entity window resets interior sizing forcing resize each time it is opened Fixed: Spline curves should not be created with a model spawnarg Fixed: Newly appended curve control vertices aren't shown at first Fixed: Light entities are zoomed out in preview window Fixed: Entity inspector spawnarg fields not always updated by UI windows such as Model Chooser Feature: Skin Editor (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.7.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. Keep on mapping!

Yes, it does. Which makes it interesting that you yourself explicitly said that it's interesting nobody had complained here on the official forums: I did, which is why it stood out to me so much that even though you yourself had personally been involved you would reply claiming nobody had complained here on the official forums. I'm not colorblind at all. Does that make people pointing out that almost no modern games have proper colorblindness support hyperbole? Just because it doesn't affect you, or you choose not to pay attention to the discussion of something, doesn't make it hyperbole. Pick pretty much any modern FPS and you will find plenty of discussion about the near universal disregard for FOV and camera movement as accessibility issues. Denigrating those as hyperbole because you personally don't feel the affects is as bad of a look as demeaning people who bring up the importance of valid allergen warnings like gluten or colorblindness and deafness support.

Hey, Every time I've try to use the Full Editor when PM'ing someone, and every single time I get an error. Whoever is in charge of the forum, is it possible that this could be fixed? Thanks Neon

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.

PLAYERS * Volumetric lights appeared late before the previous beta, so the quality of volumetrics in 2.10 was rather poor, and the dithering pattern was very annoying to look at. The feature received a lot more development, and now adheres to the standards of modern rendering. The dithering pattern is gone, performance should be much better, and now you won't miss volumetrics even if you prefer to play with stencil shadows all the time! (thread) * Thanks to a certain "AI-heavy" mission, the game code has received major optimizations. It is most noticeable in low performance conditions, when game modelling takes a lot of CPU time. Previously the game could easily descend into the "spiral of death" with FPS falling below 5, now it is way harder due to better scheduling of AI thinking. There is a variety of other game code optimizations which make our lives slightly better. * New version includes several optimizations for shadows, mostly stencil shadows. A long-standing inefficiency of stencil shadows with antialiasing is fixed, new tile-based optimization is added for soft stencil shadows (thread), small lights with large meshes work faster due to BVH efforts (thread). On the side of shadow maps, the rules for distributing the resolution budget are changed: small distant lights no longer steal precious bandwidth for themselves. * There are several improvements on gameplay side as well. The core mechanics of blackjacking enemies has received subtle, yet helpful improvements (thread). Now you can grab many close pieces of loot by holding down the frob button, instead of picking up each item individually. There are several improvements to crouching, making it more responsive (thanks to @Daft Mugi). The in-game downloader now supports "sort by release date" ordering. * There were a ton of small bugfixes for issues like: bow stuck after load, wrong strafe-walk sound, crash when saving shortly after the death of an elemental, melee combat crash, issues with leaning onto doors, missing fracture sounds after loading a save, X-ray glitch in the first frame, toggling solidity/visibility, lightgem on game load, etc. MAPPERS * The engine now supports OBJ model format. This format is much more popular than ASE and LWO. The engine loading code is very lightweight: it will use your model exactly is as, and load it very quickly. The OBJ format is preferred for large meshes due for faster loading times. The only possible downside is somewhat larger download size compared to LWO, although not much and not always (thread). * Renderer should deal with large meshes much faster, thanks to BVH optimizations. Recall that idTech4 was made for very low-poly models. When renderer frontend sees a "surface" in a model, it always treats this surface as an atomic piece, doing all computations for all of its vertices and triangles. This is very good for low-poly models, can heavily drag performance down with large meshes, as several recent missions noticed during beta. The BVH data structure breaks every surface into smaller chunks, allowing renderer to quickly cull away whole chunks. This makes a big difference in case of large meshes (e.g. terrain) lit by many small lights (thread). * You no longer have to write frob-highlight stages in materials, since they are added implicitly. The problem with these stages was that were very easy to forget, which resulted in no highlight on frobable items. Also it increased cognitive load and scared mappers away. While writing frobstages is no longer necessary, the old stages work just fine. So mappers can still customize frob-highlighting if they really want to (thread). * It is now legal to override a single decl of core game in your mission. Recall that "decl" means a material, a skin, an entityDef, a particle, etc. Note that overriding a whole file from core game always worked as expected, but overriding a single decl from a file did not work reliably before (despite the common belief that it should). * The major cleaning of shaders resulted in some changes in lighting model. The aim was to make TDM lighting closer to the standard Phong model, and make it more logical in general. The changes should rarely make a big difference, aside from probably stronger specular (thread). * Added error-reporting to the GUI scripting engine. Implementing GUI scripts is very hard, error-prone, and confusing. Aside from surprising differences in Doom 3 GUI behavior compared to e.g. Javascript in DOM, a lot of confusion was caused by total lack of any error handling whatsoever! In the new version, all possible errors should result in easy-to-understand console warnings, so writing correct GUI is much easier. Also, we fixed a few features, and added a few new ones to the GUI engine (thread). * dmap command received minor improvements. Yet another big rewrite happened for T-junctions fixing code, since it took tremendous amount of time on one mission. Also a few precision improvements were made. * Other small fixes and additions: added script functions getAnimRate / setAnimRate for tweaking animations added script function setObjectiveNotification for silent objective change added script function getCurInvItemCount for interaction with inventory added script variable "AI_ENEMY_TACTILE" to the base AI scriptobject, which is true whenever the AI is in tactile range of an enemy added spawnarg absence_alert_increase for loot items as a proper substitute for absence_alert, giving control over how much an AI gets alerted if that piece goes missing added spawnargs allow_idle_anims / allow_random_headturning for customization during a running mission, useful i.e. for cutscenes AIs notice broken fracture entities trigger_multiple now works on stationary AIs almost doubled tracemodel limits, raising the restrictive limits for making collision meshes for moveable items door movers can now call "used_action_script" whenever something like a key, lockpick or other item is used on them, if they have the spawnarg "call_used_action_script" "1". ASSETS * Many new assets from capable creators in our community have been incorporated into the core assets. These include: Loot assets: Detailed coins and ingots with accompanying lore. Link Ancient loot items suitable for museums, collectors and ancient sites, first seen in the Volta series. A tiling treasure hoard texture for those with unimagineable wealth. 6 detailed book skins including 3 that are lootable, a first for TDM. Link Security assets Highly detailed standing and wall safes - with or without an accompanying combination lock. Link The combination "safe lock" is now part of core assets and can be operated by either scrolling or frobbing. Mappers no longer need to track down this asset and include it with their FM files as a custom asset. Wall-mounted locks in the style of those commonly found in the original Thief games. Camgoyle sentry, a magical stone guardian based on the security camera shooting magical projectiles at the player, first seen in Written in Stone. The prefab also includes a power source pedestal. Link Fully useable audiograph for playing recorded sounds, first seen in the Accountant and Shadow of Northdale missions. A new full-featured scriptobject makes them easy to implement and control via spawnargs. Wiki Furniture assets Posh upholstered armchairs and sofas for the wealthiest nobles. Link A new high-detail grandfather clock with a working scriptobject and a mantle clock. Link A gothic-style cabinet. Link Office assets Including bundled stacks of paper, blueprints, a letter, crumpled paper, waste bins, an end table and an ornate table. Nautical assets Full-scale modular ship prefabs with interiors, allowing anyone to assemble a ship for a nautical mission in a matter of seconds. 1 merchant galleon and 2 smaller sailing ships are available. Link Link Link A large galleon ship wreck in 2 pieces for those sailors who have met an unfortunate end. Decorative assets An impressive multi-tiered wall fountain, first seen in the mansion in Noble Affairs. A new pair of marble lion statues. Link A standing stone menir with carved symbols on it, ideal for pagan missions. Link Stone pedestal with purple cloth for presenting valuable items. Textures High-resolution cobblestone textures for detailing the streets of TDM. Link Starry wallpaper. Lamps A set of 6 bronze vintage lamps has been added for particulary posh establishments. Link Thief-style charge post streetlamp. A new open-top carriage, the barouche. Link Miscellaneous other models, including: wall planter, 7 small "foliage" herbs, 2 mine carts, 6 shop signs, equippable feather duster and 5 decor plates * We fixed all loading warnings on all existing assets. This became possible after creating an automatic map generator which forces the engine to load all assets from every group. All the references to missing files are fixed too, which means a variety of assets have become available: Old noblewoman skin, plain mage robes skin, moor helmet, electrical arcs, stone window decals (5178), yellow banner skin (5563), wine barrel (Link), grass particles (5689), lampion lights and more graffiti decals. PROGRAMMING Under the hood, we updated third-party libraries, and moved to Visual Studio 2022. The "Debug With Inlines" configuration was split into "Debug Editable" (with hot-reload support) and "Debug Fast" (fastest debuggable). Marking the final step in transition to tdm_installer, the old tdm_update program is finally removed, with TDM packaging code extracted to standalone program.

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.

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!

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!