Search the Community

I liked the atmosphere, build up of tension, without actual scares. Although, when I started, and got into Captain's quarters... I read the readable and thought.... Okay, so there are 11 sailor thugs, only to find a lot more in the house, and wonder what the heck. Maybe I didn't scroll it? I liked the dialogue too, but I was a little disappointed that the interior didn't match the description, it wasn't until I returned for the first time did it change to match. And I expected some sort of ghost or ghoul to pop up. Then the transition, and when I went looking for the spot, I noticed the way it was highlighted. =D That was pretty funny TBH. Then - Two missions in one was a bigger surprise than I expected. How does it even work? The only thing I don't get is the finale, but I suppose that's the point.

At long last, I am finally releasing my first mission, A Score to Settle. It's been a long road! I started this mission three years ago, when I didn't even know you could move the verts of a brush, and knew nothing about visportals or patches. I'm sure I've made every noob mistake in the book. I have learned a huge amount from this map, and have developed a great deal of respect for anyone who goes through the entire process of building and releasing a mission. A Score to Settle is a small to medium sized mission, where you set out to find and humiliate the leader of a rival gang. It is meant to be a challenge to players who are familiar with TDM, and is probably not a good mission for those still getting accustomed to TDM's mechanics (it's also not appropriate for children). ASTS uses 1.06 features, which means that AI are capable of relighting lights. The chance of this happening goes up depending on the difficulty level you choose. Difficulty levels also affect the number and quality of AI, the number and type of lights, and AI acuity (AI have slightly better than normal hearing on Hardcore). The difference between Casual and Hardcore is considerable. The mission includes several video and audio files, so it is hefty at 135MB. edit: Please follow the objectives carefully. If you don't do the "first" objective first, you'll spoil some of the story for yourself. Hope you enjoy it!

In case anyone decides to pursue this further, here are a couple more references: https://discourse.gnome.org/t/pointer-warping-on-wayland/9197 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158 Seems like this feature is also common in PCB design software. The "correct" solution would be to use Wayland's pointer locking interface and relative mouse events, which is essentially what the FreezePointer class accomplishes by continuously warping the pointer back to its original location. The complication is that the way it works now all goes through wxwidgets which then goes through gtk3 on Linux. To fully implement this, I think someone would have to: Create a platform-specific alternative to the cross-platform FreezePointer that we have now Make sure it's only called on Wayland, and only if the pointer locking API is available Work your way through the wxwidgets / gtk3 layers to get hold of the native wayland surface and pointer handles Reconcile the Wayland mouse events with the mouse events received by wxwidgets If someone was motivated enough to pick this up, it might make sense to try to build this in at the wxwidgets level and try to get it accepted there. It would help keep platform-specific code in the right place and also make a couple other projects happy.

Well, let's explore this a bit. How can this be solved? Currently, creeping overrides running (like you said). Here are a couple issues or considerations: What about players who want to keep the fine control of toggling each one independently? Perhaps some players want to go from creeping to running. At the moment, the code is written in such a way (due to its Doom 3 history) that toggling creep can set the toggled run state, but toggling run cannot set the toggled creep state. The toggle creep key can set the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. Fixing this would require a lot of code rewriting. Brainstorming: It almost sounds like increase and decrease speed keys are desired. Run key to go from creep to walk and from walk to run. Creep key to go from run to walk and from walk to creep. If you're curious to give this a try, here's a Linux test build that matches beta212-05 (rev 16950-10635) with the following change: The toggle creep key sets the toggled run state to walk but only once. If the player presses the toggle run key again, it will toggle without regard to the toggled creep state. https://drive.google.com/file/d/1osTCQRf7LQ5wPvhGl2uRU4NcFnJPEu9_/view?usp=sharing

big problem with that is that we are nearing a point where the electrons cant travel safely anymore (something to do with things on the quantum level), i guess they need to speed up development of light based computers or get smart with autoreconfiguring gateways internally in processors.

