Search the Community

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

hmm i should have thought about that when i noticed the built in ram on the lunar lake, though also usable on a micro computer it makes more sense for mobile. 4070 ti super sounds like a good deal if the price is right, not so sure about the other models ?, performance wise they are already up there but may lack a bit more memory for higher resolution gaming, 12 gb iis mostly ok though, strangely it seemed the 4060 16 gb model was a flop but being the lowest model of the midrange cards might have been a hinderance (not performant enough to warrant the memory increase) the 4070 should have the muscle to make it a hit though. agree on the m4 socket still being popular and actually a smart move to also make the 3d cache chips availiable on those boards, looking forward to see the performance.

With TDM 2.12, after the credits finished, the "Mission Complete" screen did not display. I found that the screen was black and I could hear my footsteps when I tried to move around. I think the reason for the mission not completing successfully was that the "Do not kill or harm allies" objective was never marked as "1 = STATE_COMPLETE" instead it was left as "0 = STATE_INCOMPLETE". Note, I didn't use noclip throughout the mission. Same as: https://forums.thedarkmod.com/index.php?/topic/18054-fan-mission-the-accountant-2-new-in-town-by-goldwell-20160509/&do=findComment&comment=458491

How about using TDM automation framework (and maybe pcem/qemu)? More info see: https://forums.thedarkmod.com/index.php?/topic/19828-automation-features-and-discussion/

I'd still be on XP if they hadn't dropped support. I didn't say anything to that effect. I just grew to hate having to keep switching OS due to their business model that keeps imposing that. Been doing that for nearly 30 years now. I don't expect Linux to be paradise. I just hope it's less infuriating than MS products. Either way, that's besides the point here.

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...

Update: @JackFarmer The root cause of the turret crash has been found. It seems that it was given the same physics code as the security camera but does not have handling for cases where no clip model exists. Removing the physics code fixes the issue. That said, I guess we may look into adding it back so that the turret follows the same destruction features as the camera?

If the "mission fails as soon as stealth score turns non-zero," that would not be good for ghost players. They might need to find out "how" they failed and experiment to avoid alerting guards. They might need to take those score points as a "bust". They might need to take those score points to complete an objective. Then, mission authors would need to encode exceptions into their missions, which would be a lot of work (if they decide to do it at all). However, part of what makes ghosting challenging and fun is when mission authors do not create their missions with ghosting in mind. Please see: Official Ghosting Rules: https://www.ttlg.com/forums/showthread.php?t=148523 Writing code for these rules would be a huge undertaking. Ghost Rules Discussion: https://www.ttlg.com/forums/showthread.php?t=148487 Creating an official mode could alienate these dedicated ghost players, because it would clash with what is considered ghosting in the community. Including the Stealth Stat Tool mod in the official release would be more useful. Or, making the audible alert states of guards quick and easy to recognize could help as well. For these reasons, I don't agree with an official "Ghost" mode. If the dev team were to do it, we should consult with @Klatremus so we get it 100% correct or not pursue it at all. (This ghosting bit should probably be in its own thread.)

Something I just ran into, so I figured I'd share what I learned. I had an AI doing a path back and forth from A to B to A, etc. It would work fine for a while, and then suddenly he would stop and just stand there. At that point he would never proceed on the path. I cranked up the logging and saw something in darkmod.log about "handle door task" associated with that AI. I realized the problem. I had a dummy door nearby - it is a "door to nowhere" (solid wall behind it). But instead of using a door model, I had cloned a nearby atdm:mover_door and set it to frobable=0 (and removed the handles). That certainly keeps the player from using the door, but apparently it confuses the AI pathfinding. I replaced it with a model door, and now the AI path works fine. Bottom line: always use a model for dummy doors. Sounds obvious, I know.

...and if the model of your fan should also have a rotation (as for example in the greenhouse in HH VF), then proceed as follows: 1. convert the unrotated model of the "real" fan into a func_rotating (A) as described by dragofer. 2. depending on the orientation, select the x or y_axis property (if you enter zero for both, the fan will rotate around the Z axis) 3. now give A the desired rotation 4. clone A, place it in a blue-room and convert it into a func-static (B) 5. give A the property "bind" - B"

Glad it worked it means that is a global material token, btw those 2nd brackets are called "stages" and a single material can have more than one stage (draw call). But I still don't get the reason why an AI vision feature, is handle at the material level?! Normally you mark a entire entity/model invisible to the AI, not just a single surface on a model.

