Search the Community

For the FM? For beta 1 it's here: https://drive.proton.me/urls/H1QBB04GA0#oBZTb1CmVFQb I've already done around 100 fixes though, so you might want to wait for beta 2 which should be ready in a couple of days hopefully. All links are in the first post of the beta thread here: https://forums.thedarkmod.com/index.php?/topic/22439-the-lieutenant-3-foreign-affairs-beta-testing/

Damn right, and I personally am going to keep making changes on how I want MY mission to be played and what I think is best for MY FMs. If that's not to your tastes, then I'm sorry these changes don't align with your preferences, but there are tons of other missions you can play that do. FM authors have ZERO obligation to provide uniform experiences that try to cater to everyone. Some people are going to enjoy these custom changes (I really loved the Resident Evil style saves, and I can't wait to see more missions with that) and other players are gonna be unhappy about them, and that's a crying shame, but it is not going to stop me from making FMs how I want them to be. Never once has a beta tester or a player brought up an issue about these kinds of choices I made for my FMs

Hello all. I use a laptop with a small screen -- 14 or 15 inches, I think. So, screen space is very important. I rely on keyboard shortcuts and undocked windows extensively. The only issue I have at the moment is the aggressive docking of window panels. So, hopefully this is a reasonable layout for a small screen.

Funnily enough, I was going to ping you and see if you wanted to draw the map. There is something included which could technically be called a 'map', but it sucks. The issue is the FM doesn't cover a huge area, but there is a LOT of vertical overlap so the options are a single map which provides vague guidance (the option I've gone with), or loads of tiny maps for each area (which would suit an automap probably).

That almost works perfectly. A slight modification completely solves the issue for me: $player1.setImmobilization("missionspecific", IM_ATTACK | IM_WEAPON_SELECT); THANK YOU @stgatilov!!! I'll fix that mission tomorrow.

well, I guess this is just where we disagree. It isn't really a mapper's job to inventory and highlight every change they make because most players don't have an issue with it. There are a lot more important fish to fry if you wanna get an FM released

Oh, some implementations might work a little differently from what I remember the term megatexture referring to. From what I used to know, it meant turning the entire level into a single model or set that uses a single enormous texture. While the concept may have its upsides, there are two major issues that negate any benefit in my view: The first is system resources, you don't benefit from any reuse as every pixel is unique, the only way to do it at scale is with a gigantic image thus a huge performance drop in pretty much every department. The second issue is that level design becomes far harder and more specialized... while here in TDM we only need to draw a bunch of brushes and place some modules to make a level, an engine based on megatextures would require level designers to sculpt and paint the entire world in software like Blender which is far more difficult and we likely wouldn't have even half of the FM creators we do today, even for those that know how to do it imagine the task of manually painting every brick on every home and so on.

I agree, that is an issue. It would be better if the system handling briefings/readables could be revised as you indicated, to handle individual sentences as #str_, rather than whole pages. Baring that, having a key field like "#str_This is a whole page\nfull of text that goes on and on and on [...] until done" would appear as a very long single line. That is nasty to look at in the Readables Editor, and even worse in the .langs file, where the too-long text would appear twice on a line (once with #str_ prefix of English version, another in translation). So for those, it would be better in the short term to stick to symbolic keys, e.g., existing #str_12345 or revised form #str_myfm_book_of_spells_page_1 I might add, in the longer term, enhancing the Readable Editor to use the .lang files would be an enormous improvement for FM authors and a significant accomplishment. A fair amount of work though, but probably doable in increments over several releases.

My issue with the Gold filter in HR is that overpowers all colors making the game monochromatic. These artistic liberties work on short games but in long games once the novelty wears down it could make the game feel monotone. Something similar happens in Thief 4. The art director made the textures almost colorless to add a bleak and sad effect to the game, cool but overtime the player might feel the game is dull and boring. Colors not only give look but also feel. Bur regardless. Here's my attempt to Replicate the Gold Filter in Deus Ex Art Director's Cut OFF ON The Directors Cut has this Pinkish Copper Tone: ON

Interesting idea. Not sure about my upcoming time availability to help. A couple of concerns here - - I assume the popup words uses the "Informative Texts" slot, e.g., where you might see "Acquired 80 in Jewels", so it likely wouldn't interfere with that or with already-higher subtitles. - There are indications that #str is becoming unviable in FMs; see my just-posted: https://forums.thedarkmod.com/index.php?/topic/22434-western-language-support-in-2024/

In post https://forums.thedarkmod.com/index.php?/profile/254-orbweaver/&status=3994&type=status @nbohr1more found out what the Fixup Map functionality is for. But what does it actually do? Does it search for def references (to core?) that don't excist anymore and then link them to defs with the same name elswhere? Also I would recommend to change the name into something better understood what it is for. Fixup map could mean anything. And it should be documented in the wiki.

