Search the Community

Well, my idea does not work. In reality, the penis gets created/recreated/reattached many times: anim urinate models/md5/chars/guards/proguard/animation_urinate.md5anim { prevent_idle_override frame 1 call overrideLegs frame 30 attach atdm:penis_s penis hand_l frame 30 sound snd_rustle frame 55 reattach penis LeftHips_Dummy frame 70 destroy penis frame 70 attach atdm:penis_urinating_s penis_urinating LeftHips_Dummy frame 70 sound urinate frame 340 destroy penis_urinating frame 340 attach atdm:penis_s penis LeftHips_Dummy frame 375 reattach penis hand_l frame 425 destroy penis frame 425 sound snd_rustle } As you see, the penis is already destroyed at the end of animation. And then there are two more ways to delete it: "attach" command looks at "remove_delay" spawnarg, and if it's positive, then schedules removal of the attachment penis also has "tdm_suicide" script attached, which also checks the same "remove_delay" spawnarg and deleted the same entity after this delay from script thread. So, why do we have 3 ways to destroy the penis?

I am going to sort-of reveal that this is loosely like the nature of my upcoming mission. I noted it here when JackFarmer asked about things that are coming along in this post: https://forums.thedarkmod.com/index.php?/profile/37993-jackfarmer/&status=3943&type=status It too is a builder church. The player is requested by a hopefully famous character in another mission to handle some business that is affecting the congregation. I am looking to invoke some info and history laid down in other missions as a hook story.

I created the page: https://wiki.thedarkmod.com/index.php?title=Lightgem In the source I placed the following text: <!-- Page text made by forum user Fiver: https://forums.thedarkmod.com/index.php?/topic/22327-how-can-i-create-an-account-on-the-tdm-wiki/&do=findComment&comment=491145 --> Personally I think the page isn't really necessary because the info is already present under HUD.

In the first post of the other topic Geep proposed: Then Stgatilov's answer: But I think applying subtitles in different languages shouldn't be too hard I would think, but I don't know how the current translation system works. The engine should apply the correct subtitles based on the applied language setting, this doesn't need a whole new language system I think. Not sure who's going to write those subtitles though. I can only do Dutch and English and nobody needs Dutch I think. I suggest further discussion of this to take place in topic https://forums.thedarkmod.com/index.php?/topic/21741-subtitles-possibilities-beyond-211/

I'm pretty sure this would turn into simple "frob hold delay" slider if this approach is taken as default.

Creating a new thread for this as it was being discussed in an old beta-testing thread starting here: https://forums.thedarkmod.com/index.php?/topic/21822-beta-testing-high-expectations/&do=findComment&comment=490751 I suppose the main questions are: when should this spawnarg be used, if at all? why was it introduced in the first place? Can we get it documented properly on the Wiki so misuse isn't propagated? @stgatilov @Dragofer

Hello! Tracking down information on software and plug-ins that work with D3 / TDM can be a tough. So I have created a thread here where people can post what software/ plug-ins/ tutorials or other references they've had success or failure with in TDM. 3DS MAX 2013 64bit .ase - Default .ASE model exporter works. However you have to open the .ase file in text edit and manual change the *BITMAP line on each material to read something like: "//base/textures/common/collision" which allows the engine to read the correct material path. md5.mesh / animation - Beserker's md5 exporter/importers for 3dsmax. http://www.katsbits.com/tools, Importing and exporting works. The model must be textured, UV'd, with a skin modifier attached to the bones to export. PM me (Kingsal) for help with this. Imported models using the script will not be weighted appropriately, so this is not recommended if you are simply trying to edit existing tdm content. (Use blender instead) MAYA 2011 32bit md5.mesh - So far I've not had any luck with Maya 2011. I am using Greebo's MayaImportx86 for Maya 2011. I've got the importer working however I get a "Unexpected Internal Failure(kFailure)" and the import fails. This could be due to something finicky in Maya that I am not doing correctly. Will keep trying.. Blender 2.7 about - Blender is commonly used and pretty well supported on the forums/ wiki. Various versions may work as well - https://www.blender.org/download/ md5.mesh / animation Blender MD5 importer/exporter (io_scene_md5.zip): https://sourceforge.net/projects/blenderbitsbobs/files/ Sotha's guide Blender Male/ Female rigs by Arcturus - Here Edit by Dragofer: more links found in this post.

