Search the Community

Thank you. And Thanks to wesp5 and snatcher for keeping this game looking fresh and feeling current.

The Frob Outline is already in the core game but not accessible without console commands, so I added it as option in the Unofficial Patch.

While working on something I analyzed the Frob Helper. The Frob Helper was enabled by default in 2.11. The options were: Show Frob Helper: Yes [Default] No [Tip] Makes interacting with small objects easier by temporarily displaying a white dot. ------------------------------------------------------------------ In 2.12 the Frob Helper remains enabled by default but things changed: Show Frob Helper: Always Hover Fade In [Default] Fade In Fast No [Tip] Makes interacting with small objects easier: Always = Show crosshair dot at all times Hover = Instantly show dot on highlight Fade In = Gradually show dot on highlight Fade In Fast = Same as Fade In but faster ------------------------------------------------------------------ If I was new to TDM I would expect a "Frob Helper" to help me identify frobs: you can interact with this, here is the helper so that you know it and you know where the center of the screen is in case you need it. The Frob Helper however was designed to compensate for the shortcomings of other mechanics of the game, and as such, the Frob Helper is flawed by design: it only shows up if the size of the object is smaller than the arbitrary value of 40. I will say at this point that I am well aware of the tdm_frobhelper_ignore_size cvar but this isn't the point. This game isn't a shooter and "Always on" is not required unless we are talking motion sickness, in which case it belongs in a hidden cvar, for the few that may need it. The starting point of the Frob Helper should have been: On (the helper shows up whenever you can interact with something) Off From this point we can expand with more options, of course: Always on (not recommended based on the nature of the game) On for all items - Hover On for all items - Fade In On for all items - Fade In Fast [Default] On for small items - Hover On for small items - Fade In On for small items - Fade In Fast Always off

https://store.epicgames.com/en-US/free-games Epic is giving away "good" games, probably a summer event, each one is a mystery before reveal. Starting with Dragon Age: Inquisition - Game of the Year Edition. Steam has this until May 27: https://slickdeals.net/f/17490963-machinika-museum-pc-digital-download-free https://store.steampowered.com/app/1507190/Machinika_Museum/

I have great news! There was an interview me from ThiefGuild . com! Check it out! https://www.thiefguild.com/news/1/66709/a-thief-inspired-fm-influenced-immersive-stealth-game-in-works

I hope that is not the new TDM version. https://forums.thedarkmod.com/index.php?/topic/20784-render-bug-large-black-box-occluding-screen/

The topic says it all, the error goes away when Bloom is disabled, otherwise it looks like this in the training mission for basically all items you can take:

About the chest sounds, I wasn't aware the Modpack does change them too. Would it make sense for the patch to use your way or would it produce another duplicate script? I can set the blinking to another frequency, but are you sure this is not due to the game trying to apply two blinking scripts at the same time? It looks fine if I only use the patch. Your blow skill is just a last resort for mission unique lights that can't be extinguished by my frob script. Also my version does not include free relighting so it is inferior to yours ;)!

WOW, what a pleasant surprise! I expected this day would come but not this soon. There they are :) Here is an initial, quick assessment. Currently the Modpack loads last, therefore it takes preference. We can test the other way around at a later stage. tdm_frobactions.script No conflict detected. The Modpack's version takes preference and it apparently works as intended. The Patch changes some chest sounds in a separate script at mission start but then the Modpack overrides these sounds on the fly. Blinking items Threads from both the Modpack and the Patch run in parallel throughout the mission. I don't notice anything unusual except that sometimes the blink is out of sync. The reason is that something fishy is going on between milliseconds 16 and 17 in Uncapped FPS mode. In v4 of the Modpack I set the wait time to 15 milliseconds to avoid the issue and you should do the same in the Patch: tdm_froblock_frobability.script > mod_frob_highlight_blinking() > sys.wait(0.015) Containers Threads from both the Modpack and the Patch run in parallel at mission start. I honestly don't know what the game is doing in this case but the outcome apparently is not negative. No issues detected. Body names Threads from both the Modpack and the Patch run in parallel throughout the mission. I don't notice anything unusual but most probably names are being displayed twice. Shock / Electric mine No conflicts that I can detect at a glance. Whistle No conflicts that I can detect. Players however end up with two different versions of the same feature in different categories. Blow No apparent conflicts. Players however end up with two different versions of a same feature in different categories. This one is interesting because the Patch introduces "extinguish on frob" on small candle sources and players are spoiled by options now.

