Search the Community

No, not really, have only seen him on the forums many years ago. He deserves a lot of credit for providing the SVN infrastructure in the beginnings of the project, it's been only later when we transferred this to a hosted server. Memory is blurry, but I think my time working on TDM and his don't overlap that much - I had been getting more active, and he pulled back a bit. He bootstrapped quite a few important systems, IIRC he's been working on light gem and the first Stim/Response and Inventory implementations. From what I recall, he gave the project an organisational backbone in the technical department which is crucial to keep things together. Folks like Spring and NH who have joined long before me could give more insights, I guess. (Looking at my join date makes me feel old either way. From TDM's current view point, the year 2006 seems like right at the beginning, but actually the mod had already been existing for two years by that time I joined. With the first release in 2009, 2006 is rather in the middle. Heck, I haven't touched the mod code for at least 10 years - and I can still remember a few things, which is a testament of how much it occupied my thoughts back then).

There are other complications though. How much fall damage should player take, if they decide to jump off a rope with the body? Should the player let go of the body or not? Also, right now it's much harder to jump off the rope with the body than without it. Why? And last but not least, how would you teach players these things, possibly without much hand-holding and text prompts explaining the rules? I guess I'm with @STiFUon this one, if you restrict dropping the body, you'll save yourself (and mappers) a lot of headaches. But even that doesn't solve all the problems, I know I'm in the minority in these forums, but as a player, I really appreciate the beauty and efficiency in simplicity of the design. Not overthinking everything and adding more and more rules for the sake of realism (or anything else).

I think the reason the dev forums exist is to provide a place where the implementation of features can be discussed without getting mixed up with other debates when someone believes what the devs are doing is wrong. We often post public discussion threads for features with subjective elements like the frob outline, because community feedback is very important. But there will always be vocal defenders with strong views for or against certain features, or how exactly it should be implemented in their opinion. At some point a decision has to be made and be carried through, which is what the dev forums are for. Almost all of the threads are very technical, basically explaining and discussing recent or potential code changes with other devs. Its hard to say. Its a hobby the devs do in their spare time, so people come and go when they're in the mood and when they have the time. The team page is mostly accurate except for some relatively newer additions like myself.

This is basically "do include my work ASAP because I worked so hard, or else *sulk*". This is similar case: https://forums.thedarkmod.com/index.php?/topic/21679-beta-testing-211/page/10/#comment-482352 This is neither a commercial product, nor a phishing email. That sense of rush and pressure is artificial. These releases typically do take long, and even then, there are often many things broken by mistake or omission. Often there aren't enough people to test stuff, or they're not competent enough, etc, etc. There's little point in hurry.

Looking at the source code and the core pk4 asset files, I don't see any changes that would make a difference. Does this happen with a single FM? Does the FM pk4 file include an "autoexec.cfg" file? From the source code, here's the load order of config files. exec default.cfg exec Darkmod.cfg exec DarkmodKeyboard.cfg exec DarkmodPadbinds.cfg ==> exec autoexec.cfg <load language> <exec command-line arguments> <init input> <init sound> <init OpenGL> <init ui> <load DLL> <init session> ==> exec autocommands.cfg Details about the addition of "autocommands.cfg" are at https://bugs.thedarkmod.com/view.php?id=3199 I thought "autocommands.cfg" was the right way to do it, because that is what I've read on the forums. It seems that "autocommands.cfg" was originally designed for one use case: running "dmap". However, maybe over time "autocommands.cfg" became the de facto config file for user commands and "autoexec.cfg" became the config file for FM authors to use. I don't know. Does anyone know for a fact whether or not this is the case?

