Search the Community

Thanks @Bergante. Glad you like the mission. @RedEmberI played around with this a bit and its a cool idea! A couple things I found: The card: Having the card drop to the floor could create a lot of issues, it could fall through a mesh, be dropped on a platform that moves, dropped in water or to an inaccessible place. For this to work it would likely need to be something that floats in place and is generally unaffected by the world or accounts for those edge cases somehow. Loot: This is a cool idea to earn saves via loot, but be aware loot varies wildly across missions. 60 percent of loot could be in the last few rooms of a mission. Maybe you get a save token at 25, 50, and 75 percent of the loot collected. Save restrictions: One idea I played around with but never prototyped was a kind of a "potion of recall" so to speak that the player drank and acted as your save. You could then find them in the level or start with a limited amount. Having the saves be an item could be interesting and totally optional via the shop. If you buy the potion of recall you basically activate save restrictions as a challenge mechanic. This isn't something easily done via add ons, but just thought Id share the thought. Doing this via the location could work, but location sizes will vary wildly across missions. Hope this helps!

Beta 11 Fix finished-on state auto-update was unreliable Slighty improve scanner title/author detect Tags are now named some whatever regular-version-looking thing to force GitHub to put the newest at the top

Okay. I got it this far: I'll write a list so another noobs, like myself, can follow: 1. Create a custom.def in your def folder 2. insert this model CUSTOMNAME_tdm_ai_priest { inherit tdm_ai_proguard mesh models/md5/chars/builders/priest/builderpriestmesh.md5mesh channel torso ( *Spine_Dummy) channel legs ( origin Pelvis Pelvis2 *Hips) anim idle_eat_muffin models/md5/chars/guards/proguard/idle_eat02.md5anim //reaches out to table and eats food { no_random_headturning frame 1 object_call syncLegsWithTorso frame 21 attach atdm:moveable_food_muffin muffin hand_r frame 48 sound_voice tdm_crunch frame 125 sound_voice tdm_crunch frame 130 destroy muffin } } 3. Then add the spawnarg 'model' 'CUSTOMNAME_tdm_ai_priest' to your muffin eating man. 4. Target him to a path_anim with the spawnarg 'anim' 'idle_eat_muffin' You may need to restart DR/The game to make it reload definitions and god knows what...

And this is my gamer yep thats a 32" 4k ultrawide screen. And sadly this one is a lightshow well not that much actually due to the x99 deluxe board not having led functionality for that you need the deluxe II hehe. allways liked asus boards but this one is a bit strange. the nvme slot is vertical so you have to take care when fooling around in there so as to not break it off. the speakers are some modified b&o cx100 with builtin amps (yeah i made those myself "radio technician by trade") and a woofer under the table also from b&o. the cx100 model sounds really good but it is not as good as the c75 which had way better units (especially the tweeter which was from focal). cabby is a lian li lancool III, unfortunatly they went away from using alu in all but the most expensive cabbies like the oddysey, but the build quality is good and airflow is some of the best i seen (9 fans in total!!!). its a mesh construction so it does tend to drag ludicrous amounts of dust but atleast it is easy to clean hehe. EDIT: it is actually 10 fans i forgot the back fan.

I dom't use it, i found it here with the filter set to OpenSource. the TOS and PP isn't excluding for an OpenSource app, if they use ads mean that they also need to pay an server for this online service. OpenSource is not synonymous with free either, perhaps after the beta phase it is no longer free, so perhaps you can take advantage of the fact that it is still free to create a series of textures that can be used or search another one in Futuretools. AI generated textures and assets, by definition, don't have any copyright, so you can use them as you want. https://www.futuretools.io/?pricing-model=free|open-source&tags-n5zn=gaming

"May his iron mold the current as we were molded. May his instrument expel all obstruction as we are his instruments." - Collected Sermons of Master Plumber Roto Rooter Few would dare cross the Bridgeport Plumber's Guild. Fewer still could glimpse their secrets and live. CC0 POLYHAVEN PLUMBER PACK BETA Includes: Fully modular pipe kit with optimized shadow mesh, two skin variations and near perfect grid snapping at grid level 4 Moveable plunger prop which is fully compatible with the AI weapon system Worry free CC0 license All credit to the great polyhaven.com for the original mid poly meshes - consider supporting them on patreon. I just decimated and then rebaked the assets as well as converted the maps from pbr and made the additional model and material variations.

