Search the Community

I feel like I am in a loop. Unless I am mistaken, mission.cfg was supposed to only temporarily apply cvars while a mission is installed. I do recall a great deal of back and forth on this. In the original Doom 3 you could add a doomconfig.cfg file to your mod pack to override default cvars and this config would only be active when the mod was active.

Mandrasola is a small sized map in which aspiring thief Thomas Porter steals some herbal products from a smuggler. The mission was created by me, Sotha and I wish to thank Bikerdude, BrokenArts and Ocn for playtesting and voice acting. Thanks goes naturally to everyone contributing and making TDM possible. This mission occurs chronologically before the Knighton's Manor, making it the first mission in the Thomas Porter series. Events in chronological order are: Mandrasola, The Knighton's Manor, The Beleaguered Fence, The Glenham Tower and The Transaction. The winter came early and suddenly this year. Weeks of strong blizzards and extremely harsh cold weather hit Bridgeport hard. With the seas completely frozen, a rare occurence indeed, most of the City harbor commerce has stopped completely. Vessels are stuck in the ice and no ship can leave or enter the City, resulting in the availability imported goods declining and their prices skyrocketing. One of these imported items is Mandrasola, a rare herbal product, which is imported overseas from the far southern continents. Mandrasola has its uses in alchemical cures and poisons, but mostly this substance is used for its narcotic qualities by commoners and even the nobility. The problem with Mandrasola is that excessive use is extremely addicting and the withdrawal effects are most grievious. Many are utterly incapable of stopping using Mandrasola and are transformed into quivering human ruins if they do no get their daily dose. And now this expensive and rare substance is running out from the whole City. Me and my fence, Lark Butternose, would love to grab this monopoly to ourselves: selling the last few doses in the City would probably be worth a fortune. According to Lark's sources, there remains only one smuggling lord who still has Mandrasola in stock. The problem is that this individual maintains an exclusive clandestine operation and only supplies a few nobles. Despite our best information gathering efforts we couldn't learn who the smuggler is and where he or she operates. Luckily we have an alternate plan. While searching for Mandrasola related information, we learned that a noblewoman called Lady Ludmilla is addicted to the substance and has paid high prices for small amounts of it. We also know that she has visited frequently someone in the Tanner's Ward waterfront, and since she goes to the area personally we believe she is visiting the smuggler. The plan is simple: I must monitor Ludmilla's most likely entryway to the Waterfront and then follow her to the smugglers hideout. I'd better be very careful around Ludmilla. She must not realise I'm following her or she probably won't lead me to her dealer. Hurting her is also out of the question. After she leads me to the smuggler's hideout, I can take my time to break in carefully and steal all the Mandrasola I can find. While I'm there it wouldn't be a bad idea to grab some loose valuables as well. I've now waited in the blistering cold for a few hours already. Looks like there are a few city watch patrols in the area to complicate matters... I think I heard a womans voice beyond the north gate. That must be lady Ludmilla, I haven't seen many ladies in these parts. I'd better get ready.. Links: Use the ingame downloader to get it. WARNING! Someone always fails to use spoiler tags. I do not recommend reading any further until you've played the mission.

@Mike__ could you please put this in spoiler tags?

Well, I've made some hacks on Doom3.exe in order to "convince" it to support 3Dc format (ATI1/BC4 and ATI2/BC5). Of course, all other texture formats still should work as well. I must admit that I haven't try these hacked Doom 3 executables with 3Dc normals, but I've ran both Doom 3 and TDM with these hacked executables, and everything seems was ok. Does anyone want to try? If yes, please notice that my archive consists of two executables: Doom3_LATC.exe and Doom3_RGTC.exe. Jean Michiel Paul van Waveren, id Software, and Ignacio Castaño, nVidia, think that LATC is more convenient than RGTC in some cases, so I provide both versions: LATC and RGTC. I must warn you: there is no warranty that my executables will work as it should, so use it on your own risk.

Earlier this year, GOG began publishing mods. Doom 3 already has the Phobos mod published. It would not be that much of a stretch to get The Dark Mod on there as a mod for Doom 3. Anyone’s thoughts on this?

