Search the Community

A sad and happy day all at once! I will be crying while downloading, then smiling as I install, crying while sneaking, smiling while grabbing loot. Very bittersweet and confusing.

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.

Since I'm bored and haven't posted in a while and yet still finished Thief 4 a few times, I feel compelled to post. In response to a number of observations @Rio_Walker made: Seeing your hands and all the animations newGarrett would do was fun... at first. But given all the looting and environmental interactions the game has it really did slow things down a lot, especially when the game would occasionally realign the player just perfectly before playing an animation to open a drawer. If they had an option to disable these animations or speed them up significantly I'd have been happy. I've played using the Custom difficulty with the option to disable focus and the experience is kinda mixed. While it does make things a bit more traditional without the superpower ability to find loot more easily, it does seem like the game is designed very much for focus and disabling it can hide things you never even knew were present. If it weren't for the focus for example, I would never have noticed the "special" candles hidden around the city that talk when you light them. This game reminds me of a movie that has been reshot several times with footage from separate reshoots blended together with bad editing. It's painfully clear the story has been chopped and changed over the many years of its development and there's assets in the game that clearly had greater importance in a previous iteration but for which their plot points were cut. The most obvious example is the automatons. There's a dude who provides missions on obtaining pieces for one he's building, but apart from that there's also signs in other areas they had more importance (e.g. you see rooms full of them when going up an elevator, the Baron has disassembled ones on tables in his cutscene, etc.) Some plot elements just feel not fleshed out because they had to cobble together something to create this Frankenstein's monster of a game from so many elements. The ending sucks and is incredibly abrupt. Do we even know what the deal is with that half-built ship? Probably another abandoned plot point. With all of its problems, I still kinda like it in so far as its general gameplay. But it doesn't have the longevity of something like TDM or the classic Thief games especially with all the user missions available for them. Oh well, maybe I'm just pining for what it could have been in the hands of a better developer.

@AluminumHaste thanks! Downloading now

@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.

It occurred to me that, by now, this package goes well beyond mere bugfixes by including a range of gameplay changes (i.e. adding the ability to frob-extinguish oil candles, which isn't a bug that was patched). Maybe players would have a better idea of what this package does if it had a more fitting name, similar to how Snatcher calls his work a modpack? In other communities the term "unofficial patch" is typically associated with collections of community fixes to bugs that exist in the core game and were never addressed by the devs. Most players would therefore expect an "unofficial patch" to provide them the same experience as originally intended by the devs, but without technical problems.

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

I think the default gamma was raised to 1.2 to reduce banding and color precision artifacts at the low end of the brightness scale. There are probably some confounding factors that make that a questionable decision. 1) At the time of this discussion, I believe TDM's bloom settings were generating extra contrast and thus lowering gamma 2) By the time that soft gamma was implemented, we also were using a new bloom system that does not tie the bloom effect to other post processing effects 3) There was some attempt to make TDM shaders compliant with industry gamma defaults but that attempt to adhere to standards may have caused problems because most games are much brighter than TDM so using calibration established for use in brighter games may cause unintended results. These days, I normally set gamma to 1 ambient gamma to 1.1 and set my postprocess color curve to 0.2 or 0.3 which darkens gamma back to something similar to 1. Maybe someday I'll purchase a monitor calibration machine and try to sort out the ideal default state.

Congrats on the release! Thanks for the great mission, I had a lot of fun. I played the mission with Linux and had no problems

