Jump to content
The Dark Mod Forums

Aosys

Member
  • Posts

    277
  • Joined

  • Days Won

    8

Everything posted by Aosys

  1. Just wanted to say that I too have been diving into the modules, and not only are they a ton of fun to use, they're also an amazing source of inspiration: So thanks for making them!
  2. So I tried my original func_static method and didn't get the same console printout as last time, which is odd. Still no head in-game though. Also tried the atdm:attachment_point_swinging_lod and actually got a full-blown game error (x y z are just the numerical coordinates of the object): Game Error idAnimated 'atdm_attachment_point_swinging_lod_1' at (x y z): cannot find anim 'idle' func_animate produces console printout: WARNING: idAnimated 'func_animate_1' at (x y z): cannot find joint 'origin' for sound playback
  3. I know there's been a lot of talk about lighting recently, and while I know absolutely nothing about how TDM's lighting systems actually work or what's been done technically to tweak them, this video seemed like it might be relevant? It's completely Blender-centric though, but I thought it was an interesting watch:
  4. Bit of an odd question here. Besides the zombie, are there any decapitated AI head models available? The .md5mesh versions just give me an error and don't appear in-game (I'm assuming they're there for internal purposes and can't actually be used as func_statics).
  5. Revisiting an old WIP from 2015, just for fun; I'd forgotten how much I like this elevator
  6. I know I haven't been all that active here lately, especially on the mapping front, but I might be able to lend a hand with readables if you're interested.
  7. I too need to work on lighting, tbh But this bit on level design in Thief Deadly Shadows has a blurb about lighting you might find useful: http://web.archive.org/web/20050306134336/mavra.perilith.com/~faceless/.sux/thief.shtml It's just one of the many interesting Thief-related design docs floating around out there: http://www.ttlg.com/forums/showthread.php?t=129827
  8. @Obsttorte Do I need any special permissions to file a bugtracker? Also, are there any particular conventions I'd need to follow?
  9. Hey all, I'm back with another(!) texture issue. This time around, it's three textures: diamond_pattern_andbars01_lit, diamond_pattern_andbars01_moonlit, and diamond_pattern_andbars01_unlit. All of them appear to be missing a bumpmap. It's written in the .mtr but the actual .tga file isn't present in the folder structure. Can anyone confirm where it went (if in fact it ever existed)?
  10. Speaking of free games, Mass Effect 2 is available "on the house" on Origin right now: https://www.origin.com/usa/en-us/store/mass-effect/mass-effect-2/standard-edition Don't use Origin, so don't know if this is worth it or not... But hey, if it's in my library I guess it could be an option at some point?
  11. I might be able to help - I know my way around texture creation (for the most part), and I've got the Nvidia Normalmap plugin for Photoshop, though that can be a bit hit or miss depending on the texture. Don't know what my schedule will be like once the semester starts though, so no guarantees. Also, I'm still working on those duct modules, if you're still interested.
  12. Just some notes on the bed fix: - The two textures are currently set to noshadows, since that's what the original texture had. If this isn't correct for these particular models, feel free to delete the line in the .mtr - It appears that the .skin also fixes some awning models that used the same fleshy texture before (: - This doesn't replace the old, fleshy skin, it adds two new ones with new materials
  13. Aosys

    Happy Christmas

    Happy Holidays, all! May they be filled with loot and cheer!
  14. Palazzo Valguarnera Gangi, Palermo, Sicily
  15. Wait, so do you NEED UPlay PC to play these games, or just install them? Also, is it normal for only 3 of them to show up in my "Owned Games" when the other page is saying I claimed all 7?
  16. Hey all! Fleshy bed skins have now been fixed (and get a new skin to boot). Now they act and sound like cloth: https://drive.google.com/open?id=0B7b8gaL5s9huZWR1MnVSdGF5Zm8 .mtr definitions are currently geared to my custom textures folder structure; they'll likely have to be adjusted for your own usage.
  17. I found the brown equivalent of that same texture, it is indeed for AI: I was finally able to locate the diffuse and normalmaps (both in completely different .pk4 files) for the cloth_rough_generic01 texture (and found cloth_rough_generic_brown along the way), though I have no idea where the editor images are. Should be easy enough to drum up a custom texture for both, but I've never played around with skins before, so this could get interesting... [Edit] After a brief reenactment of that scene from the Prancing Pony Inn, it would seem that beds/worldspawn with the texture applied do not, in fact, bleed when hit (at least with a sword, I haven't tried arrows but I think the same thing applies).
  18. So, I'm having a bit of a strange issue here. I'd like to insert singlebed1.lwo into my map - in particular, the rough_green version. I can get the model in just fine, and when I jump vertically up and down on top the correct cloth sound plays. When I try to walk or run on the bed, however, it makes squishy mud noises instead. None of the other versions of that model suffer from this problem. Am I going crazy? Is this a bug? Or do the denizens of Bridgeport just really like green waterbeds? [Edit] A bit more experimentation, and I've found that all models using the rough_green texture are like this. I guess there's something wrong with the material definition, I'll see if I can have a poke around and find the problem... [Double Edit] Alright, here's the problem: I'm pretty sure the beds are using the tdm_roughcloth_green texture - which is for ai use if I'm not mistaken. The .mtr is as follows: Basically, right now our beds are making fleshy noises. Any chances of this getting fixed at some point?
  19. Voted, and recruited several votes from friends (:
  20. Sorry for the lack of updates on the duct sections; been a bit busy, but here's what I have now: All of these should snap together seamlessly with Grid4, and I think they just about cover all the base section shapes I could think of people wanting (sans a couple of extra connecting bits I want to make for maximum customization of how sections hook up). Any suggestions/requests for additional shapes? I'm also interested in hearing what kind of detail work people would like to see, and how they'd like it implemented.
  21. I'd say that's a best-case scenario though: wide open spaces mean plenty of room to kite AI around and avoid getting hit. In a full-blown mission things can get more complicated, as areas tend to be (but aren't always!) smaller and populated with architecture/clutter/obstacles, which can skew things in favor of either the AI or the player, depending on the area and how the player can/chooses to utilize it. When it comes to combat, getting backed into a corner or stuck at a dead end usually doesn't end well for me if I've pissed off the local constabulary, so in that case the AI usually have the upper hand - which is fine, since this is basically what you'd expect IRL. Where I really think AI have trouble is when the player can exploit level architecture, monsterclip, and AI pathing in general to get the best of attacking enemies. I know I've been guilty of wedging myself in some awkward corner or small crawlspace, leaning forward, and stabbing away at enemies that I'm just out of reach of.
  22. @Bikerdude Is this looking about right so far? Connecting brackets are still brushes, but actual duct sections are all patches now. These are just base duct sections and connectors, nothing fancy yet.
  23. Happy Halloween, fellow taffers!

    1. demagogue

      demagogue

      Happy Hallowed Evening to you too

    2. Diego

      Diego

      Merry Halloween! Never understood why we don't use merry for halloween

  24. Should probably mention that as I was testing these, I tried stringing a bunch of the sections (converted into individual func_statics) together, and a bunch of the ones at the end became non-solid. I had to merge them all into one big func_static in order to get them to work properly. Is this a bug, or a quirk of the engine I'm not aware of? Also will mention that the dimensions of the working duct are 56 height x 56 width, and at the connecting brackets are 55x55. Any smaller and player pathing becomes borked (not being able to nicely enter the duct without mantling or jumping, even from a flat surface; not being able to get out without mantling or jumping; getting stuck on brackets; etc.).
×
×
  • Create New...