It would be nice to be able to create your own EFX presets, this will solve that issue. https://github.com/kcat/openal-soft/blob/master/include/AL/efx-presets.h lists all the presets. Here they can be seen in the tdm source file. I think these could be read from an external file instead of inside game code? If TDM reads the presets from an external file, anyone could easilly make their own presets by overriding that file and these could be used inside a spawnarg when that gets implemented.

So path_follow_actor actually DOES work if you want it to follow the player. You just need to target the player entity dynamically in game. It doesn't work if you target the player_start entity. I can't remember if that's what people were doing (or even if that's what I was doing), but that won't work because the player_start entity and the player entity aren't the same thing. You can use a atdm:target_changetarget entity to do this, or a script: $path_follow_actor_1.addTarget($player1); Both can just be triggered by another path node, a atdm:target_callscriptfunction, whatever. Also you need to add the player target to the path_follow_actor node BEFORE the AI gets to it. If the target gets added after the AI reaches that node, it won't work. Video where the AI hits a node that triggers a atdm:target_changetarget entity: https://drive.proton.me/urls/A3DJW5EYFM#0WgYnCVOU6nv test map attached as well. EDIT: I have no idea why just manually setting 'target' 'player1' on the path_follow_actor node in DR doesn't work. I'll try to look into this. UPDATE: It appears the the player1 entity simply isn't there during initialization when the path_follow_actor's targets are evaluated. As a result, the 'actor' is null and the node does nothing. I didn't mention it before, but when I used the script method I just stuck in the map script's main function like so, and this works too: void main() { sys.waitFrame(); $path_follow_actor_1.addTarget($player1); } UPDATE 2: Wiki updated: https://wiki.thedarkmod.com/index.php?title=Path_Nodes#path_follow_actor path.map

Will this be included into the core game and if not, may I use it in my Unofficial Patch until it is?

Stone 24pt Font Upgrade, May 9 2024 Interim Release This first release just clears away some of the low-hanging fruit, while buffing the new datBounds program. In summary - stray mark next to W removed poor spacing of J and AE improved 6 characters got accents added. The download is made up of: .dat and 2 .dds files, for distribution/game inclusion .ref [with changes annotated] and .xcf [master source GIMP project, including datBounds layers] 2024 May 9 Stone 24 Interim font update.zip The changes were also doubled-checked using the testSubtitlesANSI FM. As this work continues, with an interim release approximately monthly, characters to be fixed will be chosen seemingly "at random", but actually due to layout considerations... you don't want to know. They'll all be done eventually. Details of Improvements:

For free ambience tracks it's as Freky said: you look around on the internet for tracks with the appropriate license to be included in your FM. Fortunately, you likely don't even need to bother doing this as a beginner as there's an entire "Music & SFX" section of the forums full of good ambient tracks for you to use if the stock tracks do not meet your fancy. You might also be interested in Orbweaver's "Dark Ambients", which come with a sndshd file already written for you.

A big thank you and congratulations for this mission I would rate 10/10. I can't find a better one in my memory. It's so big and varied, full of new assets. Just... wow ! Finding a way through the was hard for me, as well as being able to jump and go through a narrow hole in the I also gut stuck in this area just below the horizontal mesh hatch that opens with Oh, and my game use to crash when firing a fire arrow at a Thanks again, you are so good at this.

