Search the Community

A couple of things you can try (yes .ase files should work): I'm no expert with models, but do you have a field in the .ase file that looks something like this: *MATERIAL_NAME "textures\darkmod\plaster\plaster01" ? If the material name there isn't exactly as you specify in the skin it won't get replaced Check the console log in DarkRadiant to see if you have any errors when loading the skin. It's there in the 'console' tab.

I've seen fun workarounds like that in other game modding as well. Years ago, maybe even a decade, some fella who was making a mod for Mount & Blade over at the Taleworlds forums revealed that he put invisible human NPCs on the backs of regular horse NPCs, then put the horse NPCs inside a horse corral he built for one of his mod's locations/scenes and then did some minor scripting, so the horses with invisible riders would wander around the corral. The end result was that it looked they're doing this of their own will, rather than an NPC rider being scripted to ride around the corral slowly. Necessity is the mother of invention. I don't know about the newest Mount & Blade game, but the first generation ones (2008-2022) apparently had some sort of hardcoded issue back in the earlier years, where if you left a horse NPC without a rider in its saddle, the horses would just stand around and wait and you couldn't get them to move around. Placing an invisible rider in their saddles suddenly made it viable again, at least for background scenes, of riderless horses wandering around, for added atmosphere. First generation M&B presumed you'd mostly be seeing horses in movement with riders, and the only horses-wandering-loosely animations and scripting were done for situations when the rider was knocked off their horse or dismounted in the middle of a battle. Hence the really odd workarounds. So, an invisible NPC trick might not be out of the question in TDM, even though you could probably still bump into it, despite its invisibility.

I plan to gradually try out all or most of the different path node types and adjust them depending on the interaction. Though I don't plan to use it in this particular mission, I have a keen interest in the follow type, as I'll want an NPC to follow the player character in another, future FM I'd like to create. Never too soon to try out various functions while I'm already learning new FM-building skins after a long hiatus. Thank you for the suggestion. I completely forgot about the location system ambients as an option ! A few years back, when I was testing various stuff in DR, I did actually use that approach instead, once or twice. I haven't used DR much in recent years, so I eventually forgot about setting it up that way. Acknowledged, and I'll look into it. It'll save a lot of time concerning the audio side of the mission. My first few missions won't have much a natural environment, they'll largelly be small and focused on buildings or urban spaces, so I won't need to bother with detailed audio for rivers yet. I have an outdoor FM planned for later (it's in the pre-production phase), and I'll have a good reason to study it in greater detail. It's actually okay, I don't reallt need rectangular speakers. Given that I've been reminded I can set a main ambience for each room - something I did know before, but forgot, after not working properly with DR these past few years - I'll do just that, and use the speakers for more secondary ambience concerns. Handy indeed. A rectangular shape would be easier to remember. I'll just use the filters in the editor to put away the speakers if I ever the get the impression they're blocking my view. Also, I don't actually mind the shape all that much. As you and the others say, the size/radius of the speaker is the actual key aspect. I'm a bit disappointed it's seemingly not possible to resize speakers the same way you can resize brushes or certain models, though you can still tweak the radius numerically, manually. As long as I can work with that, the actual shape of a speaker isn't really important. My main concern is expanding the minimum and maximum radius areas to an extent where they'll be audible for most for all of the respective areas the player will visit, rather than fading away quickly once the player leaves the hub of the speaker behind. As was already said above, I'll use the different utility to set the main ambient for the individual rooms, rather than a manually placed speaker, and I'll reserve the speakers for additional sound effects or more local ambience. I've already added some extra parameters to the speakers I'm testing out in my FM, so I'll take a look at those soon, though I'll deal with the main room ambience settings first. I'd like to thank everyone for their replies. While I'm not surprised by the answers, I'm now more confident in working with the path node and speaker entities. On an unrelated sidenote to all of this, the same in-development FM where I'm testing the speaker placement and range was tested yesterday for whether an NPC AI can walk from the ground floor all the way to the topmost floor, without issues. Thankfully, there have been no issues at all, and the test subject - a female mage, whom I won't use in the completed FM, sadly - did a successful first ascent of the tower-like building that'll serve as the main setting. (That's all your getting from me for now, concerning the FM contents.)