Here is an alternative way to simplify extinguishing candles and shouldering bodies. Player can double-press / double-click frob button to do a mixed frob + use action. The test build is available in tdm_installer as "test-frob-stgatilov". Attached the source code patch too: FrobUse_By_DoubleClick.patch The original TDM controls are left unchanged. The difference starts only when double-click is registered (which unfortunately can happen accidentally). Also, the double-click action always continues the single-click action. So when you grab a body/candle, the single-click action happens immediately: there is no need to delay it. The maximum time between double-clicks is controlled by cvar in_doubleClickDelay, default is 200 ms. In principle, you can set it to zero to return to the old behavior: then double-clicks won't be registered. Here is how it works internally. There is an utility class which tracks held buttons (which are called "impulses" --- Doom 3 has too few "buttons"). I have extended it to also register double-click. So whenever player clicks frob and this is registered as double-click, then: If there is nothing grabbed, then do ordinary "frob" to grab item (this allows to double-click on already grabbed item). If there is nothing grabbed now, then fall back to normal single-click frob (this happens for ungrabable stuff like doors). If there is something grabbed, then "use" it (that's the main part: it shoulders/extinguished/eats the thing). Unless we have a body shouldered, release currently grabbed item (we want to ungrab extinguished candle). And there is also a special case: If there is something equipped at the moment of double-click, the just "use" it instead of anything else (this allows to unshoulder body by double-click).

Yeah, I think I made the mistake taking the whole long-frob instead of the delay. But as you explained it with the key-down key-up way, shouldn't stgatilov be able to replicate that in his version? Also isn't multi-loot already implemented that way?

I think people will have way more misclicks with single-click vs long-click prototype: you don't even need a second press to do the wrong action. And increasing the duration threshold to reduce this chance will also increase delay of single-click actions, which is hard to notice on 200 ms.

If this is the case, I certainly didn't notice a 200 ms delay ;). Can you please do a test version of your setup with delayed long-frob instead of double-frob? This would be the perfect solution for me and snatcher, as it is consistent also to the current multi-frob. And maybe add the consumable long-frob eating for everything to fit together?