As everyone know, right now we have both stencil shadows and shadow maps in the engine, and the player is mostly free to choose whichever he likes more. Due to the reasons I provide below, stencil shadows will most likely be dropped in some future, but that future is definitely not here yet. Unlike shadow maps, stencil shadows do not support: Alpha-tested shadow occluders. Shadows on translucent surfaces. Volumetric lights with account for shadows. Soft shadows with contact hardening. Point 4 can be ignored, point 3 has an automatic workaround by forcing lights with volumetrics to shadow maps. Points 1 and 2 result in major difference in behavior between the two modes. For the reference, we have one more technical difference: Front faces cast shadows in shadow maps mode, but don't cast them in stencil shadows mode. I recall how initially volumetric lights had their shadows disabled in stencil shadows mode, and mappers were not happy because that's a big difference in behavior. One issue was that every mission has to be beta-tested in both modes. That's why right now I mostly follow the same strategy: Alpha-testing is disabled when rendering shadow maps (since 2.12), unless you enable r_shadowMapAlphaTested. Shadows are disabled on translucent objects (since today's 2.13 dev build), unless you enable r_shadowMapOnTranslucent. I wonder if this is still what majority of the mappers think is best?

http://k.min.us/jCfGA.jpg "At night, they say, the Builders' hand comes loose from his mighty hammer and creatures wander out from their hiding places while he slumbers. But tis this night, above all others that unholy vapours cloak the land with gloomy curtains and night creatures dance and sing in the twilight. I can't say I'm looking forward to my endeavors this night.... I've been given a job by a Priest to retrieve two holy artifacts from an abandoned cloister in Eldin woods north of the city, simple job I thought, but the priest failed to mention the placed was haunted." Build Time: - version 1.0 was about 5 weeks, but we are now upto version 3.11. Thanks: Respect to the Dark Mod team for putting up with all my questions and knocking up the various updates in short order!. Special thanks to Flanders and Springheel for their models and my testers for helping me squash all the bugs etc. Testers: Flanders, Jaxa, nbohr1more, Aluminumhaste, Baal,l Oldjim, Cookie, Obsttorte, lux, Mat99, AluminumHaste, thebigh Readables: Darkangel/Flanders/b1k3rdude with special thanks to Flanders for his original story.. Resource: Flanders/Springheel - art direction and models. Misc: This is a homage to the original Thief2 mission from 2001 (The Cathedral of the Damned) Download: - The latest version is now available via the in-game downloader. Info: This version has been heavily updated from the original, this came about as a result of need to be compatible with TDM 2.10+ Repeat after me, "Read and explore, Read and explore" The mission is fully l10n ready. (thanks Tels) The mission now has EFX Reverb The mission now has Volumetric Light effects The mission now uses LOD settings for different detail levels There is now a script event related to the "Curse" A few new surprises... Known issues: This mission will have less than optimal fps at a few points on the map, but most of my testers with lowish end rigs (P4/HD4650) are getting 30fps+ at the worst spots) For very low end PCs I recommend the following settings: V-sync is off, AA is off, Aniso is 4x or lower, advanced settings are simple/default & Post processing of disabled and as a last resort the command line arg ' r_skipFogLights 1 ' (turns off the fog)

Type of mission: Mansion/Estate/Horror Story: Lord Blackgrove recently purchased a rare expensive artifact. The whole family has now disappeared leaving the manor empty. Time to check out the manor and see if the artifact can be found. Build time: My first map ever, 300 hours (5 months). Credits: Kingsal - Breaker script for light switches and elevator Dragofer - Ambience Track 'Intent' Springheel and Sotha - Video Tutorials (those videos really helped) Feedback and testing: Cambridge Spy, Dragofer, nbohr1more, Acolytesix, wesp5, Shadow, Zerg Rush, AluminumHaste, prjames The whole community. Download (1.03): https://drive.google.com/file/d/1wZc_nqHoX7kQvzfg08EpoRy2hyuH7mw3/view?usp=sharing Edit: Version 1.02 provides large performance improvements in the outdoor areas. Be sure to set TDM Object Details (LOD) to Normal (or lower) to take advantage of some of the optimizations. Edit: Version 1.03 further improves performance around hedges thanks to HMart's alternative hedge model. I’ve had a mission like this in mind for years. My main influences and inspirations are: Deus Ex - Chateau DuClare (https://youtu.be/9QLT_l8aH78) Clive Barker’s Undying - Main Mansion (https://youtu.be/t8PyXhCQB3Q?t=90) Thief Deadly Shadows - Shalebridge Cradle (Almost everyone should be very familiar with this one) (https://youtu.be/Rw4YZuRUgXA) In case anyone gets stuck and needs help, I’ve listed some questions and answers below that will hopefully help. FAQ

