Search the Community

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.

Ah, pity I wasn't reading the forums back in February. I'm fond of that game, along with Bugbear's other early title, Rally Trophy. I was never too good at FlatOut, but it was always a hoot to play.

Thanks. No scripts were harmed in the making of this. It's pretty simple to do because of the broken and brake spawn args. 1. It does distinguish, but I don't even know why It must be a property inherent in the glass material. 2. Good question, I'll have to get back to you. 3. I don't know how to use skins. OK, I tested it on a stock model. That doesn't work. If you use the same model for "broken", but just change the skin in the properties, it also applies the skin to the unbroken model (and vice versa). Oh, I just discovered you don't even need to put a stim/response on the arrow. It automatically breaks glass when you add the break and broken spawn arg on the object (you still need to make a broken model of course). Isn't that handy?

It took awhile to get used to the size of this mission. The long loading times didn't help, but after passing a certain point, I get it now. However, I will say this - the AI is crazy on this map. I started, right? And the first thing I see - all guards going ape because some thug cut loose. I sat in the dark corner, for like ten minutes, waiting for them to calm down, because I figured I should look around for loot (I only found some of it much later when I was returning here after finishing the mission) The same thing happened later, when I needed to pass an abandoned mansion. I waited for the epic battle, instead it was a massacre, but like an idiot I saved AFTER I left the tunnel, not before. So I couldn't reload and see if next time the battle will go differently. (Am I crazy or do leather thugs spawn after a moment?) I had to use up all gas arrows to pass that part because they kept trimming the bushes. The evidence part got me confused because I dropped a piece of evidence, but it didn't count, so I dropped everything that said evidence. Only then it counted, but later, as I was still hunting for loot, I finally remembered that I had a vent key and came looking and found yet another piece of evidence?! Finding Smythe was funny, because he kept saying "Show yourself" and the moment I did... I gathered skulls before I was prompted to, but Edgar... I don't get it. edit: Those glasses, tho. Holy crap, I did not expect to see "actual glass" in this game. The hidden room took me ages to find, despite TWO blatant hints. But I was sleep-deprived at the time. There was one snag, and one confusion that I had. The snag was that, when I finally reached the alchemist, the note told me to use the vent, right? But... I couldn't open the second vent in his lab. I don't know which key I was missing for that. So I figured - I could just go back the same way... and game CTD. I walked there again - CTD. I noclipped through that locked vent, killed the spiders, and tried to open the doors to my left (got spooked by friendly guards) - CTD. Only when I walked right and up the stairs did I finally progressed. Not sure what that was about. The confusion, however, came from Builders. I knocked out most of them in the Builder's outpost, but when I dealt with the Mr. Nom-nom-zom, they vanished. I guess they needed that many people to dig him out of the spider outhouse? (Never found the second news flash either) I still somehow missed 3.5k, and noticed that lights kept poking through walls (there is a piece of light pointed at doors leading into the inner garden of Builder's outpost that nearly got me killed a few times) Overall, however, this was an impressive piece of work.

I liked the atmosphere, build up of tension, without actual scares. Although, when I started, and got into Captain's quarters... I read the readable and thought.... Okay, so there are 11 sailor thugs, only to find a lot more in the house, and wonder what the heck. Maybe I didn't scroll it? I liked the dialogue too, but I was a little disappointed that the interior didn't match the description, it wasn't until I returned for the first time did it change to match. And I expected some sort of ghost or ghoul to pop up. Then the transition, and when I went looking for the spot, I noticed the way it was highlighted. =D That was pretty funny TBH. Then - Two missions in one was a bigger surprise than I expected. How does it even work? The only thing I don't get is the finale, but I suppose that's the point.

As soon as I started, I was hooked. Intro, our thief's reactions (can never have enough of those), cutscenes (YES!), dialogue with NPC's... It was great. And the further I went, the more it opened up. Overhearing conversations, a freaking tape recorder?! I found a very sus table in the pantry, and thought that maybe I need to light the candle, which did nothing. But you gotta admit, that looked like a puzzle of sorts. Turns out I was overthinking it... I too completely missed the hidden "chest" with the second book, only after coming here did I went back and found it. , but it's sad that Mage's readable turned out to be only partially true. =D Thank you for your work and release!