Complaint From Players The player must pick up candles before extinguishing them, and then the player must remember to drop the candle. The player must drag a body before shouldering it (picking it up), and the player must remember to frob again to stop dragging the body. The player finds this annoying or easy to make mistakes. For players who ghost, some of them have the goal of returning objects back to their original positions. With the current "pick up, use item, and drop" system, the item might not return easily or at all to its original position. For example, a candlestick might bounce off its holder. (See player quotes at the bottom.) Bug Tracker https://bugs.thedarkmod.com/view.php?id=6316 Problems to Solve How can the "pick up" step be eliminated so that the player can directly use or interact with the item where it is in the game world? How can so much key pressing and mouse clicking be eliminated when the player wants to directly use an item? How can candles be extinguished and lanterns toggled off/on without first picking them up? How can bodies be shouldered without first dragging them? Solution Design Goals Make TDM easier for new players while also improving it for longtime players. Reduce tedious steps for common frob interactions. Make it intuitive so that menu settings are unnecessary. Do not introduce bugs or break the game. Terms frob -- the frob button action happens instantly. hold frob -- the frob button is held for 200ms before the action happens. (This can be changed via cvar: 200ms by default.) Proposed Solution Note: Some issues have been struckthrough to show changes since the patch has been updated. Change how frobbing works for bodies, candles, and lanterns. For bodies: Frob to shoulder (pick up) a body. Second frob to drop shouldered body, while allowing frob on doors, switches, etc. Hold frob (key down) to start drag, continue to hold frob (key down) to drag body, and then release frob (key up) to stop dragging body. Also, a body can be dragged immediately by holding frob and moving the mouse. For candles/lanterns: Frob to extinguish candles and toggle off/on lanterns. Hold frob to pick it up, and then frob again to drop. Frob to pick it up, and then frob again to drop. Hold frob to extinguish candles and toggle off/on lanterns. For food: Frob to pick it up, and then frob again to drop. Hold frob to eat food. For other items: No change. New cvar "tdm_frobhold_delay", default:"200" The frob hold delay (in ms) before drag or extinguish. Set to 0 for TDM v2.11 (and prior) behavior. Solution Benefits Bodies: New players will have less to learn to get started moving knocked out guards. With TDM v2.11 and earlier, some players have played several missions before realizing that they could shoulder a body instead of dragging it long distances. Frob to shoulder body matches Thief, so longtime Thief players will find it familiar. Second frob drops a shouldered body. Players still have the ability to both shoulder and drag bodies. Compatible with the new auto-search bodies feature. Dragging feels more natural -- just grab, hold, and drop with a single button press. There is no longer the need to press the button twice. Also, it's no longer possible to walk away from a body while unintentionally dragging it. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Candles: New players will have less to learn to get started extinguishing candles. With TDM v2.11 and earlier, some players didn't know they could extinguish candles by picking them up and using them. Instead, they resorted to throwing them to extinguish them or hiding them. Hold frob to extinguish a candle feels like "pinching" it out. Once a candle is picked up, players still have the ability to manipulate and use them the same way they are used to in TDM v2.11 and earlier. For players who ghost and have the goal of putting objects back to their original positions, they'll have an easier time and not have to deal with candles popping off their holders when trying to place them back carefully. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Solution Issues Bodies: Frob does not drop a shouldered body, so that might be unexpected for new players. This is also different than Thief where a second frob will drop a body. "Use Inv. Item" or "Drop Inv. Item" drops the body. This is the same as TDM v2.11 and earlier. This is the price to pay for being able to frob (open/close) doors while shouldering a body. Patch was updated to drop body on second frob, while allowing frob on doors, switches, etc. Candles: Picking up a candle or lantern requires a slight delay, because the player must hold the frob button. The player might unintentionally extinguish a candle while moving it if they hold down frob. The player will need to learn that holding frob will extinguish the candle. The player can change the delay period via the "tdm_frobhold_delay" cvar. Also, when the cvar is set to a delay of 0, the behavior matches TDM v2.11 and earlier, meaning the player would have to first "Frob/Interact" to pick up the candle and then press "Use Inv. Item" to extinguish it. Some players might unintentionally extinguish a candle when they are trying to move it or pick it up. They need to make sure to hold frob to initiate moving the candle. When a candle is unlit, it will highlight but do nothing on frob. That might confuse players. However, the player will likely learn after extinguishing several candles that an unlit candle still highlights. It makes sense that an already-extinguished candle cannot be extinguished on frob. The official "Training Mission" might need to have its instructions updated to correctly guide the player through candle manipulation training. Updating the training mission to include the hold frob to extinguish would probably be helpful. Similar Solutions In Fallout 4, frob uses an item and long-press frob picks it up. Goldwell's mission, "Accountant 2: New In Town", has candles that extinguish on frob without the need of picking them up first. Snatcher's TDM Modpack includes a "Blow / Ignite" item that allows the player to blow out candles Wesp5's Unofficial Patch provides a way to directly extinguish movable candles by frobbing. Demonstration Videos Note: The last two videos don't quite demonstrate the latest patch anymore. But the gist is the same. This feature proposal is best experienced in game, but some demonstration videos are better than nothing. The following videos show either a clear improvement or that the player is not slowed down with the change in controls. For example, "long-press" sounds long, but it really isn't. Video: Body Shouldering and Dragging The purpose of this video is to show that frob to shoulder a body is fast and long-press frob to drag a body is fast enough and accurate. Video: Long-Press Frob to Pick Up Candle The purpose of this video is to show how the long-press frob to pick up a candle isn't really much slower than regular frob. Video: Frob to Extinguish The purpose of this video -- if a bit contrived -- is to show the efficiency and precision of this proposed feature. The task in the video was for the player to as quickly and accurately as possible extinguish candles and put them back in their original positions. On the left, TDM v2.11 is shown. The player has to highlight each candle, press "Frob/Interact" to pick up, press "Use Inv. Item" to extinguish, make sure the candle is back in place, and finally press "Frob/Interact" to drop the candle. The result shows mistakes and candles getting misplaced. On the right, the proposed feature is shown. The player frobs to extinguish the candles. The result shows no mistakes and candles are kept in their original positions. Special Thanks @Wellingtoncrab was instrumental in improving this feature during its early stages. We had many discussions covering varying scenarios, pros, and cons, and how it would affect the gameplay and player experience. Originally, I had a completely different solution that added a special "use modifier" keybinding. He suggested the frob to use and long-press frob to pick up mechanics. I coded it up, gave it a try, and found it to be too good. Without his feedback and patience, this feature wouldn't be as good as it is. Thank you, @Wellingtoncrab! And, of note, @Wellingtoncrab hasn't been able to try it in game yet, because I'm using Linux and can't compile a Windows build for him. So, if this feature isn't good, that's my fault. Code Patch I'll post the code patch in another post below this one so that folks who compile TDM themselves can give this proposal a try in game. And, if you do, I look forward to your feedback! Player Complaints TTLG (2023-01-10) Player 1: TDM Forums (2021-03-13) Player 2: Player 3: TDM Forums (2023-06-17) Player 4: TDM Discord (2021-05-18) Player 5: TDM Discord (2023-02-14) Player 6: Player 7: Player 8:

