Search the Community

Hello TDM-ers. I am encountering an issue where textures seem to partially disappear. I tried searching the forums, but, I don't know what to search for. The missing textures are a worldspawn brush acting as a roof with {for now} flat iron texture. There are other worldspawn brushes right below to create an attic ceiling with roof framework board texture. These gaps appeared a few edits ago. I can't "undo" to get back before whatever edit did this. The gaps are only visible during play and are not visible during editing. Closing and reopening DR and TDM do not fix anything. Some of the brushes overlap in areas behind the play area but I have never seen an issue doing that. The attached image has the effect I am now seeing. Ideas on where to start debugging this? Very much appreciated. Clint

(I apologize for the odd poll question layout. I wasn't able to add five yes-no questions, because polls are limited to three questions.) Hi everyone, I've recently been working on some patches for issues that I've read about from players on the TDM and TTLG forums — and Discord. My goal is to make it as easy as possible for players, especially new players and those who need usability/accessibility options, to find what they need in order to have a better TDM experience. I've already written the GUI and game engine code for these settings, which I've been using in my personal build. The reason for this poll and discussion is to both guide the finalization of my work and collect data to help inform the dev team. Which patches I submit depend on the outcome of this poll, discussion, and what the dev team agrees to accept. Once decided, I can coordinate with the dev team. I've attached screenshots of what the new settings menu would look like if all of the settings are accepted. Below, I have detailed each menu setting, so you can have an easier time understanding each one. Very important to keep in mind: None of these settings change TDM default behavior. They are all opt-in. If you are already happy with the behavior of 2.10, 2.11, etc. and these menu settings are accepted, nothing will change for you. Rename "Always Run" to "Run Mode" with options "None, Always, Toggle" After 2.11 was released, @i30817 requested that "toggle run" be added to the settings menu. Its cvar is already in TDM as "in_toggleRun" (same as Doom 3). I propose renaming the "Always Run" setting to "Run Mode" with options: "None", "Always", and "Toggle". None = in_alwaysRun 0; in_toggleRun 0 Always = in_alwaysRun 1; in_toggleRun 0 Toggle = in_alwaysRun 0; in_toggleRun 1 Show Blackjack Helper @Wellingtoncrab suggested that the new blackjack helper be added to the settings menu. Its cvar was added to 2.11 as "tdm_blackjack_indicate". More info: It's the new blackjack helper added to 2.11. When the game detects that the blackjack can be used for a successful hit or KO, the blackjack will rise slightly. I propose a "Yes/No" setting for this. Slider for "View: Head Bob" @ChronA requested a way to disable head bobbing, because a viewer watching him play was having severe motion sickness. Also, there was a bug in TDM that made setting the head bob in the console not stick after loading a saved game. (Even with 2.11, if a mission overrides the "tdm_player_thief.def" file and sets "pm_bobroll", "pm_bobpitch", "pm_bobup", and other cvars, it will override player preferences.) As far back as 2008, players have had trouble setting head bob. Another one from 2018. At the end of 2022, @Shadowex3 registered just to voice the need for a way to control head bob. I propose that a slider be added to adjust the amount of head bob. This would use a new "pm_headbob_mod" cvar with a value between 0.0 and 1.0 (default 1.0, no change). The "pm_headbob_mod" would be a multiplier for "pm_bobroll", "pm_bobpitch", and "pm_bobup". The advantage to this approach is that missions like Volta 2 and Hazard Pay would not need to adjust their "tdm_player_thief.def" files for head bob to work properly. And, the player can still adjust "pm_bobroll", "pm_bobpitch", and "pm_bobup" as they like. Slider for "View: Mantle Roll" This is similar to head bob for those who are sensitive to motion. Its cvar was added to 2.11 as "pm_mantle_roll_mod". A Thief player on Discord said, "2.11 will have a cvar to tune down the mantling animation at last." I propose that a slider be added for "pm_mantle_roll_mod". Auto-Search Bodies @Zaratul requested the "auto-search bodies" feature from Thief 1 & 2. Its cvar was added to 2.12 dev16783-10307 as "tdm_autosearch_bodies". I did a poll on the a Thief Discord server and roughly 20% of players there use the Thief auto-search bodies feature. I propose a menu setting for this, so that players coming from Thief 1 & 2 can easily find it.

Awesome! Post is up! https://forums.thedarkmod.com/index.php?/topic/22200-beta-testing-the-house-of-delisle/#comment-487365 Thanks!

Hi guys, through the "cheats" topic I got the idea, that it would be quite useful, if there were tags for missions (the post was about removing the killing restriction in some missions to suit the prefered play style). I don't know how easy or difficult this is, but with them, it would be quite convenient to pick missions with playstyles, environment, etc one does want to use. This could also be expanded to other mission properties. I remember a discussion about climbable drains, handles on doors, that cannot be picked and other things the map author chooses for himself. That way these things would be clearer and as I said before, it is easier to choose missions with playstyles that suit oneself. What do think?

@vozka vozka thank you for this excellent review. I'm sorry to say I can't give much of a reply as I'm suffering severe health and cognitive problems. Most likely this is temporary but for now I'm in a fix. __________________________ @vozka I can now give a more coherent reply and I'm recovering nicely. I agree with every point of the critique and I'm in a quandary about how I should go about applying fixes. I think your preamble to the actual critique shows an exact understanding of what I was attempting to do in the FM. You understand that it is story driven. You understood the main elements of the story, that basically a farm boy of pagan background entrusts himself with a mission. His village needs help. Because he's earned a certain bad reputation and fits the bills requirement for having daring and a certain amount of cunning, so the mission is a natural fit; also amongst other things he wants to earn himself a good name. He has friends to help him along the way, and makes friends of friends along the road of the pagans. The FM uses devices to distinguish the pagans from the enemy they face and divides the space into distinct enemy and pagan areas, and areas in between. The pagans are opposed by corrupt nobles and their army of fundamentalist Builders, as corrupt as the nobles they serve. It's very black and white. Then there's the city guard who, being ousted from real power by the Builders are resentful and won't help the Builders and will ignore the player unless attacked or the player is caught trespassing in their inner court. That's about it. The critique mentions some gameplay elements that detract from the story and I agree about those. It also mentions gameworld failings that interfere with enjoyment, with gameflow and immersion. It seems to me that to fix these flaws will require a total rewrite of the FM, rebuilding the entire thing. For example, I understand the problems mentioned w.r.t. the lighting and know how to fix them, or at least bandage them over so technically there's no apparent problem. But I have a notion that the not so apparent problem here is in what's being lit. That there should be a rearrangement of things so light can be more focused and contrasted with the dark. I'm only starting to think through ways that I might do this. Needless to say anything like this would take time, probably a year, and I'm not sure whether I'm up to it. I've been playing a new mission by Kingsal and know I haven't anything near that level of skill. IMO the FM is unplayable right now. Actually I had asked that it be removed from the TDM database. I don't like the idea of leaving a blot. Thank you again.

Release 1.2 now available. Mostly minor fixes, but includes one fix that will hopefully prevent the prison key from not spawning. Full changelog: https://github.com/FrostSalamander/fsx/releases/tag/1.2 Download: Proton Drive: https://drive.proton.me/urls/4YTT2D72EW#FJ9furObjD19 Github: https://github.com/FrostSalamander/fsx/releases/download/1.2/highex.pk4 @nbohr1more could you do the honours and add to mission DB please?

id Studio did a poor job in defining its categorization of variable nomenclature, so in subsequent documentation and discussions there are divergent views (or just slop). In my series, I had to choose something, and went with what I thought would be clearest for the GUI programmer: Properties, which are either Registers (like true variables) Non-registers (like tags) User Variables (also true variables) I see that your view is more along these lines (which perhaps reflects C++ internals?): Flags (like my non-registers) Properties, which are either Built-in (like my registers) Custom (like user Variables) Also, elsewhere, you refer to "registers" as temporaries. I am willing to consider that there could be temporary registers during expression evaluation, but by my interpretation those would be in addition to named property registers. I'm not sure where to go next with this particular aspect, but at least can state it.

I wouldn't necessarily say there is a lack of interest, rather this is lower on the priorities list than other things. I agree that we should consider xdata support though. Especially since it would be easier to hook existing translation code into. ( Though there is also a line of thought that we should completely revamp our translation mechanism and expanding the existing mechanism will make that even harder. ) There's no hard and fast rule but I would say the priorities go something like: 1) Crashes or breakage that needs to be fixed ASAP 2) Community code contributions 3) Community asset contributions 4) Things that are "interesting" or "fun" to implement 5) Things that are "easy" to implement 6) Things that the developers feel would really improve the project game-play 7) Code cleanup and structural fixes 8 ) Performance improvements and optimization 9) Accessibility improvements ( subtitles, translation, etc) 10) Bugfixes for existing assets 11) Enhancements to existing assets 12) New graphics features Given that we are a volunteer project, the priority list is always gonna be a mixture of "proper priorities" and things that are easy, interesting, or fun to implement. Grayman's approach was to survey the bug tracker for trends that revolve around a somewhat narrow topic and then compare that to community comments about the topic and develop a new design that covers all contingencies related to the topic. This would fix a large number of bug reports at once since it would either make them obsolete by removing the wonky parts of the prior design or make the design better match how players interfaced with the issue. The only downside to that approach was that covering "all contingencies" sometimes meant a very large conditional tree and that would span a huge swath of the project code ( thus risking lots of unforeseen bugs ).

