Jump to content
The Dark Mod Forums

demagogue

Development Role
  • Posts

    5897
  • Joined

  • Last visited

  • Days Won

    93

demagogue last won the day on February 28

demagogue had the most liked content!

Reputation

1470 Deity

About demagogue

  • Birthday 09/22/1976

Profile Information

  • Gender
    Male
  • Location
    Tokyo
  • Interests
    international law, cognitive science, piano/guitar

Recent Profile Visitors

20470 profile views
  1. One way to do that would be to link the map with the location system. A mapper can already make a system to do that with the location scripts. Basically when the player enters a location (or a set of locations), it can trigger a script that switches out the map for one with that location highlighted. That's how Thief used to do it, and I think it's still fitting with the setting. Having a literal dot moving around the map would be much harder. I'm not sure we could do that without source code support. But It also wouldn't be as fitting to the genre. I'd be happy to see some mappers having a highlighting-map though, just for some interesting variety.
  2. The Thief2 FM "Mission X" was structured like that. But from the perspective of someone making or using a multiplayer system, it should be as general as possible so mappers can make whatever set-up they want for their FM, like that, or leave it open to the players to play it however they want. I think one way for the system to work most basically is have a coop mode (shared objectives, loot, scripts, etc.) and a "thieves vs. guards" mode (separate objectives, tracking loot count & capture count; it should probably be set up like the old Thievery mod) and those are pre-made so a mapper can just turn one on and tweak some things. Those are the two most popular MP cases for this game. But then if they want to, mappers could micromanage the parameters if they want to make their own mode, and the system should facilitate that. That was my thinking. But I think coop is the big one for us, since all of the FMs will already be set up for that, and that's the way I imagine it'd be most used. So that should come first.
  3. Since it's a one-off problem, only for the first ambient at game start, then the way you fixed it is really the right way, because the system-level alternative would be whole a little subsystem (a specialized fidelay and mandatory _z soundshader) just to handle the first 0.1 seconds of game start, and then the old system for all the maps already out there, which is a bit much. And I think it's not even that common because many ambients start quietly to begin with. That said, there might be an easy bit of code that could make sure the fade in always works for the first ambient that doesn't mess with anything else in the system, like a hardcoded initial 0.1 sec. delay only for it, and that may be worth doing. But it'd need experimenting and testing to make sure it works as intended and doesn't have unintended consequences. Anyway, it's good we have this documented for now as the way to fix the problem for other people in the future that run into it searching for a fix. In fact it'd be good to put in the wiki to make sure the fix doesn't get lost.
  4. This is a different issue than the click of sound at the start of every transition that I was talking about in earlier posts that you're referencing. This may be a problem that's always been there but nobody really noticed or commented on it, or maybe only for certain ambients? So the first problem is that the ambient starts abruptly at game start presumably because the sound system isn't online yet to process the fade in, and it just starts the ambient at full sound. So then you added a delay, but since you're not coming off of a previous fade out to sets the volume to zero, it plays the full volume ambient through that delay and then cuts to zero and fades in. My idea is that if you want a fade in from the start, don't start with that ambient as it is. Start with a .1 second of silence, and then fade in the ambient. There are two ways I can think to do that. (There might be other ways.) 1. Some ambient soundshaders start with a "leadin" spawnarg that starts it with a bit of silence, originally used to stop the click of sound (soundshaders ending in "_z", there were two versions, one with and one without the _z, unless that was later changed). You could confirm that the soundshader for that ambient uses a "leadin" arg, or if it does but it's not long enough, maybe use a custom soundshader to use a longer leadin blip of silence. (In that case you'd have to make the longer silence file yourself.) 2. Or another possibly easier way may be to start with an "override" sound, look at the Sound Override part of the tutorial with silence, and then after .1 second or whatever, transition that to the normal location-based ambient according to the instructions, and then the override sound will fade out and yours will fade in. I think you'd do that by setting the override arg to "1" from the start and then change it back to "0" after 0.1 seconds using Target_setKeyVal as the instructions say. Confirm that the "silence" sound is stereo. I noticed if you start it with a non-stereo sound, the system stays non-stereo. I think that was fixed, but good to double check. If it isn't, then you could do the same thing with a normal ambient that just starts off silent or very quiet for that first .1 second.
  5. No I can't see the videos. Put them up on Youtube as non-listed videos. Also, what's your system? Is it a relatively slow or older system? The first time one enters a location, there's some work being done that might be pre-churned from then on, so I think it might have something to do with the work load slowing all kinds of things down, including the ambient going online. If you know your way around DR (or editing the map file directly), you could test things like setting the native volume of the location entity to zero from the start, and see if it happens when other speakers turn on for other reasons the first time, like a trigger. It may be an issue that all speakers face that this system inherits.
  6. Keep in mind we're usually talking about something like a massive forest or mansion or cathedral, etc., where it's absurd to think you're going to cover it very well with a simple circle the radius of the whole area, or even 30 circles for all the different rooms or areas, whereas with the location system, the locations are created out of walls and doorways, so 99% of the time they're exactly overlapping where you want your ambients transitioning on and off.
  7. Bumping this thread. I was trying to parse the code for LibreCoop recently, the multiplayer coop mod for Doom3, or Dhewm3 more exactly. The main alternative is OpenCoop, but I think LibreCoop is more developed. Anyway, it got me thinking how much work would have to go into a coop mod for TDM. It's still my biggest wish item. The idea I got was one has to basically walk system by system through the code and think about the client and server side of packet swapping. TDM has a lot more and more complicated systems than Doom3, but once you start getting a feel for it, I think the basic system doesn't change that much. In a way it reminded me a bit of a pared down save/load system, what you need to update a game state, except you're streaming it in in real game-time, and you using tricks to fill in gaps to ease the load. The other thing I noticed is that maps themselves need their scripts tweaked and anything else happening in the world. But I wonder if there's a way to procedurally do that when a map is loading, so one could just use the FM files as released. It looks like it'd take more than a year or two if one were working steadily through it, although I think one would get efficient at it over time. Like I was noticing, there's a consistent logic to it. But most of all I think it'd be worth it. I really like Thief coop, and I think it'd be great for TDM. I'm just FYI'ing about it now because I was browsing through the other coop mods. Not even soliciting opinions or anything. Just thinking aloud (avisible?) about it.
  8. We had extensive discussion of why our license is the way it is, especially when we were going standalone. There are reasons it's CC-NC-etc., and one of the big ones is that anything that tries to link the mod with money and formalization has been trouble for us, like team-breaking trouble. Well the asset license was settled long before that just in dealing with the contributors (and the engine came with GPL3 from the start of course). There would be asset creators that would (rightfully) riot if money were able to flow to some creators and not to them, because they didn't spend 1000s of hours on this mod for some knucklehead to spend 2 hours for some crap whatever and get paid for it. But the debates happening during the run up to 2.0 validated it. But even before that, we've talked a lot about the basic principles for how the team works, and avoiding entanglements with money and formalization are like two of the central pillars that most of us (I understand) wouldn't like to open back up to debate. What I see from this whole line of discussion is that you want to make a branch project with the engine. That's fair by itself. The engine license let's you do that. But it's something that should be a true branch, like you ought to make your own forum for it and develop it there. Then I think it's fair for you to let us know it's happening and even ask if anyone is interested in joining you there, and some people may want to do that. But I think it's best if you branch off and develop it separate from this forum and team if you're going to drop one of our central organizational pillars in what's gotten us this far.
  9. Our assets are all under CC-NC. If that's not allowed under their system, then it's not allowed. I don't know how it gets around that.
  10. In the early versions there was an initial pop of sound right at the moment of transition, then an immediate drop to zero sound, and then the fade in, or that's what I thought was happening. I never really understood the source of the problem to begin with, I guessed what I said above, and the shader business was a speculation about how to fix it if that really was the problem. I don't recall hearing that kind of pop since like 2010 though. So I figured it fixed itself at some point. It may have been that my laptop at the time was very, very slow, or something like that too.
  11. You can walk through every entity and spawnarg in the set up piece by piece and see if there's a logical problem buried in there. I don't recall how the fade-in works for the initial ambient anymore. It's been too long. But you can experiment to see if it's really borked. But what I came to say is that note there's a Sound Override setting where you can just set up an ambient transition yourself by some trigger if the location transitions aren't working properly for some reason. One thing you might try, if the initial ambient always borks the fade in no matter what you do, is to set a dummy initial sound by immediately triggering the Sound Override as soon as the map starts, like just a quarter second of silence, and then turn the Sound Override off a half second later to have the system immediately transition back into the initial location ambient, and then the fade in should work properly. It's a bit of a hack, but it could fix your problem. You might be able to think of other ways to deal with it along those kinds of lines.
  12. Alright, here is the crash dump, and here's my system info. Hopefully you can let me know if DR is something I can run on this laptop or not.
  13. Thanks. Anyway even the prehistoric version is crashing a lot, so I'm getting the message that it's not worth building on my little travel laptop and I'll stick to my gaming computer. It's not such a big loss. I used to build all the time using a really underpowered laptop, and it's nice sometimes, but I guess the game has evolved past that now.
  14. The new version of DR is crashing on startup, and an older version (2.8), the one I'm trying to update, still opens fine. Do you know of any reason why the new version of DR would crash over older versions and a fix that I might try? Also, I set the initial configuration "mission" slot to a possibly bunk folder, and I wonder if that's contributing to the crash. So I wanted to know how to either reset the initial config window, or anyway where the config file is so I can either delete it or edit it directly. Edit: Okay, I found the config file in ...\AppData\Roaming\DarkRadiant. I deleted it, I redid the initial config & left off the mission info, and it did reset. But that didn't stop the crash on start up. So it must be for some other reason. This laptop uses an Intel graphics card (not a specialized one), so that might be related to the crash too. Anyway if you know how I can stop the crash, let me know, otherwise I'll use the older version. This is a convenient little laptop to build on, even without a graphics card.
×
×
  • Create New...