I'm at the beginning of a new area, where bandits fights each other. Near the end, I imagine, but I'm not going to bother finishing it. The thing is tedious. It's very obvious your focus was on telling a story. The issue is that's not my thing, and I also think this is not the right game for it. You're trying to make it do things it was never designed to, so it feels clunky. I think the game shines best in a smaller map with some backstory and little touches in the mission, like notes one character leaves for another. Here, it feels like I'm being pulled along from place to place, having to go back where enemies have artificially respawned, with locked doors everywhere, JUST to further the story, not to give me an interesting challenge. And in terms of story, it's the same thing we see all the time: Pagans are the poor, downtrodden, nice people, and the Builders, are the heartless monsters. Yawn. I don't get how the gargoyle switch works in that guy's office, even after having read your explanation. I don't even understand what the situation is supposed to be. The gargoyle looks like it's locked inside a glass case, and therefore you want to get that glass case open. The note says the gargoyle switch is behind the downstairs desk. Downstairs from this note, there is no desk. And the note calls it the "gargoyle switch", which implies it's a switch for the gargoyle, not that the gargoyle itself is a switch. It's confusing for no good reason. Random notes: Boring name, as others have mentioned. A cursive font in letters is annoying to read. Loud music and sound effects are not fun, it just hurts the player's ears. The map is a screenshot. That ruins immersion. The light issues have been covered. For me, it never felt like I was in shadows, as opposed to other missions. Almost everything looks pretty brightly lit. I saw someone mentioning rope arrows are pointless, and I agree. You asked how that player could have made it past something without using one; well, I haven't used it either. You can just mantle. Of course, that's not an issue in itself. There's not reason to cry "I'm getting review bombed" when people are just giving their opinion.

That's what we originally did, but mappers (or at least one mapper) complained in bug 6062 about the spawnargs disappearing if they were the same as the sound shader. I suppose we could have considered that "not a bug" and kept the original behaviour, but perhaps there are situations where the old behaviour was problematic — there would be no way to distinguish between "this speaker has default radii from the shader" and "this speaker has fixed radii which happen to be the same as the shader but must not change, even if the shader is edited". I don't know how common such a situation is in practice. Correct, but the freezeTransform method is called after the end of any transformation, and does not distinguish between what type of transformation was previously happening. I imagine resizing the speaker to the same size as the shader would also have triggered bug 6062, but speakers are resized less often than they are moved and hitting an exact size with the mouse would be rare, so the issue was only noticed when moving speakers. That's what I'm confused about. I have yet to see any situation in which DR will set a max distance of 0 on a sound shader, other than by explicitly editing the spawnarg to have a "0" value.

@The Black Arrow That's a good analysis. I don't disagree but we're referring to different time periods with different quality aims: In the early days of 3D and low-res CRT screens when we had 256x256 textures, detail textures were used to make surfaces appear as if they have 1024x1024 textures... today in the age of 1080p monitors such texture can appear blurry from up close, we want to make 1024x1024 textures appear of 4096x4096 quality. Back then the goal was to get at least a little bit of perceived sharpness, today the goal is to see those microscopic details on every surface as if everything is real... while the concept of detail textures is old it scales to cover both aims. As you correctly pointed out, the ideal solution would be upgrading the actual textures themselves. Sadly there are two big problems with this that will likely never be possible to overcome: Someone must create or find identical textures to replace existing ones, which have to retroactively fit every old FM. That would be a huge effort for so many images, and will not look exactly the same way so people would complain how "this wall used to be made of small red bricks which are now larger and yellower which isn't what I intended and no longer line up". An advanced upscaling filter may be able to bump the resolution with good results, this would be a lot less effort and retain the exact appearance of textures. The even greater issue is storage and memory use would go through the roof. Imagine all our textures (from surfaces to entity skins) being 4096x4096 which would be the aim for decent quality today: TDM could take over 100 GB of drive space, you'd need at least 16 GB of RAM to run it, and the loading time of a FM will be 5 minutes. Detail textures are a magic solution for both problems: They're overlayed in realtime on top of the standard textures without changing their base appearance. This means you see pixels several times the scale of the image without requiring any image to actually be at that resolution, no vRAM or loading time increase. And if detail layers are disabled with distance you also don't lose FPS in per-pixels calculations when distant lights update.

The new behavior is available in the latest dev17026-10712. If you set cvar s_overrideParmsMode to 1, then you get the new behavior. The old behavior is under value 0, which is default yet. Also there is "debug mode" if you set value to 2. In this case the new behavior is used, but console warnings are posted when a sound being started shows difference in behavior (i.e. the engine computes both behaviors and complains if they are different). Right now you'll see regular warnings about various AI sounds: they have wrong effective volume in TDM 2.12 and before due to this issue. As for modifying the missions, I think the main blocker is the new DarkRadiant behavior. @greebo @OrbWeaver, could you please comment why DR automatically sets s_minDistance and s_maxDistance spawnargs since recently?

