Robert Anderson

Vectorworks, Inc Employee
  • Content count

    2,655
  • Joined

  • Last visited

Community Reputation

14 Good

3 Followers

About Robert Anderson

  • Rank
    Vectorworks Addict

Personal Information

  • Occupation
    VP Integrated Practice
  • Homepage
    practicalcyclist.blogspot.com/
  • Hobbies
    Vectorworks, Bicycle commuting, Choir singing
  • Location
    Ellicott City, MD, USA
  1. @CJustinStockton, People often get confused about scale because our Design Layer environment has what is called "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. If you have symbols, they are all stored in a 'hidden' part of the file called the "Library" that contains Symbols as well as other resources (such as hatches and textures). You access all these through the window called the Resource Manager. No need to put them on a layer.
  2. It is possible to work this way, but this is a rather AutoCAD-style workflow. Why not use sheet layers (the equivalent of Paper Space) and viewports? This gives you much, much more flexibility in presenting and composing your sheets...
  3. Katharine, 250MB is no problem. Send me a Dropbox link or sim.
  4. Ah, are you using Vectorworks Fundamentals? It does not have that option. It's non-sensical that Drawing Labels would have a performance impact. If you can send me (randerson_at_vectorworks.net) a sample file that exhibits the problem, I'll look into it.
  5. OK, this is just a wild stab, but try going to the Document Preferences command (at File:Document Settings) and turning off "Use Automatic Drawing Coordination" in the first tab of that dialog. See if that setting makes any difference.
  6. Here's a small 3-story office that I use. Very basic. Small_spec_office.zip
  7. TTillisch, the title blocks in your old sheet borders should convert automatically. For more information on title block borders, here's a Help topic that you may find useful:
  8. Beth and Martha, SP1 will fix many issues with titleblock conversion. However, in the short run, you should be able to convert titleblocks using the guidelines in this thread: Do not use invisible classes in your titleblock symbol; Do not shift the page or change the origin on your sheet layers; If you have followed these guidelines and are still seeing conversion problems, please send the files to me. Thanks!
  9. inbinder, I use a 3-story file for testing that I do. What is it you are looking for? (A "plain, multi-floor office building" could be almost anything.)
  10. Based on the engineer's comments (see above), I think that either the moved-origin or the hidden-classes issue can cause this bad centering on conversion. I think the hidden-classes issue may be more likely than the moved origin.
  11. This will no doubt be controversial, but who cares: I think it's easier to come up to speed with a computational design capability (as in Marionette) integrally applied to an existing BIM product rather than come up to speed with a BIM capability applied to a computational design product. (Discuss..)
  12. I have just received the following message from the engineer working on this problem; "I have investigated TB_Le_Pham.vwx and in the classes Signature and Stamp there are objects that are part of a Title Block Border Layout. In the test file these classes are invisible. That is the reason why the group boundary of layout is different from visible objects boundary. For the second problem with Drawing list worksheet the user have to update formulas to the new records of Title Block Border object. For example =('GEP Titleblock Record'.'S_Sheet Number_SN') has to be =('Title Block Sheet Data'.'Sheet Number'). Also the user has to edit the criteria. The field S_Drawing List is not added into new Title Block Sheet Data record because its value is not linked to text into Sheet Border symbol. The problems with file TB_John_Crosetti_v2018.vwx are fixed for 23.0.1 and with VW389180 the file is updated correctly. The problems with file TB_Andrew_Carr.vwx are fixed for 23.0.1 and with VW389180 the file is updated correctly. The problems with file TB_Crawford.vwx are fixed for 23.0.1 and with VW389180 the file is updated correctly."
  13. Hi Joe, There are some already-existing solutions for pedestrian flow (look up SimTread on our website.) There is a group of researchers at LSU that are developing some code compliance checking based on Marionette at the current time. I'll check in with the lead researcher to see what we can share here.
  14. Open a 2017 file in 2018. Select an old Sheet Border object. You will see on the Object Info palette the "convert" functionality. You should not have to rebuild entirely. There was a bug discovered that occured if the user had shifted the page on a sheet layer, but as long as your origin has not been shifted on a sheet layer, you should be fine.
  15. I am sorry you're having the problem with the incorrect conversion of the Title blocks. I believe it has to do with (as one poster suggested) the changing of the origin on the Sheet layers. I have created a bug report covering this issue and referencing this thread. If anyone is having trouble converting a v2017 Title Block, please send me a copy of a Vectorworks file with a single sheet layer and that title block in it. If we can reproduce the conversion error, we will fix it ASAP. Send to randerson@vectorworks.net and I will make sure the example files are attached to the bug for testing.