Search the Community

Gosh.. Since when did the image upload in the forums stop working... Anyway.. I tried out the new view setup - thanks a lot for all the advices. I positioned a little "attribute bar" to the right. So as soon I select an entity I can see its spawnargs. However what did not matter as it opened as a new window before does come to light now that it is just a small bar: The size of the spawnargs view is really small and there's lots of empty space that could be used for it instead - however I cannot enlarge the attribute / value part of the window - it just stays by a few rows. Maybe I'm doing something wrong - maybe it is a possible new feature in the next update - here is the screenshot: https://ibb.co/PcSmFT2

Thanks, I can also recommend gog galaxy. The idea of the custom tags is really nice, I'll have to try this out too!

DarkRadiant 3.5.0 is ready for download. What's new: Feature: More customisable layout, all windows and panes can be dragged and arranged Layouts like Embedded, Regular and Splitpane are superseded and have been removed Tweak: The LayerControlPanel's tooltip popup is now less annoying Tweak: Clarify distinction between Shadow render mode and other render modes Fixed: Show/hide Light Volumes for combined entities inconsistent Fixed: Currently applied particleDef not selected in Particle Selector Fixed: Layer visibility checkbox not reacting to double-clicks Fixed: Cannot toggle visibility of layers in Linux Fixed: Drag-and-dropping layers is not working in Linux Feature: Customisable Layout (click to see the videos) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.5.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!

1. If you want to use custom work (sound, models, textures) from released missions, best thing is to ask the author if he/she agrees. So far, Sotha is the only one who permits unlimited usage of his custom work (he expressed that here on the forums). He just wants to be credited. 2. If mission authors from released maps are not available anymore, then I do not know what to do. @Dragofer@nbohr1more: Any suggestions? I would say, that's the same situation as described above, just replace "released mission" with "abandoned work". As for my released work, feel free to use whatever you want.

Also, fllood isn't active on the forums a lot it seems, so maybe another person can give authorisation when @fllood isn't around? Just an idea. I guess I could pm this to fllood. Edit:

Would be interesting to also see a shot of the mission in DR too for mappers to get a better idea of how much there is and how dense (brush, patch and entity counts would be good too). @Baal Have you tried sending a PM to fllood? Simply pinging them with @ only gives them a notification when they log into the forums, while a PM will also get sent to their email.

To be honest I can't remember ever using TAB to choose between items in a group. I certainly wasn't aware of it when writing the user guide, which is why the section on converting to func_static mentions using TAB, but the section on grouping doesn't. But it would certainly be useful and consistent behaviour.

Hello! I just joined the forums to report an annoying bug. I don't know if it's specific to this map or just a game bug but I have played most of the other missions and this is a first for me. Before i picked up the key to the junkroom i tried to open the door and i got the "needs junkroom key" message on my screen... but that message never went away. I had to complete the mission with that on my screen the entire time, overlaying all the other messages that appear. a reload/restart didnt do anything to solve the problem. A few of the on-screen messages at the beginning didn't make sense to me and were kind of cryptic, like a riddle i didn't get. one of them was something about an alarm? otherwise i liked the mission, pretty challenging and I know i missed some spots. cheers

DarkRadiant 3.4.0 is ready for download. What's new: Feature: Allow Layers to be arranged into a Tree Fixed: Readable Editor displays "shader not found" in view Fixed: Undoing snap to grid with prefabs causes crash Fixed: Include doc in building instructions Fixed: Decal textures causes DR to crash - (textures/darkmod/decals/dirt/long_drip_pattern01) Fixed: Skin chooser: double click on materials list closes window Fixed: Selecting and deselecting a filtered child brush through layers leaves the brush selected Fixed: Material editor re-sorts stages on pasting image map resulting in wrong material stages list and wrong selected stage Fixed: Crash on start if engine path is choosen (Doom 3) Feature: Layers can now be arranged to form a hierarchy Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.4.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!

Is this to install Flatpak? To install Flatpak follow this guide: https://www.flatpak.org/setup/Debian See also: https://wiki.thedarkmod.com/index.php?title=DarkRadiant_-_Flatpak_Installation_Guide Sorry if this is redundent info. I wasn't sure if you do it right. Sorry for derailing the topic.

Here is an index of video's: https://wiki.thedarkmod.com/index.php?title=DarkRadiant_Video_Tutorials , in case you need more. I had this idea as well. I have not made anything yet. Nice to see others agree with it as well. I thought some aspects of this mapping guide of Unvanquished are interesting: Source: https://wiki.unvanquished.net/wiki/Tutorials/Mapping_guide

It's interesting because I recently read a thread on the Doomworld forums on people's opinions of single-segmenting maps in classic Doom/Doom 2. In other words, playing a map from start to finish without using saves - if you die, you have to replay the entire map. The general consensus was that saves are useful, however there was some merit in there being extra tension and challenge knowing that death couldn't be rewound easily by reloading a save. On the other hand (and speaking as an adult), people have to work and often have limited time for gaming. Having to replay a long map because you died can be quite off-putting and takes the joy out of a game if it happens often enough. Savegames keep the tempo going, keeps the feeling of progress going. Also someone pointed out that starting a map from scratch after a death is kinda like using saves anyway, just a single save at the beginning. You're just being tedious by denying the use of saves in this case. Dunno where I'm going with this. Trying to be diplomatic and say I can see all sides to the discussion.