This is a work of fiction. Unless otherwise indicated, all the names, characters, businesses, houses, events, incidents and particpants in this forum thread/fm are either the product of the author's imagination or used in a fictitious manner. Any resemblance to actual persons, living or dead, or actual events is purely coincidental. Hello everyone, I am saddened that my first post here is to bring you all the news concerning the disappearance of my dear friend, wellingtoncrab, which was last seen on March 10 of this year by heading to the woods of northern California . Unfortunately, without trace or tracks, we have no choice but to cancel research. In addition to finishing 1.25 FMS, wellingtoncrab was known as an partner of many famous people and models, and to have the largest animal crossing house. We will miss them a lot. Of course, an immediate concern was devoted to determining the status of their unpublished FM(s). I must admit that the passage through their hard drive has not turned much, but I was intrigued to find a file called "IRI2.PK4". Unfortunately, my computer cannot load the card (too old, lol ), but I will download it here for posterity as well as the text included in the README: https://drive.google.com/file/d/1SdZswFLUh5VwReIq79uFL_ahXyKxg34F/view?usp=sharing ========================================= WellingtonCrab Presents: IRI2: The Totally Unauthorized Sequel to Moving Day: Moving Day 2: Look Who’s Moving Now *For Richard and Linda* “There once was a hole here. Now it is gone.” With enduring gratitude to: Testers: ImaDace Goldfish Kingsalmon Acknowledgments: @Jedi_Wannabe for graciously unauthorizing this sequel to his great mission "Paying the Bills 0: Moving Day." Mr. Squirrels: you know who you are and what you did. The name "Lampfire Hills" originates with the author Purah and now is part of the extended universe of many subsequent Thief missions. Bikerdude and Goldchocobo then brought the name into the setting of The Dark Mod with the FM "The Gatehouse." It then came to me in a dream. @Dragofer for all of his scripting work and support over the years. Polyhaven.com for its many excellent CC0 assets. I recommend supporting them on Patreon if you can spare the change: https://www.patreon.com/polyhaven/ Textures.com "One or more textures bundled with this project have been created with images from Textures.com. These images may not be redistributed by default. Please visit www.textures.com for more information." Google Image Search.

I've started futzing around with ideas and models. Not sure if I'll have something in time, but I'll give it a shot!

DarkRadiant 3.9.0 is ready for download. What's new: Feature: Add "Show definition" button for the "inherit" spawnarg Improvement: Preserve patch tesselation fixed subdivisions when creating caps Improvement: Add Filters for Location Entities and Player Start Improvement: Support saving entity key/value pairs containing double quotes Improvement: Allow a way to easily see all properties of attached entities Fixed: "Show definition" doesn't work for inherited properties Fixed: Incorrect mouse movement in 3D / 2D views on Plasma Wayland Fixed: Objective Description flumoxed by double-quotes Fixed: Spinboxes in Background Image panel don't work correctly Fixed: Skins defined on modelDefs are ignored Fixed: Crash on activating lighting mode in the Model Chooser Fixed: Can't undo deletion of atdm_conversation_info entity via conversation editor Fixed: 2D views revert to original ortho layout each time running DR. Fixed: WX assertion failure when docking windows on top of the Properties panel on Linux Fixed: Empty rotation when cloning an entity using editor_rotatable and an angle key Fixed: Three-way merge produces duplicate primitives when a func_static is moved Fixed: Renderer crash during three-way map merge Internal: Replace libxml2 with pugixml Internal: Update wxWidgets to 3.2.4 Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.9.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep creating Fan Missions! 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. Keep on mapping!

Ah, pity I wasn't reading the forums back in February. I'm fond of that game, along with Bugbear's other early title, Rally Trophy. I was never too good at FlatOut, but it was always a hoot to play.

This is probably the most practical way of indicating breakable electric lights and can be done with existing models if the effect consists of something like sparks + flickering.

It might then be best to add it to new light models designed for the purpose. The visual cue should be making them more glassy and fragile looking: Existing lamps look pretty solid, we can argue those were made of reinforced glass built to withstand powerful impacts, something something Inventors Guild... in contrast we'd have a few lamps with very transparent glass that show the light bulb inside, their design shows their fragility and makes it clear those are meant to be shot.

