Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About Hans-Olav

  • Rank

Personal Information

  • Occupation
  • Homepage
  • Location
    Reykjavik, Iceland
  1. Monitor for vectorworks

    Hi @FElicity Here is a resent monitor discussion :
  2. Thanks for the link @rDesign
  3. Hi Christiaan We have the same problem. Have been using the apple wiki a lot on the old server and need a replacement. We moved our mail server to outlook.365, and as part of the oneDrive there is a wiki option. I haven't had time to study the options yet but the first impression is not as easy or straight forward as the old wiki.
  4. iMac Pro information

    Same here. A crash once in a while. But much better. Hopefully 10.13.5 is out soon
  5. Annotating areas of polygons

    Hi Steve I use the space tool to display areas. Kind regards Hans-Olav
  6. iMac Pro information

    Hi Updated to 10.13.4 I have been working for a whole day without crashing but mainly in 2d, after navigating with Flyovertool VW crashed. Not yet fixed
  7. Project sharing workflow

    Thanks for the info
  8. Project sharing workflow

    Thanks for the input @_c_
  9. Project sharing workflow

    @_c_ do you have an opinion?
  10. Cant edit proposed site contours

    I think direct editing of counter lines was introduced in VW 2018. Depending on how the DTM was created you can right click and edit the source geometry.
  11. Project sharing workflow

    Thanks a lot for the input @Christiaan I haven't yet dared to put a whole project in one file. Our current setup keeps the size of each phase-file smaller, we are referencing just the layers needed for each phase. Typically prelim face is less than ten sheets A1, building permit 20-30 sheets and construction phase is 60-100+ A1sheets. Section viewports are working fine when using old style layer referencing, and I believe we have a more manageable model file when we have less rendered viewports in the file. We have some temporary sections and elevation viewports in the model file to use the edit in place function, but the final rendered viewports are all in the target files. I guess its all about balancing file size versus file management in a project. My main question is if it is sound or dangerous to use project sharing on two files in a layer referenced row, like in my fig.1. Theoretically each user are have both files open and are committing changes to both and updating the reference without talking to each other. Maybe @Gunther can answer?
  12. Project sharing workflow

    Agree - but if project sharing of the target file is dangerous I could split it into several files. Plans in one, sections in another and so on.
  13. Project sharing workflow

    Hi We have for many years worked with "old style" layer referencing from a model file or set of model files into files for each phase of the project. The target files have typically plan and section viewports with annotations and the same data can be presented in different style and resolution depending on each phase's requirements. When Project Sharing was introduced we could reduce the number of files and had less recourse conflicts, but a set of new Project Sharing problems occurred. A lot of the bugs are now solved. The improved publish command is a timesaver when you can produce a complete drawing set with pdfs and dwg's from one file. When Project Sharing was new we tried to share two files in the row, the model file and the construction document file. We had a LOT of trouble. Since then we have only shared the Model file. In one of the current projects we need more people to have access to the construction document file. I wonder if it is a recommended workflow to share two documents in a row, and what happens if two people are updating the reference and committing changes to the same file. anyone here using the same workflow? or is it better to somehow split up the files to give more people access? Kind regards Hans-Olav
  14. Is it just to wait patently for a fix or are there some bug site at Apple or AMD one can contribute with crash reports?
  15. So we need to wait for Apple to fix the issue?


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