After editing some objectives, now I'm getting this console warning pop up any time I check the objectives in game. I've never seen it before. Everything appears to be working though. I have not edited the tdm_objectives.gui file and it is intact in the tdm_gui01.pk4 folder in TDM. It references DestroyDelay here. onAction { set "gui::DestroyDelay" OBJECTIVES_DESTROY_DELAY; set "gui::CloseGUI" "1"; set "cmd" "updateObjectives"; } but I have no idea what I could have done in my fm to give it issue. [EDIT] I get this warning in other missions now, not just mine. I reinstalled TDM and I still get this warning. Is this a 2.12 thing?

Sorry, the mission must somehow be bugged for you. I'll need to figure out what went wrong and issue an update. It's likely linked to not reading the note.

Done. @nbohr1moreWould you mind updating this on the server? Its a fairly bad bug, I've updated the OP but here is the link to the new pk4: https://www.dropbox.com/s/u279b60l40p29cq/moongate.pk4?dl=0 - I've fixed the issue with players getting places they shouldn't be. - Fixed an exploit with secrets - Fixed a few minor issues @snatcherIve included the stock tdm_playertools_flashbomb.def

Yes. Sure, I will change it, but I do mind. In addition to changing the forum title, I have also had the name of the pk4 changed in the mission downloader and the thiefguild.com site’s named changed. It's not just some "joke". The forum post and thread are intended to be a natural extension of the mission’s story, a concept that is already SUPER derivative of almost any haunted media story or most vaguely creepy things written on the internet in the past 10 or 15 years. Given your familiarity with myhouse.wad, you also can clearly engage with something like that on some conceptual level. Just not here on our forums? We can host several unhinged racist tirades in the off-topic section but can’t handle creepypasta without including an advisory the monsters aren’t actually under the bed? (Are they though?) I am also trying to keep an open mind, but I am not really feeling your implication that using a missing person as a framing of a work of fiction is somehow disrespectful to people who are actually gone. I have no idea as even a mediocre creative person what to say to that or why I need to be responsible for making sure nobody potentially believes some creative work I am involved in, or how that is even achievable in the first place. Anyway, apologies for the bummer. That part wasn’t intentional. I am still here. I will also clarify that while I love the game, I never got the biggest house in animal crossing either. In the end Tom Nook took even my last shiny coin.

So I've been cleaning off updates on the missions page by updating and replaying them and have been having difficulty with this one. I don't know if there's a trigger broken or what. Aside from my issue listed in my spoiler, I found the update plays much smoother, so thank you for that. I realize this is an older mission so may not get fixed at this point, just thought I'd mention in case.

I havent tried in 2.11 yet but I will. Just an update on this. For now I think I fixed it by: - Addressing most of the warning in the log above. Outside common errors like some missing textures and such that are part of the core. - Made sure to give my parallel lights "parallelSky " "1" spawnarg. - Deleted my .aas files and rebuilt them - Dmapped the entire thing Right now I am not getting the load error . It's a very hard problem to nail down because the console isn't giving a specific script name that it's getting hung up on (if that is even the issue similar to Amadeus's problem) AND I am actively working on the mission, creating new errors, fixing other broken things. ect. Its definitely something I fear will pop back up in beta testing though

Thanks for the feedback @Rio_Walker As mentioned in other comments in this thread, the optional objective was meant to be for players who enjoy exploring every inch of the map. If all you want to do is complete the mission via the primary objective it's pretty straightforward. It was also meant to be sort of 'open world' in that if you explore everywhere you pick up little hints and bits and pieces and put them together at the end to solve that objective with. It wasn't meant to spoon feed the player. But again maybe not everyone enjoyed that approach. It was also kind of a knee-jerk reaction to players not liking 'linear' missions. But it seems some people still do like that And yeah, some players don't like big maps. I get that. I don't like playing them myself a lot of the time The issue with the bow crash is a known issue (not just with this mission) which we haven't got to the bottom of unfortunately:

Looks great, thank you! That looks even better: It's where DeusEx had its player status screen, feels even more like TDM with DX characteristics now I think I placed it above the light gem as that's where player info was technically being stored, with the new subtitles covering that position the move is a great decision. By the way: If anyone wishes to continue and improve this mod, I'd appreciate seeing your remixes of it. I had it mostly finished last time on my end; I think the main issue was upgrades require items to be placed on maps, augmentations may not work on every FM without a way for them to automatically spawn in random places... my imagined solution was to also offer upgrades based on loot gathered or other achievements but I never got around to adding that.

I also take it the skin editor isn't among the most used parts of DarkRadiant, making this less easy to spot. Hopefully now the team will notice the issue, and it's ideally nothing hard to fix since DR has a history of GUI issues like this that stabilized.

I think the devs just haven't had much time to put into it the past year (myself included). I took care of the mouse issue finally, since it became a 100% showstopper for me to use DarkRadiant at all on Linux. I've only ever made my skins using a text editor, but I tried reproducing the issue and it crashes with a backtrace for me too. This means debugging it should be straightforward, I'll look at it this weekend.