To cater to both audiences. I mentioned LibreGameWiki as one example. nbohr1more mentioned other uses. Explicitly allowing reuse and spread will help TDM reach a wider audience and would hopefully attract more volunteers. More volunteers which can help improve both TDM versions. There are several benefits for a project of being in the Debian repo. One is that TDM Debian-users can report defects on any package directly to Debian (no need to register on separate forums). Debian may then fix the issue themselves (in their "TDM-libre" package) and will offer the patch upstream to TDM, who can then choose to accept or reject the patch. I envision "TDM-libre" to have the same capability of downloading any mission as regular TDM. The only difference is that "TDM-libre" would come packaged with the regular engine (which is GPL+BSD) and an included mission that has libre media/gamedata. When I play TDM by myself, I want the unlimited-play and can accept commercial restrictions. But if I were to promote it somewhere, or charge for a stream when playing online, or make a video, I would want a version without commercial restrictions (and can temporarily accept limited-play) to make sure I don't violate anyone's copyright. Perhaps. That's what I'm trying to find out.

I suggest you use the term "I", to make clear that it is something YOU want, and that you speak for yourself. But, as wesp5 mentioned, I don't really know what this is about, at all. And, I'm also wondering about all the newly registered people lately, who just arrived at this forum, and already want to revolutionize this mod. This is a thing I noticed 2 or 3 years ago, and which hasn't been present in the 15 years I play this mod and frequent these forums now. Really seems like a common thing these days, to not knock on the door, but kick it in, and stomp right in.

I would only leave it as worldspawn if you need it to act like worldspawn. For example, if you have a nodrawsolid_wood brush covering a wonky wooden model and you want AI to be able to walk over it smoothly or it is to perform some sealing function. Other than that, just make a func_static so it gets filtered out in DR when you want to only look at sealing brushwork. So no harm in leaving it as worldspawn, but on the other hand you might get some benefit to making it a func_static.

TDM has tons of textures from "free" texture resources that do not allow redistribution and cannot be incorporated into a commercial project. Someone would need to create a huge replacement pack of textures that do not break the look of existing missions and do not infringe on the copyrighted textures. Also, many artists who contributed to this project do not want 3rd party entities to use their work in commercial projects. They intended the models, textures, sounds, animations to be exclusively used for Darkmod content. You would either have to replace ALL assets or contact every contributor and ask them to re-license their assets. Many contributors are no longer active with the project and haven't visited the forums in years so it would be no easy feat. I cannot speak to Debian policy but I think that they treat installers that add non-free content the same as non-free content itself. One could argue that Steam is such an installer but I guess Debian would counter that there are a few fully Libre games on Steam. I think Debian, Ubuntu, or Linux Mint need to consider a repo that allows for games (etc) that include non-libre content but intentionally offer this content for free to the community with no stipulations other than "don't try to sell it as a product".

The gamepad implementation allows for a great degree of flexibility to personalize settings, aside from a few minor issues that I mentioned here: https://forums.thedarkmod.com/index.php?/topic/22337-gamepad-bindings/ I would say that playing TDM with a gamepad works very well, especially considering that it was implemented as experimental and hasn't been changed since then. If I could, I'd go back to 2021-you and congratulate you on buying that gamepad. I notice that your DarkmodPadbinds.cfg looks very different from mine...

It seems like more and more "thief" and "thief players" is becoming a short hand to dismiss community members earnest desire to improve the game - which happens to be a barely legally distinct "thief style" game which was made by thief fans for thief fans and is "designed to simulate the stealth gameplay of Thief". Who is the predominant player base of the game supposed to be beyond fans of the thief games? Is there some better avenue to find feedback for the game beyond this forum? FOSS and linux forums? I have seen maybe half a dozen posts from that segment. I am a thief fan, I play thief fms, my association with those games is what drives me to play and make things for this game. Are we supposed to pretend the original games are not a huge reason why most of us are here at all? TL;DR version:

At first I thought it was some wild precision bug but it looks like the skin might be nonsolid somehow and SteveL's change made the nonsolid attribute work? Either that or skin detection is somehow borked in this map. Feel free to edit the map, I'm no expert mapper but I might be able to perform some workaround by manipulating the entity. Edit: I fixed it with the following change: // entity 4 { "classname" "atdm:mover_door" "name" "atdm_mover_door_8" "lock_picktype" "-" "lock_pins" "0" "locked" "1" "solid" "1" "model" "atdm_mover_door_8" "origin" "710 -248 2050" "rotate" "0 90 0" "snd_close" "door_shut_06" "snd_open" "door_open_08" "used_by" "Balcony_door_keey" // "skin" "door_007_1" // primitive 0 Will upload the fix to the mission database. I don't see anything wrong with the door_007_1 skin but I would advise testing it in-game before using it going forward until this is fully sorted. Edit 2: The updated mission is now available in the mission database. Feel free to offer other fixes to this mission as long as they do not: Change visuals Change gameplay design ( Any purely bugged things that the mission author acknowledges "needs fixing" such as keys that are inaccessible or critical items that fall through surfaces when touched, etc can be fixed by any mapper and submitted for validation by the team. )

