Search the Community

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.

The latest dev build (dev16629-10139) supports Wavefront OBJ format for static models. Some details: Model must consist only of triangles. Quads/polys will produce warnings and won't work properly. NURBS/lines/etc are ignored. Normals and texcoords are mandatory for all triangles, otherwise model loading will fail. Widely used extension for RGB vertex colors is supported (standard OBJ does not support vertex colors). TDM materials are referenced by "usemtl textures/test_obj/rock". Standard MTL files are not supported yet. Unlike LWO and ASE imports, which try to automatically merge close vertices, no postprocessing is done for a model in OBJ format. As far as I understand, it means less suffering with smoothing groups for instance. Also it means that loading OBJ model is very fast, even for a large model. The only downside thus far is that zipped LWO file can be smaller than zipped OBJ, but I don't have exact numbers yet (I'd be happy if someone can help me with it). Speaking of OBJ format, there are several pending questions: Should we support MTL format (common subset) in TDM engine? Or as import plugin in DarkRadiant? Should we support referencing part of OBJ file as model in TDM map? Is it common to export several LODs into one OBJ?

The current version of the fm contains neither of both models referenced above (font_medium and misc_junk_18), it contains misc_junk_X with X up to 17, though. The font model isn't referenced in the map file, but the junk model is exactly once, at the location pointed out by @Daft Mugi. // entity 6876 { "classname" "func_static" "name" "func_static_1098" "origin" "704.037 -464.909 -395.714" "rotation" "1 0 0 0 1 0 0 0 1" "model" "models/darkmod/props/misc_junk_18.lwo" "noclipmodel" "1" } My suggestion is therefore to replace the model with one of the 17 other junk models or to just delete the entity.

WARNING:Couldn't load model: 'models/darkmod/waterworks/font_medium.lwo' (nor the fallback to ASE) WARNING:Couldn't load model: 'models/darkmod/waterworks/font_medium.lwo' (nor the fallback to ASE) WARNING:Couldn't load model: 'models/darkmod/props/misc_junk_18.lwo' (nor the fallback to ASE) WARNING:Couldn't load model: 'models/darkmod/props/misc_junk_18.lwo' (nor the fallback to ASE) I would assume these are causing the issues, most propably the first one, as the junk is probably easy to overlook. Besides that it appears that a ton of the assets shipped with the mission are in the meantime part of the core mod causing tons of warnings to spam the console. So it may be worthwhile considering an update either way.

A background image is useful if you're closely working from a reference image to create shapes. I use it quite often in Blender, but haven't done so in DarkRadiant yet. That said, I've only discovered its existence like a year ago and would probably have used it heavily when I was still in the business of modelling ships in DR from line plans and blueprints. I can imagine it being useful for various other DR-based modelling, too.

Look I'm still trying to learn how to render donuts in Blender, it's gonna take time! Anyway, I like the hand-le but to be honest, that's the kind of detail that even with a super high-poly count you're not likely to notice as a player. You'd have to get really close and be in the mindset of wanting to pay attention to the details to actually notice. Most players (including myself) would be preoccupied with the act of lock-picking and/or opening and then grabbing what's inside. It's one of the dangers of putting in a lot of detail into assets that barely get a second look by players. I do try to stop and "smell the roses" from time to time, but I also miss a lot of nice details even when trying.

I actually had a go at this myself once, but found it far too difficult. Personally I too hate the default input style, particularly the requirement to constantly hold down modifiers just to select things, but changing the defaults just breaks too much stuff because the selection system isn't designed to work that way. In order to allow "normal" selection rules, we would also need: A different method to create a new brush (since left-drag is now a selection or manipulation operation), for example something like Blender's Shift+A shortcut. A different way to resize brushes. Currently dragging anywhere outside the brush performs a resize, but if clicking/dragging on empty space is supposed to define a new selection, this will no longer work. So we would need something like traditional resize handles instead of the planar dragging approach. The selection system to decide what operation is being performed after the initial click or drag starts (as Greebo already mentioned). [Optional but almost certainly necessary] A system for setting up alternative keyboard profiles so people could choose between classic Radiant selection or the new system, since not everybody would agree with the changes.

Heyo! So the render is coming out pretty snazzy so far. My only big criticisms would come down to just maybe adding some extra edge bevels (even if they end up being baked into the normal map), just to make the case/door edges a little more interesting. Now honestly this could be achieved via some crafty texture work, or just hard modeling the details. I did a safe set some time earlier for TDM and I think I went the material route to highlight the edges. Albeit, a bit more edge distressing than I might do now, this is essentially how I handled it for those... So while I've tried to refine my detail masks a bit since these two were made, I'd still suggest a tad more on the grunge side. Main reason is that the assets that already exist for TDM are far from clean. While this does come down to the case usage (posh manor vs dock foreman office) is trying to match the current look of the game. I initially had a harder time making assets too clean and just had to develop my own style based on trial and error... or too many complaints Also, golden inlay can really pop if you highlight it more on the specular channel vs the color itself. Or at least so I found. Lastly, just make sure you mind the hinge alignment. I export the individual pieces from the same scene for this reason. As you've gotta remember, the mapper must reassemble the parts in Dark Radiant. So they'll have to line up on the grid somehow, else you might have gaps or little inconsistencies. Same goes for knobs and levers. My suggestion is to try and orient those pieces on your own gridsnap (in whatever app you model with) so that they just turn out this way by design. Nothing feels worse than importing a switch, just to see it clips oddly into the adjacent bezel. So basically, plotting the position of those things ahead of time saves the trouble. All in all I think your safe looks pretty awesome. I tend to make my stuff pretty loud but part of that is my own personal style too. Some of the things I like to go off on, are bits about how this mechanism would look with primitive casting & machining techniques. CNC machining is a pretty modern thing, so in the Dark Mod you can imagine a lot of metal details should appear to be cast iron or rolled steel plating. Otherwise man, I'd say you're pretty close already. Maybe just some extra detail to tie the door details together a bit more and just some general (natural) wear patterns.

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!

hi, make is at 31% thank you this might take another 20 minutes and then the install it self tomorrow we know for sure and it feels good. i have a simple start idear with just a single room. maybe a type off escape room. talking waybefore i have everdone some, i would like to take a eye with red or green ligth and turn it in a laser detection on the floor. i guess its reducing the surface off the ligth into a very small spot , then you have to use a gas arrow to enlight that laser with smoke reflexion. but i realy never done anything like 3d at all. even blender complains about me that i start but never finish anything. 46% and counting thanks!

The best place to look would probably be creative commons online repositories, especially 3D scanned models from museums (which however require some processing to get down to a reasonable tri count for a game). Otherwise, Goldwell has a bear rug. A different approach could be to pose the werebeast in Blender and export it as a model.

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!

In this case for a shadow and physics mesh imo is very easy, just make two extra copies of the lowest LOD, slap the shadow material in one and the collision material on the other and make sure both occupy the same space and are on the same item mesh/layer has the main model. In blender (or any other 3D Tool) you don't need to import any TDM material or texture, you just make a basic material for the shadow and collision mesh and make sure to give each the name of the shadow and collision material respectively (not the .mtr file name the full material name, inside the file), is that easy! bear_statue_example.7z ps- here is a fast example of what I said, sorry for not making it plug&play to TDM. I add too mess with the model because I use Modo and it doesn't open ase files, I add to convert to obj using another tool and also rotate it in Modo to be able to work with it, so now is not a, one to one, to the original model and so shouldn't be used with the LOD's that were provided, this because I assume they will not match, but I didn't tested, plus the material name for the main mesh is not the correct, only for the shadow and collision mesh's are correct (follows doom 3 convention). This should be seen just as a model for anyone to know how a shadow and a collision model should be setup. (for those that don't know) I also used the second LOD counting from the last because the lowest LOD seems to not follow the main model silhouette perfectly, it could very well work at the distance but not for a shadow and collision mesh.

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.

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!

https://www.violationentertainment.com/temp/threedeescanseisbarosab1_prev.jpg I'm back again with another statue, as a thanks to the entire TDM team and community. Originally from here:- https://threedscans.com/vienna/eisbaer_und_seehund/ This involved putting into practice some new methods using primarily Blender and MeshLab, remeshing and getting an actual neat and curated UV unwrap (a lost art), useable geometry and even some new methods for getting decent LOD stages. Amazingly, I managed to get the LOD spanning from 22K down to under 500 triangles, which is a crazy threshold for this kind of process. It's all thanks to the UV map, I think, being able to keep UV islands in relative comfort while lowering the polycount. The geometry is still very "matrixy", in my opinion, but it's 1000X better than older remeshing methods I'd tried before. Just almost good enough for game development. Almost. Anyway, it is still a much nicer result than in my previous bake and I learned a lot. I spent about 7 hours cleaning out all of the little fleas (geometric artifacts from the original 3D scanning) from the normalmap, followed by some loving texture-painting and other manual adjustments. All textures are 4K but I expect those to be mostly downsampled, and I apologise for not making this engine-compatible out-of-box, but I doubt many of you will struggle. It already contains ASE and DDS files. All it really needs is MTR file, as far as I remember. Once again, all textures (mixed with the bake from the original 3-million triangle source) come from:- www.goodtextures.com License remains CC0 and hoping some of you find it useful:- https://www.violationentertainment.com/temp/threedeescanseisbarosab1.zip Cheers!

I just checked the tarball which can be downloaded from my GitLab repository (https://gitlab.com/orbweaver/DarkRadiant/-/tree/maint/3.1.0) and .gitattributes is not appearing in the resulting archive, so it looks like GitLab at least is honouring the export-ignore attribute.

My default position is that pure editor state changes should not be considered part of the undo stack — in other words, if a particular operation would make no difference to the map file on disk if you saved immediately afterwards, then that operation would not be part of the undo stack. Under this criteria, selection changes would not be undoable. The advantage of the above approach is that the "map changed" status can be tied to the undo stack: if (and only if) the stack is empty, the map is unchanged. Although this is an implementation detail that is of little interest to end users. However, there clearly is a case for having selection undoable if certain selection operations are tedious or time-consuming to perform, as has been mentioned with patch vertices. The fact that Blender is making selection undoable indicates there must be a significant demand for it.

This is exactly the use case I had in mind that got me to open this thread and ask. I recently moved back the undo queue to select an item I had deleted earlier, selected it, copied it to the clipboard, then redid all the steps and pasted the item into the map. A move like this is no longer possible when the redo stack is cleared by selecting the item. But then again, I'm used to selections being undoable from Blender, where this is quite a time saver. It's very easy to mis-select a vertex when moving fast, and being able to remove those wrongly selected items by hitting Ctrl-Z is really nice. For this one feature I'd be interested whether anyone is using it at all - are many people using selection groups in their maps? I found it less useful myself, and the workflow is clunky, having to think of a name for the group before saving. - edit: scratch that, I've been thinking about selection sets here.

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!

Here's the pre-release build 3.1.0pre2 After this pre-release phase I'm going to consider doing this differently, like pushing out the releases more regularly, skipping the "beta" phase. It's a lot of work putting the pre-releases together, and I'm somewhat tired of it. 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. Download Windows Portable x64: https://drive.google.com/file/d/12zKwbeesRIMP7DNeGd0znGl5xqBVrrPX/view?usp=sharing Download Windows Installer x64: https://drive.google.com/file/d/12u5YtpDvpIPL7cR8EPdIIFcnjx9TzpCe/view?usp=sharing Linux folks need to compile this stuff from source, instructions for various distributions are on the wiki. If you happen to run into a crash, please record a crashdump: How to record a crashdump Changes since 3.0.0 can be seen on the Bugtracker changelog, here's the summary: #6065: Feature: DR doesn't consider wildcards in skins #5503: Feature: Reload Images #5805: Feature: Texture Tool free scale #6021: Feature: Add "Show Definition" to all ResourceTreeView instances #6003: Fixed: "Reload Defs" doesn't remove entities that have been commented out #6007: Fixed: 'Reload Sounds' doesn't load new FM sound shader definitions #5504: Fixed: Reload Defs is not sufficient for reloading modelDefs #6035: Fixed: Models are reset to origin after reloadDecls #6064: Fixed: Skin Chooser doesn't preselect non-matching skins #6062: Fixed: Moving speakers deletes distance spawnargs if they're the same as in shader #5988: Fixed: Unable to select func_emitter with particle attached #6000: Fixed: Particle Editor Preview lacks vertex colours in lighting mode #6061: Fixed: Particle effects still visible when hidden via layers or filter #6036: Fixed: Entities referring to modelDefs should use the "idle" pose where possible #4910: Fixed: DR does not parse materials in def files #5982: Fixed: Modifier Hint Popup can crash when hitting Ctrl/Alt/Shift keys during shutdown #5981: Fixed: Insignificant digits displayed in Surface Inspector shift/scale/rotate values #5727: Improvement: Skin Chooser: show in which .skin file the skin is defined #5977: Improvement: Declaration Block Parsing overhauled #6023: Improvement: Python Interface for IDeclarationManager #5972: Improvement: leave player start entity selected after placemen #6066: Improvement: Let Map Info show materials used by models #6073: Improvement: Renaming Declarations causes problems when saving it later #6057: Improvement: Light Texture Preview should display editor images if present #6002: Improvement: Remove comments about particle generator in .prt files #6071: Material Editor: New Material is locked if the default unnamed name is already in use #6031: Material Editor: allow to delete materials #6054: Material Editor: image browser's "cancel" button rewrites the material source text #6030: Material Editor: does not save manual edits to source text #6055: Material Editor: should show .mtr the material is defined in #6069: Material Editor: after "Reload Images", image previews are only updated when selecting a different material #6050: Material Editor: suboptimal preview for cubeMap materials #6042: Material Editor: preview object doesn't have smooth shading #6043: Material Editor: preview doesn't take "scale" into account in Textured Mode #6053: Material Editor: blend add stages are rendered separately in preview in lighting mode #6059: Material Editor: test frob highlight button not working #6045: Material Editor: doesn't remember settings from previous session #6046: Material Editor: image thumbnails use "scale" keyword from previously selected material #6056: Material Editor: frob highlight stage not updated correctly when changing diffusemap #6049: Material Editor: using Escape to close ignores unsaved changes #6051: Material Editor: Global Settings should be preselected #6052: Material Editor: some declaration text is lost while editing#6047: Material Editor: clicking "cancel" when selecting a light classname clears the classname field #6034: Material Editor: new materials always sorted last #6033: Material Editor: filter for image browser #6037: Material Editor: can't unlock editing on materials in "Other Materials" folder #6029: Material Editor: tries to save materials in DarkRadiant folder if no FM is installed #6048: Material Editor: allow to change preview backgroun #6040: Material Editor: preview renders shadows for noshadows materials Changes since 3.1.0pre1 #5997: 'Export selected as Collision Model' doesn't auto-create path folder and throws error #6013: Model exporter: manually enter export origin #6012: Model exporter: export origin choice should use a radio button #6014: Model exporter: only 1 entity's model is reloaded #6011: Model exporter: "Use entity origin as export origin" still uses map origin #6015: Model exporter: rename "Center Objects around Origin" Thanks for testing, as always!

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

I've set the export-ignore attribute on .gitattributes itself, so I guess we'll see if this makes any difference to what GitHub produces. Another possible source for the tarball would be the one attached to the Ubuntu package, which is effectively a "pristine upstream" tarball since I am generating that package myself without any Ubuntu-specific patches. It would also be (indirectly) signed as part of the PPA publishing process. However I don't know if you or Debian would have a problem with basing a Debian package off an Ubuntu package source, since it's usually the other way around.