Robert Anderson

Vectorworks, Inc Employee
  • Content count

  • Joined

  • Last visited

Community Reputation

15 Good


About Robert Anderson

  • Rank
    Vectorworks Addict

Personal Information

  • Occupation
    VP Integrated Practice
  • Homepage
  • Hobbies
    Vectorworks, Bicycle commuting, Choir singing
  1. You can import both Revit and AutoCAD files to use as backgrounds for your design. You can then add layers and draw additional information. If you are doing AV system design, you really should look at Connect-CAD, a plug-in to Vectorworks Architect. I think this could be a good fit for your needs.
  2. Take a look at your "printer setup" and make sure you have the "Scale" setting at 100%.
  3. Yeah, I agree about the NIL handle thingie. Don't have time to search the VS Function Reference, though...
  4. Pat, to get the handle to the default object or tool settings record, I think you don't pass a NIL handle, instead pass a handle obtained by GetObject() and the universal name of the PIO or command. For example, to set the default top shape of a door to a Gable, use the following one-line script: setrfield(getobject('Door'),'Door','TopShape','Gable'); HTH.
  5. Were these callouts placed in Rotated Plan mode?
  6. Enable 'unified view' in the View Bar. If you want to change how non-active layers appear, this is set with the "Layer Options" menu on the View menu.
  7. Set your OpenGL rendering quality to High or Very High. This is caused by a "Low" OpenGL render setting.
  8. Glad to help. Welcome to Vectorworks.
  9. Dimension markers are page-scale objects (as are all line markers). I can't imagine anyone needing one at 2". It's important to understand the Vectorworks concept of "Layer Scale", which is the property (of Design Layers) that controls the size of page-scale objects. (Layer Scale -- and page-scale objects -- do not exist in AutoCAD AFAIK.) If (say) you're going to be doing most of your drawings at 1:50, set your Layer Scale setting for your Design Layer at 1:50. Then set the size of your marker to 1/4" or whatever you want as an output size. You will still be working on all your objects in "World Scale" (the size of things in the world). One of the nice things about Vectorworks is it manages these two things (the size of things that belong only on the page and the size of things in the world) separately and (mostly) transparently -- once you understand it and quit trying to make your markers work as if they were real things. Somewhat deeper intro into "Layer Scale": The "Layer Scale" used by VectorWorks comes primarily out of "WYSIWYG" drawing, pioneered on the Mac (and therefore part of Vectorworks' history). "Layer Scale" exists to allow graphic properties of the drawing or model to be represented properly, as though you were drawing at a particular scale on a piece of paper. It is a scaling value used to allow proper representation for PAGE-SCALED (as opposed to WORLD-SCALED) attributes: -Line weight; -Line style (e.g. length of dashes); -Marker (arrowhead) size; -Text size; -Hatch scaling; -Page symbol scaling; In "WYSIWYG" drawing, in order to properly display these attributes, there has to be an intended output scale so you can see how the drawing will look at that intended format. The practical upshot of all this is that you should set your "layer scale" to be the same as the predominant output scale of your project. This will necessitate the least amount of attribute-scaling in viewports. But in all design layers, at all times, you are drawing in world scale. An inch is always an inch, a foot is always a foot, no matter the "Layer Scale". "Layer Scale" serves only to set page-oriented graphics.
  10. Jen, what version of Vectorworks do you have that doesn't have Export to DWG? Or are you an ACAD user?
  11. What happened when you converted to NURBS? Did that work successfully (before the lofting)? If so, I would try this: Convert your mesh to NURBS. This will give you NURBS curves. In the 3D Powerpack menu, select your curves and choose "Create Surface from Curves". (you may have to do this in several sections to get everything). Now try shelling from the NURBS surfaces. Let me know if this works..
  12. Hi, TDM I would start by turning off textures and texture mapping and changing "Import other objects" to Meshes. I'm guessing (because i'm not an engineer) that this is the lowest-memory impact import. If that works in a reasonable time, try turning textures back on and re-importing. Good luck!
  13. It's far better to use the conversion process provided that start from scratch, IMO. Then make any minor graphical adjustments needed (if any) and then copy the style symbol to a new file. Repeat for all your different title blocks, then put the file where you've collected your style symbols into the appropriate subfolder in the Object Styles folder in the Resource Manager. The second thing to learn is to get friendly with the "Edit Plug-in Style" when you want to make changes to your TBB.
  14. I partly agree with Jonathan here. It's true we didn't include Sheet Border --> Title Block Border in Migration Manager. This was a conservative decision based on the fact that we wanted users to review the updates first hand to verify things would convert properly. And this approach has turned up some limitations quickly, many of which are fixed in SP1 and the other known ones will be fixed in SP2. The conceptual difference is that in VW_2017 and before, you used a symbol definition text-linked to a series of (rather cryptic) records to define the layout and textual content of the Titleblock. Now you use a Style-symbol to control everything about the Title Block Border, and of course the Vectorworks Style system for PIOs gives you full control over what you control by-style and by-instance. You can convert the old SB-PIOs to TBB-PIOs one at a time and, if they look right, they are right. Collect these style-symbols into your template files or (better) into a VWX file that you put into the Object Styles / Title Block Border and, as Jonathan might say, Bob's your uncle. (You'll have to ask him what that means, exactly.)
  15. I'm not 100% sure on this issue, so you might want to get in touch with Tech Support. But just guessing, you're running an 8-year-old version of the application software on a 2-year-old version of the OS. I'm guessing there may be a basic incompatibility and you may need to upgrade your Vectorworks. Apple is known for introducing incompatibilities from version to version of their OS, and we often offer an "SP5" to fix incompatibilities from the previous version. But 8 versions back is a little long in the tooth. Tech Support should be able to give you a definitive compatibility answer, though.