DarkRadiant 3.3.0 is ready for download. What's new: Feature: Remove menu options which are not applicable to current game Feature: Grey-out menu entries that are not applicable Feature: FX Declaration Parsing Support Feature: FX Chooser Feature: Renderer now takes "translucent" keyword into account Fixed: Lighting Mode Renderer draws hidden lights Fixed: Loading map results in "Real Hard DarkRadiant Failure" exception Fixed: Crash when trying to set default mouse or keyboard bindings Fixed: Unit Tests intermittently get stuck on Github runner Fixed: xmlutil thread safety problems Fixed: Some materials aren't displayed correctly Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.3.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!

@STiFUBeen a while but hoping you don't mind I bug you again on this topic. I lurk in a certain VR discord and saw this paper mentioned https://iovs.arvojournals.org/article.aspx?articleid=2613346. And it was hypothesized that the conclusions of this research may have significant implications for dynamic focus VR displays, and now I'm kind of wondering about this as well. The general assumption of the, I guess, "XR community" is that you can solely use various forms of artificial defocus (and not optical vergence) as feedback to guide the eye's accommodation to a desired focus depth, and thus even VR displays capable of displaying only a single varying focus depth (as opposed to a multi-focal display) can actually function: as the user's eyes move from the in focus part of the image to an out of focus part of the image, the artificial defocus blur generated in that out of focus part of the image is considered to be sufficient feedback to trigger the eyes to accommodate to the new focus depth (even though the optical vergence of that part of the image is still incorrect). But, assuming I'm understanding the paper correctly, without the presence of "genuine" optical vergence corresponding to each potential focus depth in the scene, there wouldn't be sufficient feedback for the eye to accommodate to that depth correctly. There are apparently many accommodation cues for the human eye, but the claim here seems to be that true optical vergence is necessary. And wouldn't that mean a multifocal display is necessary? It seems interesting to me because from what I've gathered over the past few years the varifocal prototypes in various labs are said to "kind of" work for certain people and not work at all for others. So, even assuming eyetracking were perfect, if they are nonetheless unable to provide the required feedback to guide accommodation, then the very kind of dynamic focus display that everyone is banking on (for the near term) to address the major optical issue with modern VR headsets would seem to be a dead end. You would instead need something like the CREAL lightfield headset I mentioned a while back. And facebook recently pushed their timeline for varifocal headsets out from 2022 to ~2030. (again, assuming I'm even understanding this correctly)

I found the forum post I did about it here: https://forums.thedarkmod.com/index.php?/topic/9082-newbie-darkradiant-questions/&do=findComment&comment=459121 I don't think I got a reply, and we were near release time so I just gave up on it. It worked at some point, so was probably something on my end. Regardless, having to use a Perl script hosted on some obscure server that nobody maintains anymore doesn't seem like a robust process. I think you can build the FM from the start to support i18N and not have to use that script. That's the approach that I think I will take for my next FM. Looking at the Wiki page, it's not that clear how to do it so that's what I'll aim to sort out. But then again, unless there are plenty of people waiting in the wings to perform translation work, not sure how motivated FM authors will be to support this.

And follow the compilation guide at the wiki. https://wiki.thedarkmod.com/index.php?title=The_Dark_Mod_-_Compilation_Guide

That was a very ambitious fm! Many steps to complete, but also some helpful read-ables and maps to guide you though. Lots of new looking assets, like those lamps That also led to a different play style than usual. I enjoyed knocking out dozens of Hammerites for a change - I love to hate those guys. No major bugs, but I managed to get outside the map in a couple places. One was where I climbed some rocks and got over the gate the back of the farm (I was able to get back in though). One small issue was I think if the Objective page was updated to say "after all other objectives have been completed, bring the cure to the Hospice" it would be a bit clearer. One question: Anyway, thanks for the mission, it was time well spent!

DarkRadiant 3.2.0 is ready for download. What's new: Feature: Show entityDefs related to selected models in Model Chooser Feature: Support for rendering blend lights Feature: Implement sorting of Interaction Stages Feature: Recognise type of "set x on y" spawnargs Feature: OBJ files: loader supports usemtl keywords directly referencing material names (without .mtl file) Fixed: Material editor: additional preview object in textures/glass/ materials Fixed: Every attempt to load a texture will trigger a SIGSEGV signal caught: 11 Improvement: Update to wxWidgets 3.2.0 Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.2.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!

Hi! Welcome to this forum. Like many others who would like to compile TDM for their favourite Linux Distro: We advice to look for sollutions or do it yourself (using some guides), let us know how you did it and where you got stuck. Or Dont compile the code and just try the binaries. This by downloading the tdm installer binary (from the website or your packagemanager) and use it to download the game files. (Or downloading old standalone package from moddb) Installation guide: https://wiki.thedarkmod.com/index.php?title=Installer_and_Manual_Installation Compiling Guide: https://wiki.thedarkmod.com/index.php?title=The_Dark_Mod_-_Compilation_Guide After reading and following the guides, do a forum and google search and then try again. For example, I found a TDM on nixos issue on github: https://github.com/NixOS/nixpkgs/issues/98936

DarkRadiant 3.1.0 is ready for download. What's new: The Texture Tool got its Free Scale operator now, allowing you to fit the texture with the mouse instead of having to type in the percentages. A lot of work went into the Declaration handling (EntityDef, Skins, Materials, Particles, etc.), which is now much more robust and more conformant to how the game is doing things (at least until TDM 2.10). The Material Editor got a plethora of issues resolved Improved the Model Export dialog and options For more things that have changed or fixed, see the list below. Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.1.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! And I'll gladly repeat myself, by thanking 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. Changes since 3.0.0 Feature: DR doesn't consider wildcards in skins Feature: Reload Images eature: Texture Tool free scale Feature: Add "Show Definition" to all ResourceTreeView instances Fixed: "Reload Defs" doesn't remove entities that have been commented out Fixed: 'Reload Sounds' doesn't load new FM sound shader definitions Fixed: Reload Defs is not sufficient for reloading modelDefs Fixed: Models are reset to origin after reloadDecls Fixed: Skin Chooser doesn't preselect non-matching skins Fixed: Moving speakers deletes distance spawnargs if they're the same as in shader Fixed: Unable to select func_emitter with particle attached Fixed: Particle Editor Preview lacks vertex colours in lighting mode Fixed: Particle effects still visible when hidden via layers or filter Fixed: Entities referring to modelDefs should use the "idle" pose where possible Fixed: DR does not parse materials in def files Fixed: Modifier Hint Popup can crash when hitting Ctrl/Alt/Shift keys during shutdown Fixed: Insignificant digits displayed in Surface Inspector shift/scale/rotate values Improvement: Skin Chooser: show in which .skin file the skin is defined Improvement: Declaration Block Parsing overhauled Improvement: Python Interface for IDeclarationManagerImprovement: leave player start entity selected after placemen Improvement: Let Map Info show materials used by models Improvement: Renaming Declarations causes problems when saving it later Improvement: Light Texture Preview should display editor images if present Improvement: Remove comments about particle generator in .prt files Material Editor: New Material is locked if the default unnamed name is already in use Material Editor: allow to delete materials Material Editor: image browser's "cancel" button rewrites the material source text Material Editor: does not save manual edits to source text Material Editor: should show .mtr the material is defined in Material Editor: after "Reload Images", image previews are only updated when selecting a different material Material Editor: suboptimal preview for cubeMap materials Material Editor: preview object doesn't have smooth shading Material Editor: preview doesn't take "scale" into account in Textured Mode Material Editor: blend add stages are rendered separately in preview in lighting mode Material Editor: test frob highlight button not working Material Editor: doesn't remember settings from previous session Material Editor: image thumbnails use "scale" keyword from previously selected material Material Editor: frob highlight stage not updated correctly when changing diffusemap Material Editor: using Escape to close ignores unsaved changes Material Editor: Global Settings should be preselected Material Editor: some declaration text is lost while editing#6047: Material Editor: clicking "cancel" when selecting a light classname clears the classname field Material Editor: new materials always sorted last Material Editor: filter for image browser Material Editor: can't unlock editing on materials in "Other Materials" folder Material Editor: tries to save materials in DarkRadiant folder if no FM is installed Material Editor: allow to change preview backgroun Material Editor: preview renders shadows for noshadows materials 'Export selected as Collision Model' doesn't auto-create path folder and throws error Model exporter: manually enter export origin Model exporter: export origin choice should use a radio button Model exporter: only 1 entity's model is reloaded Model exporter: "Use entity origin as export origin" still uses map origin Model exporter: rename "Center Objects around Origin" The list of changes can be found on the our bugtracker changelog. Have fun mapping!

Have you tried this? https://forums.thedarkmod.com/index.php?/topic/14126-ftpthedarkmodcom/&do=findComment&comment=333594

Nice effect, but not for me. Found a topic about it: https://forums.thedarkmod.com/index.php?/topic/17426-stereoscopic-rendering-red-cyan-anaglyph/

Interesting that they would complain but not here, on the official forums. If enough people bring it up, it's always looked at, even if there's no one who can actively work on it.

Shadow maps could be applied to vegetation, we just need to decide how to handle the special cases and not break the appearance of existing missions. Relevant discussion: https://forums.thedarkmod.com/index.php?/topic/19659-feature-request-emissive-materialsvolumetric-lights

I enjoyed this mission, but fell at the last hurdle: I can't figure out how to "Leave with the loot"! I tried going back to the starting point, but nothing happened. All of the windows have bars, and I can't find any doors out of the bank. I also had to consult the forums to find out how to empty the teller safe. That key hiding place is very non-obvious (at least from a Thief perspective — I guess it makes perfect sense in real life).