Search the Community

Correctly me if wrong. Apperantly xdata formatting doesn't work well with the lang references. So this: maps/man2/mission_briefing { "num_pages": "1" "page1_body" : "#str_b1" "" "#str_b2" "" "#str_b3" } Doesn't work. You can only do this: maps/man2/mission_briefing { "num_pages": "1" "page1_body" : "#str_b1" } And then in the lang file you have to add the whole text of page 1 and get newlines via \n etc. So writing a (text only) briefing or readable and after that translating, is probably not something you want to do. I didn't actually test this with readable's, but it seems to me it would have the same limitation.

If it's supposed to be an octagon, I don't think the corners need to be bevelled. Certainly it looks much better to bevel square corners, but the angles of an octagon don't look bad imo. If you want a smooth cylinder though, the default cylinder patch has 16 sides, which looks smooth enough in game. That would be easier than bevelling 8 corners. Speaking of smoothing; I was pleasantly surprised to find that if you make a model in Blender with smooth-shading ticked, then export an ase file, it will retain the smooth shading when imported to darkradiant.

My issue with the Gold filter in HR is that overpowers all colors making the game monochromatic. These artistic liberties work on short games but in long games once the novelty wears down it could make the game feel monotone. Something similar happens in Thief 4. The art director made the textures almost colorless to add a bleak and sad effect to the game, cool but overtime the player might feel the game is dull and boring. Colors not only give look but also feel. Bur regardless. Here's my attempt to Replicate the Gold Filter in Deus Ex Art Director's Cut OFF ON The Directors Cut has this Pinkish Copper Tone: ON

It is not included in the Modpack. It is a little side project, that's all I know today. You know the drill: do what you please with the stuff I release. And if you can make it better or different: do it!

LOL. Recently I have reassessed the infamous "Gold Filter" of DXHR, thanks to enabling it in DC with this: CookiePLMonster/DXHRDC-GFX: A plugin for Deus Ex: Human Revolution Director's Cut, restoring the gold filter, post processing and shading from the original Deus Ex: Human Revolution (github.com) It fixes the lighting system and the bad (really BAD) DC bloom too (you can force the original 2011 one)! And just avoid the SSAO, it's terrible (temporally unstable) in the DC. Without the Gold Filter the game really looks washed out (and see my avatar )

Hey, sorry you had trouble. You need to find several of the glowing white mushrooms and put them in the pot. After that you'll be able to carry it around with you.

that´s why i will give you a patchnotes for version 0.0.7.5 (and in a vid you showed so) Okay - if German was maybe only for settings ?! - then it doesn't matter otherwise? Why eliminated? and a 2GB game with no chance to save - looks ambitious to me Of course - the biggest part will be the engine! - but the game itself ? I'm going to take up the challenge and definitely : I'm going to have a lot of fun ( sure : it's not just "girls that want to have fun" ) CU ! Edit (24.04) Ohhh : I see (no save needed)

The Blender export scripts have been updated to work with the new Blender 4.1 series. In this Blender version, they removed "Autosmooth" altogether, along with the corresponding parts of the Python API. This meant that the "Use Autosmooth settings" option had to be removed from the LWO exporter, where it was previously the default setting. The new default is "Full", which smooths the whole mesh, giving similar behaviour to ASE models, although "None" is still an option if you want a completely unsmoothed mesh.

I tried the German translations for fm The Thiefs Den. Doesn't work. When I include the russion translation pack from Darkfate, the original German translations work as well. The translation package from Darkfate adds a lot more files, including the xd and map files.

The translation pack has the german string in the base pack rather than in the fm subfolder. I will fix it in the mission database. Edit: Fixed in the mission db Edit 2: Nope. Not exactly fixed. It seems that lang files in the mission string folder need to be "complete" because they fully override the core strings. If I am correct, this was broken in 2.11 when we permitted in-file overrides of core files in missions. Edit 3: Still broken in 2.10, rolling back to 2.07 Edit 4: Still broken in 2.07. Something has gotta be wrong with the translation specific to this mission. Edit 5: The core mission XD files don't use the strings so nothing happens if the lang files are in the strings/fm subfolder. Probably means that the translation packs "never worked" for many missions unless impacted players sought out special editions of the missions on Tels' server. What a mess. Fuzzy recollection time: I think Tels was trying to push the team to mass convert all missions to move XD data into strings/fm/english.lang but nobody wanted to broach it and even mission authors weren't happy about this way of handling things. If the translation pack takes precedence, the best way forward is to include the converted XD file into it. Testing... Edit 6: Couldn't get the XD update to work, so I decided to checkout Darkfate's version. It works flawlessly. I copied their pack into the standard translation pack and the added string files for the other languages worked as well. Darkfate's packs include map files so I'll need to study whether we can avoid that. Otherwise we are basically doubling our mission db or "damaging" our hosted versions to make them translatable. Since this mission is so small and probably will never be edited again we can probably use darkfate's version as-is.