In case anyone decides to pursue this further, here are a couple more references: https://discourse.gnome.org/t/pointer-warping-on-wayland/9197 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158 Seems like this feature is also common in PCB design software. The "correct" solution would be to use Wayland's pointer locking interface and relative mouse events, which is essentially what the FreezePointer class accomplishes by continuously warping the pointer back to its original location. The complication is that the way it works now all goes through wxwidgets which then goes through gtk3 on Linux. To fully implement this, I think someone would have to: Create a platform-specific alternative to the cross-platform FreezePointer that we have now Make sure it's only called on Wayland, and only if the pointer locking API is available Work your way through the wxwidgets / gtk3 layers to get hold of the native wayland surface and pointer handles Reconcile the Wayland mouse events with the mouse events received by wxwidgets If someone was motivated enough to pick this up, it might make sense to try to build this in at the wxwidgets level and try to get it accepted there. It would help keep platform-specific code in the right place and also make a couple other projects happy.

Mouse look is essential so no. We should use whatever behind-the-scenes solution of messing with the pointer will work... once Wayland or WxWidgets or GTK3 will offer one, it's kind of on them that they haven't up to this point. Until then Jonri's PR works by forcing the X11 backend, which isn't a real solution but in practice solves everything for now. Here's a modified snippet of what I did in PyGame which works. Obviously this code has no effect, just an example to show what works in my project, just in case it's a similar situation here: Maybe Wayland expects us to hide the mouse pointer at a core level before it allows locking, and the reason it doesn't work is DR only hides it visually at top level? pygame.mouse.set_visible(False) x, y = pygame.mouse.get_pos() pygame.mouse.set_pos((x, y)) pygame.mouse.set_visible(True)

Oh well, I guess that rules out any kind of mouse grabbing behaviour that will work on Wayland desktops. I'm not sure what the alternative is. Some kind of on-screen widget that you can click and drag to rotate the camera, like a sort of circular scroll-bar?

Yeah, I guess I didn't consider making a new entity for future mappers to implement in their future maps when I responded to you (sorry!), but that is not a bad idea. The changes should be done in a way where it wouldn't affect older FMs, and it would be a fair chunk of work. I actually have a few breakable lights in my WIP, although they are kinda glitchy and far from perfect.

Hello again I just want you guys to double check fms because i think files got mixed up Localization Packs: Vengeance for a Thief Part 1 its says it is for a pawn in the game localization pack String table English (iso-8859-1) for: Vengeance for a Thief Part 1: A Pawn in the Game But it is under VFAT1: The Angel's Tear download I have looked in my fm archieve and i foun fm named The Accountant: Part 1 - A Noble Home (prologue) It is not listed in download section. any idea about this one ?? is it a part of accountant campaign ? Is it obsolete ? or it is missed ? Also i came across Samhain Night on Bone Hill By PranQster Version: 0.9.7 Back again to version matter. Maybe it is not important to keep versions, maybe it is. For me it is important as i am updating my archive of fms so it is nice to just see version straight away than looking in every pk4 file for it. Also it would be very helpful just to add in download section beside released date, update date as well Maybe Sir You just like me. You look but you can not see TDM Fan Mission Lists: Released and Upcoming Thread https://wiki.thedarkmod.com/index.php?title=Fan_Missions_for_The_Dark_Mod

There might be another way, or at least it's what I thought of as a non-developer: Use a different way to transform mouse movement into camera rotation or viewport offset. Is there no alternative to calculating the distance from the pointer to the window center before resetting the pointer to the middle? There must be other mouse look implementations that could work. Most obvious alternative: We can detect how much the pointer moved on the screen compared not to the center, but to its previous position wherever that may be. While of course still trying to lock it in the middle, but if that fails at least it doesn't cause the view to go crazy: The only issue then will be the cursor reaching the screen edge and having to be re-engaged so you can keep scrolling in that direction, which is also a big annoyance but comparatively less bad and not as noticeable unless you do long-range movements in one go. Any reason why we couldn't give this option a try?