Ulysses 2: Protecting the Flock By Sotha The mission starts some time after the events of Ulysses: Genesis, and continues the story of Ulysses. It is a medium sized mission with a focus on stealthy assassinations and hostage liberation. BUILD TIME: 12/2014 - 05/2015 CREDITS The TDM Community is thanked for steady supply of excellent mapping advice. Thanks goes also to everyone contributing to TDM! Voice Actors: Goldwell (as Goubert and Ulysses), Goldwell's Girlfriend (as Alis) Betatesters: Airship Ballet, Ryan101. Special Thanks to: Springheel and Melan (for proofreading). Story: Read & listen it in game. Link: https://drive.google.com/file/d/0BwR0ORZU5sraRGduUWlVRmtsX3c/view?usp=sharing Other: Spoilers: When discussing, please use spoiler tags, like this: [spoiler] Hidden text. [/spoiler] Mirrors: Could someone put this on TDM ingame downloader? Thanks!

The engine has a rather cool feature of rendering perfect planar reflections using mirrorRenderMap. But it is well known that this feature can be costly, because it requires the whole world (in the worst case) to be rendered twice. There has been a request to support lower-resolution rendering to reduce GPU load (5485). This feature is added in 2.14 with new material parameter mirrorResolutionFactor. For example, in order to make mirrored rendering with 1/3 x 1/3 of native resolution, you can write the following in your material: mirrorRenderMap mirrorResolutionFactor 0.333 Of course, this has a downside of making the mirrored view more blurred. But I've seen materials which explicitly blur the rendered view, distort it, or blend with other effects, etc. In these cases the lack of crispness of the reflections is not that ugly. The second change is related to the similar feature remoteRenderMap. There has been a way to specify resolution for this feature already, but it has some weird behavior and thus is now deprecated. If you have a square screen and want it to be rendered at 512 x 512 pixels, then you can write: remoteRenderMap remoteResolution 512 512 A slightly more convoluted way is to specify three numbers: remoteRenderMap remoteResolution 1024 1024 10.0 It means: render 10.0 pixels per 1 doom unit, but limit resolution by 1024 x 1024. So if the screen is of size 64 x 64 doom units, then it will be rendered at resolution 640 x 640, if it has size 16 x 16 units, then it will be rendered at resolution 160 x 160, but if it is stretched over 200 x 200 screen, then it will be rendered at resolution 1024 x 1024 because of the cap. There is also another limit for the remote screen resolution, which is applied at the end: see below. Finally, TDM 2.14 includes a few generic optimizations for these two features: Remote screen resolution is now capped by its size on the screen. So if a remote normally has 512 x 512 resolution but the player looks at it from far enough and it occupies only 100 x 100 pixels on the screen, then the rendering resolution is lowered to 128 x 128. This is controlled by cvar r_remoteLimitResolutionByScreenSize. Mirrored view image was previously copied at fullscreen resolution. Now the copy is limited to bounding rectangle/scissor, which means wasting less GPU bandwidth for mirrored surfaces which cover a small portion of the screen. Remember however, that all the resolution/scissor tweaks can only reduce GPU load. They don't simplify the work of the renderer frontend. So if the game is CPU-limited, none of this helps.

