Search the Community

I installed DR 3.0.0 (portable version) and I see what you see now, so it's something to do with DR: The change seems to have been introduced in 3.1.0 which I also tried: There were a bunch of sound shader-related fixes done in the 3.1.0 release: https://bugs.thedarkmod.com/changelog_page.php?version_id=101 perhaps this one? https://github.com/codereader/DarkRadiant/commit/541f2638c810588ada12e9a28360f16df6143d45#diff-104c4215e1bcd3ef19a7c943fec728649b1b0ba3bccf30600084b28dc1a8e67d @greebo

DarkRadiant 3.9.0 is ready for download. What's new: Feature: Add "Show definition" button for the "inherit" spawnarg Improvement: Preserve patch tesselation fixed subdivisions when creating caps Improvement: Add Filters for Location Entities and Player Start Improvement: Support saving entity key/value pairs containing double quotes Improvement: Allow a way to easily see all properties of attached entities Fixed: "Show definition" doesn't work for inherited properties Fixed: Incorrect mouse movement in 3D / 2D views on Plasma Wayland Fixed: Objective Description flumoxed by double-quotes Fixed: Spinboxes in Background Image panel don't work correctly Fixed: Skins defined on modelDefs are ignored Fixed: Crash on activating lighting mode in the Model Chooser Fixed: Can't undo deletion of atdm_conversation_info entity via conversation editor Fixed: 2D views revert to original ortho layout each time running DR. Fixed: WX assertion failure when docking windows on top of the Properties panel on Linux Fixed: Empty rotation when cloning an entity using editor_rotatable and an angle key Fixed: Three-way merge produces duplicate primitives when a func_static is moved Fixed: Renderer crash during three-way map merge Internal: Replace libxml2 with pugixml Internal: Update wxWidgets to 3.2.4 Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.9.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep creating Fan Missions! 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!

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.

Hm strange. I had this especially with fm High Expectations. Maybe it could be related to the Flatpack install

I couldn't help thinking of another realism related suggestion, don't know if it was discussed before but it seemed like an interesting idea. If this were to be changed on existing lights by default, it would have minor gameplay implications, but the sort that make missions easier in a fair way. So... electric lights: Like the real ones of the era, they're implied to use incandescent light bulbs... the kind that in reality will explore and shatter upon the smallest impact, and which like real lamps are encased in glass or paper. In any realistic scenario, shooting a broadhead arrow at a lamp or even throwing a rock at it would cause it to go through the glass and break the light bulb inside. Is it wrong to imagine TDM emulating this behavior as a gameplay mechanic? Just as you can shoot water arrows at flame based lights to put them out, you'd shoot broadhead arrows at electric lights to disable them... you must however hit the glass precisely, there's no room for error and it must be a perfect shot. As a way to compensate for the benefit, AI can treat this as suspicious and become alert if seeing or hearing a lamp break, or finding a broken lamp at any time if that's deemed to provide better balance. A technical look at implementing this: Just as broadhead arrows can go and stick through small soft objects such as books, they should do the same if you hit the glass material on a lamp, while of course still bouncing off if you hit metal: Lamp glass would need a special material flag that sends a signal to the entity upon collisions but allows arrows to go through, unlike glass in other parts of the world which is meant to act as solid and changing that everywhere would break a lot of things. When pierced by an arrow, the lamp should immediately turn itself off while playing a broken glass sound and spawning a few glass particles. The glass material should be hidden if the model is a transparent surface, or replaced with a broken glass texture in case the glass is painted on a lamp model without an interior... obviously this would be done by defining a broken skin for the entity to switch to. This does imply a few complexities which should be manageable: Existing lamps supporting this behavior will need new skins and in a few cases new textures, the def must include a new skin variable similar to the lit / unlit skins in this case a broken skin. Any electric light may be connected to a light switch, we don't want toggling the switch to bring the light bulb back to life... as such a flag to permanently disable triggering the light from that point on would be required. For special purposes such as scripted events to reset the world, we should allow an event to unbreak lamps, setting their state back to being lit / unlit while re-enabling trigger toggling. What do you think about this idea and who else wants it? Would it be worth the trouble to try and implement? If so should it only be done for new lights or as a separate entity definition of existing ones, or would the change be welcome retroactively for existing missions without players and FM authors alike feeling it makes them too easy?

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.

