Search the Community

So what is Distortion for in the game? Both Distortion and Filtered Distortion appear as true in the Settings ini

Is it possble to make skins for brushes/patches by conferting them to func_static? Models are func_static when you add them in DR, but in the skin file you reference them with the model name instead of the entity name. When you convert a brush/patch though, it converts it uses a model with the same name as the entity name, so in this case func_static_1 for example. Would it be enough to use that in the skin file? Allthough the wiki article states it's important to add an extension.

Another leak in Written in Stone near start (230 -1820 65): This case is more interesting because it is not just light leaking vs not leaking through a wall. Here we see view-dependent scissoring rectangle which limits the light effect. The light source is in the farthest area behind a wall (on the middle of the two far visportals). There is no way to cast a ray from the light source through visportals that would reach the viewer area: if you hit one of the far portals, then you surely don't hit the near portals. So the frontend decides that the light is not active in the viewer's area. Then the light scissor is bounding rectangle around all the visportals. Normally, the wall in between should occlude the light, but apparently it was set to noshadows. This wall seals the areas, so this is the same kind of bad input as usual. But the resulting behavior is indeed interesting. So I wonder how should we fix it @Amadeus @Dragofer

I felt like an absolute dunce, when I started the mission for the first time... Because, the note confused me. I thought that I was supposed to complete the task on the note and then return to this door, it will be open I'll talk to an NPC or something and will progress further. So I spent several minutes looking for a door outside, and finding none. I thought - maybe I need to use the window, it's partially open, I bet I can squeeze through it. So I did, and fell out of the map, whereupon I saw the rest of the map and realized that the note was slipped under MY front door. Had to restart =D I enjoyed the mission, but I also missed the painting. I should've tried "the Number" right away. The sneaky boi was great, I wish we had encounters like that on some occasion. It's such a novelty IMO. I wasn't attempting the Ghost so eventually I was fed up with this guard and used my gas arrow, then... this happened. I enjoyed the final stretch, but my immersion was broken a little, because the area where we get a new mission had a missing wall and a floating tree, for some reason. Great map, and mission. PS: I realize that they probably just drop them, but taking first mission into the account, I can't help but think that people eat fingers with rings on them.

Why not use the modified weapon scripts from the April Fool's FMs? Those seem to be working just fine on this dev build

Do we have any volunteer to participate in fixing these missions? The first (and perhapsthe most important) step is to download these missions, diff tdm_weapon_arrow.script against stock version, and list all the things that are actually customized.

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.

It is not included in the Modpack. It is a little side project, that's all I know today. You know the drill: do what you please with the stuff I release. And if you can make it better or different: do it!

I believe the engine sets mindistance = 1 and maxdistance = 10 if they are not set explicitly in the sound shader. At least that's what I see here: https://github.com/stgatilov/darkmod_src/blob/trunk/sound/snd_shader.cpp#L154 Anyway, if DR sets spawnargs to the same values as in sound shader, that's not a problem for the suggested change in the meaning of zero value. But setting maxdistance = 0 will be

The script changes standard weapon behavior and you think it's not needed to inform the player?

Why? Do you have resentment toward these 10 missions in particular? Do you not care if you break any and all missions on your whim and then release a public build? Breaking existing missions and then making a public dev build available with broken FMs doesn't really seem like a great thing to do. I get that missions get broken from time to time because improvements need to be made to the core game, but this is essentially a public release (even though it is a "dev build" it is still a "public dev build" available to anyone and everyone, and with that comes certain expectations). You didn't even notify the affected FM authors beforehand. This is just not cool.

What is the problem with bugtracker 5600? Does the player start without a bow now?

Good question. Maybe because I don't feel myself too guilty breaking these missions? Maybe because I know that fixing them will be a long story. And I feel confident that we (or more likely I ) will be able to fix all of them by 2.13. You might have noticed that I have also enabled two behavior changes in the latest build (1 2). In these cases it is not even mappers' fault that behavior change is needed. I have a script which can update all missions at once so that they work properly both in 2.12 and dev builds. But somehow I feel I should wait for at least some feedback on the new behavior before doing a massive change to dozens of missions.

