Jump to content

mgries

Member
  • Content Count

    107
  • Joined

  • Last visited

Community Reputation

29 Great

1 Follower

About mgries

  • Rank
    Journeyman

Personal Information

  • Occupation
    Architect
  • Location
    Santa Barbara, California, USA

Recent Profile Visitors

941 profile views
  1. Is it a known issue that hidden line sketch mode (I'm using Section viewports in this case), produces seriously unstable results? I've run into a few different ways it fails to draw the expected result: The most common issue is that it displays everything in the view, but sketch mode does not appear to be activated. In some cases, the line work initially displays in sketch mode, but then after drawing annotation in the viewport, sketch gets deactivated. To be clear, sketch is still checked off as the desired render option, but the viewport behaves as if it's been turned off. Other times, all of the lines "beyond cut plane" simply don't display at all. Silver lining here is that for whatever reason, this seems to reactivate sketch mode for the cut plane elements and the annotation. There's also cases where the model line work maintains sketch display, but the annotative layer displays without sketch. I've also gotten the reverse situation, where only the annotation was displaying in sketch! It's really all over the map. There does seem to be one way to control this situation (at least it's worked so far). I discovered that by setting the line style of objects beyond cut plane to "use original" in the advanced properties, I can stabilize the sketch render setting, and both model and annotation maintain the correct display. When this is overwritten with a single class, all bets are off. Unfortunately, using the original line style of each modeling object requires a lot more work than being able to quickly set all lines to the same weight. So this is an unfortunate work around to have to accept. Thanks, Matt
  2. mgries

    Barn Door

    This is a great tool @sbarrett! The major drawback, unfortunately, is that there's no way to style the door. What happens when you move this into design development, and need to represent the door as a specific style? Would it be too much to add a few simple style options to this tool? Thanks, Matt
  3. mgries

    Isolate Object command

    I saw this thread, and didn't know about this command. I went to add it to my workspace, but I don't see it! Is the name of the command something other than "Hide Objects"?
  4. mgries

    Planar Boolean from two lists of objects

    @sbarrett, could this be reworked so that the "A" polygons were on one design layer named "A", and the "B" polygons were a second design layer named "B", and then the resultant geometry gets placed on a 3rd layer? I'm thinking about how this may be applicable to creating and defining exst/demo/new surface areas on a site plan. Thanks, Matt
  5. mgries

    Automated Layout

    You were right, my spaces didn't have room numbers. After assigning room numbers, separate sheets are being created from the script. I'm getting closer to the goal! I wish I understood this whole marionette business better...i definitely need to watch some tutorials. It doesn't help that I also don't know anything about scripting. I'm still unable to correctly control layer visibility in the 1:50 viewport. When I uncheck "show all layers", it still turns on multiple layers (just not all of them). How do I make sure only the layer that the space belongs to is visible in the viewport? Also, would this marionette work equally well with Detail Viewports? Could it be configured so that the bounding box was turned into a Detail Callout Marker? If that could be achieved, this marionette would be perfect for generating Enlarged Plans.
  6. mgries

    Automated Layout

    Thanks Dom, Yeah, looks like all my handles are the same (or at least most of them). In your file, they're all different. How do I create unique layer output handles for each space?
  7. mgries

    Automated Layout

    Hi Dom, I tried this out on one of my files, and changed the criteria of the first node accordingly. When I run the script, ALL the viewports of the spaces show up on a single sheet layer, stacked on to of each other, instead of being distributed among multiple sheets. Also, ALL the design layers are on in all the space viewports. For the overall plan (reference) viewport, the correct design layer (only) is displayed. Any clue what's going on? Matt
  8. I like how this method ensures that the benchmark gridline updates with any changes to story/level data. That's pretty smart. Regarding issue with graphics, it's already very easy to apply the benchmark elevation tool directly to the annotative layer of the Section viewport. Why not just have the grid datum slab in the model w/o the anno, and apply the anno in the viewports as necessary? This carries with it the same benefit as with the data tag trick. You get to put the tag wherever it's needed. If you put it in the model, it's stuck in one location, and is only really useful for the full view drawings. You'll have to re-annotate your benchmarks for any enlarged or partial (cropped) drawings. matt
  9. what I really love about this (in addition to providing gridlines for sections and elevations) is that it solves the problem of noting gridlines in enlarged drawings. Currently, we create 4 extra viewports (surrounding the main enlarged plan viewport) as a way to pull the grid tags in close to the cropped drawing area. This can really save some time!
  10. This is FANTASTIC! It works! I'm calling this the gridtangle tool! one question, what extra "enhancements" are you getting from classing the horizontal and vertical gridlines? Is this so you can prevent a horizontal line from appearing in the section cut if you crop above or below the extent of the gridtangle?
  11. mgries

    Hide Classes Within Layers

    there are a lot of changes to 2019 that will most definitely make you have to start your table all over again.
  12. mgries

    Hide Classes Within Layers

    Yes, i agree with your assessment of top-plan view. It seems like it might be slowly going away. Looking at the advancements to symbols in 2019 (2D views), including more control using detail levels, it's more about individual elements having their own planar display settings, which could be paving the way to eliminating a global top/plan paradigm in favor of a 3D model paradigm (w/ object based 2D view overrides). AutoCAD was more like this, and I must admit that customizing display properties for every little thing was quite overwhelming
  13. mgries

    Default drawing label tool

    wow...feeling pretty dumb about now. yes, that was the issue thanks!
  14. @Pat Stanford, you can add =AREA to this list! After reporting my bug, tech wrote back to let me know they're on the case. They also offered a few alternatives to try, one of which was "=AREA". Works like a charm!
  15. mgries

    Default drawing label tool

    I know this is a bit of a tangent, but I'm having problems in 2019 with my drawing label, and can't find any thread on the forum directly discussing it. My drawing labels aren't synching to the viewport OIP fields anymore. I have to go into the annotative layer and edit the information directly. This is occurring on viewports where the drawing label is created automatically, which prior to 2019, always synched up with the Drawing Title and Drawing Number OIP fields. Is anyone else experiencing this? thanks! Matt

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×