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.

Well, in regards to the core assets it is probably worth a consideration to tune down some of the brighter gui backgrounds. (The gui in the video is the same as in your first post, so it is probably a core asset.) This would additionally result in a more consistent look, which isn't the worst thing imho. But regarding guis specific to certain fms I still think you should address this in the respective mission threads. Personally I never had an issue with this matter (although I can see that it can be one), which leads me to believe that this is heavely depending on factors like the monitor used for example which may could cause mappers not beeing aware of that effect. Maybe you can list the guis in question so we can see whether they are stock assets or mission specific?! That would be a good starting point.

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.

Just want to mention that there is a bat asset: I think horror is a nice theme to try them.

Maybe I'm just a little tired but when I opened up the thread and glanced at the image, I thought the idea was how you were going to create a new asset based off the real-life safe shown in the image. It took a bit before I realized it wasn't actually a photograph! I got nothing to contribute except to go for it, we need more safes!

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!

Welp, I couldn't stop digging and learning more about this. The first post in this thread was accurate at the time of writing, but it could currently cause confusion. What those directions imply is that the custom build and its assets are based on dev16599-10071 (16599 assets, 10071 source code). So, dev16599-10071 will have almost all of the files needed and the custom manifest includes only the very few files that are different, such as the blackjack custom assets (pk4) and custom dev build (exe). @stgatilov explained this earlier in this thread. In other words, the installer will download dev16599-10071 (many, many files) and then download and apply the custom manifest files (just a couple or a few files). @Obsttorte provided screenshots to show how to use the installer earlier in this thread. (The manifest url is now different than the screenshot, though.) @Obsttorte added the blackjack assets and scripts as revision 16607 (assets), so dev16617-10107 or dev16625-10132, will also work, since the assets are a later revision. (In the dev build name, the first number is the asset revision and the second number is the code revision.) Checking my copy of dev16617-10107: tdm_base01.pk4 2022-09-07 20:23 script/tdm_weapon_blackjack.script tdm_defs01.pk4 2022-08-22 22:15 def/tdm_weapon_blackjack.def tdm_player01.pk4 2022-08-21 20:24 models/md5/weapons/blackjack_view/ready10.md5anim 2022-08-21 20:24 models/md5/weapons/blackjack_view/unready10.md5anim These filenames match zzz_blackjack.pk4, which was posted earlier. What we need to know from @Obsttorte is: Is the latest set of assets submitted to SVN? If so, what is the asset revision number? Is the latest code submitted to SVN? If so, what is the code revision number? With the assets revision number and the code revision number, you can look at the official dev build name to see if it has everything included. If the official dev build name has a revision number smaller than what @Obsttorte tells us or something isn't included in SVN yet, then we need to use the custom manifest to fetch the latest blackjack version. Otherwise, the official dev build has everything. @Wellingtoncrab So, that's a long-winded explanation to say, yes, you probably do. If @Obsttorte says, yes, everything is in SVN as 16607 (assets) and 10105 (code), you can know if you have everything by looking at the dev build name. The name dev16625-10132 is 16625 (assets) and 10132 (code). Both are greater than required, so all is included. Again, I hope I got that right. Some of this is new to me, and I had fun figuring this out tonight. Cheers

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!

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.

Yeah, it's not high quality enough to be used for asset generation, but like all things, it will be a tool in an artists toolbelt in the future.

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!

I think it’s a barber chair as well - more of a Victorian feel which I think can work with the setting - some custom animations would definitely add a lot. There was some question on the discord whether ai would be able to sit in it at all given it’s height and the step so it at least it works (with help from a bit of monster clip) This is very tricky to get consistent across lighting conditions - the “showroom” light is fullbright which kind of exaggerates the effect and they (hopefully) look more natural in scene lighting. All of the four revisions contained some amount of tweaks to specularity on the materials always still working on that! Yeah I would say while I think it’s gotten better over time, until recently video games have seemingly never been afforded the opportunity to be concerned with consistency in terms of fidelity across assets. If you look at the xbox 360/ps3 area where things like asset streaming from disc and memory management were much more constrained the fidelity of assets was all over the place. The detail was of course typically weighted by an assets prevalence in a scene, so you could still argue TDM is at a disadvantage there, but it’s just to say I think you can still have a consistent visual style with varying levels of detail across assets. Bad news would be that kind of consistency is just as hard to achieve. That being out of whack I think is at a glance more likely to cause a player to feel something is out of place. There is obviously some problem with these assets in that they were never intended to be art in an engine like this. The low detail diffuse from a PBR material with the high level of geometric detail on the models themselves instead of say the normal map means they are never going to get as much out of the engine as efficiently as something which was built for the ground up for it. Still … the price and license arrangement is right.

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!

** As of 2.11 many of these assets have been further optimized and incorporated into the core mod** *These are reposted from the discord server* Conversions of cc0 licensed assets from https://polyhaven.com/models: **POLY HAVEN CC0 ASSET PACK 01 "SEATING"** - REV4 - narrow seats. wide seats - red seats. blue seats **POLY HAVEN CC0 ASSET PACK 02 "GOTHIC"** - Initial Release - Even more furniture - Interactive prefabs: Containers, cabinets, drawers, "working" grandfather clock - Fully modular pier kit - A very nice bed ! But AI can't sit in the chair ! Notes on "optimization": many of these meshes are particularly tricky for a very novice modeller as they contain a lot of smaller detail geometry which ideally would be baked into a normal map. That's a bit beyond me admittedly, so a much greater emphasis was put into keeping a higher level of detail but having as few shadow casting triangles as I could manage. The shadow mesh is typically only 10-20% of the overall polygon budget of an asset in the pack with some exceptions for the large "hero" assets like the bed.

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/

@wesp5 Given authors can set their missions anywhere and we all love shiny new assets I am certain there are are some who would appreciate having a new asset to use for a world map if you posted one. Why you think you should alter the art and setting of author's missions - both elements of the story - is beyond me but I doubt that will stop you. All in service of what? This fictional universe diverges from the history of continental Europe almost 1500 years ago and features ghosts and werewolves, but somehow this cannot conceivably fit in that framework? Really the wiki goes through pains to specify that everything is a suggestion and what actually matters are the intentions of fm authors. They do not need you to decide this for them. I will say I don't want your map in my mission and ask that you please exclude it from your patch. I actually spent a lot of time trying to create some continuity with the larger world and building off of elements mentioned in the background on the wiki. I have readables which speak to specific geography of Bridgeport and the larger world which do not conform with yours. The conflict with Menoa features heavily as well with many characters being Menoan war veterans. I guess in your mind Menoa was Ireland?

One consequence could be that, for consistency, all mappers use that map for world reference. Would be kinda weird if a mapper came up with his own imagined world map in one of his missions now, when everyone thinks Bridgeport is located in France (yes, the future France). Well, maybe that's what the creators of the mod wanted. I don't know how old that asset is, and who did it originally.

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.