Search the Community

I recall I speculated about this option when I started working on tdm_installer, i.e. using zipsync for FM downloads too. The common opinion was that's not necessary... now a lot of things happened, and turning the wheels would mean a lot more development. Also, it was common opinion that even though we provide older versions of TDM, we don't support them. I'll create 2.09 tag in SVN before committing the breaking changes (and will create tags before every major release), so the state of 2.09 will be saved. But I don't think players will be able to access it.

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

Recently I started listing the Abandoned Works on a wiki page. Looking through some of the project folders I encountered assets that were posted on the forum years ago (for example this fish), but I never read about them before. I don't think the forum is good for listing assets, it's off course good for discussing. So I was wondering maybe it's an idea to make a list of game assets, including scripts, centered in one place? Knowing the assets exists, people are able to find it on the forums (placing direct links on the wiki page will get outdated). I might have to ask people for permission.

For the last 1-2 weeks the forums have been really slow and unresponsive for me, when I type a post half the time it just sits there etc.. is anyone else having the same issues..?

Does anybody else have this problem? In the (European) evenings the forum is unbearable slow. The server is delivering about 8Kbyte/s, sometimes less and usually stops midwhere during loading the page. Sometimes you can't even get the index page, sometimes you can log in, but then only get half of the overview etc. In the mornings everything is snappy.

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

I've upgraded IPB to the latest stable version, and since this was a major upgrade (from 2.3.6) I also had to re-do the forum style. Most of the new stuff is in place, but I bet that the logo will be changed. One of the many new features in version 3 is rating of posts and also a "report spammer" ability which will make it easier to single out spam bots and ban then at sight. Hopefully this will stop some of the spam threads we've seen recently. Make sure to empty your browser cache if you're experiencing any problems. And please report any errors etc in this thread. Cheers, ~m2

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

Hey all, I just noticed on the TTLG forums that Xorax released a large (1600+) set of textures for public use. I browsed through them and they match well with TDM. While they don't have normal maps, I'd still recommend giving them a once-over. Here's the TTLG thread: https://www.ttlg.com/forums/showthread.php?t=151606

DarkRadiant 2.14.0 is ready for download. This release focused on DarkRadiant's texturing abilities, the Texture Tool and some of the Surface Inspector algorithms have been completely rewritten. A new model importer UI has been added with the ability to convert FBX models into a format compatible to the game (it can also convert LWO, ASE and OBJ models). The EntityInspector can now deal with more than one selected entities, showing the shared key values in the list. Copy/Paste Textures across angled faces: Texture Tool Rotate Tool (use "R" hotkey to switch) Surface Inspector Harmonise Scale / Linked Scaling Surface Inspector Normalise EntityInspector Multi-Selection Support 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/2.14.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! 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 2.13.0 Feature: Texture Tool Improvements Feature: Texture Tool: Add Manipulation Panel to shift/scale/rotate selection Feature: Show shared keyvalues when multiple entities are selected Feature: Texture Browser Filter: match multiple words (using 'AND' logic) Feature: Skin Chooser shows materials of the model Feature: Surface Inspector: Add buttons to harmonise Horizontal and Vertical scale values Feature: Improved pasting textures to angled faces sharing an edge Feature: XY view zoom is centered at cursor Feature: Texture Tool: Constrain operations to axes by holding down Shift Feature: Texture Tools: rotate function Feature: Texture Tool: UI contrast Feature: Model Conversion UI Feature: Add FBX model importer Feature: add IQM format support into lib/picomodel Feature: Spawnarg type icon not shown for inherited properties Improvement: New Game Connection GUI Improvement: "Replace Selection with exported Model" preserves spawnargs Improvement: automatically reload exported models Improvement: Search function: don't start searching while still typing Improvement: MediaBrowser toolbar: clear filter text when texture is selected through MMB or Texture Browser Improvement: Merge "Create player start" and "Move player start" options Improvement: Patch Texture Rotation should take aspect ratio into account Improvement: Texture Tool: use aspect ratio of material Improvement: Step-rotating textures through the Surface Inspector should be using the center as pivot Improvement: Surface Inspector: Option to change horizontal and vertical scale values proportionally Improvement: Apply textures to surfaces using "normalized" scaling. Improvement: Normalise button brings texture coordinates closer to 0,0 Improvement: Prevent Texture Tool "face jump" on rescaling textures Improvement: Move modifier hints out of the status bar Improvement: Flip Texture: Prevent huge face UV coordinate translations Improvement: Double click on list elements should auto-close dialogs Improvement: Texture Tool: Select items by clicking the UV space they cover Improvement: Texture Tool: Grid lines are getting too dense when zooming out a lot Improvement: Texture Tool: intercept keystrokes for grid resizing & snap to grid Improvement: Model Exporter: warn if Output Format and extension in File Path don't match Improvement: Change Quake3 map exporter to write "legacy" brush syntax Fixed: Q3 Legacy BrushDef parser sometime produce some wrong texture rotation Fixed: "Replace Selection with exported Model" assigns result to Default layer Fixed: All scene graphs connect to the same undo system, causing interference Fixed: Remove Floating Layout Fixed: EntityInspector allows to set an entity's name to an empty value Fixed: modelDefs folder starts expanded after changing selection Fixed: Particle Editor: wireframe does not render Fixed: Drag-select while in texture tool window gets stuck. Fixed: Some brushes change shape or disappear when rotated or duplicated Fixed: Texture Tool: drag operation doesn't capture the mouse Fixed: Ctrl-S does not work when focus is on inputs Fixed: Autosave filename unhelpfully overwrites 'save copy as' filename Fixed: Merge Maps: can't hide changed entities/primitives Fixed: Merge Maps: can't center orthoview/camera on changed entities Fixed: Merge Maps UI remains if DR is closed while a merge is in progress Fixed: Merge Maps: "Details" text doesn't use full width of window Fixed: Brushes colour schemes not saving Fixed: Fit Texture fields do not allow values below 1.0 Fixed: PatchDefExporter: do not write trailing white space after shader name Fixed: LWO2 Model Exporter doesn't write vertex colours Fixed: Objective components not correctly renumbered after removing a component Fixed: Applying a skin to a model entity no longer works under 2.14pre1 Fixed: Spawnarg types and tooltips not reliably inherited in entityDefs Fixed: Crash when saving map or prefab without a file extension Fixed: Texture Tool crashes when creating a new brush Fixed: "Texture tool" grid cannot decrease under 1 Fixed: Texture Tool: dragged vertices snap to grid even though it's switched off Fixed: Sound chooser not pre-selecting the inherited value of snd_* keys of an entity Fixed: User Guide (Local) doesn't work Fixed: Restore GL_LINEAR_MIPMAP_LINEAR texture filtering Fixed: Objective components not correctly renumbered after removing a component Tweak: Surface Inspector vertical shift / vertical scale arrows Tweak: Surface Inspector's minimum width is too large The list of changes can be found on the our bugtracker changelog. Have fun mapping!

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