Thanks! 1) Doing LONG_PRESS PAD_A (what I, for lack of knowledge, call "jump-mantle" or "_jumpmantle") differs from doing PRESS PAD_A ("_jump"). "_jumpmantle" differs from "_mantle", so they must be mapped to different button-calls. "_jumpmantle" differs from "_jump", so they must also be mapped to different button-calls. This appears to be the case, but it is not evident (or changeable) in DarkmodPadbinds.cfg. "_jumpmantle" seems to be hard coded to always connect to the same button as "_jump" but with a long press. It is as if bindPadButton PRESS PAD_A "_jump" is not actually just binding PRESS PAD_A to "_jump", but rather interpreted as "link PAD_A (regardless of button press time) to behave exactly like keyboard SPACE for short and long presses". I would have expected the default DarkmodPadbinds.cfg to explicitly read: bindPadButton PRESS PAD_A "_jump" bindPadButton LONG_PRESS PAD_A "_jumpmantle" bindPadButton PRESS PAD_B "_crouch" bindPadButton LONG_PRESS PAD_B "_mantle" ... but neither LONG_PRESS PAD_A or "_jumpmantle" is listed in the file. If there are actions "_jump" and "_mantle", I suppose there must also be an action "_jumpmantle" since it is possible for the player to do all those movements: * "_mantle" does the movements "crouch on the high surface, then stand up" * "_jumpmantle" idoes the movements "jump slightly forward, then land standing on the high surface" * "_jump" idoes the movements "jump up, then land exactly where you started" If the actions "_jump" and "_moveup" are not synonymous, then perhaps the action "_moveup" is what i call "_jumpmantle"? 2) Thanks for the link! It was useful in more than one way. I'll link to that page from https://wiki.thedarkmod.com/index.php?title=Bindings_and_User_Settings#Gamepad_Default_Bindings if I can get an account on the wiki, which proved more difficult than i thought (https://forums.thedarkmod.com/index.php?/topic/22327-how-can-i-create-an-account-on-the-tdm-wiki/). However, it does not answer my question how to find out the name ("<button>") used for a button on my gamepad. Basically, I would need to press the button on my gamepad and some program could tell me "That button is called 'PAD_A'". In my case, I have a gamepad "Logitech F310" (https://commons.wikimedia.org/wiki/File:Logitech_F310_Gamepad.jpg) which has a "Logitech button" (see image) that I want to use. I was hoping to find out the "button name" for that button and then edit DarkmodPadbinds.cfg to map it to a function. 3) ... but if that button has an "unusual name" that TDM does not recognize, then it may perhaps not work. E.g. if that button is called "PAD_LOGITECH" and TDM cannot recognize that name, then I cannot map anything to it via DarkmodPadbinds.cfg. Using QJoyPad I can map any keyboard key to it instead, as a workaround, but I cannot map MODIFIER to it (since MODIFIER cannot be set to a keyboard key). If current implementation is still called "experimental", then I must say it works very well; @cabalistic: kudos for that! I may not have continued playing TDM had it not worked with a gamepad.

It is possible that this is a setting that needs to be activated to work: https://mantisbt.org/forums/viewtopic.php?t=23221

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.

To assign the rotation point of a func_static made into an atdm:mover_door I go into vertex mode, select the axis of rotation (the only selectable vertex) and move it to the right spot. When I export that same func_static as .ase, import the .ase and make it an atdm:mover_door everything works, except the axis of rotation isn't selectable. When exporting as .ase I check the option 'Center objects at 0,0,0 origin', and the axis of rotation is now centered at exact center of the model. If I leave this option unchecked (default) the axis of rotation is centered at 0,0,0 of the DR grid - so when I put the cursor at a point of the grid and 'create model', that's where the axis of rotation is created while the model itself is offset accordingly. In neither case is this center, or axis of rotation, selectable or moveable independently of the model. eta: A kludge is to extend the door to be exported as .ase with a nodraw brush so the center of the combo is at the axis location desired. This works but is an abominable kludge which only gets worse since for double doors kludged versions of both L and R are required. Likewise for every other axis adjustment that needs to be made.