Personally, for this kind of game, double-clicking and double-tapping are the kind of things that instantly get a sour taste in my mouth as soon as I hear it, because I already know from experience that it not reliable enough and it's more prone to human error. You said it yourself: It may also happen accidentally if your fingers twitch, or if your mouse misregisters an extra click, or when you think you didn't hit the target and immediately click again, but it so happens that you did hit the target the first time; or when you're hasting to perform the same task multiples times in quick succession (not very relevant here, but I couldn't count how many times I died in minecraft tapping keys to adjust my position and accidentally double-tapping forward and sprinting off a cliff). Also, given that we're talking about the right mouse button, I'm feeling even less inclined. I can double-right-click, but it doesn't feel very comfortable. It's really not something I'm used to, so it requires a degree of effort (and I suppose it will get my hand tired, as @Wellingtoncrabmentioned). Yup. I like ghosting. To be fair, I play with my own lax rules, but I still feel bothered if I have to tamper with the natural order of things, if I think it's unnecessary or that I shouldn't be forced to. It might seem petty, but it's part of what makes the challenge interesting. You never know, the candle owner might have noticed before bed that the candle was about an inch away from a spec of dust, and in the morning he might realize that that distance has changed. So, from a ghosting perspective, when you tamper with things without needing to, you've introduced a point of failure. If the game requires it, that's another story -- it turns into "I can't work around it, so I have to bend the rules because of it". But as far as I'm concerned it still bothers me and kind of ruins the challenge. For example, TDM has been leaving a really sour taste in my mouth when it comes to dropping keys, because lots of missions don't allow it (because unfortunately they're not droppable by default in DR, and for no good reason, afaik). After Snatcher's post about the delay interfering with manipulating bodies, I was growing tempted to agree with reversing it, but then I realized both ways have issues of the same kind. If you can click to shoulder, then you can't click to drag body -- you always have to hold button, which is not great if you're dragging a body a long distance. If you can click to drag a body, then you can't hold to drag a body. You always have to click to drag and then click to release, which is also not great when you're dragging limbs for a pose or something. (I suppose this might be even more annoying than the other.) Maybe I should posting this in that thread.

Your implementation just falls into the following category: "you delay all single-click actions until you are sure it cannot turn into double-click/long-click".

That's the same for all versions, for both double-click or long-click. You either start single-click action immediately when first click starts (proper solution), or you delay all single-click actions until you are sure it cannot turn into double-click/long-click (ugly), or you just map the different action to a different key (proper solution). Pick your poison.

There's a group of players who have meticulously tested and adjusted ghosting rules for The Dark Mod. Please see: Official Ghosting Rules: https://www.ttlg.com/forums/showthread.php?t=148523 Ghost Rules Discussion: https://www.ttlg.com/forums/showthread.php?t=148487 Why alienate an established group of dedicated players?

Sorry for the delay. The new version is up in the mission database now.

It is not a long-click, it is click-and-hold, where holding time matters (and is much longer than long click). So with your change it would be short click, long click, and click-and-hold. Click-and-hold at least continues short click, while long click does not. When I pick up a candle, the candle is lift off with delay --- that's because long click does not continue the action of short click, so the code has to wait until mouse is released and can't apply the short-click action immediately. That's exactly the issue that you fixed with crouching, and now you introduce it in another place.

The "external argument about exact duration" is not removed with double click. There is a setting in OS preferences for setting double-click speed, is there not? The challenge of setting the exact duration is the same for both long-press and double-click frob. Therefore, the confusion is not removed with double click. I tuned the long-press frob to be somewhere between "unintentional long-press frob" and "it being too sluggish." Early player feedback guided the current default value of 200ms -- it was originally 300ms. During more play testing, if players are having trouble, the default can be increased and tested. We need to follow the data from actual play testing. The player can adjust the tdm_frobhold_delay cvar to their liking as well. It's more likely that a player will hold frob while moving an item, because for most items, nothing different or bad happens. It's less likely that a player will unintentionally double-click frob an item during pick up, because they know that would cause them to drop it. Therefore, players are more likely to discover long-press frob to extinguish than double-click frob to extinguish, which is a good thing. We want the player to discover it (if they didn't read the manual or play the tutorial mission). Also, long-press frob is used in other games, such as Fallout 4. Getting double-click frob to extinguish to work well along with drop item would be troublesome, because there would always be a double-click delay before a single-click drop initiates. Long-press frob does not have a drop issue, because the player can long-press frob until they see the candle extinguish or quick-press frob to instantly drop it. To be clear, long-press frob also "does not change existing controls, only adds new meaning for" a longer frob press. This long-press frob proposal has already been play tested and agreed to be a good control scheme by several players. Double-click frob would need new code written, would need to be play tested, and would need to be fine tuned based on player feedback. Another rewrite of the code would be a distraction and may not bring us closer to the goal of "providing a better experience for new players as well as longtime players," especially since one has already been found and proven: long-press frob. For longtime players who are not satisfied with this new control scheme, "tdm_frobhold_delay 0" restores TDM 2.11 behavior. After 7 months of player research, code experiments, early player feedback, adjustments, rewriting code, and more player feedback, I believe long-press frob is good enough, given all of the compromises, imperfections, and its iterative design. It solves the problems stated in the proposal on the first page, and its design goals are met.

It’s incredibly common in controller mapping - to the point even the game’s current controller implementation supports it. Not sure if switching this to a double click is additive or subtractive. What is getting lost is the primary interaction with a body imo is actually to shoulder it - not drag it. Obfuscating this behind a second input is clunky and confusing to new players. What is “intuitive” is a matter of perspective, but the current patched method of the initial click shouldering a body makes a lot more sense to me and actually addresses some of the complaints from new players as laid out in the initial post. There is a method via the delay cvar for experienced players who prefer the old system to restore it, so I am uncertain what the down side is really?

Ambient atmospheres are in my opinion one of the best parts of the Dark Mod experience, not just for getting a mission to have the right feel but also for inspiration and to have them playing in the background when creating maps. The more the merrier, so here's a thread to collect all the links to ambient music and environmental sounds that could have a spot in TDM's setting. Ambients from the TDM forums Gast's Eerie Lullabies Magnanimous Merry's Miscellanea Orbweaver's Dark Ambients Spadey's Ambients Radioteque's Ambients Kyyrma's Composing Ambient Tracks for Dummies - Kyyrma shows how ambient soundtracks can be made from a set of sounds. Also contains some of his finished ambients. Request for more interior sounds - this thread is a very productive community session where members came up with a large and good selection of new ambients. Uncle Peti's Sound Den Dragofer's Ambients - post #6 in this thread SeriousToni's Ambients - posts #8, 12, 15 and 19 in this thread Ambients from the TTLG forums Custom resources list Gigagooga's Ambients 1 - possibly the largest pack of ambient musics and nature sounds, all of them high quality. Gigagooga's Ambients 2 - this pack puts more weight on shorter swells/hits/pads to be layered on top of a subtle ambient. Gigagooga's Ambients 3 Yandros' ambient loop Sephy's Ambients - a large collection of ambient pieces, including many shorter ones which will be valuable for anyone wanting to try a layered ambience approach like in the Thief OMs and Full Moon Fever. Internet databases www.freesound.org - some of the better composers in my opinion are ERH and BrandonNyte. www.purple-planet.com - a large selection of all kinds of ambient and musical soundtracks to be used freely. www.darkwinter.com - an internet label that publishes a lot of dark ambient music under a Creative Commons license. www.endlessascent.com - sister website of Darkwinter for non-dark ambients. Youtube Asatru Dark - also has very nice reference images for outdoor stone memorials, statue arrangements etc. #4 Void by Raffaele du Marteau & #6 Dreaming of Nowhere by Raffaele du Marteau - possibly the most forlorn pieces I've found on the internet. Alacazam - a prolific Creative Commons ambients composer . Cryo Chamber - for-profit label for dark ambient music with a large selection on offer. Going by their Youtube comments they're fine with people using their soundtracks for games etc., although you'd probably need to buy the soundtracks first. Dark Ambient Mixed Session - as much ambient as something to have in the background while mapping.

Looking at the code, the originals were "pm_mantle_pull 750" and "pm_mantle_pullFast 450". The new "pm_mantle_pull" value is "400". A "pm_mantle_pullFast" value of "450" would be slower than regular pull, not faster. With both being set to "400", they are at least similar. Other than that, it's subjective and the feedback from playtesters was positive. Also, referenced internally here: https://forums.thedarkmod.com/index.php?/topic/22256-movementcontrols-settings-in-main-menu/&do=findComment&comment=489158

That sort of tone doesn't fly in our forums.

DarkRadiant 3.8.0 is ready for download. What's new: Feature: Support new frob-related material keywords Improvement: Mission selection list in Game setup is not alphabetically sorted Improvement: Better distinction between inherited and regular spawnargs Improvement: Silence sound shader button Improvement: Add Reload Definitions button to Model Chooser Fixed: Model Selector widgets are cut off and flicker constantly on Linux Fixed: DarkRadiant will not start without Dark Mod plugins Fixed: GenericEntityNode not calculating the direction correctly with "editor_rotatable" Fixed: RenderableArrow not drawing the tip correctly for arbitrary rotations Fixed: Light Inspector crashes on Linux Fixed: Models glitch out when filtering then showing them Fixed: Skin Editor: models not centered well in preview Fixed: "Copy Resource Path" includes top level folders Fixed: Skin Editor: internal test skins are shown if Material Editor was open previously Fixed: Changing Game/Project doesn't update loaded assets correctly Fixed: Model Chooser: initially hidden materials aren't revealed when enabling them Fixed: Choosing AI entity class 'atdm:townsfolk_commoner_update' causes crash Fixed: Sporadic assertion failure on shutdown due to LocalBitmapArtProvider destruction Fixed: Prefab Selector spams infinite error dialogs on Linux Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.8.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. Keep on mapping!

I would use this massive list for any fan missions, it includes campaigns too: https://www.ttlg.com/forums/showthread.php?t=148090 There are a lot of Fan Missions for the picking, I myself go for the lesser known ones and the short variety, because sometimes they hide a gem or two. Just like jaxa, I'm a bit outdated after the temporal retirement, but I do remember some amazing campaigns like "The Black Frog". If you intend to play The Black Frog, you should play the first two of the L'Arsene series missions, it's how I did it myself. Also, yes, L'Arsene are a fantastic series. The first mission of L'Arsene is a "rough draft", author was a bit new to Thief level making, but still great either way, after the 3rd you will see how his skill increased by a massive amount.

I would like feedback on the default "tdm_frobhold_delay" of 300ms. Is that: too long? too short? just right? I personally like 200ms. I made the default 300ms, because I thought some players might click a bit slower than me, which might cause them to do the long-press frob action unintentionally. Which delay do you all prefer? @AluminumHaste What are your thoughts?