So I think we can count 12 or 14 missions depending on our opinion of La Banque Bienveillante and Sneak and Destroy. If these two reissues are counted as new missions (as JarlFrank did here: https://www.ttlg.com/forums/showthread.php?t=152035), then we have 14 missions. If not, then 12. Personally, I don't consider them new missions, so 12 in my opinion. Have no problem with other opinion. In any case, last year was productive!

My dream is for forums.thedarkmod.com to link to thedarkmod.com

Purah also worked on Dishonored: https://www.ttlg.com/forums/showthread.php?t=136214 One of my neurons knew it started with a 'P'

We got TDM VR, for a start. https://forums.thedarkmod.com/index.php?/topic/20468-the-dark-mod-vr-210-alpha-is-now-available/

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

I literally registered just to point out that people HAVE been raising this as a serious accessibility issue since as far back as 2008. It's been repeatedly brought up over and over and over again. And that is just here on the official forums. If you really mean what you've said I think you should find it genuinely concerning that one of the single most widely discussed accessibility issues in gaming has been repeatedly brought up for over a decade with your game and apparently this is the first you've heard of it... even though it's even been subject to multiple issues in your issue tracking system according to these threads and other google results.

here use this link and never miss again its my startpage https://forums.thedarkmod.com/index.php?/discover

Wonderful, thank you! I had success in getting the base setup to work with one of the symbol textures, couldn't ask for better functionality I use the following material setup adapted from that example, might simplify it further if specular doesn't need to be defined separately like that: lights/biground1_spectrum { spectrum 1 description "Round point light." { forceHighQuality map lights/biground1.tga colored zeroClamp } } textures/darkmod/decals/symbols/magic_symbol_circle01_spectrum { qer_editorimage textures/darkmod/decals/symbols/magic_symbol_circle01_ed translucent noshadows twosided nonsolid spectrum 1 sort 5 bumpmap heightmap (textures/darkmod/decals/symbols/magic_symbol_circle01, 2) diffusemap textures/darkmod/decals/symbols/magic_symbol_circle01 { blend specularmap map textures/darkmod/decals/symbols/magic_symbol_circle01 red .25 green .25 blue .2 } // TDM Ambient Method Related { if (global5 == 1) blend add map textures/darkmod/decals/webs/web4 scale 1, 1 red global2 green global3 blue global4 } } There are three secondary problems I'll need to address now, let me know the solutions you propose. When given "texture lights/biground1_spectrum", the light will illuminate the hidden symbol as desired, but no longer shine on anything else. I presume there's no way to tell it you want "spectrum 1" but also for it to shine on everything else like a normal light? If not I'll just have to give my lantern two light sources. How to make the lantern entity work with this? I'd prefer the player being able to press the use key while holding it to turn the light on and off. I'm using atdm:moveable_lantern_oil_hand_colorme_lit: Apparently the lantern ent doesn't inherit a light type itself but attaches one similarly to the torch... I'm seeing "def_attach light_lantern_oil_omni" so I can probably just inherit and override that. Anything special I must do to ensure the still light toggles when the lantern is used? Especially if I'll have to attach the UV light separately to get both UV and standard lighting, will operating the lantern toggle both the normal light and my additional "def_attach_0 light_lantern_oil_omni_spectrum"? This works fine with a decal texture, but I was wondering if there's an easy way to make it work with an in-world GUI for text written as a spawnarg? That's when you make your patch func_static, texture it with "textures/darkmod/decals/signs/decal_gui", give it the spawnarg "gui guis/readables/sign_text_decals/sign_text_camberic.gui", then use "gui_parm1 my_text" to make it say something. Is it as simple as creating a "textures/darkmod/decals/signs/decal_gui_spectrum" with the "spectrum 1" keyword in the material and it just works? I believe GUI text wasn't rendered like a conventional material per say, as the fonts themselves don't inherit the properties of that material nor receive light to my knowledge.

You can find a test map here. Note that I remember not being too happy with it. https://forums.thedarkmod.com/index.php?/topic/19825-negative-spectrum/&do=findComment&comment=432949

I'm not, that's a standard torch with no extra spawnargs. For a moment I thought there was something wrong with the setup in my map, just noticed what's happening: There are still issues with lighting not being recorded properly in screenshots, even when using shadow maps instead of stencil shadows where it was previously known to occur.

Looks great, but PLEASE don't use no_shadows on that torch in image Makes the entire scene look flat and wrong. And it shouldn't be necessary these days. One of the biggest reasons for choosing Doom 3 engine was the use of real time shadows. Not using them seems antithetical.

DarkRadiant 3.7.0 is ready for download. What's new: Feature: Skin Editor Improvement: Script Window usability improvements Fixed: Hitting escape while autosaving crashes to desktop Fixed: Def parsing problem in tdm_playertools_lockpicks.def Fixed: DR hangs if selecting a lot of entities with entity list open Fixed: Float Property Editor's entry box is sticking around after selecting a float key Fixed: Spline entities without model spawnarg are unselectable Fixed: Entity window resets interior sizing forcing resize each time it is opened Fixed: Spline curves should not be created with a model spawnarg Fixed: Newly appended curve control vertices aren't shown at first Fixed: Light entities are zoomed out in preview window Fixed: Entity inspector spawnarg fields not always updated by UI windows such as Model Chooser Feature: Skin Editor (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.7.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!

Would it be at all possible to do this from the "main" website? I mean the one you first see when you look up "Dark Mod". Cuz it is a maze in these forums, goodies strewn about here and there but few resources that are intuitively accessible. Also @SeriousToni, what are you planning on uploading?

Originally the mug was created by @LordSoth https://forums.thedarkmod.com/index.php?/topic/13257-tdm-beginners-contest/&do=findComment&comment=287897

It seems that there is a reverse engineer group ( Amernime \ Nimez ) who are back-porting newer AMD drivers to older GPU versions. Terrascale 1 support is currently a "work in progress" : https://forums.guru3d.com/threads/amernime-zone-amd-software-adrenalin-pro-driver-release-nemesis-22-10-3-whql.436611/ If you are interested, they might have beta versions up on their terrascale discord. The downside is that these are community created drivers rather than official ones by AMD. Maybe AMD will release some sort of maintenance for terascale like they did for some of their other old GPU's.

id Studio did a poor job in defining its categorization of variable nomenclature, so in subsequent documentation and discussions there are divergent views (or just slop). In my series, I had to choose something, and went with what I thought would be clearest for the GUI programmer: Properties, which are either Registers (like true variables) Non-registers (like tags) User Variables (also true variables) I see that your view is more along these lines (which perhaps reflects C++ internals?): Flags (like my non-registers) Properties, which are either Built-in (like my registers) Custom (like user Variables) Also, elsewhere, you refer to "registers" as temporaries. I am willing to consider that there could be temporary registers during expression evaluation, but by my interpretation those would be in addition to named property registers. I'm not sure where to go next with this particular aspect, but at least can state it.

DarkRadiant 3.6.0 is ready for download. What's new: Feature: Selection Focus (Ctrl-F) Feature: Add Radiant.findEntityByName script method Feature: Media Browser shows a thumbnail preview when selecting folders Feature: Map is remembering layer visibilities between loads Fixed: ModelDefs are shown in T-pose Fixed: Patch vertices are the wrong colour Fixed: Shader Clipboard source gets cleared on 'copy shader' operation Fixed: Nodes of hidden layers are still visible after loading the map Fixed: Can't close properties window Fixed: Merge Action rendering is broken Fixed: After using ToggleMainControl_Camera, the center panel is grey after restart Fixed: When using ToggleMainControl_Camera, arrow keys cannot be used to move the viewer Fixed: Property Panel not remembering undocked/closed tabs Fixed: Texture Tool not updating during manipulation Fixed: Orthoview ignores filters for surfaces in models Fixed: Blue dot when selecting one face removed Tweak: Conversation Editor: double-click opens selected conversation Tweak: Preference option to disable drag select in camera view Tweak: ESC key should clear the resource tree view filter text Tweak: New layers function: tooltip popup getting in the way Feature: Selection Focus (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.6.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Have fun mapping!

@stgatilov, you said, RE string comparisons: I'm unclear if you are referring just to changes you made in 2.11. I think equality testing of two strings (one of which is "text") was working and is a good and expected capability, and should be supported. Including against an empty string. I noticed in your bug activities that you did remove some comparisons with ... == "". I see you also removed string concatenation with "\". No problem, but does that mean multiline macros are no longer a thing? (If so, I'll need to change some examples) BTW, the series so far hasn't really tried to cover the 2.11 changes, since I figured it's a work in progress. But since you did a great deal of GUI work in July, perhaps it's stable enough to try to consider it. I see the logs listed in bugtracker, but don't have access to the private forum threads mentioned there: https://forums.thedarkmod.com/index.php?/topic/20526-gui-refactoring/&do=findComment&comment=477179 https://forums.thedarkmod.com/index.php?/topic/21535-order-of-evaluation-in-expressions-materials-and-gui/ (Nor do I have SVN currently set up on my newer machine, for changelogs from there.) Any place else I should look?

-> https://forums.thedarkmod.com/index.php?/forum/13-music-sfx/