Araneidae

Time I think to revisit the debate: set r_frobIgnoreDepth to 0 by default? I say yes, please! I see nothing wrong with the new frob highlight with this setting, and I think there are a lot of words above to the effect that 1 is troublesome.

One comment about the new version: I know this is talked about elsewhere, but I really do think you should set seta r_frobIgnoreDepth "0" by default. Also, but I know this is insoluble ... it's a pain to have to restart my missions on every new version!

Hi @stgatilov, didn't realise it was time to drop tdm_update altogether. Can I suggest that tdm_installer delete it, then?

I think this could be an interesting idea. It's also something straight out of classic puzzle adventure games, combining strange things in the inventory to produce some essential item for progress. Of course, could be truly annoying (some of those puzzles were ridiculous), but guess that's up to the mapper!

How much difference would it make to this conversation if seta r_frobIgnoreDepth "0" was made the default for future releases? I have added that into my autoexec.cfg for now, and the frob highlight hasn't given me any issues yet.

Umm. I was asked to put the lockpicking bug in the bug tracker, and I have to say I'm having some issues with the tracker: First of all, I don't seem to be able to search. There are just under 2,000 issues shown, there's every chance my issue is already there, but I don't see how to check this. "Category" ... I have to select something, and none of the options seem relevant. What is Platform under Select Profile? At least I can leave this one blank? "Product Version" ... would be nice to be able to select the appropriate dev release, but at least I can leave this blank Ah well. Reported as https://bugs.thedarkmod.com/view.php?id=5715

Segmentation fault when loading a savegame immediately after startup: Will see if it happens again, but if so I won't be able to attach the save as it's too big for the forum. Are the numerous warnings of any significance? It'd be good to not be flooded with warnings... Edit: Yes, it's something to do with this particular save. Loading from the previous quicksave works. I'll hang onto the old save for a day or two in case anyone wants it, but as I say, I don't have anywhere to upload it. Edit: Drat, spoke too soon. Kept getting crashes from savegames, but starting the mission from scratch then allowed me to load a save game. Something seems alarmingly brittle here. Also, seems the lockpick stops working bug is still in this version.

Actually I'm not familiar with condump. However, with that keyword, google takes me to https://wiki.thedarkmod.com/index.php?title=Reporting_Problem That seems like a sensible starting point. However, I expect I can always just run darkmod >& console.log and pull out what I need to report. Will try to remember condump though.

Well, it was around about here: -482.59 2780.1 702.25 2.5 -72.6 0.0 However having restarted the game I'm not seeing the effect again. Hmm. I'll look for it again and try and see if anything in particular triggers it. When I saw it it came in and out of contrast as I moved closer or further away7. Is there a built-in way to enable console logging to a file? I had to get those numbers by scrolling back through my log output.

Seeing some odd boxy textures, both floors and windows. Here's a screenshot from The Painters Wife: This is the latest dev version, r_fboColorBits "32" set, Radeon HD 6950, Fedora 34.

So it turns out that dev16256-9358 is the first good version, and dev16238-9330 is the last bad version (truly horrible). The slow frame rate also applies when in the menu, which makes getting out of the game excruciating when it's in slow mode: I have to move the mouse very carefully ... and wait! My procedure was to use your installer and each time to restore the following Darkmod.ini: seta r_fboColorBits "32" seta tdm_mainmenu_confirmquit "0" seta com_showFPS "1" Not that showFPS was terribly necessary! Some interesting changes in the display experience, dev16202-9175 was a bit painful with setting screen resolution; I'm ever so happy with the new graphics mode using native resolution. I'd like to express my appreciation for both the new installer and the new default graphics mode. More and more things are starting to work out of the box. One thought on the Darkmod.cfg file. Would there be any way to maintain my custom .cfg changes separately from all the other settings? The current format of Darkmod.cfg with ALL the settings in a great big pile makes it very tricky to keep track of the changes I actually want to apply.

Do you want me to go back and find out? Hadn't tried TPW for ages, but the latest dev looks so good I thought I'd give it another try.

