Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Issue resolved today after some troubleshooting with Dave from VW tech support. We unchecked "Export as flattened 2d objects" and also unchecked every option in the 2D Fills and Files box. The exported file size went down from 65 MB to 217 KB, and every object could be imported back into VW as a circle. When exporting for CNC work, I recommend these options.
  2. I just exported a reasonably-sized drawing consisting of circles to .dwg, and it turned every object into a polygon, resulting in huge filesize bloat, plus not the object we need for CNC. Anyone have any experience with this? I can import .dwg circles as circles, why can't I export? Is there a trick to this?
  3. @Art V Some users may not see the need for Screen Plane objects, but those who use them do see the need, especially in design layers. No matter what working plane view you are in, Screen Plane is there to import and create geometry and relationships.
  4. The screen plane was the original VectorWorks 2d object mode, so I would not be surprised if it is embedded somewhere. The Layer Plane object is almost like a 3d polygon, while the Screen Plane object is the essential bridge between thoughts best expressed in 2d from any view, and 3d modeling. But if you don't like it - I hope they can fix the preference so you can avoid meeting them!
  5. Will, I had the opposite problem. No use for Layer Plane, but VW kept reverting to that preference. I finally figured out it was a bug that was triggered by editing the crop in a sheet layer viewport. That has been fixed as of VW2020. Maybe that will help you track down the problem. Everytime it happens, try to track what you just did, even if there is no apparent logical connection.
  6. P Retondo


    I make my own title blocks, so I don't know about the canned VW objects. But making your own works fine. Make them a symbol, and attach records to enter the info items you want. See "Link Text to Record" to display that information in each unique instance of your symbol. When you select a symbol set up this way, you will look at the "Data" tab in the Object Info Palette (OIP) to be able to manage your records. Here's what that will look like (you can have more than one Record Format for a symbol object): Other users may have advice tailored to the VW title block object.
  7. Under the “View” menu at the top of your VW application window, pick “Projection” and then one of 3 “Perspective” choices. Under the light bulb tool set you will find various ways to navigate.
  8. Thanks, Jeff. I wonder if it has something to do with which version of ACAD I'm exporting to. I'll check that out.
  9. @jeff prince Are you stating this as a NNA engineer?
  10. @jeff prince When you select "Export DWG layers as : layers", your layers should become separate layers in ACAD. That's the way it has worked in the past, and since it isn't working that way now, that would be a bug - correct? The behavior in v2020 is not consistent with behavior in previous versions, or at least that's what I'm trying to confirm with other users. Having all your layers come into ACAD jumbled into one layer is distinctly unhelpful to most of my collaborators.
  11. @jeff prince Jeff, thanks for your input. I worked with ACAD for 4 years, so I am well aware of the layer/class issue. My purpose in bringing this up here is to find out if this might be a bug so I could report it.
  12. Jeff, thanks. I have layers with different stories of a building in separate layers. I want the same layer structure in the exported .dwg, exactly as you describe. I was wondering if anyone else has noticed that this doesn't work any more. The way I know this is that my structural consultant complained that everything was in the same ACAD layer. I imported my .dwg back into VW, and everything came in as one layer - I don't maintain a license of ACAD anymore, but I trust that what the engineer told me is true. I had to export separate files for each story.
  13. Jeff, I don't want to export classes as separate layers in .dwg, I want to export layers as separate layers in .dwg. Used to work in the past, but now it doesn't seem to.
  14. Anyone else experiencing this problem? When I export a file, with multiple layers visible, to .dwg and select "Export as dwg layers: layers," the resulting .dwg has only one layer with all objects crammed into it.
  15. I hope this doesn't confuse you, but I ignore the "stories" concept completely. "Stories" offsets each layer by the story height from "ground," which is marginally handy if you want to modify story heights, but I prefer a simpler system. (Bear in mind that you can change things from project to project as you work into the software.) I just name layers by story number, with each layer set to 0 from ground, and move objects up by my floor-to-floor height for 2nd and 3rd stories. I use the "layer wall height" parameter to set the heights of my walls. These fields are accessed by editing the layer in question. When you look at a set of walls and 3d objects from an elevation view, you can select them and move them or align them to make sure everything is right. Check your doors and windows - there are some parameters in the info palette that set their heights, just play with them looking from the side to get them right. Also, when you need to extend walls up or down to meet something, use the "Fit Walls to Objects" tool in the AEC dropdown menu. I set up special layers just to make that easier. For example, suppose you want your first floor walls to go down to a foundation footing. Create a 3d polygon at the desired height, put it in a special layer, and extend your walls down to that object. The beauty of that is that your doors and windows automatically stay put after that operation. Have fun! PS: the reason I never adopted "stories" (i.e., "layer elevations") is that when you paste an object "in place" from one layer to another, it doesn't carry with it it's "actual" height when the layers have different heights above 0.
  16. The Navigation palette is not part of the Workspace. Sounds to me like you should start out by having them uninstall then reinstall Vectorworks to get a fresh start.
  17. I defer to Pat's superior knowledge. But, if your client has customized their workspace, having their actual .vww file will make your interface identical to theirs, as an added measure to Pat's Designer disabling script.
  18. The other thing you can do is have your client email you their workspace settings file (.vww file). Rename it to something distinctive, enable that, and you should have only their workspace and all preferences for shortcuts, etc.
  19. Unequal leaf is for swing bi-part doors only. I don't know how to do what you want unless you create a custom symbol (see "Use Symbol Geometry" for doors). I would create the configuration I wanted using the bi-part doors tool, then convert to group and edit the way the door looks in plan, then convert to symbol, and check "use symbol geometry" when inserting where you want the door to be.
  20. If it helps anyone, I figured out the correct worksheet formula to substitute into the column reporting rough openings for pocket doors: =IF((G4=('Pocket Bi-Part')) | (G4=('Pocket Simple')), ('Door'.'ROWidth'+'Door'.'Width'), 'Door'.'ROWidth') Provided, of course, that column G reports the door "configuration."
  21. In the real world of construction, a pocket door is placed in an opening roughly twice the width of the actual door. The Vectorworks door schedule is blissfully unaware of this reality, requiring laborious workarounds in the report worksheet. Wouldn't it be possible to easily change this parameter to report the real rough opening required? Speaking of this workaround, the best way would be a column with an "if / else" method, but since one does not know the proper Vectorscript variable names, it's not possible to construct a cell value "if type = "pocket door", = R.O.*2, else = R.O".
  22. Matt, I don't know what version you are using, but if it is recent, you can turn on GDI+Imaging (VW Preferences, Display tab, last option). Then you can set the opacity of a 2d object fill in the Attributes Palette. Placing a white rectangle with opacity around 70% would give the effect of a grayed-out look to the object below. If you want a viewport that shows object below it, you have to assign a layer transparency (if GDI+Imaging is "on") or assign a transfer mode of "Overlay" to the layer if GDI+Imaging is "off."
  23. You need to create a design layer with "Overlay" transfer mode selected instead of "Paint." That layer when converted to a .pdf can have an assigned opacity by %, allowing you to vary its transparency.
  24. Nocolas means to check your video card settings via the control panel app to see if the default processor is the GPU, not something else.
  • Create New...