A big thank you and congratulations for this mission I would rate 10/10. I can't find a better one in my memory. It's so big and varied, full of new assets. Just... wow ! Finding a way through the was hard for me, as well as being able to jump and go through a narrow hole in the I also gut stuck in this area just below the horizontal mesh hatch that opens with Oh, and my game use to crash when firing a fire arrow at a Thanks again, you are so good at this.

Maybe you can do something with the animated grass demo: Topic https://forums.thedarkmod.com/index.php?/topic/12985-animated-grass-test-map/ Video: https://www.youtube.com/watch?v=LRCzWOeYxd0

Have you looked in this topic? https://forums.thedarkmod.com/index.php?/topic/21549-fan-mission-in-plain-sight-by-frost_salamander-20220807

well it seems to be a problem for many amd users i see from skimming unity forums, everything from outright crashes to awfull framerates ouch . one user found that running unity in a window made it run flawlessly while fullscreen made it run like alan wake2 on a 1050 gtx

Google translated: https://rutracker-org.translate.goog/forum/viewtopic.php?t=6419292&_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=nl&_x_tr_pto=wapp === There are lots of topics about black screens during the main menu. https://forums.thedarkmod.com/index.php?/search/&q=Black screen&type=forums_topic&nodes=58&search_and_or=and

Hi there! Since modular meshes are a thing in TDM, and I already saw some general misconceptions in the forums on how to make them, I thought I should show you one of basic techniques to make proper modular meshes, especially if you want to release them for others to use. First off, if you're new to the concept, have some preliminary reading: https://docs.unrealengine.com/udk/Three/rsrc/Three/ModularLevelDesign/ModularLevelDesign.pdf The document is old, but the principles of modular design stay the same. It's always about building the game world as fast as possible, while trying to save on polygons, textures and resources in general, and making the environment look as unique as you can. These seem like polar opposites at first, but with creative use of modular meshes you will reach that middle ground. Now, I'm not going to discuss my modeling techniques in much detail, since that's whole other topic, but we will stick to some ground rules: 1. Your wireframe has to be clean. I know this is modeling 101, but you can never stress enough how important it is. Essentially, your low-poly model has to be made with polygons (squares or rectangles) which can be divided into triangles when you convert it to a mesh. So, any piece rectangular flat surface should be divisible into 2 triangles. That doesn't mean you can't have triangles in your model. You can, they just won't be divided further. This is very simple mesh with 3 rectangular surfaces, in other words, it has 3 polygons. And this is how it should look like after export to mesh and in your game editor. As you see, everything is fine, there are 6 triangles. Now, in TDM module library I often see something like this: This is not a clean wireframe. You're looking at 14 triangles instead of 6. That's 42 edges instead of 18. While it may not be game-breaking now, it's definitely a waste of triangles. If you're going to have a whole collection of meshes built this way, you may be wasting processing power and lowering the overall game performance. Engines using lightmaps would probably have shadowing problems with this kind of wireframe. And that's how we move to rule number two, which is: 2. Save polygons whenever you can. Get rid of the faces players will never see. Use geometry only to convey believable shape of a model. Use high -> low poly model workflow and texture baking process to imitate complicated geometry with diffuse and normal textures. You don't need a thousand-polygon wall module, if you can fake it with normalmap and little visual difference. This is not only helpful in terms of performance, but it saves a lot of time at the model UVW Unwrap stage (it's easier / faster with fewer polygons to deal with). It also can be a design decision: whether it's a distant / skybox art or closer to the player, etc., etc. Now the rule number three, which is probably the most important of them all: 3. The pivot has to be moved to a place that allows most flexible use of a model, in as many scenarios as possible, and with grid set to as high number as possible. While this is not obligatory for unique objects, decorations and clutter, architectural meshes have to be cloned, moved, rotated and snapped to grid, as fast as you can. Typically, this depends on mesh dimensions and pivot placement. Since this all may sound very technical and abstract, let's get down to proper example. For my mission, I needed a wooden wall panel, something in the Builder's cathedral aesthetics. While browsing through many references, I found something appealing to my taste, but way above my modeling skills: I was also taking screenshots of Dishonored. I liked the Overseers' HQ, and I wanted to have something similar in terms of modularity: Notice that you don't need any special columns for outward corners, or to break up panels that are next to each other. I thought that the easiest way to achieve something similar would be to have a horizontal tiling texture with sections. Since I'm using 2048 textures as a base, I knew that 128 x 256 units will be enough for a wall panel, and I'll be able to divide it properly later. I didn't want the low-poly mesh to be complex, so I thought all I need is an upper trim section, the main section with inset panels, and the ground trim section. Technically, I could probably use one trim section and overlapping UVs to save on texture space, but I thought that is a bit too far Besides, any dirt layer on that would have the same spots or scratches on both trims, and that might look weird. This was the initial basic outline of my low-poly mesh. I thought the trim parts will be 16 u high, to fit better with overall proportions. Besides, if I'd changed my mind and decided that it's better to scale the model down to 64 x 128 u, it would have looked good as well. Now, since my drawing skills are basically none, I decided to model parts and decoration that would end up as baked texture and normal. I started with the middle section. Since the panel would be 256 u long, it was easy to divide it into 8 sections, 32 u each. I added thin strips between each section to make things a bit more interesting. Notice that I cut the strip by half on each end to make it tile properly later. I made a few adjustments and started adding decoration for the insets: Since there aren't many Builder insignia concept artworks, I tried making something on my own. It's kind of too close to hammerite stuff, but I liked it enough to leave it that way. Now the trims. Actually, one trim for the ground that is reversed for the upper section: The final model wasn't even high poly, medium poly at best. You're looking at 5200 polygons. I unwrapped the initial low-poly mesh (well, a plane with 3 setions), so it was super easy to bake the medium poly mesh onto it. I was using only half of the 2048 texture space. I could crop the texture to 1024 x 2048 and reposition UVs, but I decided that later I'd make a column, or another variation of this panel, so this space would not go to waste. This was kind of crucial moment and time when fun began. First thing I did was to check the pivot. I aligned it with the plane, moved it to the left side, and placed it on the ground. This way the model would be much easier to manipulate, whether it's moving around, rotating, or snapping to brushes or other meshes. Then I had to determine the final shape of the mesh and its possible uses. I applied the baked AO as bitmap to see whether the texture tiles (it did), and decided to tilt trim sections a bit, so it reflects the shape of medium poly mesh a bit more. I knew that players wouldn't see the bottom part of the mesh, but I wasn't so sure about the upper part. I decided to make the upper finish and used the trim part of the texture for it. Then I built a few walls to see how the mesh would look placed against them. That was when I realized my mistake. The pivot was in line with the middle section now, so, when I snapped it to a wall, the middle section was z-fighting with a wall. Duh! I selected the polygon and moved it 1 unit to the front. When I made sure that I can safely snap the mesh to walls and its clones, I proceeded to divide it to parts. As you see, this is still 128 x 256 wall panel, it's not really flexible. We need different length variations. Since I divided the medium poly into 8 even sections, I could slice the low poly mesh into chunks. Since having 8 different parts isn't that useful in the long run, I decided to clone the mesh, cut off one panel, clone the result cut another panel, etc. This way I came up with panels that are 224, 192, 160, 128, 96, 64 and 32 units long, respectively: The question is: do you really need that many panel variations? Typically, no. Four should be more than enough. You can always have a panel going through a wall, where player will never see it, so you don't need to be that precise and have all the length variants. Still, there was one thing even more important: corner pieces. I cloned the two-inset (64-unit) version of the panel to cut it in half. Then I rotated the "right half" 90° to the left to see the result. It was far from satisfactory. I knew that I'd need to align the upper and lower trims to form the corner, but I completely forgot that moving the middle section 1 unit to the front (to avoid z-fighting with walls) would create half a unit gap in the corner. This is how it looked after I aligned the vertices: This is where I could go to making textures and testing meshes in the editor, but there's also a problem of having inward corners. Many developers don't even bother with these, there will be some z-fighting of the upper part, in the small corner where meshes intersect. Not a big deal, but you can have such corners if you want as well. I felt like I had complete package, so I made some preliminary textures and material, then I begun exporting all pieces in .ASE format. All in all, I managed to create 12 variants of one mesh to cover the whole variety of its uses. After a few iterations of _d, _s, and _n textures, I came up with something like this: Edit: after getting some feedback I reworked the trims to give them more depth and proper silhouette, so the final result looks like this: This also demonstrates how important it is to bounce your ideas off someone or to show your work for peer review. A fresh look and healthy criticism can have very positive impact on quality of your work. I hope you'll find this useful while designing your own modular parts, let me know if you have any questions.

