Jump to content
The Dark Mod Forums

Search the Community

Searched results for '/tags/forums/system/' or tags 'forums/system/q=/tags/forums/system/&'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. jaxa

    2016+ CPU/GPU News

    Yeah no lol. It's all getting sucked in by the AI industry. How much does 24 GB of HBM cost anyway? It could be $600 or something. Which doesn't sound like much when you consider the MSRP of an RTX 4090 but they are making a killing with those marginz. Well, I've just managed to upgrade to an i3-10105 system, possibility of future GPU upgrade (need to look for low profile), for $75. And I'm sticking in 64 GB of RAM that I happened to have lying around. This is likely to be my new TDM system if everything works properly. And I bought not one but two of these things with the other destined for media duty. I stuck the 8 GB from one in the other one. I guess I could end up putting an 11th gen Rocket Lake chip in it, but I'm in no particular hurry to do that. INB4 I'm an unironic buyer of the RTX 3050 6 GB.
  2. Is it already possible to pass information from the briefing to the mission? I don't think I ever saw this implemented apart from the starter-location selection. TDM is currelently in early dev, maybe a bit soon to start implementing in missions? I think it's better to wait for beta, so no changes will be done to the system.
  3. There's been talk over the years on how we could improve texture quality, often to no avail as it requires new high-resolution replacements that need to be created and will look different and add a strain on system resources. The sharpness post-process filter was supposed to improve that, but even with it you see ugly blurry pixels on any nearby surface. Yet there is a way, a highly efficient technique used by some engines in the 90's notably the first Unreal engine, and as it did wonders then it can still do so today: Detail textures. Base concept: You have a grayscale pattern for various surfaces, such as metal scratches or the waves of polished wood or the stucco of a rough rock, usually only a few highly generic patterns are needed. Each pattern is overlayed on top of corresponding textures several times, every iteration at a smaller... as with model LOD smaller iterations fade with camera distance as to not waste resources, the closer you get the more detail you see. This does wonders in making any texture look much sharper without changing the resolution of the original image, and because the final mixture is unique you don't perceive any repetitiveness! Here's a good resource from UE5 which seems to support them to this day: https://dev.epicgames.com/documentation/en-us/unreal-engine/adding-detail-textures-to-unreal-engine-materials Who else agrees this is something we can use and would greatly improve graphical fidelity? No one's ever going to replace every texture with a higher resolution version in vanilla TDM; Without this technique we'll always be stuck with early 2000's graphics, with it we have a magic way of making it look close to AAA games today! Imagine being able to see all those fine scratches on a guard's helmet as light shines on it, the thousands of little holes on a brick, the waves of wood as you lean into a table... all without even losing much performance nor a considerable increase in the size of game data. It's like the best deal one could hope for! The idTech 4 material system should already have what we need, namely the ability to mix any textures at independent sizes; Unlike the old days when only a diffuse texture was used, the pattern would now need to be applied to both albedo / specular / normal maps, to my knowledge there are shader keywords to combine each. Needless to say it would require editing every single material to specify its detail texture with a base scale and rotation: It would be painful but doable with a text injection script... I made a bash script to add cubemap reflections once, if it were worth it I could try adapting it to inject the base notation for details. A few changes will be needed of course: Details must be controlled by a main menu setting activating this system and specifying the level of detail, materials properties can't be controlled by cvars. Ultimately we may need to overlay them in realtime, rather than permanently modifying every material at load time which may have a bigger performance impact; We want each iteration to fade with distance and only appear a certain length from the camera, the effect will cause per-pixel lighting to have to render more detail per light - surface interaction so we'll need to control the pixel density.
  4. AHA, you're indeed correct! Changing the skin names so they start with "a1"' did the trick! This was actually a successful experiment I was trying out! The wiki goes into some detail about making "general skins" that can affect all models. My hope was that, if I made two models using the same skins, then I could just write a single skin file that would change all of them! For example, since "Straight Frame" and "V-Frame" models both use plaster_01 as their main background... ...all I have to do is make a general skin to change that specific plaster texture... ...and then any of the "V-Frame" and "Straight Frame" models can have different backgrounds! It's not a perfect system, as some skins just don't contrast well with the wooden beams, but I should still be able to get a LOT more out of my models now!
  5. Yes. Sure, I will change it, but I do mind. In addition to changing the forum title, I have also had the name of the pk4 changed in the mission downloader and the thiefguild.com site’s named changed. It's not just some "joke". The forum post and thread are intended to be a natural extension of the mission’s story, a concept that is already SUPER derivative of almost any haunted media story or most vaguely creepy things written on the internet in the past 10 or 15 years. Given your familiarity with myhouse.wad, you also can clearly engage with something like that on some conceptual level. Just not here on our forums? We can host several unhinged racist tirades in the off-topic section but can’t handle creepypasta without including an advisory the monsters aren’t actually under the bed? (Are they though?) I am also trying to keep an open mind, but I am not really feeling your implication that using a missing person as a framing of a work of fiction is somehow disrespectful to people who are actually gone. I have no idea as even a mediocre creative person what to say to that or why I need to be responsible for making sure nobody potentially believes some creative work I am involved in, or how that is even achievable in the first place. Anyway, apologies for the bummer. That part wasn’t intentional. I am still here. I will also clarify that while I love the game, I never got the biggest house in animal crossing either. In the end Tom Nook took even my last shiny coin.
  6. I have updated my Refont program, to now have a function that can analyze a font DAT file for missing or problematic characters. As part of a broader inquiry, I've just applied that program, individually, to all current 'english' font DAT files. I'm reporting the overall results here. I'm sure this will not be a surprise to some of you, but may be to others. Background As you know, TDM fonts are based a bitmap system, derived from 256-character code pages, of which "English" and "Russian" are currently supported. "English" is actually Latin-1, with additional characters to cover more European languages in a single codepage. This is (in theory) quite good for major European languages, less so for less-prominent ones. For each font, bitmaps are distributed in 3 sizes (12, 24, 48 pt), with the engine doing interpolation scaling. Current Font Findings 12-pt Size for All Fonts Only ASCII (i.e., lower range 0-127) characters are provided, no European. For some fonts (stone, mason, mason_glow), the 12-pt DAT is not distributed, so the engine will substitute a larger size, which typically has better Latin-1 coverage. For Fonts Used in Main Menus, HUD, or Subtitles The numbers shown approximate the number of "characters needing work" Fontname Size-24 Size-48 carleton 20 16 carleton_condensed 20 35 mason -- 33 Since 24 pt is not distributed, engine uses 48 pt. stone 30 83 For Additional Fonts Used in FM Readables, Etc. Except for one font (treasure_map), all the remaining fonts are ASCII-only, i.e., no characters in the upper range. In the lower range, routinely the 24 and 48 pt sizes have equivalent coverage. Most of these fonts are fully or nearly complete, while some neglect certain punctuation symbols. The worst is "everette", with 24 "needing work" characters. Further details are here:
  7. I wrote earlier that I owe this masterpiece a review, so... Here is my detailed review of this groundbreaking and seminal Mission Fan. SPOILERS ABOUND ! TDM PLAYER BEWARE, YOU'RE IN FOR SPOILERS AND MAYBE EVEN A SCARE ! This mission... subverted my expectations. Starting with the briefing video. Not since the days of Sergio Leone's Spaghetti Westerns have I seen such daring subversion right at the start. You're expecting one thing... then, bam ! I tried everything to infiltrate the mansion from the outside ! No luck ! Well and truly, expectations subverted ! NPC dialogue heard from the inside... stellar ! Brought a tear to my eye. Or was it just one of the raindrops that fell on my head ? What else brought a tear to my eye ? The senselessly slaughtered guard at the courtyard ! Clearly, a cautionary story that he who grabs a sword... and yet, forgets to dim his lantern, the fool... shall die by someone's sword or arrow. Figures ! That you hid the masterful sidequest of collecting the pennies-for-a-thought from the rather racy fountain, in order to later thoughtfully redistribute them to the poor and hungry street urchins of Bridgeport, is nothing short of design brilliance worthy of at least a two hours long, detailed GDC lecture. I'd watch such a lecture on a loop, 24 hours a day, twelve times a day. Brilliant stuff ! Ah, the side-yard, with steps and a basement entrance that looked and felt straight out of Thief II's opening mission, Running Interference... Could the cunning TDM homages to the classics get any better ?! Could they ? Well, soon enough, I discovered that, yes, they could get even better ! There was an even more amazing homage that I didn't expect ! Read on to find out what... The chefpick was... indescribably cool. I now yearn for it to be included in every single FM. The classic lockpicks feel completely passé. I knocked out both NPCs and... what is this unexpected social commentary ?! The knocked-out have names ?! I applaud your deeply incisive observation, worthy of a skilled chef with a kitchen knife, that the NPCs in games are not mere fictional constructs, but fictional beings with names, hearts and souls ! I confess, upon this moving revelation, I started shedding tears so uncontrollably, I nearly had to quit playing the mission. Yet, I pressed on, heartened and refreshed by such displays of humanity in a work of stealthy interactive fiction ! The commentary was no less subtle and stealthy, I tell you ! As subtle as the protagonist's gritty, grounded accent ! Two different entrances into the local vent system... I... I can't even... So many possible routes of entry. Truly, in the grand tradition of the TDM immersive sim design philosophy ! The choice of giving the intrepid protagonist a temporary rat companion, bribable by cheese, who fetches priceless hidden loot, was equal parts innovative and a hard-hitting social commentary on the abuse of animals for theft and burglary, and people "ratting out" their fellow tenants by revealing the hiding places of their priceless belongings ! I was deeply impressed ! I was thoroughly amazed ! You even had my 'stalgia sense tingling ! Why ? That minor element of your FM even reminded me of the old but gold Thief II FM campaign The Flying Age: The Abominable Flying Machines of Dr. Zeppelinger, where you escape a prison cell by giving a mouse a bit of cheese you've managed to find, and the mouse then provides you with a means of escape. I have scarcely ever seen such a wonderful duo of homages to other past LGS missions and fan missions ! Of course, the shocking revelation with the undead in the freezer was an even more biting commentary on the undead precariat of today, and their ruthless and dehumanizing exploitation by The Man, maaan, the snobby culinary establishment. Undeadkind merely want to roam their abandoned tombs and catacombs in peace (pieces ?) and get a bite or two out of a stray vagrant or drunk guard every now and then, no big deal. Society needs to be more charitable to undeadkind ! And you've even included a gas arrow up in the rafters ! You well and truly know your audience, as I'm an old, die-hard gas arrow collecting enthusiast. I am a sophisticated, yet simple man: I see a gas arrow in Thief or The Dark Mod, I immediately grab it, owing to its rarity. Thank you for such generous mission design. To cut a long story short, I have had a thorough, engrossing and moving cultural experience with this short-but-dazzling mission ! In the shadowed alleys of TDM fan mission sites, I have crossed paths with missions that were ruthlessly difficult and confounding, yet rewarding, but never have I played a mission this... authentic... avantgarde... thought-provoking... It even made me feel hungry ! Riveting, simply riveting. Like working on the skeleton of a 1930s Art Deco skyscraper. Ultimate verdict: 22 frommages out of 20, with a happy cheese-filled rat as the cherry on the top. (But what kind of frommage ? Cheddar ? Swiss cheese ? Gouda ?! I dunno. Don't have a cheesemaking degree.) In other words, I cannot rate this mission other than with the Chef Excellence Award for... Excellence ! *chef's kiss* Le Mission Légendaire Magnifique ! Roll over, Requiem ! Roll over, Crucible of Omens ! Roll over, Iris ! This, this... is the pinnacle TDM fan mission of all time.
  8. Also don't forget if you use the location system it makes it easy to add EAX as well (especially using the presets): https://wiki.thedarkmod.com/index.php?title=Setting_Reverb_Data_of_Rooms_(EAX)#Locations
  9. I've seen fun workarounds like that in other game modding as well. Years ago, maybe even a decade, some fella who was making a mod for Mount & Blade over at the Taleworlds forums revealed that he put invisible human NPCs on the backs of regular horse NPCs, then put the horse NPCs inside a horse corral he built for one of his mod's locations/scenes and then did some minor scripting, so the horses with invisible riders would wander around the corral. The end result was that it looked they're doing this of their own will, rather than an NPC rider being scripted to ride around the corral slowly. Necessity is the mother of invention. I don't know about the newest Mount & Blade game, but the first generation ones (2008-2022) apparently had some sort of hardcoded issue back in the earlier years, where if you left a horse NPC without a rider in its saddle, the horses would just stand around and wait and you couldn't get them to move around. Placing an invisible rider in their saddles suddenly made it viable again, at least for background scenes, of riderless horses wandering around, for added atmosphere. First generation M&B presumed you'd mostly be seeing horses in movement with riders, and the only horses-wandering-loosely animations and scripting were done for situations when the rider was knocked off their horse or dismounted in the middle of a battle. Hence the really odd workarounds. So, an invisible NPC trick might not be out of the question in TDM, even though you could probably still bump into it, despite its invisibility.
  10. I plan to gradually try out all or most of the different path node types and adjust them depending on the interaction. Though I don't plan to use it in this particular mission, I have a keen interest in the follow type, as I'll want an NPC to follow the player character in another, future FM I'd like to create. Never too soon to try out various functions while I'm already learning new FM-building skins after a long hiatus. Thank you for the suggestion. I completely forgot about the location system ambients as an option ! A few years back, when I was testing various stuff in DR, I did actually use that approach instead, once or twice. I haven't used DR much in recent years, so I eventually forgot about setting it up that way. Acknowledged, and I'll look into it. It'll save a lot of time concerning the audio side of the mission. My first few missions won't have much a natural environment, they'll largelly be small and focused on buildings or urban spaces, so I won't need to bother with detailed audio for rivers yet. I have an outdoor FM planned for later (it's in the pre-production phase), and I'll have a good reason to study it in greater detail. It's actually okay, I don't reallt need rectangular speakers. Given that I've been reminded I can set a main ambience for each room - something I did know before, but forgot, after not working properly with DR these past few years - I'll do just that, and use the speakers for more secondary ambience concerns. Handy indeed. A rectangular shape would be easier to remember. I'll just use the filters in the editor to put away the speakers if I ever the get the impression they're blocking my view. Also, I don't actually mind the shape all that much. As you and the others say, the size/radius of the speaker is the actual key aspect. I'm a bit disappointed it's seemingly not possible to resize speakers the same way you can resize brushes or certain models, though you can still tweak the radius numerically, manually. As long as I can work with that, the actual shape of a speaker isn't really important. My main concern is expanding the minimum and maximum radius areas to an extent where they'll be audible for most for all of the respective areas the player will visit, rather than fading away quickly once the player leaves the hub of the speaker behind. As was already said above, I'll use the different utility to set the main ambient for the individual rooms, rather than a manually placed speaker, and I'll reserve the speakers for additional sound effects or more local ambience. I've already added some extra parameters to the speakers I'm testing out in my FM, so I'll take a look at those soon, though I'll deal with the main room ambience settings first. I'd like to thank everyone for their replies. While I'm not surprised by the answers, I'm now more confident in working with the path node and speaker entities. On an unrelated sidenote to all of this, the same in-development FM where I'm testing the speaker placement and range was tested yesterday for whether an NPC AI can walk from the ground floor all the way to the topmost floor, without issues. Thankfully, there have been no issues at all, and the test subject - a female mage, whom I won't use in the completed FM, sadly - did a successful first ascent of the tower-like building that'll serve as the main setting. (That's all your getting from me for now, concerning the FM contents.)
  11. Why do you want a square visualization for sounds? If is because you are afraid, that because of the fact the sound shape goes through walls, in a squared like room, that sound may go as well, then don't be, afaik unless there's zero portals in a scene, sound will be blocked by "walls" automatically. It uses the portals to know where it can "flow" into other rooms. So only the size not the shape of the visualization, is what matters, like OrbWeaver said, the shape is only a visualization for the inner and outer radius of a sound. In other words the area or "field of influence" of a sound and that "field" afaik, expands equally in a 3D volume, in a sphere like manner (to be more precise two spheres, a smaller inner one and a larger outer one), so a sphere shape, IMO is the best approximation for it. I also assume, a cube would be misleading because on the current system, if the player parked at the corners of the cube, he/she wouldn't hear the sound, thou I never tested it.
  12. If you can do this, I don't know how. But it's something I want as well and was actually going to raise it as a feature request. I think speakers are spherical so they model real sound which radiates from a source outwards. I find this doesn't work so well with some scenarios though: water. For example you want to hear the sound of waves lapping a shoreline or a running water sound for a stream, river or canal. If the shoreline or stream is on the longer side, you have to have a speaker with a huge radius to cover it and the sounds extends too far along perpendicular to the body of water. Or alternatively multiple speakers but then you have to manage overlap and it becomes a pain. wind. Same idea but vertical - if you have a long edge or balcony then you need a large radius speaker to cover it and it might extend too low so you hear wind noises on the ground. @Petike the Taffer If all you want is for a sound to fill a room, just use the location system ambients instead. But you can only have one sound I think, so you couldn't have say your ambient music and also a weather sound at the same time without using a speaker for one of them.
  13. DarkRadiant 3.9.0 is ready for download. What's new: Feature: Add "Show definition" button for the "inherit" spawnarg Improvement: Preserve patch tesselation fixed subdivisions when creating caps Improvement: Add Filters for Location Entities and Player Start Improvement: Support saving entity key/value pairs containing double quotes Improvement: Allow a way to easily see all properties of attached entities Fixed: "Show definition" doesn't work for inherited properties Fixed: Incorrect mouse movement in 3D / 2D views on Plasma Wayland Fixed: Objective Description flumoxed by double-quotes Fixed: Spinboxes in Background Image panel don't work correctly Fixed: Skins defined on modelDefs are ignored Fixed: Crash on activating lighting mode in the Model Chooser Fixed: Can't undo deletion of atdm_conversation_info entity via conversation editor Fixed: 2D views revert to original ortho layout each time running DR. Fixed: WX assertion failure when docking windows on top of the Properties panel on Linux Fixed: Empty rotation when cloning an entity using editor_rotatable and an angle key Fixed: Three-way merge produces duplicate primitives when a func_static is moved Fixed: Renderer crash during three-way map merge Internal: Replace libxml2 with pugixml Internal: Update wxWidgets to 3.2.4 Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.9.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep creating Fan Missions! Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!
  14. Yet another breaking change, I'm afraid: 6346 Sounds have a bunch of parameters: minDistance maxDistance volume shakes soundClass The base value for each parameter is set in sound shader. However, it can be overridden with a different value in spawnargs (e.g. "s_volume" "-10") or in C++ engine code with SetSoundVolume (used extensively for footsteps). Unfortunately, Doom 3 engine has a special case: setting some parameter to zero means it will not override the base value. So there is no way to override sound volume with 0, because setting zero would mean "use value from sound shader", while setting 0.1 or -0.1 would mean "use volume = 0.1 or -0.1". This behavior causes confusion. It is especially bad when volume is set programmatically, because e.g. volume of player footsteps is computed as a sum of many modifiers (run, crouch, creep, in water, etc.) and it is hard to be sure you don't get zero sum in the end. The idea is to fix this mess and add a "don't override" special value in the system. Speaking of spawnargs, it would work like this: "s_volume" "13.4" = override with value 13.4 "s_volume" "0" or "s_volume" "0.0" = override with zero "s_volume" "" (empty string) = don't override Right now there are tons of zero values set in these spawnargs. It is not clear where the author intended to override with zero, and where he wanted to drop inherited override and use base value. I guess for compatibility reasons I'll have to replace spawnargs "s_volume" "0" with "s_volume" "" in all missions.
  15. Ah, pity I wasn't reading the forums back in February. I'm fond of that game, along with Bugbear's other early title, Rally Trophy. I was never too good at FlatOut, but it was always a hoot to play.
  16. Oh wow, that is amazing! It must require a custom script I imagine? Didn't think that was possible even with one and the S/R system, that's very impressive. Definitely curious about a few things: Does it distinguish between collisions with the glass and frame? If the arrow hits a metal part it shouldn't do anything, it should only break if the glass in particular was hit. If the lamp is triggered by a switch, does flipping it no longer turn the light on once it's broken? Can you use a broken skin rather than model? With some lamps it would be easier to only change the skin and replace the glass, of course both should be supported based on what works best for each lamp.
  17. A basic little detail we don't yet have is breakable decorations, I was wondering what is up with that and if maybe we can change it. Mainly thinking of new small decorations: I believe breakable crates or barrels were once experimented with, the entity may still be there but I've never seen them used, maybe someday those can be finished too. Just like metal goblets / plates / vases / bottles you can pick up and throw, it would be nice to have alternatives made of fragile transparent glass. The difference being that when they hit a surface past a certain velocity, they disappear and shatter into glass shards... I believe the fundamental system for this already exists with breakable glass panels? Gameplay wise they'd have a particular property: When they break they should make a louder noise, causing a slightly higher alert that makes AI look there for longer, not as much as the noise arrow but somewhere between it and throwing a conventional object. As a potential penalty, stepping on a small glass breakable should shatter it which is hearable to AI, FM's that use them may encourage being a bit extra careful where you're going.
  18. I was confused by this as well when I first started learning DR, the user guide is now slightly out of date. Dark Radiant now uses a modular system that you can freely rearrange and add elements to as you see fit. In your screenshot you can see the buttons to add new cameras and orthoviews, which you can move or resize like a browser window. You can do the same with the UI that contains things like the media and entities tab and even drag them out into their own separate UI element if need be. With a little tweaking you should be able to approximate the Doom 3 editor layout by hand. Hope this helps!
  19. It's okay! I'm down with any option hence why I asked. But I agree: Most players would likely not approve of such a change being done retroactively and affecting all old FM's, so it would likely be best as a derivative entity for mappers to use in the future based on new or existing lamps that can provide one. In any case it would likely require engine changes, not something you can currently do with a script: Lights already use their own hardcoded script classname which can't be overridden. Even if it weren't for that I don't think there's a way to intercept broadhead arrow collisions and check what kind of surface they hit, even with the Stim / Response system. There should probably be two new spawnargs: A breakable boolean enabling the feature on an entity, and a skin_broken to specify the skin used when a light was smashed.
  20. Cannot reproduce on Ubuntu 22.04. Although the Entity List can take a long time to load in a large map (painterswife.pk4) at no point does it lock the system or capture the mouse.
  21. When I open the entitylist DR freezes a while while loading the entitylist. On very large missions this can be very long. At that moment at first it seemed the whole system freezes, but I found that I can still use the rest of the system with the keyboard, but not with the mouse. System: Manjaro Linux xfce Version DR: 3.8 Flatpack install
  22. This is my second time opening Dark Radiant in another computer. When i open it i see this: ( i don't know why the image appears blurry here ) So far i see the Grid and the Camera are not scaling well. Notice that i am using fractional scaling in Ubuntu (Resolution: 2560x1440 - Scale: 150% - Refresh Rate: 165.00 Hz) System info attached system_info.txt
  23. Right now core count is printed by job system, and features are printed by SIMD processing system. From the implementation point, vectorization and multithreading are orthogonal...
  24. dev17008-10685 is available. Speaking of the new parallelization, it would be great to check that the new version does not get slower than the older ones The only different there is number of threads used in jobs system. Previously it was always 2 threads, now it is (NumberOfPhysicalCores - 1). However, detection of physical cores number might be buggy --- the numbers are reported near the beginning of game console.
×
×
  • Create New...