I always loved the "connections" theme and I think it is very fitting to celebrate TDM. It's a shame we can't have 4 polls per thread because then my proposal would be to have free-for-all with a "connections"-rating added that evaluates how well the mission integrates into or expands upon the existing lore.

Oh my gosh, thank you for this! After reading what you just said, I realized I've in fact noticed the same thing in another program, but assumed it must be something completely unrelated: I've been working on creasing a CPU based voxel raytracing engine in Python, for which I settled with using PyGame. When the time came to implement first person camera control using the mouse, I noticed it did not work initially... however if I told my code to hide the mouse pointer first, locking it in the center of the window started working. It must be the same thing here in some form, Wayland likely has some very particular expectation on how the mouse pointer must be set in order to be locked. In fact just a few days ago, I tried a virtual worlds software called Vircadia / Overte again to see how it's been progressing. I activated mouse look mode and guess what happened: The exact same behavior of the view spinning endlessly as the cursor drifts away from the center due to lack of locking. So it's clearly happening to many things and not just GTK / WxWidgets related... but no all of them, most games (including TDM itself) work perfectly fine and mouse control never breaks. I'll try your solution later and mention the results, likely tomorrow as it's late now and I need to head off. If it works that would be incredible! At least as a workaround, we could simply not hide the cursor on Wayland, which will look ugly but at least allow using DR without needing hacks until they can solve whatever is happening on their end. Also Plasma 6 was just released, my distribution (Manjaro) will likely be getting it a couple of weeks or at most months from now. I'm curious how that will affect it: Hopefully it won't make the issue worse, but just in case I'd be happy to have a solution in Radiant before then.

There are a few ways to state the version number: Inside darkmod.txt, included in the .pk4. The version number in here is what should be shown ingame in the mission downloader. Mappers can write whatever they want inside the readme.txt included in the .pk4. This is the same as writing a version number into the release thread. There is also the internal version number, which always has to be a whole number. It's entered directly in the admin interface, and only team members can see it. The existence of the last, internal-only number has led to some confusion among mappers. I think I used to put whole version numbers into my darkmod.txt (i.e. v2 or v3), but declare a decimal update (i.e. v1.1 or v1.2) on the forum thread and in the readme.txt. It's also possible to have different version numbers in the darkmod.txt and readme.txt. This is something that should be caught during beta testing.

Noticed all of these only because I played TDM by doing the opposite of stealth to practice swordfights. None of these bugs appeared as long as I played the game stealthily. Should also note that I used Snatcher's Core Essentials @snatcher on and off, but your mod does not alter the AI anyway, correct? Bugs happened both ways. 1) AI freezes in combat - https://bugs.thedarkmod.com/view.php?id=6371 It happens a lot with auto-parry disabled. It never happened with auto-parry enabled. It never happened with some guards, while it happened many times with specific guards. They unfreeze when player dies, or when AI is forced to re-equip the melee when player returned from a spot that usually causes them to throw rocks. Also experienced behavior of them only slowly walking towards me at the pace of "hunched sneakily searching mode", attacking once finally in proximity. 2) AI may collectively lose the ability to hear any of the players noise caused by footsteps / landing. Still unsure of what causes this, but Lockner Manor has a good layout to get to the result. Just follow the right-most path and repeat the process of winning sword-fights with City Watch, and then jump around the next guard to see if they can hear you. If they can not hear you, likely nobody can. If they still can, just combat them too and you will likely have deaf AI by the time you have dealt with the 3 Watch Guards outside. In my experience, when they hear the death scream well enough to run to its location or start searching - the deafening did not work. 3) Helmeted AI does not react to (nor hear) players overhead sword strikes made directly on helmet, stealthily from behind. Not sure if the same issue as deaf AI bug, but happened at least once while it was active. (Lockner Manor) 4) (Moor?) AI may lose the ability to hear AND see player after nearby swordfights and after two slashes to bloody their face. (I may have also Moss Arrowed them to face). Any sword strikes I make simply go through their model with no audio of impact. Collision still gets player detected. (A Good Neighbor) 5) Crash to desktop when archer puts bow away to take out melee (while I may have collided with them on staircase). (Lockner Manor) 6) Crash to desktop when I shot a shortsword-wielding charging Noble. Sound of a deflected arrow played (same that you hear when shooting a stone wall), when I expected a flesh-hitting sound. (A Good Neighbor) 7?) Sometimes AI says "Ow that hurt" merely because I block their strikes. - Is this an intended feature? Do they take actual damage too? Anyway, I didn't find mentions about many of these issues. Reporting aside, if you want me to experiment with something or find ways to replicate - I don't mind updating this thread, as I plan to mess around with sword-fights anyway. Just posted this initial version should anyone want to chime in with similar experiences, and I wanted to know if some of these bugs could be mission-, or mod-specific. Maybe caused by much or unfortunately timed quicksaving / loading?

