Jump to content
The Dark Mod Forums

nbohr1more

Development Role
  • Posts

    12704
  • Joined

  • Last visited

  • Days Won

    257

nbohr1more last won the day on April 1

nbohr1more had the most liked content!

Reputation

4308 Deity

About nbohr1more

Profile Information

  • Gender
    Male
  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. PC Gamer came through with a big article: https://www.pcgamer.com/games/sim/after-16-years-the-dark-mod-finally-has-guards-as-perceptive-as-in-thief-the-days-of-seeing-knocked-out-ai-in-the-middle-of-a-bright-spotlight-get-ignored-are-over/
  2. Sorry folks, somehow tdm_ai_base01.pk4 was uploaded instead of tdm_base01.pk4. This has been fixed.
  3. A few new articles popped up: https://www.gamingonlinux.com/2025/03/thief-like-free-and-open-source-game-the-dark-mod-2-13-brings-better-ai-vision-and-new-graphical-goodies/ https://www.pcgamesn.com/thief/the-dark-mod-update https://www.dsogaming.com/mods/version-2-13-of-the-dark-mod-thief-game-in-the-doom-3-engine-released/
  4. 2.13 version is up: https://www.moddb.com/mods/the-dark-mod/addons/fresnel-mod-213-unofficial
    1. peter_spy

      peter_spy

      One small nitpick, the link to What's New Wiki page got cut off and it redirects to https://wiki.thedarkmod.com/index.php?title=What ;)

  5. Here is a texture pack that players can install into their darkmod folder to address this: https://www.moddb.com/mods/the-dark-mod/addons/tdm-213-mipmap-hotfix-for-lowend-players
  6. Delete the mission line in darkmod/currentfm.txt then use the in-game downloader to update all missions
  7. Source code commits: https://github.com/stgatilov/darkmod_src/commit/2d1ee8aef1102e0333d0e002e190d782660ed7fc https://github.com/stgatilov/darkmod_src/commit/196163d1a1c43ad668cbea4324d8627611733404 https://github.com/stgatilov/darkmod_src/commit/e96cfcc696d3c847936026a708456fb763bd1423 https://github.com/stgatilov/darkmod_src/commit/d825de73708ad4c9ed66b826fd689b4756d7ac30 https://github.com/stgatilov/darkmod_src/commit/ad15878f73c626a6243e796beaff63a9408f5920 https://github.com/stgatilov/darkmod_src/commit/02ab4916bfba0cb267f16db5933950d9a6d1ea06 https://github.com/stgatilov/darkmod_src/commit/7893569ca5e14610380add3a7d953dcdd34b27e6
  8. Start here: All "potentially visible" ( from AI pov ) entities run the full render pipeline for a random group of nearby pixels. Light and shadow casting is interleaved with the results added to a weighted running average. Before we had the Doom 3 source, there was no good way to sample the light textures in parallel for better performance.
  9. Cannot replicate? 1) Deleted the "nowandthen" folder under darkmod/fms 2) Restarted TDM and went to Missions > Download missions 3) Now and Then is available > download it 4) Now and Then is in the mission list Maybe your Darkmod.cfg is set to use the wrong mirror? What are your tdm_mission_list* cvars set to?
  10. Sounds like you have an old mission installed. Delete the line in your darkmod/currentfm.txt then launch TDM and go to Missions > Downloads and download all the mission updates.
  11. 2.13 is out, eager to see if any new reports arrive now that the CVAR thread-safe fix is in production.
  12. Here is the thread with the impacted textures:
  13. In TDM 2.13 we restore the original Doom 3 option to change texture quality in the menu. Lowend players no longer need to tinker with the image_downSize cvars. Unfortunately, sometime after the release of "Seeking Lady Leicester" ( TDM 2.11 development ) some DDS textures were added to TDM that lacked mipmaps. On texture quality settings below "Full" ( default ), these textures will render black: If you want to use any of these textures in a mission, fixed versions can be found packed into the missions "Seeking Lady Leicester" and "The Imperial Sword". If you see any other textures that render black when texture quality is below Full, please report them to this thread. Thank you! Edit: Daft Mugi used a python script to find the remaining items ( added to the list above )
  14. The longer we keep the beta open, the more likely we are to start fixing bigger issues and thus possibly introduce more long term bugs \ regressions. We try to adhere to a regular release schedule so that we have a stable baseline for bisecting issues by first checking major releases before narrowing to betas, then dev builds, and finally individual commits. That said, I will go on record to say that I would have included these two fixes in 2.13 without another beta run. I'm not the king so I can only vote and hope others agree.
×
×
  • Create New...