. THIEF'S DEN! Thief's Den is a re-release of the first Dark Mod tiny demo mission converted by greebo to work with the main Dark Mod release. Steal back your loot and incriminate the thief who double-crossed you! This was the first of the Thief's Den series in which you play Farrell. Read the notes below while you ... DOWNLOAD HERE. (3MB) Play time maybe 30 minutes to an hour first time. This FM needs Dark Mod Update 1.02 or later. This version has been modified to work with the Dark Mod released assets but is still essentially the same. The thief and thug models are updated and there is extra loot to find. IMPORTANT: If you already have the original stand-alone demo version of Thief's Den installed in the same Doom 3 installation then you must delete or move away the folders: doom3\thiefs_den and doom3\darkmod\fms\thiefs_den BEFORE you install this re-release. The original is still available as a stand-alone demo (needs Doom 3 but does not need Dark Mod installing) from http://wiki.thedarkmod.com/index.php?title=Thief%27s_Den

The Doom 3 engine has some architectural limitations: everything which can be rendered and lit must be a "render entity", and they are usually tied to game entities. For that reason, projected decals (i.e. the ones generated dynamically using the world geometry) are rendered with some lightweight processing, which excludes any possibility to interact with lights. The architecture of projected decals has been changed in TDM 2.14, and now they can interact with lights just like any simple func_static, for instance. What's the point in this change exactly? Well, it was requested by @Dragofer a few years ago, when he tried to add some depth to guards' footsteps on the snow by applying normal maps. Normal map is only used in lighting equations, thus it had no effect at all on the projected decals previously. From now on, if decal's material has interactions stages, it will be lit. So normal map and specular map finally make sense for projected decals just like it makes sense for static ones. The new behavior is enabled by default, but is a potentially breaking change. If we discover that some missions have become visually ugly because previously inactive interaction stages have become active, we'll try to fix missions. If there are too many issues, we'll have to restore legacy behavior by default and hide the new behavior behind material parameter. Right now it is possible to switch between two systems using cvar r_decalInteractive. Here is the testmap originally made by @Dragofer, with normal-mapped footsteps generated as projected decals: You might have noticed that footsteps are too bright where they overlap. That's because light interactions are additive in our engine, so each of the overlapping footsteps makes the image brighter. The usual way to avoid this is to make surfaces opaque, but then we'll get all the joy of depth fighting which is very hard to avoid in such a dynamic scenario. So yeah, while technically decal interactions are possible, unfortunately it does not necessarily mean that it works well in every imaginable scenario. P.S. The tracker issue is tracked as 5867.