The problem does not show up with all related dev builds. However, I cannot test with the last build (16854-10518), which I simply cannot start and get the report EDIT: As per our friend dragofer's suggestion, I made a blank script file in this build and removed the turrets from the WIP for a test. Then I can start the game and the mission and can save/load without problems. Summary: 16842-10488: no problems 16854-10518: cannot test (see above) 16854-10518 (modified scriptfile, no turrets) : no problems beta 1: problem appears

Thank you! Does is also happen in the first 2.12 Dev build dev16778-10275 ? If not, can you bisect to the first dev build where it happens?

@snatcher I understand that when you feel your work doesn't live up to your goals that you don't want it out in the wild advertising your own perceived shortcomings but that leads to a troubling dilemma of authors who are never satisfied with their work offering fleeting access to their in-progress designs then rescinding them or allowing them to be lost. When I was a member of Doom3world forums, I would often see members do interesting experiments and sometimes that work would languish until someone new would examine it and pickup the torch. This seemed like a perfectly viable system until Doom3world was killed by spambots and countless projects and conceptual works were lost. I guess what I am trying to say is that mods don't need to be perfect to be valuable. If they contain some grain of a useable feature they might be adapted by mission authors in custom scenarios. They might offer instructive details that others trying to achieve the same results can examine. It would be great if known compelling works were kept somewhere safe other than via forum attachments and temporary file sharing sites. I suppose we used to collect such things in our internal SVN for safe keeping but even that isn't always viable. If folks would rather not post beta or incomplete mods to TDM's Moddb page, perhaps they would consider creating their own Moddb page or allow them to be added to my page for safe keeping. Please don't look at this as some sort of pressure campaign or anything. I fully understand anyone not willing to put their name next to something they aren't fully happy with. As a general proviso, ( if possible \ permitted ) I just want to prevent the loss of some valuable investigations and formative works. The end of Doom3world was a digital apocalypse similar to the death of photobucket. It is one of my greatest fears that TDM will become a digital memory with only the skeletons of old forum threads at the wayback archive site.

Congrats on the release! Remember to check ThiefGuild as well as the DarkFate forums (via Google Translate) for additional feedback.

TDM currently uses Scons as the build system to build the execuables from the source code for Linux and Mac. (I guess the Windows side uses whatever MS uses). This has been working more or less for a few years, and one shouldn't "fix" a working system. However, the merging of the D3 source code and the TDM source also brougth along a change to try to use pre-compiled headers. This, however, does somehow not work in the combination of scons, and gcc. Everytime a single line is changed anywhere (in fact, even if 0 lines are changed), the entire source code is recompiled from scratch. Due to the precompiled header, this goes a bit faster than before (16 mins vs 22 mins on my old PC), but it is still annoying having to wait that long, not to mention not being able to use the system during that time. So, it is highly desirable to fix this problem. Here is your chance to fame. Go fix it! Related thoughts: * the minimal invasive solution is prefered - if it can be made with scons, the better! There is no real need to rip out out and replace scons with another build system, unless this brings massive advantages (frankly, the only one I can see is "make it work with precompiled headers"). However, if you do so, prepare to get swear words thrown at because a new build system is likely to bring other, yet unknown problems Nobody will complain, tho, if you make the change to whatever, and it just works, tho Bonus points for: * Creating an automated build system. Something living on the greater internet, syncing SVN every minute, and when detecting a new checkin, re-compiling the source automatically, then publishing the build log on the web, and make the result downloadable.