Breakable lights might be an interesting concept so long as they are not implemented retroactively. Add a loud sound or other punishment for breaking them as you see fit, but it would still change the difficulty and design intended by level authors if you applied it to all previously made levels. I would also suggest that if you instead intend to make breakable variants of existing light models that you add a clear visual indicator that the light is breakable, otherwise it would require explicit messaging to the player that electric lights are breakable in that particular FM. I’m hesitant to see something of this sort added as it is in stark contrast to Thief precedent, but I would be more supportive of it if it was added carefully and responsibly.

The weapon hack is something that IIRC forces a model to render in front of everything else. It's limited by the fact that it can only apply to .md5mesh models, currently, such as the viewmodel of the player's arm and any weapons attached to the arm.

Well some good news for those who have the 2080 ti and no money to upgrade to the 4000 series. Alan Wake 2 runs at > 70 fps with the FSR3 mod on it at high at 4K need to set "m_bLensDistortion": false, in AppData\Remedy\Renderer.ini to get rid of some ghosting effect on the main char when moving, but other than that it looks quite nice. the FSR3 mod is here -> https://www.nexusmods.com/site/mods/738 an alternative is this mod -> https://www.nexusmods.com/site/mods/757 which also supports intels xee models. there is also one for slightly older AMD cards but it is a paid mod and the author got himself into quite a shitstorm due to some rude behaviour so i wont link it here, look for LukeFZ if you really must. The other FSR3 mods require an RTX or Xee card so for nvidia everything from a 20 series and 30 series. The LukeFZ mod also supports the older GTX 10 series. One thing to note is that your card must be able to handle atleast 30 FPS minimum else it will look like crap and if movement is laggy without it it will still be laggy with framegen (this also applies to cards that support it natively like the 40 series).

@snatcher I understand that when you feel your work doesn't live up to your goals that you don't want it out in the wild advertising your own perceived shortcomings but that leads to a troubling dilemma of authors who are never satisfied with their work offering fleeting access to their in-progress designs then rescinding them or allowing them to be lost. When I was a member of Doom3world forums, I would often see members do interesting experiments and sometimes that work would languish until someone new would examine it and pickup the torch. This seemed like a perfectly viable system until Doom3world was killed by spambots and countless projects and conceptual works were lost. I guess what I am trying to say is that mods don't need to be perfect to be valuable. If they contain some grain of a useable feature they might be adapted by mission authors in custom scenarios. They might offer instructive details that others trying to achieve the same results can examine. It would be great if known compelling works were kept somewhere safe other than via forum attachments and temporary file sharing sites. I suppose we used to collect such things in our internal SVN for safe keeping but even that isn't always viable. If folks would rather not post beta or incomplete mods to TDM's Moddb page, perhaps they would consider creating their own Moddb page or allow them to be added to my page for safe keeping. Please don't look at this as some sort of pressure campaign or anything. I fully understand anyone not willing to put their name next to something they aren't fully happy with. As a general proviso, ( if possible \ permitted ) I just want to prevent the loss of some valuable investigations and formative works. The end of Doom3world was a digital apocalypse similar to the death of photobucket. It is one of my greatest fears that TDM will become a digital memory with only the skeletons of old forum threads at the wayback archive site.

Congrats on the release! Remember to check ThiefGuild as well as the DarkFate forums (via Google Translate) for additional feedback.

wtf... the second cable was also the wrong type the third worked and the board runs again . corsair has some explaining to do i reckon since all my current PSU's are from them and the only indicator that the type is not for that PSU is a small badge printed on the connector that its either a type 3 or 4 (both fit on the modular types but only one will work) the models are a 750 watt cw and a 1000 watt hx. the hx was the one i swapped in and its a gold certified PSU with 10 years warranty. the cables despite the type number are also visually the same except the type 4 having 1 cable mounted differently and is the only one that fits the hx model appareantly. luckily the cable that is mounted differently has no connection inside the 1000 watt PSU so thats a plus as otherwise it would probably had incurred damage to either the board or the PSU but damn...

Welcome to the forums Ansome! And congrats on making it to beta phase!

"...to a robber whose soul is in his profession, there is a lure about a very old and feeble man who pays for his few necessities with Spanish gold." Good day, TDM community! I'm Ansome, a long-time forums lurker, and I'm here to recruit beta testers for my first FM: "The Terrible Old Man", based on H.P. Lovecraft's short story of the same name. This is a short (30-45 minute), story-driven FM with plenty of readables and a gloomy atmosphere. Do keep in mind that this is a more linear FM than you may be used to as it was deemed necessary for the purposes of the story's pacing. Regardless, the player does still have a degree of freedom in tackling challenges in the latter half of the FM. If this sounds interesting to you, please head over to the beta testing thread I will be posting shortly. Thank you!