Greetings everyone! I recently got into TDM and am already having a lot of fun playing through and ghosting missions. However, coming from Thief, I am mostly relying on the rules and my experience with that game, while there are clearly differences in how TDM works. Right now, there is talk in the ghosting discussion thread on TTLG to amend the ruleset and include clarifications pertaining to TDM. So I wanted to drop by and ask: is there an active TDM ghosting community already and have any rules for this playstyle been developed? I would also like to ask someone to take a look at the draft of this addendum to see whether everything looks correct: https://www.ttlg.com/forums/showthread.php?t=148487&page=16&p=2473352&viewfull=1#post2473352 Thanks!

I've read about this before here on the forums, even when the contest had just recently concluded, but reading about it in greater detail years later is certainly interesting. Thank you. It's a pity that it was mostly the marketing people who were involved on the Square Enix side, as I had the impression it was also the devs at EM that had played Requiem and all the other submitted missions and really liked them. I suppose it was as well, but the TDM team mostly heard from the marketing people. Yes, I wanted to note that as well. I even remember how the people over here in the TDM forums were sort of laughing at the fact that the results of the contest were favourable to TDM and had, in a sense, "proven" TDM as a worthy freeware successor to the Thief IP, with all the modding and mapping tools at one's disposal and so on, whereas Thief 4 or Thi4f or whatever Square Enix were calling it at that point, offered no such possibilities. The entire contest, while no doubt declared in good will and something I actually appreciated seeing, was such a self-own for Square Enix, ultimately to the detriment of them trying to bring back and market the reboot of an older IP. Even if Thief 2014 was a terrific reboot (which I doubt it would ever be), it would still have been hampered by people learning about modding being impossible, and looking to the trilogy and to TDM instead, to make new Thief-style stealth gaming content. Still, I appreciate they recognized the quality's of Moonbo's Requiem FM. Given many retrospectives I've seen over the years, gradually, on the 2014 Thief reboot attempt, one thing a surprising amount of them shared was noting how the game didn't feel cohesive in concept and execution, at any point. Not only not to the same level as the Thief trilogy, but also not even at the level when you consider it as an individual game, a new game on its own. Errant Signal, who's not some deep Thief fan, replayed the older games and played the reboot back when it came out, and made this exact observation already a decade ago. The reboot was just all over the place, in every department, felt clearly unfinished or rushed, and the most interesting story would be the behind the scenes at Eidos Montreal, on how mismanaged the entire project became over the course of several years. I think it's telling that, while even heavily discounted on GOG.com, Thief 2014 hasn't been selling well there, nor attracting much interest, whereas the original trilogy sells for figurative (and sometimes literal) cents on that same site - you can buy the whole trilogy for a smaller price than the reboot, which is kind of hilarious - and continues to have great sales and is considered one of the all-time bestsellers. Same here. I concur with demagogue that the actual Eidos Montreal devs behind Thief 2014, at least those who cared enough to make it at least somewhat presentable and playable - even if the actual game directors never got their act together and never decided on a consistent design approach - those would have been much more interesting to be in contact with, even regarding the fan mission contest. The sad truth of the matter is that all too many big publishers these days, especially those formed through larger mergers, like the Eidos buyout by Square Enix, are often marketing-first, interest in developers, and veteran players and new players alike, second. I still remember the sheer amount of money spent on pointless external marketing for Thief 2014, all the while that reboot attempt never really coalesced into anything that felt consistent (rather than throwing everything at the wall, in a panic, hoping something would stick), and was also plagued by all manner of technical issues. Just an overall embarassment, and I'm not surprised that even very lenient-leaning game retrospectives of that reboot attempt. The fact that the Thief IP has been sold away to Nordic Games and Embracer in more recent years, with Square Enix no longer caring about it and other older game IPs, also says a lot. Given the Embracer Group's own woes and bad decisions, I'm not sure any new development team will ever attempt another installment of Thief, even if it was a second reboot attempt.