Dear mappers, please be aware of this decorative light option introduced in upcoming 2.10 It aims to highlight the light volume and produces something like the existing fog particle with the intended effect of better speed and arguably better visuals It looks like this in game The test map we have been testing recently is courtesy of Bikerdude: download To enable this effect you will need to mark your light material with the volumetricLight keyword, like this lights/test_mansion01_window04_vol { description "volumetricLight for mansion01 window04" volumetricLight { map lights/mansion01_window04 colored zeroClamp } } Volumetric lights use projection and falloff textures to generate the volumetric effect. With shadow maps on, they also take shadows in the account. There's also an optional parameter after volumetricLight that toggles max speed vs decent look mode. Credits: @peter_spy for the original test map and direction @Bikerdude for great support during the reintroduction effort this year @stgatilov for taking the implementation on a completely different quality level @all for being cool and awesome

Just curious, based on this discussion: http://forums.thedarkmod.com/topic/19239-soft-r-gamma/?p=427350

So when you build a mission and want an automap integrated (at some point) it's best to name your info locations in a way that they are easilly integrated into the automap gui file. Also grouping them together and/or applying them to different layers. This is if not every info location is one specific location on the map and also not every location is visible on the automap (like secret area's for example). Having to figure out what info_locations match which area's on the map afterwards is a lot more work. Btw. I found that this guide shows an entity defenition, but doesn't say you have to add the entity as well. This confused me at first.

Ever since I worked on "Chalice of Kings" with Bikerdude, I have wanted to get flame particles with new particle glares into the core mod. My reasoning was that the candles have glares and the un-glared torches look mismatched. This proposal was met with mixed reactions, so (knowing the history of TDM feature proposals...) I have created a technical demo. You may download it here: zzz_flameglare.pk4.txt (fixed) Just rename without the .txt extension at the end and place it in your Darkmod directory. Here are some screens. Using particles for this is probably the wrong way to go now that Duzenko has an emissive light feature in his branch: http://forums.thedarkmod.com/topic/19659-feature-request-emissive-materialsvolumetric-lights/

All right y'all. We need some good ole data instead of 28 pages of -- well, you know. The "mantle roll" is the amount the view rolls or tilts during a mantle. So, if you could be so kind as to: Launch TDM 2.12 Beta Go to Settings -> Gameplay Set "View: Mantle Roll" to: 1.0 and test in game (100% of original mantle roll) 0.5 and test in game (50% of original mantle roll) 0.1 and test in game (10% of original mantle roll) Finally, vote for your preferred setting. The increased mantle speed changed the feel a bit and perhaps the mantle roll would feel better tweaked some to match it. (Edit: To clarify, this is about a potentially different default mantle roll value. The "View: Mantle Roll" slider in the settings will remain, regardless.) This thread is for your click-ity click vote on the poll at the top of this page. All constructive comments about the increased mantle speed in 2.12 are welcome on its own, wonderful thread:

"...to a robber whose soul is in his profession, there is a lure about a very old and feeble man who pays for his few necessities with Spanish gold." Good day, TDM community! I'm Ansome, a long-time forums lurker, and I'm here to recruit beta testers for my first FM: "The Terrible Old Man", based on H.P. Lovecraft's short story of the same name. This is a short (30-45 minute), story-driven FM with plenty of readables and a gloomy atmosphere. Do keep in mind that this is a more linear FM than you may be used to as it was deemed necessary for the purposes of the story's pacing. Regardless, the player does still have a degree of freedom in tackling challenges in the latter half of the FM. If this sounds interesting to you, please head over to the beta testing thread I will be posting shortly. Thank you!

I like the new mantle speed a lot. Though I find with the faster speed the default mantle roll of 1.0 looks rather exaggerated and can be a little jarring, so I have been dialing it back. This is pretty subjective, but I have been dialing it back to around 60-50% and find that feels like a good balance to me. Might be worth looking at adjusting the default value now that the fundamentals are different, but maybe somebody else has an opinion.

