Jump to content
The Dark Mod Forums

Search the Community

Showing results for '/tags/forums/brush/'.

  • 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. If you're using transparent textures, remember they need to be visportaled. A worldspawn brush with transparent textures won't seal. Not sure if this is the cause of the issue you're having, but I remember having trouble with it once.
  2. Yes, I started a new map, made my usual Large brush box (with default lighting/etc.) and saved it. Then loaded the box and imported the original layers. Things are fine with each layer, no internal leaks or external leaks. As I have been proceeding, and adding more structure/areas - each in it's own layer I am only having normal(?) blunders as I am trying to re-learn scripting, DEF's, etc. Can't seem to seal any building with transparent windows, and in one new area DM drops two portals but does not say why (no lin files) and throws another out as useless (inside a non leaky building but separating two rooms). Still have a long to-do list, finish town, visportals, add AI, yadda yadda. BTW I downloaded a free to use 3D cowboy hat but it is in obj format. Imported it in DR how do I orient it/attach to heads? Man, this stuff is time consuming! but loving it.
  3. A@datiswous Ah yeah, well sorry, I was quiet busy and only visiting discord. First time here on the forums since months now I think.. Thank you for the subtitles. I encourage everyone who is interested in using them to download it from here as I'm not sure when I'll be able to implement them myself into the mission. Again, thank you for your work.
  4. Hello TDM crew. I am wondering how to address the situation JackFarmer noted here: JackFarmer question on particle dripping through brush I wish to have a simple drip particle. However the drips fall through brushes and modules. I am not {yet} ready to edit particles. Is there any way to stop particles with a brush or such? Thanks Clint
    1. demagogue
    2. jaxa

      jaxa

      I've found it difficult to find where TDM is listed as #1 on Greenlight. This page ( https://steamcommunity.com/greenlight/ ) has no ranked listing. This one ( https://steamcommunity.com/sharedfiles/filedetails/?id=858048394 ) has no visible rank or stats page. Is it my script blocker?

  5. DarkRadiant 2.14.0 is ready for download. This release focused on DarkRadiant's texturing abilities, the Texture Tool and some of the Surface Inspector algorithms have been completely rewritten. A new model importer UI has been added with the ability to convert FBX models into a format compatible to the game (it can also convert LWO, ASE and OBJ models). The EntityInspector can now deal with more than one selected entities, showing the shared key values in the list. Copy/Paste Textures across angled faces: Texture Tool Rotate Tool (use "R" hotkey to switch) Surface Inspector Harmonise Scale / Linked Scaling Surface Inspector Normalise EntityInspector Multi-Selection Support For more things that have changed or fixed, see the list below. Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/2.14.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! 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. Changes since 2.13.0 Feature: Texture Tool Improvements Feature: Texture Tool: Add Manipulation Panel to shift/scale/rotate selection Feature: Show shared keyvalues when multiple entities are selected Feature: Texture Browser Filter: match multiple words (using 'AND' logic) Feature: Skin Chooser shows materials of the model Feature: Surface Inspector: Add buttons to harmonise Horizontal and Vertical scale values Feature: Improved pasting textures to angled faces sharing an edge Feature: XY view zoom is centered at cursor Feature: Texture Tool: Constrain operations to axes by holding down Shift Feature: Texture Tools: rotate function Feature: Texture Tool: UI contrast Feature: Model Conversion UI Feature: Add FBX model importer Feature: add IQM format support into lib/picomodel Feature: Spawnarg type icon not shown for inherited properties Improvement: New Game Connection GUI Improvement: "Replace Selection with exported Model" preserves spawnargs Improvement: automatically reload exported models Improvement: Search function: don't start searching while still typing Improvement: MediaBrowser toolbar: clear filter text when texture is selected through MMB or Texture Browser Improvement: Merge "Create player start" and "Move player start" options Improvement: Patch Texture Rotation should take aspect ratio into account Improvement: Texture Tool: use aspect ratio of material Improvement: Step-rotating textures through the Surface Inspector should be using the center as pivot Improvement: Surface Inspector: Option to change horizontal and vertical scale values proportionally Improvement: Apply textures to surfaces using "normalized" scaling. Improvement: Normalise button brings texture coordinates closer to 0,0 Improvement: Prevent Texture Tool "face jump" on rescaling textures Improvement: Move modifier hints out of the status bar Improvement: Flip Texture: Prevent huge face UV coordinate translations Improvement: Double click on list elements should auto-close dialogs Improvement: Texture Tool: Select items by clicking the UV space they cover Improvement: Texture Tool: Grid lines are getting too dense when zooming out a lot Improvement: Texture Tool: intercept keystrokes for grid resizing & snap to grid Improvement: Model Exporter: warn if Output Format and extension in File Path don't match Improvement: Change Quake3 map exporter to write "legacy" brush syntax Fixed: Q3 Legacy BrushDef parser sometime produce some wrong texture rotation Fixed: "Replace Selection with exported Model" assigns result to Default layer Fixed: All scene graphs connect to the same undo system, causing interference Fixed: Remove Floating Layout Fixed: EntityInspector allows to set an entity's name to an empty value Fixed: modelDefs folder starts expanded after changing selection Fixed: Particle Editor: wireframe does not render Fixed: Drag-select while in texture tool window gets stuck. Fixed: Some brushes change shape or disappear when rotated or duplicated Fixed: Texture Tool: drag operation doesn't capture the mouse Fixed: Ctrl-S does not work when focus is on inputs Fixed: Autosave filename unhelpfully overwrites 'save copy as' filename Fixed: Merge Maps: can't hide changed entities/primitives Fixed: Merge Maps: can't center orthoview/camera on changed entities Fixed: Merge Maps UI remains if DR is closed while a merge is in progress Fixed: Merge Maps: "Details" text doesn't use full width of window Fixed: Brushes colour schemes not saving Fixed: Fit Texture fields do not allow values below 1.0 Fixed: PatchDefExporter: do not write trailing white space after shader name Fixed: LWO2 Model Exporter doesn't write vertex colours Fixed: Objective components not correctly renumbered after removing a component Fixed: Applying a skin to a model entity no longer works under 2.14pre1 Fixed: Spawnarg types and tooltips not reliably inherited in entityDefs Fixed: Crash when saving map or prefab without a file extension Fixed: Texture Tool crashes when creating a new brush Fixed: "Texture tool" grid cannot decrease under 1 Fixed: Texture Tool: dragged vertices snap to grid even though it's switched off Fixed: Sound chooser not pre-selecting the inherited value of snd_* keys of an entity Fixed: User Guide (Local) doesn't work Fixed: Restore GL_LINEAR_MIPMAP_LINEAR texture filtering Fixed: Objective components not correctly renumbered after removing a component Tweak: Surface Inspector vertical shift / vertical scale arrows Tweak: Surface Inspector's minimum width is too large The list of changes can be found on the our bugtracker changelog. Have fun mapping!
  6. DarkRadiant 3.7.0 is ready for download. What's new: Feature: Skin Editor Improvement: Script Window usability improvements Fixed: Hitting escape while autosaving crashes to desktop Fixed: Def parsing problem in tdm_playertools_lockpicks.def Fixed: DR hangs if selecting a lot of entities with entity list open Fixed: Float Property Editor's entry box is sticking around after selecting a float key Fixed: Spline entities without model spawnarg are unselectable Fixed: Entity window resets interior sizing forcing resize each time it is opened Fixed: Spline curves should not be created with a model spawnarg Fixed: Newly appended curve control vertices aren't shown at first Fixed: Light entities are zoomed out in preview window Fixed: Entity inspector spawnarg fields not always updated by UI windows such as Model Chooser Feature: Skin Editor (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.7.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. 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!
  7. Yes, it does. Which makes it interesting that you yourself explicitly said that it's interesting nobody had complained here on the official forums: I did, which is why it stood out to me so much that even though you yourself had personally been involved you would reply claiming nobody had complained here on the official forums. I'm not colorblind at all. Does that make people pointing out that almost no modern games have proper colorblindness support hyperbole? Just because it doesn't affect you, or you choose not to pay attention to the discussion of something, doesn't make it hyperbole. Pick pretty much any modern FPS and you will find plenty of discussion about the near universal disregard for FOV and camera movement as accessibility issues. Denigrating those as hyperbole because you personally don't feel the affects is as bad of a look as demeaning people who bring up the importance of valid allergen warnings like gluten or colorblindness and deafness support.
  8. I actually had a go at this myself once, but found it far too difficult. Personally I too hate the default input style, particularly the requirement to constantly hold down modifiers just to select things, but changing the defaults just breaks too much stuff because the selection system isn't designed to work that way. In order to allow "normal" selection rules, we would also need: A different method to create a new brush (since left-drag is now a selection or manipulation operation), for example something like Blender's Shift+A shortcut. A different way to resize brushes. Currently dragging anywhere outside the brush performs a resize, but if clicking/dragging on empty space is supposed to define a new selection, this will no longer work. So we would need something like traditional resize handles instead of the planar dragging approach. The selection system to decide what operation is being performed after the initial click or drag starts (as Greebo already mentioned). [Optional but almost certainly necessary] A system for setting up alternative keyboard profiles so people could choose between classic Radiant selection or the new system, since not everybody would agree with the changes.
  9. I think it is a good idea! Our ingame mission downloader and mission view has long been subject of multiple improvement suggestions. Due to the sheer mass of missions that have been released in the last 15 years, things got really cluttered and especially newcomers will have a hard time finding what they want. However, improving the ingame guis is quite a task, so a web-based application might really suit this scenario well. Maybe we could even add a linke to it from our ingame menus, so user can access it quicker. Some more things to think about Would users be able to add custom tags and downvote / upvote certain tags, much like the system of Steam? This would also allow to add tags like "beautiful", or "difficult". Actually, the more users can contribute to this system, the better, because it will be automatically maintained then. The browser should also contain a flag for whether the FM belongs to a connected series of FMs or not and have the capability to go to the previous or next FM in that series. There should also be a flag for fully fledges campaigns. Some might like a flag whether or not an FM is "ghostable".
  10. Ignoring is somewhat inadequate as you still see other members engaging in a discussion with the problematic user, and as Wellingtoncrab says such discussions displace all other content within that channel. Moderation is also imperfect as being unpleasant to engage with is not in itself banworthy, so there is nothing more to do if such people return to their old behaviour after a moderator had a talk with them, except live with it or move away. I'd be more willing to deal with it if it felt like there were more on-topic discussion, i.e. thoughts about recently played fan missions or mappers showcasing their progress, rather than a stream of consciousness about a meta topic that may or not have to do with TDM. I guess the forums already serve the desired purpose, or they just compartmentalise discussions better.
  11. triggerhurt question Hello TDM crew. I am having a bugger of a time trying to get a damage_triggerhurt_5 to do anything. I create a brush, give it trig hurt texture, right-click, convert to entity damage_triggerhurt_5. In sample tests, I make the brush bigger than the player to make sure the player is within the bounds. Nothing. So, I am missing something. Advice? Clint
  12. I investigated some more. I opened the map in D3Edit and looked at the trouble spot. I narrowed it down to at least one brush which appears in D3Edit but not in DarkRadiant. I tried updating my post above with a new image but I think I screwed it up, so here's an imgur link: https://imgur.com/a/Ms4Irv3 You can see in the first image the left camera view is from DarkRadiant showing the missing brush, and the right camera view is D3Edit with the brush selected. Ok, I'm done for now. This looks like a bug, but if anyone has ideas about what I should try then I'm all ears.
  13. Here is the update. HMart; I thought that was the problem, but I searched my drive and found nothing with the same name. But HOW it was loading an older version of the map remains a mystery. And no, there were no lin files being created, or AAS files. Since everything "important" is in it's own level I thought I might just export everything and pull it all into a new map. HOWEVER, after hiding all but default level I remembered this odd looking rectangle brush that went for the lowest to highest point. Had no why idea why I (?) put that there, but deleted it and a few rocks and saved the map. Then for S and grins I reloaded in DM and now every change shows up. YA! BUT, NOW I get dozens of lin files - all on my portals and location items. ALL internal leaks. Dang. Wasn't there a script/tool/method for testing for internal leaks? Anyway, thanks for the help guys! I am plucking away at fixing the >20 leaks (OUCH!) feeling like a numb skull. Still may export it all and restart once cleaned up. BTW I am trying for a mission in Dodge city, Gunsmoke like. Wish I hadn't tossed all my notes (on paper) when it looked like I wasn't going to make 66. (Now 68 and moving on). Thanks again. Oh hey new stuff to put in this dog!
  14. Hey, Every time I've try to use the Full Editor when PM'ing someone, and every single time I get an error. Whoever is in charge of the forum, is it possible that this could be fixed? Thanks Neon
  15. I assume Shift-MMB (PasteTextureProjected) might give you better results, if a brush happens to be nearby. It will do the same projection as Cap texture, but using the given plane of the brush face. The Cap Cycle Texture command is using the fixed X, Y and Z planes for the projection, without the need to read it from a brush face.
  16. I don't recall a system for noise masking. It sounds like it'd be a good idea, but when you get into the details you realize it'd be complicated to implement. It's not only noise that that goes into it, I think. E.g., a high register can cut through even a loud but low register rumble. And it's not like the .wav file even has data on the register of what it's playing. So either you have to add meta-data (which is insane), or you have to have a system to literally check pitch on the .wav data and paramaterize it in time to know when it's going to cut through what other parameters from other sounds. For that matter, it doesn't even have the data on the loudness either, so you'd have to get that off the file too and time the peaks with the "simultaneous" moment at arbitrary places in every other sound file correctly. And then position is going to matter independently for each AI. So it's not like you can have one computation that works the same for all AI. You'd have to compute the masking level for each one, and then you get into the expense you're mentioning. I know there was a long discussion about it in the internal forums, and probably on the public subforums too, but it's been so long ago now I can't even remember the gist of them. Anyway the main issue is I don't know if you'll find a champion that wants to work on it. But if you're really curious to see how it might work, you could always try your hand at coding & implementing it. Nothing beats a good demo to test an idea in action. And there's no better way to learn how to code than a little project like that. I always encourage people to try to implement an idea they have, whether or not it may be a good idea, just because it shows the power of an open source game. We fans can try anything we want and see if it works!
×
×
  • Create New...