And those pics that Daft Mugi posted do show the problem with TDM maps, but I also have to say, that is a problem with TDM shadow maps, not with maps in general, I never seen such ugly issues in Stalker for example or Call of Juarez and many other games. Perhaps those shadow maps issues arise from people not thinking of shadow maps at all, when creating their lights, shadow maps do require a little more tweaking to look good, specially at grazing angles, because they are literally textures, so perhaps moving the lights a little solves those problems or even increasing the shadow map res. Just think about this, if shadow maps where that ugly, the gaming industry would never deprecate stencil shadows and we would still be seeing a ton of games using them, but is totally the contrary, games with stencil shadows, are the minority, even idSoftware removed them, I think since Rage (i'm not totally sure about Rage...) and up (besides obviously Doom 3 BFG). For example: Wolfenstein II Dishonored 2 Evil within 2 (this particular shot is impossible with stencil shadows, because of the blood that is a particle effect with alpha) etc. For obvious reasons TDM fans have a good opinion of stencil shadows and I comprehend that, they do look very good, TDM and Wolfenstein 2009 are the games with the best soft stencil shadows that I haver seen, but maps can also look good, if given the chance and used to their full potencial. another game with good stencil soft shadows Thou tree shadows on this game seem to use something else or literally stencil shadows because sometimes they look like a blob on the floor instead of seeing the individual leaf.

Open questions for all. As a mere player, have you ever modified other games? Have you installed unofficial fixes, patches, updates, upgrades, expansions, mods? Were you happy it all was well documented? Were you happy that you could control what was being installed? Were you happy that it worked? Were you happy that you could install other stuff alongside without problems? Were you happy that you could uninstall it? Did you care about the authors or flame wars going on in obscure places of the internet? Players download stuff, sometimes read the instructions, install it and judge it. ---------------------------------- My friend Wesp5, Listen to the feedback. As a start, I would like to see the patch, or parts of it, in pk4 format. If you were to split your patch into standalone mods, which mods would you produce?

I spend 90% of my time on Linux Mint. I occasionally pop over to Windows 10 to check a few things or run some updates but Linux Mint is my home. TDM runs better under Mint than Windows for me but your mileage may vary. When running TDM in Linux, you must set FPS to "Uncapped Mode" in the Advanced settings, the old capped mode has terrible stuttering and performance under Linux ( even native Doom 3 has this issue ). You can set Max FPS to 60 if you are worried about any inconsistencies with game timing ( the only known issues are rare problems with audio behavior at really high FPS). Just don't use the native 60FPS capped mode, use Uncapped mode with a Max FPS value.

You'll be surprised to hear but I don't quite get it either. Based on my understanding, there are a few confounding factors that make this a challenge. 1. We did a lot of work to ensure that the "included missions" were made part of the install so first time players would have a curated experience. Moving the missions back to the mission database might require undoing that work. 2. It is entirely possible to add the missions to the mission database while also being included in the installer but doing this will invite a few problems: 2a. What if the user updates the mission and then finds that their TDM install is somehow borked. They might run the installer to repair it and this will revert the mission version. If they fail to update their mission after this revert they might have incompatible save games that cause crashes and confusion 2b. What if a user starts downloading a mission update and at the same time starts a TDM upgrade ? 2c. Users opening bug tickets for a base TDM version due to problems seen in the included mission that are no longer present in the updated one, thus making it more tedious to narrow down duplicate bug submissions. 2d. Players seeing the missions on the TDM missions download page and downloading the package to install in the FMS directory then seeing duplicates in the mission list because the downloads page renames the packages with hashed filenames. All the above challenges revolve around potential user error and even though it should be obvious not to do these things, we have to compare the above to the vast swaths of folks who are begging to include TDM into Steam because unpacking a zip file and running an installer executable within a folder is "too difficult and confusing". One thing that we have the ability to do is change the file in the 2.12 installer repo so that if users run the updater it will apply the new mission. This change would not be visible to users so they would not get any alert about it. We would just have to announce it and hope that players watch for TDM announcements. I am doubtful anyone would want to work on it but I suppose that there could be some way to pass some sort of signal to the mission downloader when included missions have been changed on the installer side so they get a different update indicator. Still would be kludgy because you'd either be telling the player to exit TDM and run the installer or making TDM invoke the installer internally. So that is my take on "why" based on my own knowledge. Of course, part of my inability to "understand it" is due to my incredulity that we need to cater to players who are so below the bar in computer literacy that they would inflict these problems on themselves in the first place. None of this is an official stance just my own take on why the proposal to "let two updater processes control the same files in the same folder" has been rejected ( other than that such designs usually horrify programmers on a primordial gut level and if you mention that any program that does this you will see any programmer in vicinity instinctively reach for headache or stomach medicine ).

Excellent. This will take up my whole upcoming week, I'll take all my time off to good use testing the latest release candidate and suggest if there's really any problems. The devs are right that the beta sounds like its no longer regressed between introduced features. This is going to make my week!

Could it be anything to do with the shape of the geometry? Is a curved staircase looking at the images. Or the thickness? Thou by that image those stairs are anything but thin. Is just that I have seen thin walls leak light, while ticker ones do not and I have seen this, in more than one engine even in lightmapped ones. Also is that brush geometry or a imported triangle mesh? You will correct me if wrong but afaik the engine treats triangle mesh's, a tad differently from brush geometry, like it doesn't automatically inline the triangle mesh geometry, into the overall baked brush geometry (unless your force it), so it leaves a invisible "gap" there where the mesh connects with the brush wall? Could be floating point accuracy problems, like you recently talked about?

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!

Oops, in that last release, I accidentally didn't check character spacing in the codepoint range 128-159. And sure enough, there were problems with character 131 & 132, which needed 4 more pixels of horizontal box shifting than the 3 pixels they got earlier. So here's a better version: fontimage_24.dat of Feb 24

What do you mean by moving them around? You move them from the models folder into another folder? Models must be placed in the models folder. Otherwise, DM/DR cannot find them anymore causing the problems you mentioned in your post.

Hi, I'm messing around with patches to see what can be done with them, and I have a couple of questions. None are critical issues, as a matter of fact, I doubt I'd notice them or cared if I were playing someone else's map, but as I'm learning, knowing what can't be done is sometimes as important as what can be done. Here's the thing: is it possible to bevel a surface not parallel to one of the orthogonal axes, in other words, a slanted bevel? To be more specific: I'm having problems with snapping it to the grid; it doesn't want to. I mean, I have done the bevel, and it looks nice from a distance, but the slanted surface refuses to snap to the grid, which causes a visible, although small, seam (or at least I assume that's the reason.) And projecting the texture is also a bit of pain. Let's see if I can attach a picture... OK... [a few/lots of minutes later] messing around with it one side now looks much better (almost imperceptible seam, tbh,) but the other side still looks off. I still can't snap to the grid the four corners (interestingly, it's the main brush, the frustum, the one that refuses, not the bevel, which is perfectly snapped). I can snap three of the four corners, but there is always one that shifts on its own will, even when using the smallest grid. See the next two pictures, where I have the main brush and the patch selected; the dots overlap except that one. And if I snap that one, another will shift (clockwise? I think.) I mean, that's like... what, 1/3 of 1/8 of a Doom Unit? 1mm? Not game-breaking, really, and nothing that can't be hidden with some trim or just in shadows, but I wonder if there's a technique for this or what I did wrong. [Hmmm, after some thinking, I wonder if my issue was creating the original cube on grid X and then cutting the triangular corner for the bevel on a different grid size so the corners were weirdly placed... I'd have to test that out] And speaking of seams, is it possible to make a smooth texture transition from the surface of a cylinder (or ring or whatever) to its cap? See the third picture, which is the rounded base of a column. If it's not (or it takes a lot of effort or editing), then it's no big deal, as there are more important things to worry about. But if there's a quick & easy way (natural projection hasn't worked for me in this instance), it would be good to know. Thanks!

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.

in case you wonder my beard was white when i hit 25 only started getting some grey streaks in my hair in the last two years hehe. and for those younger here enjoy your youth while you have it at around 40 the problems start (just look at those receeding hairlines atrocious!!!), well if the hair was my only problem i could live with it hehe i also got gall stones kidney stones and a nasty fall which broke my back in two places at around that time. So enjoy it while you can or stay away from ladders

Are you aware of the pointfile feature? Dmap writes these .lin files into the maps directory. Display them with File->Pointfile and look for red lines that visualize problems like leaks and visportal problems. Which faces of a brush are sealing depends on the material assigned to the face. I don't know exactly which ones seal and which don't.