Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by Taproot

  1. I can confirm this behavior as well.  It's a bug relative to the "Clerestory" setting.

    In my file, the corner opens up at 4'-6" in height for the window with the Clerestory setting engaged.

    The left window is normal, the right has Clerestory checked. 







    I found this thread to report a different but related problem.

    All of my corner window plan views are rendering incorrectly. 


    The sash / glazing line in 2d extends well past the jamb on the side of the window opposite the corner.

    The following image shows regular corner windows.




    This image shows a plan view with clerestory engaged:




    • Like 1
  2. @MartinBlomberg If no colors are changing, then make sure that the fill in your attribute pallet is set to "solid" for the object (not "none"). 




    @Boh I thought that OpenGL rendering was available for non-renderworks users.  In which case, you would access the rendering mode via the Menu: View>Rendering>OpenGL


    ... after assigning a texture to the object.

  3. @zoomer Sorry to hear that ... but hey that's a pretty good run.  I'm just amazed that the light source is still good after all of those hours.


    1 hour ago, line-weight said:


    This is exactly what I've experienced and one of the reasons I've largely given up on multiple panes. Which version of VW are you on?


    @line-weight We're using VW2020 Designer (latest service pack). 

    Here's what the primary view pane looks like when it starts to go buggy.  Part of the image displays at a different scale.  In this example, I had just one other viewpane open.



  4. @jmanganelli Yes, I'm inclined to spend more on the perfect screen up front.  My 30" cinema display cost A LOT, but it's been going strong for 14 years and has been a great experience, so I'm inclined to go with high quality and less frequent turnover.  The 43-44" size is interesting thought.  I hadn't considered it, but will look into it further.  Beyond that, I think I would be turning my head too much and would be tempted to sit further away (which would defeat the purpose).  I appreciate the feedback.

  5. I was just working on a complicated drawing that necessitated having multiple panes open at once.  The functionality was great!  It took two sections and a plan simultaneously displayed to understand what was going on.  However, I noticed that after a while, the main drawing window didn't refresh correctly and the section displayed disjointed chunks of the image (like a puzzle before it's put together).  We've seen this bug before elsewhere ... while zooming in and out the image draws correctly, but when stopped it blows apart.  Suffice it to say that when I closed the other panes, the main drawing window rendered correctly again.


    We use a two monitor setup (one big, one small) and locate the resource browser on the second monitor as well as our internet browser (which we use a lot during design).  It works well.  


    However, as I mentioned earlier our displays are due for an upgrade.  I looked into the monitor recommended by  @jmanganelli and have concluded that we need more screen area.  It looks to me like the 38" ultrawide monitors offer about the same area as my dual monitors and would have fewer cables, power supplies, etc.  Is anyone using one of those setups and if so could they comment on how they like it?

  6. 2 hours ago, jmanganelli said:

     About 6 months ago I upgraded to two 4K, 32” monitors.


    Which ones did you end up going with?  I'm still using a 30" Apple Cinema Display from umpteen years ago and don't know how much longer it's going to last.


    And to Line Weight's question:  We just use a single pane almost all of the time.  I think it's just habit as we developed our working styles that way ... but it's also due to screen real-estate.  With all of our pallets open the actual work area is not that big and reducing that further with multiple panes start to make it hard to work effectively.

  7. @Donald G. Martin @gester  


    Would you be willing to post a sampling of some of the classes that you use so that we can get a sense of your naming strategy?

    I think the more tangible examples folks have of a system that works, the easier it will be to make one of their own.


    For us, the main obstacle to developing a new set of office class standards was the fear that we didn't know enough and were just going to create a messy confused result.

    Quite the opposite has proven to be true.  We have a few legacy projects in our old class standard and drafting in them feels like molasses compared to our new files.


    That's not to say that we got it perfect the first time.  We are adding a few classes as we go, but the standards are accommodating it well.


    Now that we've converted our legacy libraries to our new standard ... I've definitely learned the value of keeping most symbol geometry in the NONE class and then applying a container class to the whole.  Otherwise, you end up with a whole host of legacy classes with each symbol import. 



    • Like 2
  8. @Boh Yes, I've come around to using page based hatches for different scaled viewports.  That most commonly applies to sections and details.  Formerly, I had two copies of each hatch, so that details displayed an enlarged version.  Now that we're using class attributes for everything, I've found a single (compromise) hatch works pretty well.  It's not quite as good (aesthetically) as it was, but it's fast, consistent and still reads well.


    Have you found a better method?


    I've been enjoying your posts as it seems we're at similar places in our skill development and you're often tackling the same issues I am.  Your solutions are often excellent and save me loads of time in the process.


  9. @E|FA Yes, it's definitely a work around. 


    Adding to your wishlist item.


    The REVISION TOOL default attributes for the cloud won't change and appear to be locked in.  They can only be changed manually for each object after creation.

    Billow Size, Variability & Height settings won't change when using the eyedropper tool to 'set defaults'.

    You can't set a plug-in style for this tool.  Symbols won't work, etc.  That needs to be fixed.


    Similarly, I tried the REDLINE TOOL and Cloud settings can't be specified.  IMHO the default billow size is too large for encircling small to medium sized items.

    The Billow size, variability, etc of the Revision tool should be included in the settings for the Redline tool.


    • Like 3
  10. @EggFarkArch I know this is an old post, but I recently tried to tackle the same issue.  We typically draw clumps of trees and forests on our site plan using the cloud tool.  I ended up creating a custom line which works pretty well.  The arcs don't meet perfectly at vertexes, but it works well enough for our use.  The arcs are mapped to a polygon (polyline), so you can hide or show any of the edges.


    I'll include a file with the "Cloud" style line in case it's useful to anyone.






    Cloud-Custom Line.vwx

    • Like 3
  11. On 3/4/2020 at 3:09 AM, kklik said:

    Had a call back from the service select team and it turns out I was using a legacy "Create Animation" tool.

    When updating annually I kept the same workspace environment, which I had changed to the way I like to work, so the old tool was moved along.

    It was a question of editing the workspace, deleting the old one and dragging across the new tool.

    Problem solved for me


    This solved my problem as well.  Thanks for posting.

  12. I'm trying to picture the circumstance in which you would want to do this.  Typically, I report symbol data to a worksheet, so it is all in one convenient list / report and doesn't clutter up the drawing.  For instance:  A plumbing schedule.  Can you elaborate on what your intended use is?

  13. @E|FA Not quite.  I use the same classes inside and outside of viewports.  The example I gave for the Outline class was just for perimeter emboldening of drawings.

    I use many other classes in viewport annotation as well.


    For Example - Here's a very simple section.




    Classes and attributes follow materials.

    The grade line = 00-2D-Outline

    The elevation markers = 00-Notes-General

    The soil hatch = 03-Soil

    The insulation = 07-Insul Batt

    and so on...


    Incidentally, I really like using keynotes rather than callouts on my plans, elevations and sections.

    I've classed  all of the material behind the section cut to 00-2D-Section Beyond


    The same classes are applied to a detail.




    One of the main advantages to classing by material rather than individual circumstance is that attribute control can be consolidated in one place, rather than scattered about.

    For instance, elements assigned to 03-Concrete like the footings in the detail above have a concrete hatch in 2D, and also have a concrete texture in 3D.  So objects whether 2D or 3D will display correctly.


    This makes even more sense when you start building off of classes into things like wall styles.  I set the components of my walls to use attributes 'by class.' 


    We're discovering as we go, but the further we advance, I can see that the software was intended to be used this way. 

    That said, It does take some persistence to get it all to work.





    • Like 2
  14. @E|FA  We use classes throughout the entire set including viewport annotations.  Notes, dimensions, and even masks and fills (like a soil hatch for sections) are all given attributes by classes.


    There are some tricks to this.  For instance:

    Class:  03-Soil ... We use an earthen hatch that in the hatch settings is set to "page" instead of "world."  That lets us use the same class for soil in a 1:48 scale section as a 1:12 detail and have both results look good.


    Class: 00-Outline ... is a container for manual perimeter outlines of details, sections, elevations, etc.  We have it set to a 0.50 line weight by default, but will manually override the line weight for say an elevation that has multiple layers of depth.  That way we can turn the visibility on and off with one class and don't have to manage 3 or more subclasses for this singular function.


    • Like 2
  15. 43 minutes ago, Kennedyme said:

    @Taproot How do you use Classes? I see this thread is 3 years old. do you things differently now?


    That's a big topic, but a timely one.  This spring I rebuilt our office standards around a new set of classes. 

    But I think that's a great topic for discussion, so rather than add it to this thread about layers, I'll start a new thread on that topic.




  16. Has it really been 12 years since the above post (incredulous voice)?


    I recently needed to revise the plugins that I created from this thread and thought that they might be useful to some of you, so I'm going to include them here.


    These are all point and shoot tools.  Clicking on an object carries out an action.  Listed in order of appearance (icons below)



    1. TA_Set To Active Class - In the event that an object is mis-classed.  This tool lets you click on the object and move it to the active class.
    2. TA_Class Hide - Sometimes a class is in my way and I just want to hide it from view.  Clicking on an object will hide its class.
    3. TA_Activate L+C-Tool - I jump around a lot in the drafting process.  When clicking on an object, this tool makes the active layer and class that of the object.  I've set this one to a standard hot key in the workspace editor (makes it really convenient to use).


    Use at your own risk ... but works fine on my 2020 mac setup and as they are über simple and should work on most any configuration of VW.

    To use:  Download, move into your plugins folder (start or restart VW)  and then add them to your workspace.


    TA_Set To Active Class.vst

    TA_Class Hide.vst

    TA_Activate L+C-Tool.vst

  • Create New...