This might be frowned onto by tdm mappers/veterans, but I find it strange that it's considered ok to use text inside entities, which can then be found inside map files. That in general seems badly organised. Like for example with text decals: https://wiki.thedarkmod.com/index.php?title=Text_Decals_for_Signs_etc.#The_Decal Personally I think xdata could/should be used for all instances of text (except maybe darkmod.txt and subtitles), including readme files and GUI files. Or at least some kind of external text file. Could be something else, but the xdata format seems good and supported. So the sign text prefab could have a default xdata_contents spawnarg instead of gui_parm1 . Edit: Objective description text is also inside an entity inside the map file, but it could just as well be a reference to an xdata file. I posted about this before, here:

This is how i18n typically works in code: Developers write the strings in English (or their native language), but mark all the strings with a function/macro which identifies them for translation. In C++ this might be _("blah") or tr("blah") — something which is short and easy to write. A tool (which may be integrated into the build system), extracts all the strings marked for translation into a big list of translatable strings. This list is then provided to the translators, who do not need to be developers or compile the code themselves. They just create a translation for each listed string and send back a file in the appropriate format (which may or may not be created with the help of translation tools, perhaps with a GUI). At runtime, the code looks up each translatable string, finds the corresponding translated string in the chosen language, and shows the translated version. At no point do developers (who in this case would be mission authors) have to mess around with manually choosing string IDs. All they do is use the appropriate function/macro/syntax to mark particular strings as translatable. String IDs may be used internally but are completely invisible to developers. I suggest that any system that involves instructions like "search the list of known strings for a similar string" or "manually choose a string ID between 20000 and 89999 and then write it as #str_23456" are over-complicated, un-ergonomic and doomed to be largely ignored by mappers.

We get it, you don't like the mission. No need to stamp it into the ground. This is total nonsense. There are much larger missions than this with more story and they get good reviews.

That is one reason. That is 2 more reasons. You'd like a script that, if you had to run it again, would "do the right thing". Unfortunately, that right thing is very hard to program, and needs IMHO to be both bidirectional and with a better method of string version control, to support both the FM author's updates and potentially multiple translators. Yes, another reason. Currently, it is my understanding that updating an FM (from the non-converted copy) and running the conversion script again causes mis-alignment of newly-generated #str values and previous .lang #str values. Another important cause of "nobody is making these language packs" is that Dark Radiant at best tolerates converted FMs. It offers no special translation support, as expressed in this code comment: "...we don't have any support for parsing the mod-specific translation data...." [from DR's DifficultySettingsManager.cpp]. That's where we are now. So officially give up on FM Western translations? Or improve the #str system to make it work for everyone? Or invent a new system? A new system. What would that look like to the FM author? To a non-author translator

Then your experience is different than mine. I just recently downloaded a very old mission, The Outpost, that is listed as having German, French, Italian translations, to test out language capabilities. It was not converted (no "#str" found in .map file). Nor was there a language pack included (at least not from thedarkmod downloader).

As of 09e5ec1cae16b8350097fc97839de64cf96c4e88 I have changed the logic to write spawnargs if EITHER the speaker radii are different from the shader default, OR if there were min/max spawnargs to begin with. Spawnargs will no longer be created (or deleted) as a result of a speaker move, but will appear and change if the speaker is resized, which I assume is closer to the expected behaviour.

If all written strings were kept in XD files, the process would be easier. We shouldn't need map edits for this. The current system makes mission updates a real problem to the point that only long dormant missions are viable for translation.

I agree with your observations. That's the main point: to allow mappers to easily enrich a scene and/or tell little stories through useless objects. Players may or may not pick up an object though, therefore players must be trained (core objects must have default names).