For the people eager to play with the latest state of development, two things are provided: regular dev builds source code SVN repository Development builds are created once per a few weeks from the current trunk. They can be obtained via tdm_installer. Just run the installer, check "Get Custom Version" on the first page, then select proper version in "dev" folder on the second page. Name of any dev version looks like devXXXXX-YYYY, where XXXXX and YYYY are SVN revision numbers from which the build was created. The topmost version in the list is usually the most recent one. Note: unless otherwise specified, savegames are incompatible between any two versions of TDM! Programmers can obtain source code from SVN repository. Trunk can be checked out from here: https://svn.thedarkmod.com/publicsvn/darkmod_src/trunk/ SVN root is: https://svn.thedarkmod.com/publicsvn/darkmod_src Build instructions are provided inside repository. Note that while you can build executable from the SVN repository, TDM installation of compatible version is required to run it. Official TDM releases are compatible with source code archives provided on the website, and also with corresponding release tags in SVN. A dev build is compatible with SVN trunk of revision YYYY, where YYYY is the second number in its version (as described above). If you only want to experiment with the latest trunk, using the latest dev build gives you the maximum chance of success. P.S. Needless to say, all of this comes with no support. Although we would be glad if you catch and report bugs before the next beta phase starts

Glad I came to the forums to check out more details about this mission after playing. I was a little confused by a Bikerdude FM only taking 10mins to run through haha. Knowing it's a tech/build demo means I'm not going to spend the next hour or so looping through it trying to figure out if I missed a secret Krampus area or encounter xD.

You can ask people to test your mission here, but the beta tresting should be in this other section: https://forums.thedarkmod.com/index.php?/forum/59-tdm-mission-beta-testing/ Read also: I think it's so that there are no spoilers in view for new regular players.

I was cautious because I didn't want it to be perceived that I was using The Dark Mod Forums to promote my mod but I get your point - we're all in this together. Over the years we've had a few different team members, but for the past few months it's mostly been just me and one other person. The Thieves Guild project started a long time ago, when Rune was still popular. We liked Thief and we also liked Rune so we combined the two games together. We incorporated all of the cloak & dagger elements from Thief but we also wanted our thief to be able to fight like a Viking. Don't get me wrong, it's definitely a thief/stealth game. Through the 20 or so missions, we tell a story about a thief working for the local thieves' guild, operating within a dark and corrupt city. Under the cover of night, you are assigned a series of dangerous missions - success is rewarded with valuable items, increased wealth, and greater prestige from within the guild. To survive, you must move silently through shadowed alleyways, scale heavily guarded buildings, bypass deadly traps, and pick stubborn locks - all while avoiding detection by the city watch and roaming night patrols. One misstep can mean capture, failure, or worse. In this city, survival belongs to those who remain unseen. Thieves Guild was designed to be played on a computer using a keyboard and mouse. Rune uses the Unreal Engine 1. I'm glad you liked what you saw in "The Dark Side Edition Trailer". This video is a walk-through of The Training Mission.