On the wiki, I'm working on a set of pages with the title-preface and broad theme "The Parts and Whole". This looks at the hows and whys of map objects being formed into collections. The hub of this is The Parts and Whole: Overview Within the hub, so far, the section "Techniques that Affect DR Only" is built out with comparison tables and child pages. This covers these techniques: Hide/Show, Region, Layer, Filter, Group, Selection Set. I'd appreciate any eyeballs on the work so far. Please suggest or edit-in improvements. In particular, are there links to videos or other wiki or forum pages that you think most apt and should be added, e.g., to the "See Also" section? "The Parts and Whole" effort is mostly intended for newbies and so is not afraid to state the obvious at times. In some cases, it covers ground also handled by the necessarily-concise DarkRadiant User Guide, but with more depth and context. In other cases, the info was only found buried in forums. Because I'm trying to cover a fair amount of ground, the pages are text-only. Some of the child pages could benefit from screenshots some day.

Yeah it would be cool to see some more detailed statistics and it’s a shame they aren’t really captured. Since we are talking about fan mission platforms, where players also make the content for the game, I feel like the best thing we’ve got is you can look at the number of content releases for the games. Keep in mind the graph counts campaigns as single missions - so for example NHAT and TBP both count as 1 mission. A good year for TDM has has approaching maybe 50% - mostly we’re 25-30%. https://www.ttlg.com/forums/showthread.php?t=152494 You could also look at the number of ratings thief missions get on https://www.thiefguild.com/ vs TDM ones, but that is pretty iffy in that you could chalk that up to more awareness of the site in the thief community than TDM Out of curiosity is there a reason a thief player can’t be a new player? I kind of think a player is a player and new players would be ones who are playing the dark mod who weren't? Is there disagreement the base of players most likely to pick up the game are fans of the thief games? They are certainly the most fruitful place to find feedback on the game beyond the sphere of this forum that I have seen. When we were trying to finish up SLL there was a lot of discussion on the forums about how long it had been since there was a release for the game. I am thankful that the stats show at least some stability over the years in terms of releases for TDM, but the trend for all of the games is decline. Not doing anything is a valid response if that’s what the devs want to do - it is not possible to provide evidence that any effort will slow that inertia. As a player and content maker I would just prefer trying to find feedback where it is offered from players who were willing to try the game but ultimately could not engage with it and see if there is anything that can be done within reason to ease them into the game. The game has a lot to offer imo. All those players are potential contributors - contributions in turn attract players - it’d be nice to see the cycle go on as long as it can.

