Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

138 Spectacular


About CipesDesign

  • Rank
    Vectorworks Veteran

Personal Information

  • Occupation
  • Homepage
  • Hobbies
    Sailing, skiing, music & many more
  • Location
    United States

Recent Profile Visitors

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

  1. It *might* be the font. You can check by selecting the Scale Bar and then changing font (and/or size) in the Font menu. Yes they are editable, select it and look in the OIP where you find a variety of user input fields. See attached...
  2. Agree with all of the above. For most single family residential sites I ask the surveyor to include extra area in the topographic data so that I can crop out the weird random anomalies at the edge(s).
  3. Remember guys: Don't anthropomorphize your software. It hates it when you do that.
  4. As far as I know the only joist hangers included in VW's are part of the Framing Member Plug In and only for Top/Plan View. For details (front and side views) I go the the Simpson site and download their .dwg files, then import (into a separate file!) and clean them up. Over the years I have amassed a fairly large collection of the most commonly used ones which I keep up to date in their own VW's document (you could also use this document as a resource, making it browsable in all documents). As for nails, it's easy to draw one and use it. Depending on the scale, two lines in a "T" shape might be adequate. You could also maybe use the "Screw" with no threads.
  5. If you only need a visual, what not just make the tunnel entrance black, or very dark, using a 3d polygon?
  6. FWIW I use Open GL with Textures and Shadows for this type of quick look rendering. Works fine - no complaints.
  7. Could it be that your default setting in the Attributes palette is that arrowhead? Just a guess. And of course this shouldn't apply to a Railing (or other) object, only to lines. So if that's the case I would call it a bug. If it's something else, then hmmm...???
  8. This is easy in VW's as well. 1) Add a Heliodon Object (AKA sun) to one of your Design Layers. Make sure that the settings are correct as to Lat/Long, Month/Day/Time, etc. 2) Then in Open GL (and other some rendering modes, if you have RW) shadows will be generated. 2a) Make sure that you go to View>Rendering>Open GL Options and check the "Use Shadows" option. You might also want to change the quality (of both the rendering and the shadows) from the "Low" setting (which is the default) to a higher setting.
  9. 20 Plus yers ago I used a dot matrix printer. I printed multiple, tiled sheets, cut off margins with an exact-o knife and taped them together. Then I brought them to a local copy shop and they made blue prints from them. Not really fun. And these days not necessary. Here are a couple options: 1) Buy a reasonable cost ink jet printer. Around 1,000 for D size and roll feed. 2) Send PDF's to your local architectural print shop and have them print. In my town it is about 1.25 per D size sheet.
  10. You don't specify which Render Mode you are using. If it's Open GL check [View>Rendering>Open GL Options] to verify that "Use Shadows" is ON. FWIW, the default state for a new document is OFF...
  11. Usually the colors are inherited from AutoCad Layers, which are translated to VW's Classes during the Import process. If you select any of the colored objects it will probably have a little swoop-y "By Class" arrow showing in the Attributes Palette. The easiest/fastest way to change colors to black is to Select the objects ("Select All") and then: 1) Change the Line Color to black in the Attributes Palette. 2) *Sometimes* also might want to use the little dropdown menu at the bottom of the Attributes Palette to "Remove By Class Settings". Do not actually change the Class of any of the Objects. These are useful to sort out visibilities, etc. Another note: It is usually advised that all the objects from an Imported DWG File reside on their own discreet Design Layer. All of the tracing or whatever you will do later should happen on a new Design Layer. And you can Copy and Paste In Place from the Import Layer to any other Layer, thereby keeping the original imported date intact/unaltered (except perhaps the line color).
  12. Sometimes you get good 3d data from a survey. Sometimes you even get a Site Model. But not usually. In that case, see below... There are a few steps in this process. To ensure success I have learned the hard way to: 1) Start with 2d Polygons. Make sure to verify that each (2d) contour is a continuous Polygon. Data from surveys is notoriously bad at this. I generally go through and visually/manually check each and every contour. I make sure that any unconnected segments are exactly coincident at their respective ends and use the Compose command to merge/join them. Also important that there are no "loops" or overlapping double backs. This will mess up a Site Model. I sometimes find it faster to trace over (in a new Design Layer) the contours on a survey (realizing that EXACT tracing is not actually possible, I accept that this introduces small errors, which in general do not amount to more than 3 or 4" which is within my tolerable limit; can be solved at the site IRL). Sometimes you need to trace anyway, if for example all you have is a PDF... 2) Select all of the (verified!) 2d Polygons and Copy. Create a new Design Layer and Paste In Place, thereby preserving the original data, and aligning the new copies with it. 3) In the new Layer, select all the 2d Polygons and run command "Modify>Convert to 3d Polygons". 4) Select one 3d polygon at a time and assign a Z value to it (note there is a somewhat automated way to do this, but unless your original polygons were created in the EXACT order - lower to higher or visa versa- this procedure can get royally cocked up - See command "AEC>2d Polys to 3d Source Data") 5) Double check step 4. No really! 6) Optional, but highly advised: Select the 3d Polygons and run "AEC>Terrain>Simplify 3d Polys". Use a reasonable number, eg: 24". This command will result in a Group of 3d Polygons. You can and should visually compare these to their unsimplified parents. If they are not too divergent they should be fine. Again, this does introduce a bit of slop. But in lowering the vertex count in each polygon your Site Model will behave astoundingly better later on. (You can also compare the vertex count in any of the parent/offspring polys. This is telling!) 7) Usually on another new Design Layer, Paste In Place the group of simplified 3d Polygons. Ungroup them. 😎Select all the simplified 3d Polygons and run command "AEC>Terrain>Site Model from Source Data" Depending on the size and complexity of the site this process can be time consuming. But in my opinion it's worth every minute (or hour!) in the long run. Now you have a Site Model. Perhaps later I'll write another how-to on all the awesome things you can do with it.
  13. Hey Joe, I could get really long-winded here, but I'll try to be concise. Before Viewports and Sheet Layers we used a method similar to the one you describe (also, making extensive use of Saved Views). This method is still a valid approach, however... Upon the introduction of VP's and Sheet Layers I felt somewhat forced to convert to VW's new, "preferred" workflow, using Design Layers for Model Data and Viewports on Sheet Layers for all other info (dimensions, notes, annotations). There is more than one way to skin a Vectorworks cat. Do I really like the "new" (circa 2009) workflow? Not really very much. But I use it anyway. Like drinking the Koolaid. I got used to the redundancies and the need to navigate in and out of a bunch of different "environments". It's actually all pretty confusing IMO. But one can get used to anything... In any case, I am still a big WYSIWYG advocate, and so I generally create Model data in 1/4" scale, which is almost always my presentation/output scale. One sort of good by product to the "new" workflow is that it somewhat forces me to separate my process into two distinct parts: 1) I get the graphics right (for me this excludes all annotations). This is helpful because in my experience builders mostly relate to pictorial representations, and don't generally like to read; and 2) I add annotations, so when they ask dumb questions I can say (eg) "Look at note 17 on sheet 4. See what it's pointing to?" P
  14. *Sometimes* I have found instances where VW's needs to be *forced* to comply. To do this I choose "remove class attributes" then choose "attributes by class". Also, I believe this drop down menu is in Attributes Palette (as opposed to OIP).


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...