I don't know if it's related, but, I noticed since a few TDM versions that some text in readables in some missions is cut off. IIRC, also in the Training Mission. Also, the two books in JackFarmer's screenshots aren't the same height. The lower one is way shorter than the upper one.

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:

@snatcher I understand that when you feel your work doesn't live up to your goals that you don't want it out in the wild advertising your own perceived shortcomings but that leads to a troubling dilemma of authors who are never satisfied with their work offering fleeting access to their in-progress designs then rescinding them or allowing them to be lost. When I was a member of Doom3world forums, I would often see members do interesting experiments and sometimes that work would languish until someone new would examine it and pickup the torch. This seemed like a perfectly viable system until Doom3world was killed by spambots and countless projects and conceptual works were lost. I guess what I am trying to say is that mods don't need to be perfect to be valuable. If they contain some grain of a useable feature they might be adapted by mission authors in custom scenarios. They might offer instructive details that others trying to achieve the same results can examine. It would be great if known compelling works were kept somewhere safe other than via forum attachments and temporary file sharing sites. I suppose we used to collect such things in our internal SVN for safe keeping but even that isn't always viable. If folks would rather not post beta or incomplete mods to TDM's Moddb page, perhaps they would consider creating their own Moddb page or allow them to be added to my page for safe keeping. Please don't look at this as some sort of pressure campaign or anything. I fully understand anyone not willing to put their name next to something they aren't fully happy with. As a general proviso, ( if possible \ permitted ) I just want to prevent the loss of some valuable investigations and formative works. The end of Doom3world was a digital apocalypse similar to the death of photobucket. It is one of my greatest fears that TDM will become a digital memory with only the skeletons of old forum threads at the wayback archive site.

Congrats on the release! Remember to check ThiefGuild as well as the DarkFate forums (via Google Translate) for additional feedback.

For proposal #1, I imagine making a mission fitting seamlessly between the two stock missions in TDM would be a tricky endeavor, truth be told. The first mission is a small tavern robbery and the second is a modestly sized church break-in with a very reasonable jump in difficulty—fitting a mission snugly in between these two in terms of difficulty and scale is a high bar to reach. A contest to make a sequel to "Tears of St. Lucia" sounds more reasonable and would probably flow better for someone playing all three for the first time. I'd probably avoid doing something TDS related when a similar contest that allows Dark Mod entries is already ongoing, but proposal #3 sounds fun if we're given enough freedom to wildly reinterpret a Thief 1 mission. I'm somewhat mixed on the slot system as it really comes down to whether or not you want a full campaign with no repeats out of this contest. I personally wouldn't mind playing 2-3 different interpretations of something like the Bonehoard, it's bound to be interesting seeing what elements of a mission FM authors focus on.

As a mere player, I have modified Far Cry 2 and Splinter Cell games. Of course it makes me happy to see folks documenting their methods, because I would not have known where to start without them. I don't have any coding knowledge, but simply follow instructions, and merely experiment a little. As for most of your questions - the more flexibility the better, for sure. Who wouldn't be happy? Always exciting to check in on what new possibilities modders have discovered, even if these features do not interest me, so yeah I have been regularly visiting certain mod pages (including yours). Idk what anyone gets out of flame wars. There was some drama around Far Cry 2 modders some years ago that was such a bummer to see, as the plagiarizing a-hole was the same guy who also actively introduced never-before-seen possibilities. TDM has left me content so far, so I haven't really cared about learning how to mod it, but now that 2.12 introduced a faster mantling which I do not like at all - I'd give it a go if it is not too demanding.

Look pretty useful to me! On a related note, I think we need to resurrect r_showShadows. Biker has been testing maps in both 2.12 and 2.11 and 2.12 always shows higher shadow tris in r_showprimitives even though 2.12 usually runs the missions better.