For easier inspection of various culling algorithms, I created a new debug cvar. It fixes the camera position that renderer frontend uses for culling, but allows player to fly around and see the same objects from different view point. Don't expect perfectly valid/sane picture, but I think it reliably shows which objects are sent to OpenGL for rendering. Here is the demonstration (bottom-left is clipped away in this video, but I hope it is clear anyway): It will be available in the next dev build. Maybe someone will find it useful for analyzing overdraw? P.S. Aside from that, "r_showtris 2" + "r_useScissor 0" should be useful for overdraw analysis too. It is questionable though whether you should disable r_useScissor in this case...

@duzenkoTwo problems, first I did have my folders named darkmod in succession so I renamed to tdm and darkmod respectively. But the asset issue was fixed cause I forgot to run the flippin launcher... LOL So the engine boots up however... @stgatilovThe first time running, it decompressed textures but the game wouldn't start. Launched a second time and I get a fullscreen window, but it hangs on a black screen, last item in terminal is "Async thread started". When I run "thedarkmod.custom.debug" I get an ELF Exec error like it's compiled for wrong architecture, however a 'file' shows it is an aarch64 ARM executable. My terminal output below: EDIT: I noticed below the line "Unknown command '#'", I do know one project I was compiling on required me to modify a C file and change the # hashtags to // double forward slashes as ARM assembly uses // for comments. *Shrug* wooty@wootylx2k-ubn:~/build/tdm/darkmod$ ./thedarkmod.custom TDM 2.10/64 #9574 (1435:9574M) linux-aarch64 Aug 23 2021 01:34:57 failed parsing /proc/cpuinfo measured CPU frequency: 1000.1 MHz 1000 MHz unsupported CPU found interface lo - loopback found interface enx00249b1e62ae - 151.151.88.220/255.255.0.0 found interface virbr0 - 192.168.122.1/255.255.255.0 Found Unsupported CPU, features: TDM using Generic for SIMD processing. Found 0 new missions and 0 packages. ------ Initializing File System ------ Current search path: /home/wooty/build/tdm/darkmod/ /home/wooty/build/tdm/darkmod/tdm_textures_wood01.pk4 (376 files) /home/wooty/build/tdm/darkmod/tdm_textures_window01.pk4 (389 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_sculpted01.pk4 (463 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_natural01.pk4 (133 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_flat01.pk4 (302 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_cobblestones01.pk4 (224 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_brick01.pk4 (520 files) /home/wooty/build/tdm/darkmod/tdm_textures_sfx01.pk4 (69 files) /home/wooty/build/tdm/darkmod/tdm_textures_roof01.pk4 (72 files) /home/wooty/build/tdm/darkmod/tdm_textures_plaster01.pk4 (142 files) /home/wooty/build/tdm/darkmod/tdm_textures_paint_paper01.pk4 (63 files) /home/wooty/build/tdm/darkmod/tdm_textures_other01.pk4 (127 files) /home/wooty/build/tdm/darkmod/tdm_textures_nature01.pk4 (286 files) /home/wooty/build/tdm/darkmod/tdm_textures_metal01.pk4 (497 files) /home/wooty/build/tdm/darkmod/tdm_textures_glass01.pk4 (51 files) /home/wooty/build/tdm/darkmod/tdm_textures_fabric01.pk4 (43 files) /home/wooty/build/tdm/darkmod/tdm_textures_door01.pk4 (177 files) /home/wooty/build/tdm/darkmod/tdm_textures_decals01.pk4 (465 files) /home/wooty/build/tdm/darkmod/tdm_textures_carpet01.pk4 (92 files) /home/wooty/build/tdm/darkmod/tdm_textures_base01.pk4 (407 files) /home/wooty/build/tdm/darkmod/tdm_standalone.pk4 (4 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals_decls01.pk4 (27 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals07.pk4 (1111 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals06.pk4 (696 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals05.pk4 (119 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals04.pk4 (2869 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals03.pk4 (743 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals02.pk4 (1299 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals01.pk4 (82 files) /home/wooty/build/tdm/darkmod/tdm_sound_sfx02.pk4 (605 files) /home/wooty/build/tdm/darkmod/tdm_sound_sfx01.pk4 (966 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient_decls01.pk4 (8 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient03.pk4 (24 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient02.pk4 (163 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient01.pk4 (220 files) /home/wooty/build/tdm/darkmod/tdm_prefabs01.pk4 (961 files) /home/wooty/build/tdm/darkmod/tdm_player01.pk4 (125 files) /home/wooty/build/tdm/darkmod/tdm_models_decls01.pk4 (103 files) /home/wooty/build/tdm/darkmod/tdm_models02.pk4 (2053 files) /home/wooty/build/tdm/darkmod/tdm_models01.pk4 (3163 files) /home/wooty/build/tdm/darkmod/tdm_gui_credits01.pk4 (49 files) /home/wooty/build/tdm/darkmod/tdm_gui01.pk4 (721 files) /home/wooty/build/tdm/darkmod/tdm_fonts01.pk4 (696 files) /home/wooty/build/tdm/darkmod/tdm_env01.pk4 (152 files) /home/wooty/build/tdm/darkmod/tdm_defs01.pk4 (187 files) /home/wooty/build/tdm/darkmod/tdm_base01.pk4 (198 files) /home/wooty/build/tdm/darkmod/tdm_ai_steambots01.pk4 (24 files) /home/wooty/build/tdm/darkmod/tdm_ai_monsters_spiders01.pk4 (80 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_undead01.pk4 (55 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_townsfolk01.pk4 (104 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_pagans01.pk4 (10 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_nobles01.pk4 (48 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_mages01.pk4 (8 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_heads01.pk4 (100 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_guards01.pk4 (378 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_females01.pk4 (172 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_builders01.pk4 (91 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_beasts02.pk4 (229 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_beasts01.pk4 (23 files) /home/wooty/build/tdm/darkmod/tdm_ai_base01.pk4 (9 files) /home/wooty/build/tdm/darkmod/tdm_ai_animals01.pk4 (82 files) File System Initialized. -------------------------------------- Couldn't open journal files failed parsing /proc/cpuinfo alternative method used /proc/cpuinfo CPU processors: 16 /proc/cpuinfo CPU logical cores: 16 ----- Initializing Decls ----- ------------------------------ I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1277 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. Couldn't exec editor.cfg - file does not exist. execing default.cfg Unknown command '#' Couldn't exec autoexec.cfg - file does not exist. I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1277 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. ----- Initializing OpenAL ----- Setup OpenAL device and context [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) OpenAL: found device 'SB Omni Surround 5.1 Analog Stereo' [ACTIVE] OpenAL: found device 'Kensington SD4700P Dual Video Dock Digital Stereo (IEC958)' [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) OpenAL: device 'SB Omni Surround 5.1 Analog Stereo' opened successfully OpenAL: HRTF is available OpenAL vendor: OpenAL Community OpenAL renderer: OpenAL Soft OpenAL version: 1.1 ALSOFT 1.21.1 OpenAL: found EFX extension OpenAL: HRTF is enabled (reason: 1 = ALC_HRTF_ENABLED_SOFT) OpenAL: found 256 hardware voices ----- Initializing OpenGL ----- Initializing OpenGL display Borderless fullscreen - using current video mode for monitor 0: 3440 x 1440 ...initializing QGL ------- Input Initialization ------- ------------------------------------ OpenGL vendor: AMD OpenGL renderer: AMD Radeon (TM) Pro WX 4100 (POLARIS11, DRM 3.40.0, 5.11.0-31-generic, LLVM 12.0.1) OpenGL version: 4.6 (Core Profile) Mesa 21.3.0-devel (git-2b4b310 2021-08-21 hirsute-oibaf-ppa) core Checking required OpenGL features... v - using GL_VERSION_3_3 v - using GL_EXT_texture_compression_s3tc Checking optional OpenGL extensions... v - using GL_EXT_texture_filter_anisotropic maxTextureAnisotropy: 16.000000 v - using GL_ARB_stencil_texturing v - using GL_EXT_depth_bounds_test v - using GL_ARB_buffer_storage v - using GL_ARB_texture_storage v - using GL_ARB_multi_draw_indirect v - using GL_ARB_vertex_attrib_binding v - using GL_ARB_bindless_texture X - GL_ARB_compatibility not found v - using GL_KHR_debug Max active texture units in fragment shader: 32 Max combined texture units: 192 Max anti-aliasing samples: 8 Max geometry output vertices: 256 Max geometry output components: 4095 Max vertex attribs: 16 ---------- R_ReloadGLSLPrograms_f ----------- Linking GLSL program cubeMap ... Linking GLSL program bumpyEnvironment ... Linking GLSL program depthAlpha ... Linking GLSL program fog ... Linking GLSL program oldStage ... Linking GLSL program blend ... Linking GLSL program stencilshadow ... Linking GLSL program shadowMapA ... Linking GLSL program shadowMapN ... Linking GLSL program shadowMapNG ... Linking GLSL program ambientInteraction ... Linking GLSL program interactionStencil ... Linking GLSL program interactionShadowMaps ... Linking GLSL program interactionMultiLight ... Linking GLSL program frob ... Linking GLSL program soft_particle ... Linking GLSL program tonemap ... Linking GLSL program gaussian_blur ... --------------------------------- Font fonts/english/stone in size 12 not found, using size 24 instead. --------- Initializing Game ---------- The Dark Mod 2.10/64, linux-aarch64, code revision 9574 Build date: Aug 23 2021 Initializing event system ...852 event definitions Initializing class hierarchy ...172 classes, 1690368 bytes for event callbacks Initializing scripts ---------- Compile stats ---------- Memory usage: Strings: 45, 7160 bytes Statements: 20303, 812120 bytes Functions: 1278, 166124 bytes Variables: 91948 bytes Mem used: 2019680 bytes Static data: 3989840 bytes Allocated: 5034004 bytes Thread size: 7904 bytes Maximum object size: 884 Largest object type name: weapon_arrow ...6 aas types game initialized. -------------------------------------- Parsing material files Found 0 new missions and 0 packages. Found 3 mods in the FM folder. Parsed 0 mission declarations, no mission database file present. -------- Initializing Session -------- session initialized -------------------------------------- Font fonts/english/mason_glow in size 12 not found, using size 48 instead. Font fonts/english/mason_glow in size 24 not found, using size 48 instead. Font fonts/english/mason in size 12 not found, using size 48 instead. Font fonts/english/mason in size 24 not found, using size 48 instead. --- Common Initialization Complete --- WARNING: terminal type 'xterm-256color' is unknown. terminal support may not work correctly terminal support enabled ( use +set in_tty 0 to disabled ) pid: 4706 Async thread started Killed

@stgatilov In Written in Stone at 308 -1768 123 -13.7 68.3 0 (noclip) using stencil shadows (r10166), the FPS drops from 60 to 45-50. There is no FPS drop with r9853/2.10; it's 60 fps. I found that enabling Frontend Acceleration improved the situation and FPS was a steady 60 fps. Summarized: Frontend Acceleration enabled r10166 stencil 60 fps Frontend Acceleration disabled r10166 stencil 45-50 fps r10166 maps 60 fps r9853 stencil 60 fps I thought you might want to investigate this scene. Maybe there's an optimization that can be done.

A couple more: https://forums.thedarkmod.com/index.php?/topic/21739-resolved-allow-mantling-while-carrying-a-body/ https://forums.thedarkmod.com/index.php?/topic/22211-feature-proposal-new-lean-for-tdm-212/ https://forums.thedarkmod.com/index.php?/topic/22198-feature-proposal-frob-to-use-world-item/ https://forums.thedarkmod.com/index.php?/topic/22249-212-auto-search-bodies/