The *DOOM3* shaders are ARB2 ('cause of old GeForce support) carmack plan + arb2 - OpenGL / OpenGL: Advanced Coding - Khronos Forums

ok thanks, yeah there is no reason that shouldn't have worked. I've created a new version and sent it off to @irisx and @DavyJones to see if it helped with the Linux crash (I also fixed the missing material warning). If anyone else wants to try it it's here (version 1.1): https://drive.proton.me/urls/K90XY99T8C#knRJbEEliX18 Ideally I'd get the crash sorted before I publish an update, but I'd be surprised if this fixes it.

Thanks, I can also recommend gog galaxy. The idea of the custom tags is really nice, I'll have to try this out too!

"Has there ever been so villainous a perversion of the printed page... As brazen and pernicious a scheme to feed the blossom of youth into the gaping maw of chaos and flame?" -Concerned Citizen IRIS has been updated to 1.2 Download via the link in the original post or here Changelog: Higher acuity for AI in hostile areas on higher difficulty levels (original AI scripting is retained on the Nostalgia difficulty) Improved path finding and fixes for AI patrol routes Additional bug fixes New and expanded content! Thanks to: @Dragoferfor scripting consultation @Amadeusfor editing/proof reading Bikerdude for consultation on AAS optimization @Klatremusfor copious testing Carry the light of The Builder, unto its end.

Keep in mind also that mission size, and complexity have increased dramatically since the beginning. For a lot of veteran mappers, it can take over a year to get a map made and released. The last dozen missions have for the most part been pretty massive, with new textures, sounds, scripts, models etc. We seem to be long past the point of people loading up the tools, and banging out a mission in a few weeks that's very barebones. We still do see some of those, but I noticed in the beta mapper forums and on Discord, that mappers seem to make these maps, but don't release them, and instead use the knowledge gained to make something even better. Could just be bias on my part scrolling through the forums and discord server though.

YOU TAFFERS! Happy new year! Deadeye is a small/tiny assassination mission recommended for TDM newcomers and veterans alike. Briefing: Download link: https://drive.google.com/file/d/1JWslTAC3Ai9kkl1VCvJb14ZlVxWMmkUj/view?usp=sharing Enjoy! EDIT: I promised to someone to write something about the design of the map. This is in spoiler tags below. Possibly useful to new mappers or players interested in developer commentary.

someone familiar with the quake engine should probably take the time and update xash3d with MH's vbo and shader driven code from remakequake, lately the code has made it into quakespasm as well (yep it is that good). it fixes practically all the gripes with the quake engine like seamless skyboxes, water effects, and a whole lot of nastiness with how planesides were calculated (was one of the big ones if you wanted PPL lighting). It is also uber fast and if someone took the time i have the code for some rather ingenious DOT3 bumpmapping developed by me and MH which uses a clever way of getting light angles to bumpmaps (in the old days you pretty much had to use PPL to make the bumpmaps look right but this was seriously heavy work on quake which only supported ambient originally so we had to use hacked entity lights coupled with PPL untill we developed this).

Have you figured this out? Do you mean the 3d-view (so how it shows in the game world) or when you click on it and opens fulscreen? I ask this because I remember I stumbled onto something when doing fixes to StLucia (making the church book visible in color in the game-view).

This is a not bad small street FM with a bit of climbing here and there, a few builders, the inevitable city watch, and, oh yes a couple of dead zombies. Or is they? The town is completely locked down by the city watch because of bandits. You've found a way in. Complete your objectives - then find a way out! DOWNLOAD HERE. Notes: If you find the way out before completing the objectives then it's blocked - just come back later. One objective on Expert causes a forced drop. This is intended so you cannot take the thing away again! Loot is rather easy for Expert (didn't realize until I'd burnt out with beta testing and fixes and uploaded! But you can still get all you want. If this FM seems familiar to anyone it was beta'd fairly openly about a year ago but the author has had no time to finish off the fixes. Althought it appears to be Part 1 of a series; don't hold your breath for a follow up!

Alright, a new version is up with a handful of the bug fixes that have been reported

Seems to confirm: https://bugs.thedarkmod.com/view.php?id=5718 does it happen in the latest dev build: https://forums.thedarkmod.com/index.php?/topic/20824-public-access-to-development-versions/