I just made an interesting discovery. In my FM that's in beta I have custom main menu music, but it doesn't always work. Basically it works: When you first start the game (whether the FM is currently selected or if you change to this mission and the game restarts) during the text briefing It doesn't work (i.e. you only get silence) When escaping back to the main menu while in-game After quitting a mission and it goes back to menu As far as I know I had all the correct settings in mainmenu_custom_defs.gui: /// Menu music after startup (not in-game) #define MM_MENU_SOUND_CMD "music fs_muslim;" /// Played in main menu when in-game (ESCaping out of the game) #define MM_INGAME_MENU_SOUND_CMD "music fs_muslim;" /// Played during non-video briefing #define MM_BRIEFING_SOUND_CMD "music fs_muslim;" It turns out the problem was I had this line set in the sound shader: leadin sound/ambient/ambience/silence.ogg Commenting that out on a hunch fixed the problem. So you might be saying to yourself 'that's all very interesting but who cares?'. My point is: Just an FYI in case someone else runs into this I don't think there is anywhere on the Wiki that covers menu customization? @Geep you've done a whole bunch around GUI scripting recently - is there somewhere you can recommend I can stick this?

I'm now considering the .xcf files as being in effect the source texture for the game fonts, at least those that have been bitmap edited in GIMP. So that's an argument for putting them in the TDM assets repo. But, in any event, they do need to be backed up somewhere official.

This is the continuation of my first post above. Weeks ago i got a string of bad days. My main PC(elitedesk 800 g3) suffered a SSD failure and i noticed my thinkpad charger have an exposed wire. So i decided to dust off my old lenovo ideapad(ideacrap) yesterday. The spec is i3 6th generation, 4 gigs of RAM, 2.5" 500GB spinning drive and it's equipped with Intel HD & Nvidia GT 920MX. It runs Ubuntu mate 20.04 with Nvidia proprietary driver version 470 installed on it. I tried running TDM 2.12 on it and i got a somewhat 'playable' framerate at 25-33 FPS. I could hear this poor thing groaning when running TDM. It got hot quickly around 25-30 minutes into game.

@HMartI am not sure that is correct - you can even see in your screenshot that the green or "y" areas of the normal map are not shadowed correctly in game relative your point light. They are in shadow where they should be lit and the appear illuminated from the bottom when the light source is above. Here is another example: OpenGL: DirectX: Notice in DX how light source hits the tops of the tiles and shadows the bottom - where as this is inverted in openGL which does not look physically correct to me given the light position. It is very confusing given the legacy of the game being OpenGL, but I have learned from (painful) experience that directx formatted normals are what look physically correct in the game, at least in my opinion.

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/

Seems to be OpenGL I tested right now. edit: I was wrong so I deleted my original reply to not induce others in error.

So, that's how it was explained to me. Even though it seems counter intuitive, using Direct X maps has worked for me. I was recently trying to import a bunch of textures from Polyhaven.com (they offer both OpenGL and directX normalmaps) and I used the OpenGL version at first, but when I put it in-game there was an inverted green channel. I then used the directX version and the normalmap worked just fine I'm happy to be corrected on any of this though. Maybe Polyhaven does something different with their normals, or I'm doing something wrong

Well, I actually found that initial folder in the HiRes SVN repo. This is different from the TDM assets repo as it has a bunch of source files for textures, fonts, etc, but they aren't really game-ready assets. This is where I found the tga image files for the fonts I thought you were looking for. I haven't uploaded Tels folder yet, but I was thinking of uploading them in the HiRes SVN repo, just for the sake of backing it up

Well, I disagree. I play this game for the features it offers, not the features some mission author thinks he has to change to his personal favor. And, frankly, some of the more current missions offer too much of that "I think this works better" feature change. For example, the sounds some missions introduce add nothing over the original sounds, but are rather worse in my opinion.

Again, that's not the point, The point is that the game is all over the place, if every mission feels and plays different. If you want that, hey. But, in my opinion, that's a big mistake.