Jump to content
The Dark Mod Forums

Baal

Member
  • Posts

    1180
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by Baal

  1. Does this help?
    I was asking out of curiousity mainly but, yes, thank you.

     

    you can't drop things into a static bucket, since the bucket model is also used as a movable and thus has a collision mesh which blocks the top
    But you could disable the model with "noclipmodel" on a static bucket, right? And there's also the "clipmodel" key through wich you can assign a different cm. And, if I'm correct, that isn't as restricted for non movebales.
  2. I need a bit of clarification on the subject of collision models, clip models, trace models and collision detection. I was browsing the source but that's time consuming and I am now heavily confused. :) So I'll just ask some (hopefully not to stupid) questions.

     

    There are some models that need a collision model to be used as moveables. If a model contains such a collision model is this also used on static objects?

    What kind of control has a mapper over this?

    Do projectiles (arrows) collide with the render model or the collision model?

    What about blocking of AI vision?

     

    SDK related questions:

    There is a so called trace model that's restricted to a few vertices. I guess this is the collision model used on non static objects for efficiency.

    How are clip and trace model actually related?

  3. Well, moving shadows would make a neat prefab. I could give it a shot, moving it with an osscilator?
    I meant scrolling the projected texture (through the material definition, in case you meant something else). The water materials are a good example for this.

     

    The tiling comment was concerning the landscape. It sticks out at least in the screenshot.

  4. Thanks.

     

    The release is not to far away and a lot of things need to be done. What can I do apart from finishing my maps? I know a few things about mapping, programming, scripting (no experience yet but I need to look into it sometime anyway) and the doom engine in general.

  5. The light volume of a point light IS a cube. It projects a texture in all 6 directions and the intensity changes with the distance from the origin (falloff). It's spherical because of this falloff (the texture also affects this) but the affected geometry is determined by the cubic volume.

    Please correct me I'm mistaken somewhere. :)

  6. Demagogue posted a problem with a decal in the "Newbie DarkRadiant Questions" thread. I looked into it and it's a simple error in the mtr file. I can fix stuff like that and it would be much easier if I didn't have to ask a team member to commit something for me. So I would like to become a contributor (or team member).

  7. I thought that the red pointer showed the exact path of the leak.
    It normally does. Did you reload the point file after dmapping again? Or maybe the old one wasn't overwritten for some reason.
  8. Outdoor sections are just big rooms with a special skytexture on the ceiling (a simple case).

    You should start with the interior (which is much more easy if you're new to the engine and editor) and add "outside rooms" later. Don't worry if this explanation is a bit confusing, it all becomes clear with a little experience. :)

  9. If you plan to use it outside under bright light conditions you need a bright display (I think at least 200 cd/m^2).

     

    Netbooks are great only if size and weight are important. They are easy to carry around but don't compare to a cheap notebook performance wise. Some of them have really good battery life time though (4 hours and more). Most notebooks don't reach that.

     

    If you want to use an external monitor on high resolutions the VGA out that all current netbooks have is not optimal. I'm not an expert on this but I know it's something to consider.

    It all depends on what exactly you want to with it.

  10. The treeview selection affects the texture browsers display (only active categories are displayed) and vice versa. I don't want them to communicate directly but through their parent (the material browser widget containing them, not the tree store singleton if I think about it further).

    But I can't get to specific because there's not enough done yet. And I'm still looking through the code to see how things are done.

  11. I intend to do it something like this:

    There's a singleton (material browser or -store) that keeps the tree store and (multiple, so that you can have texture browser and media browser windows) browser widgets. They each contain a treeview and a texture browser in a paned layout (among other things). You can hide one of the two panes or show them both (3 layouts accessible through buttons or maybe tabs).

     

    The widgets need to communicate their input. I could do that through callbacks or maybe call methods on the singleton directly.

×
×
  • Create New...