Majic

We see Tags have given to default resources for 2017. Is there a list of these Tag terms available?

Bear, if you find auto-classing useful, but need to turn it off to assign some normally auto-classed objects to another unique class, it is very important, when turning auto-classing back on, to uncheck to option to auto-class existing objects! ...auto-classing was once a useful feature but has not been upgraded to add new auto-classed objects in years, and all the effort spent setting up our custom auto-classes now applies to only a fraction of the classes populating our documents.

+1 for a "renovation filter" Others may do things differently, but my system is as described in the 2013 thread "best practices for a renovation project using stories"...how much repetition/duplication depends on the scope of the renovation and alteration, but yes, the various states need to be represented where appropriate. Classes provide the "filter" in Vectorworks. Assigning all attributes and textures by class optimizes ability to control appearance in SLVPs.

Well, I dunno that I completly agree...the information may better, even "fantastic", but for me the UI has been utterly frustrating. I would prefer to use my iPad Mini to consult the Help topics while I work at my iMac, but can't seem to get the screen gestures to produce the results I expect: a reverse pinch automatically produces a display that is way too large for my screen; and the pinch doesn't just allow an user-adjusted resizing but exits to the 9/12 open tab chooser (or whatever it's called) -- a seamlessly unending Catch-22! The video links don't seem to work under iOS either. On my iMac, under Firefox, I have experienced very long-running rotating squares while I wait for my search results to appear. So I am using Safari now which seems to work somewhat better in that regard, but while I can easily scroll the left hand lists, it is very difficult for me to scroll the right hand topics -- activating the hidden scroll bar. Am I alone in this regard, or what are the tricks?

Jcaia- wonder what are your software and hardware specs. Adding them to your "signature" can be quite helpful in getting answers to your questions. Relevant in my response: because in 2014 I used a clip cube for isolating parts of my 3D model for editing. In 2015 the clip cube doesn't work with my hardware, yes, time for the upgrade with more graphics memory. So, I use a camera to get a wide angle perspective views which works quite well - even better than an elevation view, I think. ...those CA parametric cabinet objects looked pretty good to me.

Sure! Just not from the OIP, which lacks the Pitch field and even a Settings button like Door and Window objects... But, like them, double-clicking the object or right-click>Edit works.

Chris-just now taking the time to respond. I have used the Standard Naming tool/command on occasion. I have found it can be quite powerful in setting-up a project, but for me has proven less useful than it potentially could be, and in need of a major overhaul. Not sure that I understand your question, but will summarize my use of the commands and experience for what it is worth: from the Document Settings>Standard Naming menu, one selects the naming Standard to be used in the current document. Selecting a User-X Standard and clicking on the Details… button, one can customize names of Classes (& attributes), Design Layers and Sheet Layers by selecting the appropriate tabs and editing the desired fields. To actually access and include Standard Name Design Layers and Sheet Layers in a document, one must first establish a story structure. Then using the Document Settings>Create Standard Viewports menu (CSVPs), one selects the desired drawings for the project. When the command executes, Design Layers, Sheet Layers with SLVPs, and Classes are automatically created. The SLVP visibility settings are even appropriately set for Layers and Classes, i.e. a Reflected Ceiling Plan VP shows the Ceiling Main class and not the Sills class. I have found however, that even though having set up Stories prior to using the Create Standard Viewports Command, Design Layers created by the CSVPs didn’t seem to be automatically assigned to appropriate Stories, or formatted as Stories-created Design layers. Also using a default Naming Standard, design layers have a “Mod-“ prefix and include Design Layers, suitable for designing in 2D – which for me is are unnecessary legacies of previous document structure. One more thing, once one uses the Standard Naming tool, several worksheets are also created in the document: ClassNameStds, SheetNameStds and ViewNameStds. Edit these to change the name of User-X as you wish, and to export/import custom Naming Standards between documents as you would with any resources. HTH

So I find the Help system for 2015 is pretty good, but I can't find the PDF files for this version, which I miss. Mostly I miss being able to read through a section, "turn pages", and read all about a topic on my iPad when not connected to the Internet. Are PDFS available for 2015?

Sure. Yes, use classes. By default, doors tags are set to the Door-Spec class, I think. Click the Settings button in the OIP to change it; select ID tag from the list on the left, and choose another class for the Tag in the center of the pane on the right or create a new class, then set the appropriate classes visible or not, as you wish, in your viewports.

This has been an issue that frustrated us too. We found that if we added another field to our title blocks called something like "S_Sheet Title Line 2" linked to the title block record for our office, and then, in our list of drawings, used the concatenation function, i.e. =CONCAT(('our office title block data'.'S_Sheet Title_SD'),' ',('our office title block data'.'S_Sheet Title Line 2')), we were able to have both our Title Blocks and our Drawing Lists read satisfactorily. Only Sheet Titles appear in our navigation windows, but this has worked for us. It would sure be nice if the multiple-line fields would simply work like, I think that we all agree, they should, though.

Our standard is to indicate door and window openings in our Ceiling Plans as they serve as reference and orientation in the field. We don't really like the way Vectorworks' Door and Window Main Classes display the double lines at jambs, but have accepted it as our standard...for some time now. Yes, cutting sections through a Sheet Layer Viewport above openings would work. Another way???

Humm, with all due respect, Messieurs, this works as expected for me as the specified eve detail geometry is applied to the edges below the axis (spring) line.

Bill, personally I haven't found a reason to use the default layer type as I've really only found need for one, and want just one, of each type of layer in my models. But, I suppose that I could only have types as I haven't thought of a reason to filter a view of my model based on layer types. I've found that a single EXISTING story default layer type and model layer affords me the level of control I require to display and quantify existing building features; for other story defaults, I do as have since I started using a pin-bar layer system, I have PLAN, STRUCTURE, CEILING layer types and layers. Also have found FLOORING, OVERHEAD, MEPS and ANNOTATION layers useful to easily control visibilities for groups of objects, as, even though they can be controlled by classes, the lack of hierarchical class control for SLVPs makes this a more cumbersome approach for me. Additionally, I have non-story model layers for the SITE, for instance, and maybe for alternative schemes before one is adopted and its objects are moved to my PLAN layer(s). As far as classes, I generally start with a basic set and then, add more as I find need for, say, E-REMAIN, E-DEMO, E-REFINISH, WOOD-1, WOOD-2 ... As I generally have a lengthy list of classes in my files, I put A-, C-, M-, E-, P-, S-, etc. prefixes on my class names to more easily navigate and manage them by discipline, rather than just alpha-numerically. Alas, this is not as workable as I would like because of the many auto-generated classes the program creates outside of the Auto-Named list, but the best organization I've come up with.

I have found that stories can be useful in structuring a renovation project file, especially for template files and vertical additions, where automatic height adjustments can be beneficial. While only one level type is permitted in a story, one may create level types suitable to practice and project -- I.e. (E) floor and (N) floor default types may be appropriate for your projects -- or as many layers as desired. Several layer types may have the same "offset" elevation. Levels assigned to stories and their offsets can be easily edited. Objects can be bound to levels within a story and to levels of stories above and below. Vectorworks 2014 doesn't change the story feature, but sure improves the 3D working experience and offers so many quicker ways of accomplishing things, I have been quite pleased to work with it for weeks now.

Certainly don't consider myself an expert, but in my opinion your sample images use depth of field to soften distant objects while those in the foreground are sharper. I don't use Cinema 4D but have for years used Renderworks and Photoshop to illustrate my designs. I might suggest that through the use of Layers and Classes in Vectorworks you might try to isolate parts of your scenes and render those separately. Then bring those images into separate layers in Photoshop and use various filters and adjustment settings to achieve a desired look.