============== -= IRIS =- ============== WELLINGTONCRAB TDM v 2.11 REQ Ver. 1.3 *For Maureen* -=- "Carry the light of the Builder, Brother. Unto its end." -Valediction of the Devoted "What year is this? Am I dreaming?" -Plea of the Thief Dear Iris, I am old and broken. When we were young it felt like the words came easily. Now I find the ink has long dried on the pen and I'm as wanting for words as coin in my purse. I can tell we are nearing the end of the tale; time enough for one more job before the curtain call... ============== -Installation- Requires minimum version of TDM 2.11 **Dev build dev17056-10800 (2.13) fixes several visual effects which have been broken in the mission since the release of 2.11. For that reason playing with that version or later is currently recommended** -Iris does not support mods or the Unofficial Patch- Download and place the following .pk4 into you FMs directory: Iris Download ============== *Thank you for playing. Iris is a large mission which can either take as quickly or as long as you are compelled to play. I hope someone out there enjoys it and this initial release is not completely busted - I tried the best I could!* *Iris both is and isn't what it seems. If commenting please use spoiler tags where appropriate. If you are not certain if it would be appropriate a good assumption would be to use a spoiler tag* *Support TDM by rating missions on Thief Guild: https://www.thiefguild.com/* ============== WITH LASTING GRATITUDE: OBSTORTTE - Whose gameplay scripts from his thread laid the foundation which made the mission seem like something I could even pull off at all. Also fantastic tutorial videos! DRAGOFER - Who built upon that foundation and made it shine even brighter! And whom also provided immeasurable quantities of help and encouragement the past couple years on the TDM discord. ORBWEAVER & GIGAGOOGA - For generously offering their ambient music up for use. EPIFIRE - Who lent me his fine trash and trash receptacle models. AMADEUS - Who was the first person who wasn't me to play the damn thing and provided his excellent editorial services to improving the readers experience playing TESTERS AND TROUBLESHOOTERS: AMADEUS * DATISWOUS * SPOOKS * ALUMINUMHASTE * JAXA * JACKFARMER * WESP5 * ATE0ATE * MADTAFFER * STGATILOV * DRAGOFER * KINGSAL * KLATREMUS - What can I possibly say? Playing this thing over and over again could not have been easy. Deepest thanks and all apologies. -=THANKS TO ALL ON THE TDM DISCORD AND FORUM=- ==SEE README.TXT FOR ADDITIONAL ATTRIBUTIONS & INFORMATION== HONORABLE MENTION: GOLDWELL - If I hadn't by chance stumbled into Northdale back in 2018/2019 I would probably still be trying to get this thing to work in TDS, which means it probably would not exist - though more details on that in readme. ============== Boring Technical Information: *Iris is a performance intensive mission and I recommend a GTX 1060 or equivalent. I find the performance similar to other demanding TDM missions on my machine, but mileage may vary and my apologies if this prevents anyone from enjoying the mission.* *Iris heavily modifies the behavior of AI in the game, how they relate/respond to each other and the player. So they may act even stranger than they do typically in TDM. Feedback on this is useful - as it can potentially be improved and expanded upon in future patches.* -=- This is my first release and it has been a long time coming! If I forgot anything please let me know! God Speed. 2.10 Features Used:

We know. There is already a support topic for that. https://forums.thedarkmod.com/index.php?/topic/22533-tdm-for-diii4a-support-topic/ And earlier: https://forums.thedarkmod.com/index.php?/topic/16672-trying-to-run-tdm-on-android/ And other systems: https://wiki.thedarkmod.com/index.php?title=Installer_and_Manual_Installation#Other_Systems

I guess this is basic stuff for you talented model-boys but now I've trudged for several hours without results and from what I have read in several forums/threads, it's even not that trivial. Therefore I dare to start a thread... I've download some models from the web but these come in some new and fancy format; (FBX, USD etc) not exactly the old and brittle format that we use in TDM So to import these into DarkRadiant I need to convert these to lwo or ASE, right? How do people go about this? I have tried to: - install Blender 5.0 and added an ASE-exporter plugin. Blender actually puts out an ASE-file but as I try to open it in DR, the model is only showed as that checkerboard error-box. Do I need to tinker with the model in a text editor first? I read something about changing something about a BITMAP-line... - use an ancient version (7.0) version of Lightwave but that program cannot even open the files (Not surprising)...