I mean moving models around inside the models folder. If I try to restructure my models folder via internal folders, but have already placed models, it causes the placed models to break. Thankfully it looks like I was careful enough to save models into the map folder and not somewhere else.

I mean that moving them from one internal models file to another causes it to break. Example, building with models before creating a folder inside the models folder, and then moving models in there, causes all placed versions of those models to become blue/black squares.

What do you mean by moving them around? You move them from the models folder into another folder? Models must be placed in the models folder. Otherwise, DM/DR cannot find them anymore causing the problems you mentioned in your post.

I have been building my map using some models I've created. I noticed that moving the models around in the folders caused the models in-game to break. Are there any precautions I must take for when I want to upload the map for beta-testing/finalizing the upload?

Something I was thinking of: Even if some assets are non-commercial, are all assets at least accounted for to make sure they're credited accordingly and can be distributed? I ask following an issue in another great project I work with called Red Eclipse: They don't have NC assets but did have a few texture packages they had to remove because they later found out their clauses were incompatible with the project. If this hasn't happened in well over a decade it's very unlikely anyone would complain today and request removal for any reason, but if any resource had its license misunderstood that could destroy existing FM's unless perfect replacements were found. Obviously I presume the team never included any asset randomly found on the internet without verifying their explicit requirements in detail, but it doesn't hurt to check. I think the best that can be done otherwise would be to have a list of which assets are libre or have the NC clause: That way a map can choose to use those models and textures that are free if the author wants their FM to be fully libre, albeit this would handicap an author in what packages they can use. If core assets like character models or textures are also NC, the idea is likely pointless as you can't make a FM without those, at best you can skip a few texture packages... not sure about other things like core scripts or defs, since they're technically code I presume those are GPL?

TDM Latch Pack (Beta) By Frost_Salamander and wellingtoncrab with special thanks to Dragofer Tired of picking another lock or hunting for that missing key? Imagine The City is itself an elaborate lock, and you are the key. Embrace progression through careful exploration and navigation of the environment. Embrace the latch pill: Included is a new entity type and scripting for a door mounted toggle lock, or "latch", as well as new CC0 assets and prefabs. https://github.com/thedarkmodcommunity/test-latch/wiki Example Video Asset Pictures All models and textures in this pack are released under CC0 license and may be used freely without need of attribution. We waive copyright to the extent that possible, but aren’t lawyers. Latch Lock Features Supports single and double doors across all cardinal directions, as well as trap doors Uses the location system to handle context sensitive frob highlighting of the latch and the doors Automatically determines the correct latch state on map start based on the targeted door's "locked" spawnarg Options for rotate, translate, or both with unique sound slots for each Supports any model or func_static To get started head over and grab the latest release (available with or without demo content) and read the getting started guide. This is a beta release - so your feedback is appreciated!

I was able to reproduce this in 2.12 beta as well as 2.11. Start mission setviewpos -5727 974 292 24 -57 0 Wait for new objective setviewpos 3795 5676 -3164 18 160 0 Wait for objective complete Shoulder body setviewpos -1643 3574 -1903 4 180 0 Drop body on elevator platform Press elevator button Setting "logFile 2", I was able to capture some console messages before the crash. "MISSION COMPLETED" displays twice instead of once. I haven't had a chance to look further into this. WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model WARNING:idClipModel::Handle: clip model 0 on 'bellero' (dc8) is not a collision or trace model MISSION COMPLETED MISSION COMPLETED ----- idRenderModelManagerLocal::EndLevelLoad ----- 0 models purged from previous level, 1031 models kept. --------------------------------------------------- Regenerated world, staticAllocCount = 0. Getting threadname failed, reason: No such file or directory (2) --------- Game Map Shutdown ---------- ModelGenerator memory: 133 LOD entries with 0 users using 2128 bytes. WARNING:idClipModel::FreeTraceModel: tried to free uncached trace model (index=0) --------- Game Map Shutdown done ----- Shutting down sound hardware idRenderSystem::Shutdown() ...shutting down QGL I18NLocal: Shutdown. ------------ Game Shutdown ----------- ModelGenerator memory: No LOD entries. Shutdown event system --------------------------------------