From a design perspective, the mission types are a mixed bag consisting of locations (mansion, city), genres (horror) and game play types (platforming). Ideally we'd want to split these 3 groups and allow multiple tags in each group. This would cover both single missions and campaigns. It could possibly facilitate an advanced tag-based search if we'd ever want one. And maybe even something fancy, such as a mission recommendation system based on, for example, highest percentage overlap of type tags from already finished or downloaded missions. I wouldn't do those features in C++. Python has easier access to data science tools to do such things. To keep it simple, I'd say the wiki mission type list has a high overlap with the TTLG mission type list that has been in use since 2006. So after 13 years of use, maybe it's just a good list. Mission authors can choose a single mission type that most represents their mission. It can be an artistic decision. A campaign simply remains a "campaign" and missions without a type remain a "single mission". I added a screenshot of the mission download menu with mission type included in the existing layout, marked with red. Because the release date value is fixed in width, there's room for a type value next to it. Since type names are not finalized yet, we can make each type name fit in that type value space. This would always be a single value. I don't know how missions are uploaded. If it's a form, the mission author can select a mission type from a drop-down list. If it's a PM, maybe the mission author can simply mention the mission type in the PM. Because it's a fixed type list, I think we should exclude type from darkmod.txt. Otherwise we'd either have to allow a free type text that could deviate from the online types in the mission manager, or guarantee fixed types in the mission manager by matching the type text with the fixed type name list using something like Levenshtein distance. I'd say the mission type is always read from the online mission mirrors. I think the idea is to help players to more easily select missions to download. Once a mission is downloaded, we can assume players have already made their preferred selection, so mission types in the offline mission manager are less important and more a nice-to-have. I don't know how missions are updated, can I assume they are updated the same way they are uploaded?

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

I mentioned this in the improvements thread - https://forums.thedarkmod.com/index.php?/topic/11058-things-that-could-be-improved/page/95/#comment-473534 Bright readables in a game that is 99% darkness literally burns my eyes.

@HMart, you took issue with me saying: This was my summary of what I thought you meant in these post fragments from a forum linked to by Ref 10 (namely, https://forums.thedarkmod.com/index.php?/topic/20100-idtech-4-gui-scripting/#comment-439778 )... I see I probably shouldn't have added the "[as float parameters]" to the ambiguous "as well" phrase, and perhaps "recommended TDM try" is too strong. Overall, would this be better? "In Ref 10, it is noted that in transition statements, a 4-value color vector must be either a literal or (less reliably) a definevec4. Using a #defined macro for the color vector won't work currently... an idea for a future improvement?" EDIT - I see that a broader revision was needed. So changed to this in https://wiki.thedarkmod.com/index.php?title=GUI_Scripting:_TDM_vs_Doom_3,_Quake_4 ====transition 4-6 parameters==== Often, transition statements have a pair of 4-value color vectors as their 2nd & 3rd parameters. As the discussion in [[GUI Scripting: References & Resources | Ref 10]] indicates, each vector is traditionally represented by a double-quoted literal: transition "matcolor" "1, 1, 1, 0" "1, 1, 1, 0.8" "300" This was id Studio's preferred method, but using a definevec4 user variable was a possible alternative. In addition, TDM can #define colors for transitions. Unfortunately, due to syntax differences, for a particular color, it is not possible to create a single #define that would work with both properties and transitions; thus: #define INACTIVE_COLOR 0,0,0,0.50 #define SINACTIVE_COLOR "0 0 0 0.50" See [[GUI Scripting: Preprocessor Directives]] for further examples. (Possible future improvement: Changing TDM's parsing to let a transition also accept color vectors with commas.) See also the discussion above about 4vect properties and _x, _y, _z, _w suffixes.