Hypothetically if Ray casting was used to bake efficiency into the brushwork itself it would make the penalty of a forward renderers lighting under id Tech 4 more agreeable. If Gemini AI is even half right this state of content efficiency would make id Tech 4 10-20 times more efficient per watt than Unreal Engine 5. For mobile platforms you are sitting on one of the best game engines on Earth. Of course I've yet to find a mapper that's willing to spend 3 to 4 years refactoring an entire commercial products slop. From the 13 objects overlapping in space, to decals hidden behind walls, entire rooms unused, brush faces behind other brushes. I'm the first. The ability to automate what I've done even just 90% would take the weaknesses of id Tech 4 and turn them into strengths. There is nothing faster than precomputation. If you can reverse engineer the flexibility of modern game engines without the per frame overhead it's going to curbstomp Unreal Engine 6 in raw efficiency. You also would be taking the former Chief Technical Officer of Metas core design and making it achieve what hasn't yet by industry. They probably would be knocking at your door with offers to commercialize or at minimum rush to replicate your work. They are all in in Alternate Reality Virtual Reality. Too bad their 5% GPU utilization offended one of their best employees. It's because thermal throttling boost behavior modern game engine inefficiencies and battery life. The Dark Mod could be a technology demonstrator that can do things modern game engines super can't. My texture pack 60GB+ (Prey 2006 Remake) is entirely custom. 5120x5120, 7168x7168, 9216x9216, 10,240x10240 and beyond. My texel resolution is extremely uniform and optimized at point blank mip map 0 for human vision. So it's literally a 2002 game engine beating id Tech 8 in asset resolution. Texture streaming doesn't like custom resolutions. Nor do development teams. It's just another way id Tech 4 is superior to modern game engines in a not abstract way. The general public is not aware of how inefficient modern game engines are or how much technical debt they tolerate. It's a more interesting topic to an engineer than a entertainment seeking random individual admittedly. There are inherent advantages to the older methods that are incredibly underappreciated. If I can motivate some of the software engineers to develop this capability that would be rather useful. Especially since it's already in part been done to bake shadows into Doom 3. Which in part defeat the purpose of unified lighting. But it's an existence proof. If you would like to see my 60GB file in its development state that can be arranged. But you also better have 24GBs of video memory. Most people will opt for lower resolution packs when generated by my Python scripts. The ability to hit per pixel 4k point blank is not just overkill. It's a measuring rubric.

I'll probably try Thief 3 for the first time in forever after snobel finishes making a Linux version of Sneaky Upgrade. https://www.ttlg.com/forums/showthread.php?t=138607&page=82 https://www.ttlg.com/forums/showthread.php?t=153010

Sorry, I think it should be #include "guis/mainmenu_briefing_preamble.gui" At least that's what I see in some existing gui files: the guis subdirectory is important. I think it is irrelevant. Just like in C/C++, C preprocessor runs before the main language and does simple textual transforms only. It does not know the main language at all. It understands only directives (lines starting from #) and some strings which were #define-d beforehand. After preprocessor is over, the main language starts working, and it only sees what is produced by preprocessor, it has no way to know about the directives. So in the first example it will check if the current mission is indeed 1. If it is not, it will remove the section inside #if from the source code, the Doom 3 GUI language will not even know it was there. If it is, then the section will survive. Then it will handle the #include, which basically says "please copy/paste the contents of that file here". In the second example, the preprocessor has no freaking idea what the first line means. It is not a directive. So it will leave it as is, regardless of which mission it runs now. The it will handle the #include, i.e. copy/paste the file contents regardless of which mission is now. Given that Doom 3 GUi language only allows to use if-s inside event handlers, the second approach is only valid if you use it inside a single script event handler. Which is often too small. But then the parts which are not specific to either mission will be included/present twice, no? In fact, if #include sounds complicated to you, you can just do everything without it. Imagine that file2.gui contains the full GUI code for mission 1, and file2.gui contains the full GUI code for mission 2. Just put contents of both files into mainmenu_briefing.gui surrounded by appropriate #if MM_CURRENTMISSION == ? and #endif. Preprocessor will process each #if and drop the ones which are false. Since #include is just a command for preprocessor to copy/paste, it works effectively the same way. It just allows you to have one mission per file instead of one megafile with the stuff for all missions (well, as long as paths are correct).

A set of some 200 missions is a lot to sift through to find what one likes. I never used your site but if it provided functionality to search missions for parameters like approximate playtime, series v standalone, and tags like undead, spiders, mansion, city, etc, then it sounds plenty useful. Can the functionality be incorporated into the main web page? Perhaps even integrated to fetch underlying data from the wiki (so that trusted editors can keep the parameters up to date)?

KARANTIIN In KARANTIIN you can use anything you find. Manage your inventory, monitor your vital stats (food, thirst, health, bleeding, radiation,infection), search for supplies, and fight to stay alive. The game features an open world and two additional game modes. https://karantiin.itch.io/karantiin A little curiosity to play in the Browser https://doompdf.pages.dev/doom.pdf