So because of bugtracker 5600, does that mean that 10 FMs (Written in Stone, Northdale 1 and 2, Volta 2, Hazard Pay, etc.) do not work in this new dev build, and yet, the dev build was released anyway? That's not cool.... The bow is kind of an important gameplay element, especially for Hazard Pay. Why even release this build if it breaks 10 existing FMs?

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.

Wow! These shots look incredible, you really nailed the architecture! Unfortunately, I don't think I'm gonna have the time to beta test this, but we'll see. I just wanted to tell you that these shots look rad!

Hi, I've tried to install the latest version of TDM four times now (no previous installation), each time I get the same error: ERROR: Unexpected CURL error 56 on URL The urls seem to change (examples are http://darkmod.taaki.za.net/release/zipsync/release/release200/tdm_textures_metal01.pk4, /tdm_models02.pk4, /tdm_textures_carpet01.pk4) but the installation always fails around 20% of the way through. Am I doing something wrong? I tried the default mirror and the German mirror (also version 211 just in case). I'm using Windows 10 (64 bit) and don't seem to be having any internet issues that would cause the error. Any help would be appreciated!

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.

"The Threepenny Revue" https://www.thedarkmod.com/missiondetails/?internalName=threepenny "I've been in the business of other peoples' valuables for as long as I can remember, so I'm no stranger to breaking and entering. But until today, I've never done a robbery on commission. I guess there's a first time for everything..." Randal Cartier, a local theater owner, thinks himself above paying protection money to the local gangs. You've been hired to prove him wrong. "The Threepenny Revue" is a first attempt at a Dark Mod Fan Mission. After playing TDM for ages and loving it, I wanted to try my hand at creating one of my own. As such, this is a short, simple, and relatively straightforward mission made to learn the ropes. The experience was very enjoyable, and I'm planning to work on another one in the future. In the meantime, I hope you enjoy this one. It's available now in the mission list, but in the event anybody wants or needs a backup source I'm hosting the files on my own site here. Special thanks to @Cambridge Spy, @thebigh, @Shadow, @wesp5, and @boissiere for Beta Testing and giving feedback, which helped enormously in ironing out problems in DarkRadiant

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.

I usually share other people's photos of historical and industrial architecture in this thread, but I've decided to finally share some of my own photos that I've accumulated over the years. Over the years, especially the last twenty or so years, I've wandered many of the old town quarters in cities and towns all around my country, taking snapshots. Wereas many of the main streets and major landmarks have long since had nice and beautiful restoration work done, many of the more obscure side streets, back alleys and occassional overlooked corners had interesting sights to behold. I've particularly been fond of old townhouses that show elements from different eras of history, as well as all the wear accumulated over the years and decades. As much as I like that many of these eventually also receive decent restoration work and look nice again, the sight of a well-worn, dilapidated or even ruined house or ocassional public building can prove really stimulating for the imagination. They've got a lot of proverbial "texture" (not just in the surface sense) and "character" that can hike one's imagination, especially with regards to lived-in environments with long histories.

This was a great purchase for me, covers all my needs, and brings me up to immunity to any massive chip shortage as a result of geopolitics. It appears to be running a core at 4.2 GHz basically forever even with low usage, but is quiet most of the time. Clearly faster than the i5-6600T despite the years of quad-core stagnation. The higher TDP and hyperthreading really helps. I doubt there's any noticeable improvement going from HD 530 to UHD 630 iGPU, but it does gain the better H.265/VP9 HW decode that came immediately after Skylake.

I havent tried in 2.11 yet but I will. Just an update on this. For now I think I fixed it by: - Addressing most of the warning in the log above. Outside common errors like some missing textures and such that are part of the core. - Made sure to give my parallel lights "parallelSky " "1" spawnarg. - Deleted my .aas files and rebuilt them - Dmapped the entire thing Right now I am not getting the load error . It's a very hard problem to nail down because the console isn't giving a specific script name that it's getting hung up on (if that is even the issue similar to Amadeus's problem) AND I am actively working on the mission, creating new errors, fixing other broken things. ect. Its definitely something I fear will pop back up in beta testing though