I took a quick look at the training mission and I didn't notice many changes in the first place. Some new windows on walls that didn't have them, but was something gameplay related changed? I found there are still a lot of unique items missing in the object handling section which I added in my patch for example. The main issue I have with the TDM training mission hasn't been tackled, namely that it isn't a mission at all, just a loose collection of tutorial areas. Which is fine when you want come back and re-train something, but bad if you want new players to have fun discovering TDM! Yes, the two campaign missions try to do the latter, but in other games the training/tutorial is done much better in a linear fashion (e.g. Half-Life and Opposing Force) or is even integrated in a story (Bloodlines and many others). It would probably be a lot of work, but maybe it would be possible to modify the training mission, so it represents a linear sequence in which you learn one basic principle after another while actually playing a mission that is has a story and is fun! If you really think people are going to replay it, maybe shortcuts could be added to the single areas. Right now all areas start from a central room, maybe they could be connected so that there is one way where you enter a door and go around the whole room to exit at the end? (If people agree, that the training mission should be changed, maybe we should open a new thread for this discussion.)

Welcome to the forums Ansome! And congrats on making it to beta phase!

"...to a robber whose soul is in his profession, there is a lure about a very old and feeble man who pays for his few necessities with Spanish gold." Good day, TDM community! I'm Ansome, a long-time forums lurker, and I'm here to recruit beta testers for my first FM: "The Terrible Old Man", based on H.P. Lovecraft's short story of the same name. This is a short (30-45 minute), story-driven FM with plenty of readables and a gloomy atmosphere. Do keep in mind that this is a more linear FM than you may be used to as it was deemed necessary for the purposes of the story's pacing. Regardless, the player does still have a degree of freedom in tackling challenges in the latter half of the FM. If this sounds interesting to you, please head over to the beta testing thread I will be posting shortly. Thank you!

Alberic's Curse v3.11 is now out! It features: 1) A new script event related to the "Curse" 2) EFX Reverb 3) Volumetric Light effects 4) Different detail levels depending on LOD setting 5) A fix for a very old bug that caused stuttering in the basement, along with a long list of standard bug fixes 6) A few more surprises... Check for the mission update in the in-game downloader!

Here is another update to the English Stone font's DAT file used for subtitles and some readables: fontImage_24.dat This supercedes the Jan 30th update. As agreed, now all character spacings - as given by xSkip - are preserved (from this file in TDM 2.11). Exception: the Jan 30th repair of garbage metadata for "<" and ">" remains, including xSkip repair. ASCII Characters (lower 128). The earlier Jan 30th post summaries those ASCII characters that needed metadata changes to avoid adjoining stray marks. (The detail report below updates newer reversions and minor revisions.) ANSI Characters (upper 128). An analysis was also made of the status of the Stone 28 pt font's characters in the upper codepoint range of 128-255. This could be of interest if the subtitle system was some day expanded to include European languages, and continues to use the historic codepage method. The analysis also prompted some additional DAT tweaks now. Broadly, implementation of the upper-range characters (standard or TDM-specific, as defined in the TDM wiki's I18N - Character mapping I18N) is incomplete for Stone 24 pt. The status is: 43% (55 chars) Good as is. 9% (12 chars) Good enough after DAT tweak included in this update. 6% (7 chars) Missing and shown as hollow box. 30% (38 chars) Missing accent/diacritic. 7% (9 chars) Otherwise weird. But often suggestive of glyph work started but not completed. In addition, 7 chars within categories (3-5) were "improved", but are still not good. To really solve categories (3-5) requires DSS bitmap surgery (and corresponding DAT adjustments), which is beyond the scope of planned work. DAT tweaks of ANSI characters (like with ASCII) were careful to avoid changes to xSkip. Tweaks can be further grouped by problem solved.... In category (2): - (4 chars) Char is clipped, with stray mark from adjoining character on other side. - (7 chars) Stray mark, without char clipping. As improvements in categories (3-5): - (3 chars) Stray mark, without char clipping - (4 chars) Out of valid range on top edge A categorized itemization about treatment of specific problems and characters, with further details, is here: Information about methods, including new tools, to conduct this analysis and tweaking will be forthcoming, mostly after the 2.12 release.

The problem does not show up with all related dev builds. However, I cannot test with the last build (16854-10518), which I simply cannot start and get the report EDIT: As per our friend dragofer's suggestion, I made a blank script file in this build and removed the turrets from the WIP for a test. Then I can start the game and the mission and can save/load without problems. Summary: 16842-10488: no problems 16854-10518: cannot test (see above) 16854-10518 (modified scriptfile, no turrets) : no problems beta 1: problem appears

New script for mappers: my flavour of a fog density fading script. To add this to your FM, add the line "thread FogIntensityLoop();" to your map's void main() function (see the example in fogfade.script) and set "fog_fade" "1" on each foglight to enable script control of it. Set "fog_intensity_multiplier" on each info_location entity to change how thick the fog is in that location (practically speaking it's a multiplier for visibility distance). Lastly, "fog_fade_speed" on each foglight determines how quickly it will change its density. The speed scales with the current value of shaderParm3, using shaderParm3 = 1000 as a baseline. So i.e. if shaderParm is currently at 1/10th of 1000, then fade speed will be 1/10th as fast. Differences to Obsttorte's script: https://forums.thedarkmod.com/index.php?/topic/14394-apples-and-peaches-obsttortes-mapping-and-scripting-thread/&do=findComment&comment=310436 my script uses fog lights you created, rather than creating one for you. Obsttorte's script will delete the foglight if entering a fogfree zone and recreate it later more than one fog light can be controlled (however, no per-fog-light level of control) adding this to the map requires adding a line to your void main() script, rather than adding an info_locations_settings entity with a custom scriptobject spawnarg in my script, mappers set a multiplier of fog visibility distance (shaderParm3), while in Obsttorte's script a "fog_density" spawnarg is used as an alternative to shaderParm3 smaller and less compactly written script fogfade.scriptfogfade.map

