Jump to content
The Dark Mod Forums

jonri

Member
  • Posts

    71
  • Joined

  • Last visited

  • Days Won

    7

jonri last won the day on October 15

jonri had the most liked content!

Reputation

100 Excellent

Profile Information

  • Gender
    Male
  • Location
    Charlotte, NC

Recent Profile Visitors

852 profile views
  1. The backstory to my still-WIP warehouse FM contains a few loose connections already, so I've decided to flesh it out a little more and turn the story into its own little FM for the challenge. I've given myself a cap on the number of "rooms" to avoid feature creep, and I'm about 80% done with the blockout. Hopefully the deadline will help me push this one over the finish line, plus having a prequel will let me cut back on the intro and readables in the following FM.
  2. @stgatilovI went ahead and updated the related wiki page here. There are a couple of us that I know of developing FMs making use of the feature, and I'm also still planning to put a little tutorial for creating seed maps on the wiki as well. For completeness, can you verify whether the premade maps listed on that wiki page are in the correct format and location?
  3. @MirceaKitsuneto be clear, you can still use vertex color blending to blend two materials and that shouldn't break the other maps, it was just my experimental approach to terrain that did that. And you are correct, it wouldn't be something you could attempt with patches, you'd want to build it all in a 3d modeler.
  4. The term for this is called triplanar mapping. Before getting your hopes up, the answer is no, TDM does not have this capability. That said, I once did an experiment some time ago, I achieved some degree of success but there were some major drawbacks: The features: Using an RGB splatmap, I could paint 3 different textures onto the ground. A 4th texture would automatically be used for vertical areas using triplanar mapping. Where different textures meet, instead of linearly blending them together, they are blended based on heightmap. Lacking actual heightmap data for the textures in use here, I substituted a grayscale map of the texture and still got good results. Why you shouldn't do this: Custom shaders are fun to toy around with, but they're likely to get broken in future releases. There was another thread for discussion of this here. This isn't great for performance, it's a heavy material that will get run on large portions of your screen. All the magic happens by modulating the diffuse texture. You can't have normal or specular maps.
  5. I got a whole lot done on the inside the past week, but decided to switch gears and try my hand at landscaping: SEED seems to do pretty well at scattering grass, but I need to tweak things to get them to floor better. I came up with a nice little trick to draw the image maps SEED can use to spawn entities: 1. Take a screenshot of the top view from DR, and import it into your favorite photo editor 2. Add a new half-transparent layer and draw your image map on top 3. Crop and export your top layer with the right settings, and apply it to your SEED entity
  6. I've taken the poll, but please be aware that after playing with it when it first came out, I've really only gone back to using the connection feature consistently for the past week. I might find other parts more useful later on, but right now for me the biggest advantage is in setting up and tweaking lighting, and adjusting model positioning for player navigation and sight lines. I mostly just turn on "Game position follows DarkRadiant camera" and "Update entities on every change", and only have to toggle them if i restart TDM and need to force it to reconnect.
  7. I threw together a really basic proof-of concept: https://streamable.com/9m9vgd None of the options in the dialog are actually hooked up yet, but it's just a matter of adding the math for them. The actual brush creation seems to be working ok (although I had to get a little creative with the scripting to do it, which I should probably improve in the DR source code itself).
  8. This sounds like something I could knock out in an evening or two using a Python script. I've got no decent blocks of free time at the moment, but if nobody beats me to it I'll give it a go sometime. I've also been thinking of a script that would work something like the blender "array" modifier for easy duplication+offset of your selection, optionally combining the result. That might make the carpet placement a little faster once you drew one step's worth.
  9. I created a script which is now included in DR to detect them so you don't have to run around you map looking for them. There's a little bit of discussion in that thread about the lack of rotation offset being a bug vs feature too.
  10. Confirmed! When you said this, I thought maybe spawning an object too close to the AI might be disrupting it, but it seems to work no matter where I move it. Chalking this one up to the random map gremlins...
  11. I reorganized my modules once, and what I did was just open the .map file in a text editor and use find/replace to swap out the old model path for the new one. Make sure your map isn't open in DR before doing it, and consider making a backup copy as well, but the .map file is just plain text so it should be safe to do it this way.
  12. Here's a weird one. I have an AI on a patrol that was working fine, until I added a hacky little script. I wanted to add shouldBeOn to a candle as the result of trigger, and my solution was to spawn a new identical candle with the additional spawnarg and delete the old one. This all actually works great, the AI will notice and relight the swapped-out candle. The weird part is that if you trigger my replacement script while the AI's sit animation is playing. Then the AI gets stuck sitting and won't get up unless you alert him. I pulled out a simplified section of the map to reproduce the issue. When you start, the lever to trigger the replacement script is behind you. If you do nothing, the AI will leave the candle unlit as expected. If you pull the lever while the AI is walking, he will notice the candle and relight it. And if you pull the lever while the AI is starting to sit, then he gets stuck there forever. Any ideas? buggeroo.zip
  13. Some preliminary results from me: This works great so far on KDE Plasma/Xorg, in addition multi-montiors and alt-tab working as expected I like the ability to resize in windowed mode. I could see that being helpful during mapping. I switched over to the Wayland version of plasma and the mouse is fairly unusable. When you move around on the main menu, it will suddenly jump back to where it was a few moments ago. I'll try to do more investigation as it could very well be plasma's fault. Plasma/wayland still has too many glitches for me to use as my daily driver so I normally stick to Xorg.
  14. @Frost_SalamanderJust started playing this one last night - great job on the intro! Before I got too far into playing it, though, I did remember seeing your comment on collecting things for a future update. I've been noticing a handful of minor geometry issues here and there and I'd be happy to collect them as I play though, if it would be of value to you. Nothing I've seen is super-obvious or gameplay-breaking, but just smaller things I've become accustomed to looking for in my own mapping activities.
  15. I'll give this a go on Arch Linux / KDE late this weekend or early next week. I should be able to try both X and Wayland to see what happens. Having looked at the windowing code once before I like the approach of picking up a library that's built to be good at this. Thanks for taking this on!
×
×
  • Create New...