This engine doesn't support quads at all, all models need to be triangulated at export time. Don't take my word for it but IMO that limit seems to be a old recommendation for Doom 3, today is very possible to have a character with more polys (triangles), those Dragfer suggested sound reasonable but I would be surprised, if you couldn't have one or two 10 000 or more characters moving around, all depends on the amount of characters you want on view and the minimum PC you want to support. But with all respect, please make those polys mean something, don't make a high poly model, where many triangles are wasted in flat peace's, I've seen this in some games. Also it seems this engine, cares more about material complexity than raw polygon count, of course within reason, don't go crazy on polys just because, when many lights cast unto a single model, all at the same time, it is re-rendered per frame, for each light that strikes it, that can potentially mean, millions of triangles being rendered per frame (including all the rest of the scene), please have that in mind. Btw afaik for animated MD5 models the higher poly it is and the more complex the skeleton is (many bones), slower it will become, I assume because bones will have to transform (move around) more vertexes, so imo is always good to test and if necessary optimize animated md5 models and use only the strictly necessary bones. And to finish , like Dragfer said, TDM has a level of detail system, so please make LOD models. make a low poly shadow mesh (use the last LOD level for that?). Not sure if required for animated md5 models (I think those use a ragdool? "articulated figure") for that, but at lest for static level geometry, making a low poly collision mesh, is necessary (can be the shadow mesh), if not the engine will use the real mesh for collision, very slow. Not important for animated characters or static models but for dynamic rigid body models, (those moved by the physics engine) unfortunately there's a limit of 16 polys/triangles for the collision model the visual model can be higher poly. Hope this helps.