Search the Community
Searched results for '/tags/forums/buy a new/' or tags 'forums/buy a new/q=/tags/forums/buy a new/&'.
-
@WellingtoncrabThe download link is no longer functional: "This content is no longer available". Think you can shoot me a new download link for the asset pack?
-
i want to try darkradiant on linux. Not sure how heavy the software is. i don't want to abuse this poor thing Now i am in the process of researching new SSD replacement & GaN charger. i have found a primer on magnetic spinning disk & the underlying technology of solid state drive but i still found it hard to grok the magic behind this technologies cylinder, head and track number.. That's the last thing I heard when I was messing around with the solaris installer
-
Beta Testers Wanted. The Lieutenant 3: Foreign Affairs
Frost_Salamander replied to Frost_Salamander's topic in Fan Missions
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/ -
That's a very valid question. Personally, I'd say the key is to watch what the otherwise-disengaged fringes of the community are saying. If first time posters or long time lurkers start coming out of the woodwork about well made new missions, praising them for their geometry and story but saying that innovative parts of the gameplay felt frustrating or off, that's probably the first sign that the innovations are starting to get out of hand. For a more concrete example, re-read the comments on Hazard Pay. As much as I and many others love that mission, it's clearly a case where the author strayed further than many people were comfortable with. It also points to the likely endgame if authors do take their customization too far. After getting the negative feedback, kingsal made adjustments, and now the mission is much more friendly towards player preferences that don't match the author's original vision. You don't need to restrict the mapmakers' tools to stop them from straying too far from the traditional formula. When people start speaking up, the authors will rein themselves in on their own.
-
Just wanted to say thank you for this install script. Made life easier! I'm new to the dark mod (but not to thief) and have just set up my steam deck to try it whilst away for a few days. Looking forward to some portable sneaking!
- 32 replies
-
- 1
-
-
- steam deck
- steam
- (and 2 more)
-
I hope you didn't forget the (controversial) discussion about his implementation of a Resident Evil style save room in Hazard Pay. Or the change to the arrows, which one head shot zombies. These changes are anything but commonly accepted and wanted. Rather something he implemented, because he thought it was a good idea. Which is fair enough, but, it unfortunately leads to the lack of uniformity that I was talking about, when every FM author thinks he has to reinvent the wheel. Especially new players can't get used to how the game, weapons and enemies behave, if the behavior is different in every FM.
-
I think this is a slippery slope fallacy. Just because the ability to customize exists does not mean most mappers will use it. On the contrary, if one considers the customization that are already available, we see that the overwhelming majority of mappers stick to the defaults. The exceptions are interesting also. Kingsal's the only mapper that readily comes to mind who habitually deviates from presets seemingly just for the sake of being different. However everything they make is clearly in service of cohesive visions. Hazard Pay, no matter how you feel about it, unarguably loses a great deal of its survival horror character if you take away the napalm arrows or the punishing save system. The Voltas don't need to use Thief style elemental crystals in place of TDMs arrow model, but the fact that they are there makes a definite statement about the author's awareness of their inspiration for their work in TDM from the original games, which in turn draws attention to other, subtler creative choices. I think it's also telling that some of kingsal's modifications have been adopted by other authors. As OrbWeaver said, "If the defaults are widely disliked, they should be changed." However, how can the community come to a consensus unless there are maps to showcase the advantages of new innovations? Requesting, or worse requiring, players to go in and manually change settings in order to experience a new mechanic is never going to gain any traction. Certainly it is not worth the effort of creating an entire map built around a new paradigm.
-
As a player, one thing I'm also not too fond of is the lack of uniformity. I think mission authors should take into account that especially players new to the mod want to figure out how the weapons work, and, they will have a hard time doing so, if many missions tweak the weapons. Apart from the "WTF" moment, they will also not know what the default behavior of the weapon is. Also not a fan of some other things some missions introduce, like the different sounds for foot steps etc. Most of them don't improve anything over the default sounds, to be honest. They're rather worse, and irritate me every time I play a mission with custom sounds.
-
Some good news! Tels dug around further in his old computers and found some gold. Namely, a whole fonts directory that includes GIMP .xcf files. Tels says: "The XCF files esp. are what I used to manually draw the new characters (like adding dots to an u to convert it to ü etc.) They contain many layers with different characters, that are layout exactly in the place where they need to be for the patcher script." That is, for english stone 24 pt, one .xcf file contains two independent RGBA bitmap layers, that can be saved separately as two .dds files. A quick glance of that content appears to match the current distributed stone_0_24.dds and stone_1_24.dds. So I won't need to back-convert from DDS to TGA after all. @Amadeus, I think a copy of this should be added to the TDM assets repository. Could you do that? * http://bloodgate.com/mirrors/tdm/pub/scripts/tdm_font_source.7z
-
Do you disagree with the core defaults in general or is this a character-specific setup for your mission? Or is it a test or...? ---------------------------------------------- Sometimes we must take things to the extreme to see the whole picture. Let's pretend all these years mappers have been tweaking the player slightly and depending on the mission: You walk faster or slower. You jump very high or you barely get off the ground. You jump long or fall short. You can mantle high or low. You make more noise or less. The lightgem is more sensitive or less. You inflict or take more damage or less. ... Any thoughts from anyone about this scenario? I wonder how the playerbase would feel. My opinion is that the above tweaks are justified when a different universe is competently established. Or when a new, fully realized character is introduced. Otherwise we are tweaking simply because we can, nothing to do with the story.
-
I created discussion here and mentioned authors (maybe I missed someone though). Unlike the previous thread about main menu GUI overrides, I think the new one does not look aggressive . The main question there is why this was done, and how to adapt to avoid this problem now and in the future. Indeed, all the missions will be fixed by 2.13 even if some authors don't respond. Dev builds regularly break something, although usually it is done unintentionally. I added "known issues" point on the dev build, which happens pretty rarely. I apologize for the negative emotions this change has caused. Sometimes I am too rough in communications. Moreover, I am not a creative kind of person, I'm more a technical type of person. Thus I believe in interface boundaries, so in my mind the blame for breakage is always on the side that violates these boundaries. Anyway, I know I'll have to fix the breakage, probably myself if necessary.
-
I totally agree that players usually don't care whether some non-customizable constant like bow shoot time is same as in core or not, as long as the mission plays well. This is a problem only for TDM development. But I don't know a proper way of solving this: mappers usually want to customize something "right now", and waiting for new release is rarely an option. And often customizations are not implemented until someone really wants them (or right away uses them), so that's also the chicken-and-egg problem here.
-
Good question. Maybe because I don't feel myself too guilty breaking these missions? Maybe because I know that fixing them will be a long story. And I feel confident that we (or more likely I ) will be able to fix all of them by 2.13. You might have noticed that I have also enabled two behavior changes in the latest build (1 2). In these cases it is not even mappers' fault that behavior change is needed. I have a script which can update all missions at once so that they work properly both in 2.12 and dev builds. But somehow I feel I should wait for at least some feedback on the new behavior before doing a massive change to dozens of missions.
-
Innovation is good: someone has a new idea (or need) and executes it to the best of his/her knowledge and ability. When we start borrowing and adopting other people's innovations we are no longer innovating but creating a trend, for better or worse. Stgatilov is touching the tip of this, still small, but growing by the mission iceberg.
-
So because of bugtracker 5600, does that mean that 10 FMs (Written in Stone, Northdale 1 and 2, Volta 2, Hazard Pay, etc.) do not work in this new dev build, and yet, the dev build was released anyway? That's not cool.... The bow is kind of an important gameplay element, especially for Hazard Pay. Why even release this build if it breaks 10 existing FMs?
-
Welp it's about that time again to wheel out The Lieutenant for another mission and I could use some help making sure it's at least somewhat playable. Please register your interest here and I'll start a new beta testing thread soon. Due to custom assets the file size is quite large (about 500 MB). Potato users welcome. Some screenshots:
(-842.41-637_2245.55)(Custom).thumb.jpg.a07bf93584f1c88b9799db87001aec6e.jpg)
(-1347.19-1041.56613.07)(Custom).thumb.jpg.495fc21bd10146821cad5a70f5f6c121.jpg)
(-2574.541001.05252.75)(Custom).thumb.jpg.182adde69de1317bbc9d55154ae5277b.jpg)
(-2101.2-612.24119.33)(Custom).thumb.jpg.4141251a6ab79428c3705c00a87eceec.jpg)
- 14 replies
-
- 11
-
-
I think you need to do things at the exact moment in DR that the user changes a field, so you can capture both the old value and the new value. Would be way better if DR just handled everything natively, but could be done through a hook to an external script too, I suppose. Or some complicated logging.
-
One of the problems with the old #str_number system, that would not be automatically solved in the new #str_phrase system, is lack of versioning/history. For example, suppose in the FM I provide a new string: #str_Mother! which (by magic TBD, ideally in DR) generates this placeholder in all the .lang files: "#str_Mother!" "Mother!" The translator in the fr.lang file later does this: "#str_Mother!" "Mere!" Still later, the FM author revises the string in DR: "str_Mother!!!" In a naive implementation, this breaks the link to the existing translation(s), which becomes orphan in all the .langs, and creates a new entry: "#str_Mother!!!" "Mother!!!" OK, how could we do better? Case 1 (as above): the FM author knows the change is trivial, and so (at revision time in DR) might ask the translations to be retained but marked for review. So maybe the fr.lang files gets: // WAS UNTIL 2025-01-01: "#str_Mother!" "Mere!" "#str_Mother!!!" "Mere!" // Needs minor review with removal of the orphans (after they become comments and moved to before their replacements) Case 2, where the revision is not trivial: the FM author (at revision time in DR) might ask the translations to be replaced by english but marked for review, e.g.: #str_Mother of Pearl! causes the fr.lang files to have (with orphan removal as case 1): // WAS UNTIL 2025-01-01: "#str_Mother!" "Mere!" "#str_Mother of Pearl!" "Mother of Pearl!" // NEEDS REDO Then the translator could eventually fix it: // WAS UNTIL 2025-01-01: "#str_Mother!" "Mere!" "#str_Mother of Pearl!" "Nacre!" // Done 2025-03-14 by Henri
-
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.
-
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
-
Well if you go to the mission downloader again, it will show a new update for the mission, which is the translation pack. If I select Germain language and activate The Outpost, TDM will not start anymore (2.13 dev)
-
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/
-
i am so euphoric to see new FMs keep coming out and I am keen to try it out in my leisure time, then suddenly my PC is spouting a couple of S.M.A.R.T errors...
tbf i cannot afford myself to miss my network emulator image file&progress, important ebooks, hyper-v checkpoint & hyper-v export and the precious thief & TDM gamesaves. Don't fall yourself into & lay your hands on crappy SSD
- Show previous comments 4 more
-
-SNAP- somehow the forum double posted the same message, I think we are in The Twilight Zone of the Internet.
-
@The Black Arrow woah i remember the time when SSD was in its infancy. This took me back to late 2011 to 2013 when the capacity of ssd was extremely small (with the smallest one ranging from 40 to 60Gb) and utterly expensive. It costed an arm and a leg to buy SSD with the capacity of 120GB and above. You would often see big brands like Intel (intel 3xx and 5xx), OCZ and corsair fighting SSD market dominance. On that day, most people on tech forums advised you to put the OS on SSD and leave the HDD as the second storage because there was a notion that ssd is not good for long term data storage. Despite a series of ads showing that ssd makes your system faster, at that time I wasn't interested in upgrading to ssd because win7, 8.1 and early version of windows 10 could run fine on spinning disk. It was not until windows 10 1809/1903 that i felt it had become unusable on spinning disk.
-
anyway thank you for the suggestions. i feel like i have to swallow a bitter truth that SSD sometimes doesn't give you a hint in advance when it's on the way out as opposed to HDD. I've seen the worst with HDD : click of death, rough scratching sound and etc. My anecdote is that even though I didn't see anything suspicious about the s.ma.r.t status through the crystaldiskinfo and hdtune software, the end result is that I still get severe errors suddenly.
I think i have neglected SSD maintenance guide. Yep this is purely my own fault. First, I should reevaluate running multiple hyper-v VMs on SSD. I guess the heavy I/O of the VMs could put a strain to SSD wear leveling. Second, i should closely monitor SSD operating temperature , the third is i should do due dilligence when it comes to buying a good SSD and the last is the importance of having UPS(not because my area often has power outages & power brownout but because the electronics in my house often experience short circuits and tripping the circuit breaker)
-
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/
-
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
(-842.41-637_2245.55)(Custom).jpg.498e8c48b2c8e3b538055e166525da94.jpg)
(-1347.19-1041.56613.07)(Custom).jpg.c866f3cf80cdd0b8ef6cbf8e9e0ede2b.jpg)
(-2574.541001.05252.75)(Custom).jpg.5a85d0a862cf0cb8e67e8eadfab6052a.jpg)
(-2101.2-612.24119.33)(Custom).jpg.59d0a7e8ab87a390b29df31f518dd9e8.jpg)