BTW, my concern about #str values is about those distributed in FM-specific .lang files. For standard assets, where the info would be in tdm_base01.pk4/all.lang and its derivative .lang files, I guess that's less of a problem. In that case, maybe, instead of using a #str_<number>, you could use a fixed prefix, like: #str_shouldered_<english_name> or #str_moveable_<english_name> That is, like #str_shouldered_chair A general string like that might be used with multiple different chair models, as you intended. If the author overrode the shouldered name with a non-#str name: #str_shouldered_chair --> cushy chair with clue then any translated general strings would be hidden, and just the English version shown.

I have familiarized myself with DaVinci Resolve. After a short training period, I'm already getting on relatively well. If push comes to shove, I'll use it to create the briefings myself. If I wanted to buy such an editor, I would use Movavi (stumbled over it when looking for Openshot alternatives). I tried the trial version and I got to grips with it straight away. I've never seen anything more intuitive, but that's subjective, of course. Unfortunately, you can only render videos with watermarks with the trial version. https://www.movavi.com/video-editor-plus/

Interesting idea. Not sure about my upcoming time availability to help. A couple of concerns here - - I assume the popup words uses the "Informative Texts" slot, e.g., where you might see "Acquired 80 in Jewels", so it likely wouldn't interfere with that or with already-higher subtitles. - There are indications that #str is becoming unviable in FMs; see my just-posted: https://forums.thedarkmod.com/index.php?/topic/22434-western-language-support-in-2024/

In considering my possible upcoming TDM projects, such as upgrading some fonts to Latin-1 or "TDM Latin", I reviewed the current status of support for European Latin-based languages. Basically, for FMs, the translation system has fallen into disrepair and disuse (or perhaps kicked into the grave). Neither "converted" (i.e., #str using) FMs nor Language Packs are now being maintained and distributed by thedarkmod.com. As to other sites, for Cyrillic/Russian, DarkFate provides such resources. Are there any such sites in native Western European tongues, say, German, French, Italian, that likewise offer translated TDM FMs? So, turning back to thedarkmod.com, questions - - is Western Language support (outside the main menu system) officially dead? - if so, maybe it's time to stop pretending otherwise. - if not, should the converted #str system be revived, with better infrastructure? - or an alternative translation system be devised... if so, what? I'm just trying to identify work worth doing. (I started to draft a doc with a litany of problems with Western language support, and possible sub-projects to address them, but TL;DR. And really, not pertinent if support is considered dropped.) Thanks for your thoughts.

EDIT - v1.1 can be found a few posts below ------------------------------------------------------------------ Nameless Objects Mod v1.0 Description: this mod adds names to almost all core objects players can grab and hold in their hands. ------------------------------------------------------------------- How to use: As of this moment the Mod only works if you have "Core Essentials", which is included in TDM Modpack v4.0. Make sure to have "Core Essentials" and then download the *.pk4 attached to this post and place it in your TDM folder. I try my best to provide stuff people can experience first hand to form an opinion. I suggest you try "Business as Usual" by Bikerdude since this mission includes quite a few items you can grab right at the beginning. ------------------------------------------------------------------- Technical: The mod consists in a couple of def files and a script. I had to include two defs because otherwise there can be issues related with inheritance. The script does most of the work and it will run in the background as soon as a mission starts. The script runs once but it takes its time (10 to 30 seconds) not to hinder performance. All this is transparent to you. ------------------------------------------------------------------ Future: I wouldn't like this to remain as a mod and I volunteer to add names to all core defs for 2.13. I would, of course, use the translation system so that names can be translated in the future to languages other than English. I can name all core defs in a couple of rainy mornings but the Development Team must guarantee this work won't go to waste. The idea is that we name all core objects today and we let it stay: nothing changes in the source code and nothing gets displayed on screen. We get stuff done in the background and someday perhaps, all or part of it sees the light in some form. ------------------------------------------------------------------ There are quite a few things that must be discussed and agreed before we get started but the first step is: yes or no. People that might be interested in supporting and helping with this initiative: @datiswous, @Geep. Cheers! z_nameless_objects_mod_v1.0.pk4

To my surprise, i have a new update on the project! Its a big update with many new contents! Please take a look, its a glorious new update. p.s I am still working on stableizing the AI, it has alot of issues currently https://filly-the-owl.itch.io/project-thf-alpha

In post https://forums.thedarkmod.com/index.php?/profile/254-orbweaver/&status=3994&type=status @nbohr1more found out what the Fixup Map functionality is for. But what does it actually do? Does it search for def references (to core?) that don't excist anymore and then link them to defs with the same name elswhere? Also I would recommend to change the name into something better understood what it is for. Fixup map could mean anything. And it should be documented in the wiki.