Congratulations on your mission, hard to believe its your first, well done. Thanks for all your hard work, I hope to see more missions from you.

I think we can use this script (mod) to extract all textures with specular maps, and if possible, create a map for testing. Unfortunately, I'm not yet familiar with the editor to help with this. I came here because I plan to work on textures more thoroughly, and I'm currently reading the wiki on texturing issues. In general, I'm interested in this topic. Maybe I'm not competent at all, but is it possible to make a texture have a constant reflection (yes/no) and a variable with a setting in the editor/accompanying document (?) that controls the intensity? For example, the same object/texture can behave differently on different maps.

I have updated the thread with poll options. Please vote I even though I have given-up on the connections part of this, it might be nice if authors used Corbin as the protagonist to at least pay homage to the included missions.

Finished this up yesterday and for the most part, found it enjoyable. The puzzles weren't too hard as your clues were good for them. Thank you for all your hard work and I look forward to more missions from you.

Well, I don't know about adding new difficulties, that seems like a lot of work. A hack way of getting the same effect, and which I use, is to create a simple .cfg file with the required changes and then execute it in-game (e.g. a text file called brutal.cfg then, in-game "exec brutal"). You could redefine the modifiers for, say, the hardcore difficulty, which are usually tdm_ai_hearing_hardcore "1.5" & tdm_ai_vision_hardcore "1.005" to something higher, although I don't know if they are capped or how to interpret those values. There are other cvars that might be useful, but I have never tried them. tdm_ai_sndvol seems useful. You'd have to test the changes in-game, probably in the Sound & Blackjacking map. For this, there are some very useful commands to see the sound direction, propagation, and values, but I can't remember them right now. There's an important caveat here, and why messing around with this stuff should be done at your own risk. I have found that some cvars go back to their default values as soon as you load or die, while others seem to stick around. Modifiers to the player's height (like pm_normalviewheight), revert to default if you load, but modifiers to the player's speed (pm_walkspeed) don't. And I know this because I have a .cfg file named halfling.cfg, and you can imagine what it does. To avoid this, I have a "default" cfg to restore the game to the normal values if (or when) something goes wrong (it's basically a copy of the Darkmod.cfg, but with a different name, and I only use it for this purpose.)

Shouldn't it already work in the training mission?

If shadow maps support more detail that stencil shadows can't offer, I'm absolutely in favor of enabling them: It makes sense to use them for obtaining new details and effects that weren't possible previously. Geometry based shadows are technically a legacy thing anyway, I imagine that once every player and their hardware work well with shadow maps then stencil shadows may someday be deprecated.

Excellent FM Ansome! It's a really tense one that's for sure. High quality alround. Worked brilliantly with the recent new Darkmod and my framerate was hitting max fps @ 144 with my gfx card and processor barely getting warm. I could not wait to get the hell out of there Thanks for all your hard work and to all those who helped you. I hope you make another one - bigger, creepier

In the interest of preventing the loss of investigations and mapping work, does anyone have a prefab of the dynamic moonlight map that SteveL made a while back? All the download links are dead, but here is a link to the thread: