Search the Community

Inn Business It's business, at an inn, over three nights. Development screenshots: Download: https://drive.google...dit?usp=sharing Update 1.48 uploaded March 8th, 2014, one change: patches key rarely not being frobable in one of its possible spots Big thanks to my beta testers: Airship Ballet, Kyyrma and AluminumHaste! Development supporters of note: Sotha, Springheel and Obsttorte. Also thanks Sotha, for urinating in my mission. ;-) And thanks Kyyrma for the title screen! My appreciation to all forum/wiki contributors, without whom, this wouldn't exist. Thanks to positive commenters on my previous mission too, extra motivation helps! :-) Note this uses campaign features, what you use the first night, impacts subsequent nights. And to quote a tester, "...the level is maybe best experienced in more than one sitting". If you do pause between nights, please be sure to save, you can't begin partway through effectively. (If you accidentally start a night you already completed, just fail the kill objective to switch to another night.) If your frame rates are too low facing the cemetery, please reduce your "Object Details LOD" setting. It was designed with "AI Vision" set to "Forgiving", to be able to sneak through with minimal reactions, if you want more/less, adjust your settings accordingly. There are several random, conditional aspects, and ways of going about things, so others might have slightly different experiences. Post here if you discover hidden objectives for extra points! My condolences to loot completionists, I made a bit on the third night hard, you've got your challenge cut out for you! Speaking of which, there's a TDM bug that mission complete totals too high, here are the real amounts per night: 2026/970/202. Oh, there is something that in the U.S. would be rated PG, in case you play with kids in earshot. I hope you enjoy playing it, feel free to let me know you did, and I'm glad to respond to inquiries (like how stuff was done, nothing was scripted). (Note which night you are referring to if it's something specific.) (Please remember spoiler tags to not expose things meant to be discovered by playing.) Like so: [spoiler]secrets[/spoiler] Developed for TDM 2.01. PS: Thiefette, good news, no spiders! Springheel, if you find an optional objective you can skip...you might find it immersion breaking. Others, no undead! There are a couple other interactive critters though. :-) Edit note: Some posts below were from users of an unreleased version of TDM 2.02 which broke several things, they do not reflect regular game-play.

Many thanks for bringing this to TDM: it looks great!

I remember I was surprised it couldn't run Invisible, Inc. properly. But I'll give it a try later.

I guess I could try to make it run on this: https://www.notebookcheck.nl/Fujitsu-Siemens-Lifebook-P1620.8269.0.html Not sure if an Intel GMA 950 will be enough..

That is one reason. That is 2 more reasons. You'd like a script that, if you had to run it again, would "do the right thing". Unfortunately, that right thing is very hard to program, and needs IMHO to be both bidirectional and with a better method of string version control, to support both the FM author's updates and potentially multiple translators. Yes, another reason. Currently, it is my understanding that updating an FM (from the non-converted copy) and running the conversion script again causes mis-alignment of newly-generated #str values and previous .lang #str values. Another important cause of "nobody is making these language packs" is that Dark Radiant at best tolerates converted FMs. It offers no special translation support, as expressed in this code comment: "...we don't have any support for parsing the mod-specific translation data...." [from DR's DifficultySettingsManager.cpp]. That's where we are now. So officially give up on FM Western translations? Or improve the #str system to make it work for everyone? Or invent a new system? A new system. What would that look like to the FM author? To a non-author translator

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

I wanted to internationalise The Hare in the Snare before I released it but I couldn't get the scripts to work and had some other questions as well. I posted about it Newbie Dark Radiant Questions and nobody replied, so I gave up. It being my first FM I didn't feel confident digging into it and just wanted to release the FM. I just got the impression that it wasn't a big deal and nobody cared about it. From memory, the script worked once but I needed to re-run it and just couldn't get it to work. It's also Perl which nobody really uses anymore. I think I recommended to a 'I want to help' person to convert it to Python, but that didn't go anywhere. I don't think you need the script though if you internationalise from the very beginning (i.e. create your own dictionaries). At the end of the day it's extra work for the mapper and if it adds too much overhead (i.e. is broken or is a PITA) then nobody is going to use it. https://wiki.thedarkmod.com/index.php?title=Internationalization

I've seen fun workarounds like that in other game modding as well. Years ago, maybe even a decade, some fella who was making a mod for Mount & Blade over at the Taleworlds forums revealed that he put invisible human NPCs on the backs of regular horse NPCs, then put the horse NPCs inside a horse corral he built for one of his mod's locations/scenes and then did some minor scripting, so the horses with invisible riders would wander around the corral. The end result was that it looked they're doing this of their own will, rather than an NPC rider being scripted to ride around the corral slowly. Necessity is the mother of invention. I don't know about the newest Mount & Blade game, but the first generation ones (2008-2022) apparently had some sort of hardcoded issue back in the earlier years, where if you left a horse NPC without a rider in its saddle, the horses would just stand around and wait and you couldn't get them to move around. Placing an invisible rider in their saddles suddenly made it viable again, at least for background scenes, of riderless horses wandering around, for added atmosphere. First generation M&B presumed you'd mostly be seeing horses in movement with riders, and the only horses-wandering-loosely animations and scripting were done for situations when the rider was knocked off their horse or dismounted in the middle of a battle. Hence the really odd workarounds. So, an invisible NPC trick might not be out of the question in TDM, even though you could probably still bump into it, despite its invisibility.

HAZARD PAY 1.5 [ TDM 2.10 REQUIRED] AUTHOR'S NOTE ================================ Hello! Its been a while since I’ve released something so I figured I'd join the Connections Competition and make a stand-alone adventure to try out the new 2.10 features. ================================ DESCRIPTION ================================ This is a medium size mission with an emphasis on adventure and stealth combat. !!! WARNING !!! I recommend NORMAL if you're looking to cruise and HARD / EXPERT if you're looking to sweat a little. EXPERT uses a prototype save room mechanic and is very tough. ================================ PLAY IT ================================ Requires TDM 2.10 DOWNLOAD HAZARD 1.6 ================================ PLAYTHROUGH ================================ Courtesy of Filizitas Part 1 Part2 Part3 ================================ CREDITS: VOCALS courtesy of the very talented : Goldwell, Mortem Desino, and Yandros. TESTING by the diligent and awesome : Amadeus, Epifire, Goldwell, Mike_A, and Moonbo ADDITIONAL SCRIPTING provided by the very talented Dragofer ADDITIONAL AUDIO by the masterful Goldwell PLAYTHROUGH by Filizitas

After some amount of work I'm happy to be able to share my Christmas gift for TDM! Or at least half of it, considering the other half is still only in design phase. I created an addon that implements detailed player functionality, inspired by the first DeusEx game (The Conspiracy). It's NOT a mission script but an addon, meaning you place the pk4 in your TDM directory to enable the system and it will automatically work in each and every FM. Note that due to using tdm_user_addons.script / user_addon_init() it may disable or get disabled by other addons you have installed... this is a design limitation which can hopefully be lifted at some point in the future. This plugin will be included in my cyberpunk total conversion The Dark Module and automatically active with it, but first I shall design it and make it available as a small independent addon for vanilla TDM. In the current initial release it implements just per-limb damage; The upcoming plan is to add a skill / augmentation system, allowing the player to use loot as skill points to enhance various body parts and gain new or improved abilities. Due to the scripting system being very limited in what it lets me modify, I'm still gathering documentation on how to implement those skills and which I can have. So until then detailed body damage with penalties remains the only part that's theoretically finished so far (further improvements are required here too)... including a HUD component above the lightgem showing the status of each body part: Green = full health, yellow = half health, red = (close to) no health, black = no health left. The individual limbs available: Head, Torso, Left Arm, Right Arm, Left Leg, Right Leg... arms and legs work in unity however. They each take damage with the player as well as healing together with them. The more damaged a group is, the more a respective penalty is applied to the player. Groups and penalties include: Head: When the head is damaged, the player begins to get dizzy and has their vision impaired. Currently the only effect replicates the flashbomb, causing white dots to appear around the player and disrupt their view until the head is healed. As the player can't live without a head, reaching 0 will cause instant death. More effects are possible and pending. Torso: Damage to the torso translates to damage to the cloak, increasing the player's lightgem and rendering them more visible even in dark spots. As the player can't live without a torso, reaching 0 will cause instant death. Given script limitations I'm unable to simulate lung damage and decrease / limit the amount of air the player has. Arms: Arm damage makes it difficult for the player to hold items: In-world objects being held will probabilistically get dropped, more often the worse your arms are hurt. When both arms reach 0 health, the player can no longer pick up anything in the world without instantly dropping it... you also become unable to use any weapons. Due to limitations in the scripting system, I'm unable to decrease the speed or accuracy of the blackjack / sword / bow as was desired. Legs: As expected leg damage will make the player walk more slowly. It was desired that when one leg is lost the player can no longer jump, whereas when both legs are gone you remain stuck in crouch mode until healed... due to limitations in the scripting system this part is also not possible at the moment. A crude limitation is the fact that limb damage is primarily based on the direction the player is walking toward... for example, increased likelihood of suffering damage to your right arm and leg if strafing right the moment you take the damage. The script system doesn't let you extract the vector direction of the last damage event, thus I can't use the real direction the hit came from when calculating which body part should absorb the most health loss. This means that even if an arrow comes from above and hits the player's head area, the player will only take damage to the legs if they're falling downward the moment they got hit... for the time being this provides a bare minimum amount of realism but is a very bitter implementation. For this reason it would be greatly appreciated if any of the code developers could join this discussion and verify if they can help with adding the necessary hooks to external scripts: With 2.09 getting periodic beta releases at this point in time, it would be a great opportunity to make changes to the builtin player script that allow an external function to modify more player variables. This includes the efficiency of weapons, if the player is allowed to jump or forced to always crouch, and I'd also really appreciate a hook to manipulate the breath so air can be lowered as if the player is underwater. I understand other priorities exist or if the work may be considered too much, however this would help in being able to finish this mod with the proper functionality and planned skill set. In the meantime let me know what you think of this idea and how I went about it! So far no new assets are included except the GUI graphics: Everything is done with less than 250 lines of script which I'd say is a good achievement I've attached the pk4 and since it's so lightweight I'll also add the main script straight in this post. player_damage_1.0.pk4 #define DAMAGE_WAIT 0.0166667 #define EXPOSURE_ARM_LEFT 2 #define EXPOSURE_ARM_RIGHT 2 #define EXPOSURE_LEG_LEFT 2 #define EXPOSURE_LEG_RIGHT 2 #define EXPOSURE_HEAD 3 #define EXPOSURE_TORSO 1 #define PENALTY_TORSO_LIGHTGEM 4 player self; float damage_gui; boolean dizzy; entity dizzy_particles; float bound(float val, float min, float max) { if(val < min) return min; if(val > max) return max; return val; } // Range based probability: Calculates a probability per frame independent of wait time (0 - 1 range at 1 chance per second) boolean prob(float x) { return sys.random(1) > x && sys.random(1) < DAMAGE_WAIT; } // Directional exposure calculator float dex(vector dir, float ex_front, float ex_back, float ex_right, float ex_left, float ex_up, float ex_down) { float maxvel = 100; float dir_front = bound(dir_x / maxvel, 0, 1) * ex_front; float dir_back = bound(-dir_x / maxvel, 0, 1) * ex_back; float dir_right = bound(dir_y / maxvel, 0, 1) * ex_right; float dir_left = bound(-dir_y / maxvel, 0, 1) * ex_left; float dir_up = bound(dir_z / maxvel, 0, 1) * ex_up; float dir_down = bound(-dir_z / maxvel, 0, 1) * ex_down; return dir_front + dir_back + dir_right + dir_left + dir_up + dir_down; } void player_damage_update_arm(float dmg_l, float dmg_r) { float hl_l = self.getFloatKey("health_arm_left"); float hl_r = self.getFloatKey("health_arm_right"); float hl = (hl_l + hl_r) / 2; if(dmg_l != 0 || dmg_r != 0) { hl_l = bound(hl_l - dmg_l, 0, 1); hl_r = bound(hl_r - dmg_r, 0, 1); hl = (hl_l + hl_r) / 2; self.setKey("health_arm_left", hl_l); self.setKey("health_arm_right", hl_r); self.setGuiFloat(damage_gui, "PlayerDamage_ItemArmLeft", hl_l); self.setGuiFloat(damage_gui, "PlayerDamage_ItemArmRight", hl_r); // Penalty #1: Disable the weapon once the arm are damaged to minimum health if(hl == 0) { self.selectWeapon(WEAPON_UNARMED); self.disableWeapon(); } else { self.enableWeapon(); } } // Penalty #2: Probabilistically drop held items based on arm damage if(hl == 0 || prob(hl)) if(self.heldEntity() != $null_entity) self.holdEntity($null_entity); } void player_damage_update_leg(float dmg_l, float dmg_r) { float hl_l = self.getFloatKey("health_leg_left"); float hl_r = self.getFloatKey("health_leg_right"); float hl = (hl_l + hl_r) / 2; if(dmg_l != 0 || dmg_r != 0) { hl_l = bound(hl_l - dmg_l, 0, 1); hl_r = bound(hl_r - dmg_r, 0, 1); hl = (hl_l + hl_r) / 2; self.setKey("health_leg_left", hl_l); self.setKey("health_leg_right", hl_r); self.setGuiFloat(damage_gui, "PlayerDamage_ItemLegLeft", hl_l); self.setGuiFloat(damage_gui, "PlayerDamage_ItemLegRight", hl_r); // #Penalty #1: Make movement slower self.setHinderance("health", 0.25 + hl * 0.75, 1); } } void player_damage_update_head(float dmg) { float hl = self.getFloatKey("health_head"); float time_current = sys.getTime(); if(dmg != 0) { hl = bound(hl - dmg, 0, 1); self.setKey("health_head", hl); self.setGuiFloat(damage_gui, "PlayerDamage_ItemHead", hl); // Penalty #1: Without a head the player dies if(hl == 0) self.damage(self, self, self.getOrigin(), "damage_suicide", 1); // Penalty #2: Simulate dizzyness starting at half health if(hl <= 0.5) { if(!dizzy) { dizzy_particles = sys.spawn("func_emitter"); dizzy_particles.setModel("flashbomb.prt"); dizzy_particles.setOrigin(self.getEyePos()); dizzy_particles.bind(self); dizzy = true; } } else { if(dizzy) { dizzy_particles.remove(); dizzy = false; } } } } void player_damage_update_torso(float dmg) { float hl = self.getFloatKey("health_torso"); if(dmg != 0) { hl = bound(hl - dmg, 0, 1); self.setKey("health_torso", hl); self.setGuiFloat(damage_gui, "PlayerDamage_ItemTorso", hl); // Penalty #1: Without a torso the player dies if(hl == 0) self.damage(self, self, self.getOrigin(), "damage_suicide", 1); // Penalty #2: Torso damage negatively affects the lightgem self.setLightgemModifier("damage", (1 - hl) * PENALTY_TORSO_LIGHTGEM); } } void player_damage() { sys.waitFrame(); self = $player1; damage_gui = self.createOverlay("guis/player_damage.gui", 1); float health_old = 100; // Init by sending a heal event filling the limbs to full health player_damage_update_arm(-1, -1); player_damage_update_leg(-1, -1); player_damage_update_head(-1); player_damage_update_torso(-1); while(1) { // sys.waitFrame(); sys.wait(DAMAGE_WAIT); float health_current = self.getHealth(); float dmg = (health_old - health_current) / 100; float dmg_arm_left = dmg * EXPOSURE_ARM_LEFT; float dmg_arm_right = dmg * EXPOSURE_ARM_RIGHT; float dmg_leg_left = dmg * EXPOSURE_LEG_LEFT; float dmg_leg_right = dmg * EXPOSURE_LEG_RIGHT; float dmg_head = dmg * EXPOSURE_HEAD; float dmg_torso = dmg * EXPOSURE_TORSO; // If this is damage and not healing, apply directional damage to each limb if(dmg > 0) { // Currently we estimate damage direction based on the player's velocity, we should fetch the real direction of a damage event when this becomes possible vector dir = self.getMove(); vector ang = self.getViewAngles(); // Protections based on the player's position and relation to the environment // protection_look: 1 when looking up, 0 when looking down // protection_low: Higher as the lower part of the body is exposed float protection_look = 1 - (90 + ang_x) / 180; float protection_low = 1; if(self.AI_CROUCH) protection_low = 0; else if(self.AI_ONGROUND) protection_low = 0.75; // Use the dex function to calculate directional exposure patterns, direction order: Front, back, right, left, up, down // Arms: Somewhat likely to be hit, no added protection // Legs: Somewhat likely to be hit, added protection when the player is crouching // Head: Unlikely to be hit, added protection when the player is looking down // Torso: Likely to be hit, no added protection float exposure_arm_left = bound(sys.random(0.375) + dex(dir, 0.5, 0.25, 0.0, 1.0, 0.0, 0.25), 0, 1); float exposure_arm_right = bound(sys.random(0.375) + dex(dir, 0.5, 0.25, 1.0, 0.0, 0.0, 0.25), 0, 1); float exposure_leg_left = bound(sys.random(0.375) + dex(dir, 0.75, 0.5, 0.0, 0.5, 0.0, 1.0) * protection_low, 0, 1); float exposure_leg_right = bound(sys.random(0.375) + dex(dir, 0.75, 0.5, 0.5, 0.0, 0.0, 1.0) * protection_low, 0, 1); float exposure_head = bound(sys.random(0.25) + dex(dir, 0.25, 0.75, 0.5, 0.5, 1.0, 0.0) * protection_look, 0, 1); float exposure_torso = bound(sys.random(0.5) + dex(dir, 0.75, 1.0, 0.0, 0.0, 0.0, 0.0), 0, 1); // Apply the exposure to damage, multiplied to simulate the sensitivity / resistance of each limb dmg_arm_left = exposure_arm_left * dmg * EXPOSURE_ARM_LEFT; dmg_arm_right = exposure_arm_right * dmg * EXPOSURE_ARM_RIGHT; dmg_leg_left = exposure_leg_left * dmg * EXPOSURE_LEG_LEFT; dmg_leg_right = exposure_leg_right * dmg * EXPOSURE_LEG_RIGHT; dmg_head = exposure_head * dmg * EXPOSURE_HEAD; dmg_torso = exposure_torso * dmg * EXPOSURE_TORSO; } player_damage_update_arm(dmg_arm_left, dmg_arm_right); player_damage_update_leg(dmg_leg_left, dmg_leg_right); player_damage_update_head(dmg_head); player_damage_update_torso(dmg_torso); health_old = health_current; } }

Is it not possibly to just add a small script to these missions that only does this: #define ARROW_ZOOMDELAY 3 //VOLTA MOD Edit: I haven't installed the newest tdm version yet, so I guess this might be complete nonsense..

So what is the training mission for then? Apparently it's not showing standard tdm gameplay necessarily. Edit: Maybe it's not really worth it to keep discussing this. I mean I don't want to derail too much what the topic is actually for.

I totally agree that players usually don't care whether some non-customizable constant like bow shoot time is same as in core or not, as long as the mission plays well. This is a problem only for TDM development. But I don't know a proper way of solving this: mappers usually want to customize something "right now", and waiting for new release is rarely an option. And often customizations are not implemented until someone really wants them (or right away uses them), so that's also the chicken-and-egg problem here.

You are confusing how the core game is packaged with a "standard". The “standard” TDM experience imo would actually be however the mission author intended the mission to be played. There are lots of different types of missions which as experiences deviate from anything packaged in the core game. You are not owed a disclaimer.

Hello taffers, The campaign "Hidden Hands: Blood & Metal" consisting of five missions is now basically ready for beta testing (the briefing videos are missing and there are still some "real" speakers missing, at the moment there are tentative robot voices in these places, hope to replace them in the next two or three weeks). Unfortunately, the project has become somewhat more extensive than originally planned. It took me about two hours to test each mission. So you should allow at least12 hours for all five missions on the first run. Beta testing shall start at the beginning/middle of next week. The difficulty level is somewhere between "The Anomaly" and "The Lost Citadel". Some things are easier, others are not, but proper exploration and usage of the available resources/objects should always pave the way to success. Sign in here, if you are taff enough! Jack Testing thread:

Early TDM 15yr anniversary contest entry?

Why the sad face? Also, Kingsal would be better able to explain the changes, and he actually modified the script so that it is more TDM-friendly. This modified script is in Eye on the Prize and Moongate Ruckus

So id recently started dablling with linux derivatives as a main OS again after holding off for years due to some problems running my hardware when i stumbled upon Solus. Solus is a distro that was developed independently from mainstream linux (from the ground up) and uses its own desktop model called budgie (also comes with a plasma gnome and XFCE dektop). Solus uses its own package manager called eopkg and it handles flatpak and snap as well. I been very impressed with it so far as things just worked out of the box for most parts, only real problem i had was getting steam running which turned out to be due to my machine loosing internet connection when it was installing it which left some broken files and after an uninstall / reinstall it worked quite nicely. one warning though Solus comes with a linux steam integration tool which while cool has a rather annoying bug if you try to use the intercept library no games will launch (well alledgedly one will and it was made for that because it wont launch without it on groan...), so do not enable that setting. lutris also works pretty much from the get go though i had to do some reading to find out how to get it to synch up with steam (steam profile must be set to public in pretty much everything). So how does games work on it, well actually rather well proton has made strides in getting even the newest games to run on steam and the only games i so far have not been able to run is the division 1 and 2 but this a'int a problem with steam but with ubisoft connect which crashes and might get fixed in the future (damn launchers...). So far i been plaing baldurs gate 3, callisto protocol, crysis remastered trilogy, DOOM, starfield and a wealth of older games with it and no problems besides having to run baldurs gate in DX11 mode (not really sure why the vulkan driver is not working for this game on linux ???). I might actually step onto the linux platform for good when win10 goes out of support, and ill probably stay with solus since it is less cluttered than most other distros and main packages are built explicitly for it which again means stability as you dont get puckered into installing something which was newer meant for your OS (yeah i f.... up numerous linux distros over the years because you can install pretty much what you like even if it breaks everything, not so with Solus). This does not mean you cant have some nice app you need which was built against say gnome because you sit on a plasma desktop, you absolutely can but they are only avaliable as snap / flatpaks so each of them run in its own sandbox with all the dependencies only avaliable to said program and keept isolated from the system. try it out :) https://getsol.us/download/

Alright, so, I'm a Texture Artist myself for more than 20 years, which means I know what I'm talking about, but my word isn't law at all, remember that. I've worked (mostly as mods, I am a professional but I much prefer being a freelance) with old DX8 games up to DX12. When it comes to Detail Textures, for my workflow, I never ever use it except rarely when it's actually good (which, I emphasize on "rarely"). This is one reason I thought mentioning that I worked with DX8 was logical. One of the few times it's good is when you make a game that can't have textures higher than what would be average today, such as, World Textures at 1024x1024. Making detail textures for ANY (World, Model) textures that are lower than 128x128 is generally appealable. Another is when the game has no other, much better options for texturing, such as Normal Maps and Parallax Mapping. Personally, I think having Detail Textures for The Dark Mod is arguably pointless. I know TDM never had a model and texture update since 2010 or so, but most textures do seem to at least be 1024x1024, if there's any world texture that's lower than 256x256, I might understand the need of Detail Textures. Now, if this was a game meant to be made in 2024 with 2020+ standards, I would say that we should not care about the "strain" high resolution textures add, however, I do have a better proposition: Mipmaps. There are many games, mostly old than new ones, that use mipmaps not just for its general purpose but also to act as a "downscaler". With that in mind, you boys can add a "Texture Resolution" option that goes from Low to High, or even Lowest to Highest. As an example, we can add a 2048x2048 (or even 4096x4096) world texture that, if set to Lowest, it would use the smallest Mipmap the texture was made with, which depends on how the artist did it, could be a multiplication of 1x1 or 4x4. One problem with this is that, while it will help in the game with people who have less VRAM than usual these days, it won't help with the size. 4096x4096 is 4096x4096, that's about 32mb compressed with DXT1 (which is not something TDM can use, DXT is for DirectX, sadly I do not know how OpenGL compresses its textures). I would much rather prefer the option to have better, baked Normal Maps as well as Parallax Mapping for the World Textures. I'm still okay with Detail Textures, I doubt this will add anything negative to the game or engine, very sure the code will also be simple enough it will probably only add 0.001ms for the loading times, or even none at all. But I would also like it as an option, just like how Half-Life has it, so I'm glad you mentioned that. But yet again, I much prefer better Normal Maps and Parallax Mapping than any Detail Textures. On another note...Wasn't Doom 3, also, one of the first games that started using Baked Normal Maps?

It's a big project, so it's important to test everything thoroughly and run several tests. "The Lost Citadel" had a lot of bugs in the first release because I didn't test enough. I will not repeat this mistake. I have fixed all problems found during beta 2. Beta 3 shall include all subtitles and briefing videos. The problem is that I'm still missing some voices. This means we can't complete the game subtitles and produce the briefing videos. In the worst case, I'll have to do a new audition for this stuff, but currently I don't feel like it.

Want to hang out with fellow TDM enthusiasts? Want an answer to a question but don't want to wait for hours on the forum? Need a break from that marathon mapping session? Join our Discord The Dark Mod channel! Discord is a very easy-to-use hangout platform. You can easily chat, swap screenshots, or get feedback on a WIP. With around 35 members in the TDM channel, there are usually a couple active people on any time of the day. Adding screenshots is just drag and drop, and you can link directly to videos or images with automatic previews. It's extremely easy to use and very handy when you need some quick feedback on a project. You can download the free Discord app here: https://discordapp.com/download But you don't have to! You can access Discord directly from your browser by following this link: https://discord.gg/M96zPHD Hope to see you there!

Paying the Bills: 0 - Moving Day You've just heard a sweet tip. Get to work before the window of opportunity closes. Download Link: https://drive.google.com/drive/folders/1hMqw99FgTk5jkezPnI1aaU2xX_gJ8fwo?usp=sharing Credits Assets: Amadeus - the Golden Lute STRUNK - new kitchen assets as well as fireflies & bats Alpha Testers: Amadeus, Baby Genius, Bienie, dragofer, Epifire, Jack Farmer, joebarnin, kingsal, NeonsStyle, Rotary Racer, The Dark One Beta Testers: Cambridge Spy, Shadow, Abusimplea, JackFarmer, thebigh, wesp5, Amadeus, kingsal, s.urfer, joebarnin, grayman, nbohr1more, prjames, AluminumHaste, Dragofer, datiswous, stgatilov, duzenko, Goldwell, Wellingtoncrab, If I forgot anyone PLEASE LET ME KNOW Notes - TDM 2.10 Beta 5 or later is REQUIRED to play this mission. - This is my first FM and took me roughly 4 years and 1000+ hours. I had originally planned a city map for my first FM, I even had an over-arching story set across 4 missions, but I decided to whip up a prequel to use as my "training-wheels protocol" for DarkRadiant before I move on to my magnum opus, hence why this one is #0. Subsequent entries will be on a micro scale compared to this map. - This FM implements the func_peek mechanic, allowing players to peek through any door that has a keyhole on it by leaning forward. PLEASE NOTE: This function has been known to cause crashes for a small number of players in the past, likely due to using the 32-bit version of TDM. At no point in this mission is it required to use the func_peek mechanic; it is purely optional, so feel free not to use it. - There are spiders - Suggestive themes/references - DISCLAIMER: This is a BIG mission by TDM standards, and has a lot of wide outdoor areas; performance may vary greatly. - Lots of plans for future updates, many ideas still left on paper. Download Link: https://drive.google.com/drive/folders/1hMqw99FgTk5jkezPnI1aaU2xX_gJ8fwo?usp=sharing (drop the folder into darkmod/fms) Many thanks, have fun!

Demonstration Video I wondered if I could implement an improved lean for The Dark Mod. How was the result? Please see for yourself by checking out the video. The video shows: Leans from multiple games that show less view angle and more slide. Comparison between Thief and this lean proposal. Comparison between TDM 2.11 and this lean proposal. Aiming and shooting arrows while standing and crouching. Tap lean ability. Motivation There is something about the original Thief game's lean that feels really good. It feels close to actually peeking around a corner while not jarring the view. In an interview with former Looking Glass Studios developers, the interviewer asks them how they got leaning to feel so good while other FPS games have not. In a tweet by NamelessVoice, the author of the widely used Thief FM script library called NVScript, he said: New Lean Proposal Provide a lean that is more similar to Thief-style lean. Less view angle, more slide. Feels more natural, less awkward. Easier to aim and shoot arrows. Unlean more quickly. Feels like snapping your head back after suddenly seeing a guard. Improved lean during crouch. Compared to TDM 2.11, this lean can be used to see more around corners while crouched. Tap lean ability. Compared to TDM 2.11, this lean allows pressing the lean keybinding in rapid succession. Other: Fixed "lean getting stuck sometimes" bug in TDM 2.11. Fixed "lean getting stuck after saved game load" bug in TDM 2.11. Technical Details Bug Tracker https://bugs.thedarkmod.com/view.php?id=6320 Cvars At the moment, the new lean is toggled on via the tdm_lean2_mode cvar. Other cvars include: pm_lean2_time_to_lean (default "400") pm_lean2_time_to_unlean (default "300") pm_lean2_slide (default "200") pm_lean2_angle (default "8") pm_lean2_angle_mod (default "0.5") However, I didn't know how to proceed with this section. Does the new lean replace the old lean? Does the new lean become the default while keeping the old lean available? Code TDM 2.11 uses a sine easing function. Instead, this new lean uses a cubic bézier easing function. For a 2.11-Like Lean For a lean that is similar to 2.11, its cvars can be set to the following: pm_lean2_slide "100" pm_lean2_angle "18" pm_lean2_angle_mod "0.8" The following video shows a comparison between 2.11 and this new lean proposal with those cvar settings.