Would it help if the glow on the outline extended slightly inside the edge of the object as well (if that's an option)? I see what you mean about the highlight being obscured when a door is closed, though in a dark environment the highlighted object is bright enough anyway. I haven't tried frobbing in a well lit environment yet.

Is it technically possible to simply make the new highlight clip normally against the existing environment? That seems to be the main issue with the current design, the fact that it currently shines through anything covering it.

I for one absolutely need the 32-bit colour override (old graphics card?), but it doesn't need to be a menu option. On the other hand, the advantage of menu options is that you can see what's available. How do I know what the tunable options are? There isn't a clear link to documentation as far as I am aware. Regarding the frob highlight, I think if the new highlight didn't shine through everything it would be less trouble, and it would make sense to me to have a menu selection between "shining" and "subtle" options. To be honest, the shining bright option is quite nice when you can't find your way around ... but, yes, it is cheating really.

I do wonder if the frob outline is rendering for me as it is supposed to: it shines through everything! I can see frobbable items from half way across the room and behind obstacles, I can even see frobbable objects inside boxes and drawers. Have to confess, sometimes I'd be grateful for this, but it's feeling a bit like cheating at the moment. For instance, the impossible switch in A Good Neighbour (I had a little rant at the time about being unable to find it even after being told exactly where it is) will probably stand out the instant I look towards it.

The latest dev build is working well for me. One unexpected improvement: The Painter's Wife seems to work just fine now for me (I'm seeing say 40FPS, as opposed to maybe 4FPS on 2.09).

My apologies for the noise, this seems to have done the trick. I seem to have two versions of elixir in my fms folder ... neither of which were the version the downloader just gave me: $ md5sum elixir/elixir.pk4 ../fms-hidden/*/*.pk4 9356735038addb5c23c2852c2ddd7b31 elixir/elixir.pk4 c49669e7e9b33dbfa0a977b76476f641 ../fms-hidden/elixir_1_3/elixir_1_3.pk4 3ab3f2e4271205da51e5457b6d351159 ../fms-hidden/elixir/elixir.pk4

I do hope this is the right place to report issues with development builds. Just tried running The Elixir, and it fails to load:

Am playing The Bakery Job with dev16330-9508 and I seem to have stumbled across an interesting bug: on the upstairs door (which requires two lock picks) if I look away from the door between the first and second pick the door becomes completely unpickable. Haven't investigated elsewhere, other doors, saving and reloading etc, but imagine this might be a more general issue with this build... Edit: Have confirmed this is a problem in the training mission. To reproduce: Pick up the picks, go to the second door. Pick the first tumbler. Look away and change picks in the inventory (I have mouse wheel bound to my inventory) Picking no longer does anything: there is a green or red flash on the lock pick, but no sound or other action.

A small misfeature in the current dev build (also saw it on dev16325-9462 running the game from a terminal and running a mission causes the console colour to go yellow and stay yellow on exit from the game! The terminal colour changes to yellow a following point in the log: ============= ReloadEngine end =============== Couldn't exec autocommands.cfg - file does not exist. Found 0 new missions and 0 packages. Found 154 mods in the FM folder. [swscaler @ 0x9fd6f80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x9fd6f80] Warning: data is not aligned! This can lead to a speed loss [swscaler @ 0x9fd6e80] deprecated pixel format used, make sure you did set range correctly The text in square brackets is coloured grey, the rest of the text after that is in yellow. Earlier in the log I did notice the following lines which might be relevant: 2 warnings WARNING: terminal type 'xterm-256color' is unknown. terminal support may not work correctly terminal support enabled ( use +set in_tty 0 to disabled ) pid: 54238 Async thread started Clearly this is not an important issue, barely an irritation.

Hunt out the playthroughs by @V-Man339: these are pretty definitive demonstrations of how to ghost on TDM! Don't know about rules though.

Regarding names that don't fit on the loading screen, it would be helpful if the annotation marks (update/translation/new) could be visible even if the whole title isn't visible. I also am surprised that I have quite so many updates marked as available; I'm suspicious that TDM is a bit muddled about the missions I already have downloaded. Is there a good way to check this? For example. I saw Requiem marked as available for update, so I took a copy of my existing fms/requiem directory, let the updater do its thing, and the file dates have changed ... but the .pk4 files are identical (well, at least, their md5sum values agree as bea3c38aa9782d592a055af543c5ecb3). I've also got loads of mission directories with version numbers in their names and an annoying number of duplicates. I'm kind of reluctant to delete the lot and have to re-download 9G of files, but something seems messed up. What's the cleanest way to sort this out?

Can't straightaway say I'm a huge fan of the new bright outline around frobbable objects instead of the older highlight mechanism which seems a little more subtle; can I switch between how frobbability is shown?

My apologies