Yeah, I don't know what to say. Rev 10383 works fine and 10384 does not. It is always reproducible for me, meaning that every time I try to reproduce it, I can reproduce it. After some more testing, I found that r_multiSamples set at 2 or 4 has the glitch most often at that viewpos. When set to 8 or 16, it is still possible but less likely. Setting r_fboResolution 2 made no difference. If com_maxFPS is set to something lower, such as 30, the glitched frames display for a longer period of time. Yeah, I also wonder if it driver dependent or GPU dependent. I discovered the glitch while using graphics drivers Mesa 22.0.5, so I updated my OS and graphics drivers to Mesa 23.3.2 today as a test, and the problem is still there. It's strange that rev 10384 exposed this problem. My machine specs and settings: Linux, Ubuntu 22.04 AMD Ryzen 9 5900X AMD Radeon RX 6700 XT (Mesa 22.0.5 & Mesa 23.3.2 both exhibit the glitch) com_fixedTic 1 com_maxFPS 60 Anti-Aliasing 2x (r_multiSamples 2) The video I shared shows the viewpos. Even at the same viewpos, the glitched frame will pop in and out. I've only seen this glitch happen in this single room in Accountant 1. If I move around the room at that viewpos, I can find other view positions that also expose the glitch. Here's another viewpos for Anti-Aliasing 4x, 8x, and 16x. It requires moving the mouse slightly to get into the exact viewpos to expose the glitch. (1.7 -166.4 0.0) is not precise enough. -1460.29 1425.48 172.25 1.7 -166.4 0.0 Glitched frame (Shows the curtain texture, covering most of the frame. Also, a hint of the red carpet texture?): Good frame (Same viewpos and Anti-Aliasing settings, when the glitched frame disappeared for a moment.): (Before and after rev 10384) I wonder if this might also be related to: (Before and after rev 10384) Also, sometimes on the loading screen with Anti-Aliasing enabled, I get a glitched background, which does not show with Anti-Aliasing disabled. See left side of screenshot: I don't know if the last two examples (distorted first frame on launch & loading screen distorted background) are related, but I thought I'd mention them just in case it helps track down the issue.

I'm rather surprised, for a "first mission", this was so visually appealing that it reminded me one of many Chocobo's classics. I hope your interest in TDM is still big, because I'd love to see more missions from you! By the way, what was Bert's secret?

Wasn't sure what blind and deaf actually mean to the code: I thought they only offset the alert level increase rate, not what AI does afterward. You're right that it's kind of silly I didn't think to check on higher difficulty settings as they didn't come to mind as a possible factor. I'll do that as well and see which of those points it improves: #1 might be offset by that... I think the others aren't difficulty related and just not implemented, I'll actually check before presuming though.