Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

181 Spectacular


About Taproot

  • Rank

Personal Information

  • Occupation
  • Homepage
  • Hobbies
    Kundalini Yoga, Photography, Outdoorsy Stuff...
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. These all seem to work for me as well.
  2. @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.
  3. @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
  4. This solved my problem as well. Thanks for posting.
  5. 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?
  6. @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.
  7. @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.
  8. @Kennedyme just recently asked me how we set up our classes. This spring I decided to rebuild our office standard around a new system of custom classes. So it's a timely question. I'll offer what I learned in the process, but I encourage others to share their take on this topic to better give new users a range of successful strategies in setting up their office standards. Old Setup Initially I used the 'User 2' standard for class names. It mapped VW's standard class names to a slightly more simplified and user friendly list. The challenge I found was that many of the names were both vague and hard-coded into the tool structure. For example, what is 'Style-1' ? But 'Style-1' was built in to the door and window tool and couldn't be renamed. That put a lot of burden on us to remember OK, 'Style-1' = Exterior Trim. Repeat that scenario throughout the whole class list and it got pretty challenging to keep it all straight. VW has matured and now allows custom naming of classes without creating a new (redundant) class with the original name. It is much easier to work with now. Standard vs. Custom System If you are comfortable using an already existing class organization system, do so ... it will save you a lot of work. Specifically, one of the ones built into VW - as there are enough hidden glitches that you will have to spend some time maintaining a custom system. A custom system allows you to tune the class environment to your way of thinking. Done well, It allows you to preconfigure all of the class attributes in your file so that they are automatically applied and consistent throughout your drawing set. Custom System Tips Create a standardized system that can easily be added to over time. As your drawings develop you'll evolve how you use the software, so leave room for adaptability. I built our system around the CSI Division numbering system. In my way of thinking, classes represent materials. CSI's MasterFormat is the industry standard for material classification, so it fits nicely with material specifications, etc. Most people are already familiar with the material divisions, so it's intuitive for our staff to use Classes can become more specific and detailed over time. The numbering system makes for a concise naming system Attribute mapping makes sense when all objects within the class are the same type of material Rather than include every division, I've just used the divisions that we need. If a specific project requires a unique material, we can add that to the system easily. Make the system easy and intuitive to understand I tried to keep my class naming structure to just 3 layers deep. i.e. ## - ClassName - SubClass Name. Two layers works even better for me. Some firms prefer to abbreviate everything. I prefer names that are ordered, but easy to understand Here's a list of the divisions that I use for my template. Division 0 & 1 are general conditions in MasterFormat. I've used some creative license to re-assign them: Division 00 = Annotations Division 01 = Site Division 02 = Existing Conditions Division 03 -> are conventional categories At the end of the division list, I've assigned an arbitrary Division 50 to be 'Model Specific' items like lights and cameras... The only class that remains unchanged is "NONE". I've capitalized it to make it stand out more. Placement at the end of the list makes it easy to find - rather than somewhere in the middle. Rename Existing Classes I found that the best way to make this class standard work was to start from an already complete template file and rename the existing classes to my new naming standard. For example, I wanted the class "Dimensions" to be '00-Notes-Dimensions' VW allowed me to rename the class and from that point forward objects created with the dimension tool correctly associated with the newly named class. However, If I just created a dimension in an empty file it would automatically create a class named 'Dimension' for it. This applies to things like plug-in objects as well. I found it easier to rename 'Style-1' to what I actually wanted it to be rather than to delete it and reset all of my door and window symbols to a new class. Setup Standard Attributes Under Tools>Organization, you can setup all of the standard attributes for your classes. Class Name Maintenance We have a lot of legacy material (libraries, details, etc) that we need to pull into our current standard from time to time. Since everything is currently organized with a ##-Name structure, the legacy classes all pile up at the bottom of the list. That helps us easily find them and reassign them. We delete the offending class and then in the pop-up re-assign the objects to the correct class. In the meantime, we're going through our old libraries and upgrading them to the new class structure. It's certainly an investment of time up front, but I can already see the benefit in consistency and time savings.
  9. 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.
  10. Wow - that is a significant task. I didn't realize the vehicles were custom built for us. They are very nice. Thank you.
  11. 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) 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. 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. 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
  12. @P Retondo Excellent points. I think this is a persistent theme that (I hope) is reaching a tipping point. The software needs one or more staff members whose sole responsibility is Quality Control and are tasked with going through the existing tools and functions and cleaning out the broken bits.
  13. That got a grin - I'm glad the feedback was useful. Thanks for adding some levity to the forum!
  14. I find myself wondering if the Wish is for an Energos section or a 'Search that works'? Both! I agree with @Patrick Fritsch and have given up on trying to search the board directly ... Google works much better.
  15. This tool is a good example of how polishing up the little everyday items can make a big difference in the user experience.


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.

  • Create New...