Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

77 Excellent


About Amorphous

  • Rank

Personal Information

  • Occupation
  • Location

Recent Profile Visitors

375 profile views
  1. Very pleased to see this development, but as a Mac-based office we are yet to understand how we can benefit from this. Are there other Mac-based Vectorworks office out there who have developed a workflow for Lumion? If so, we are most interested to hear about that process.
  2. Amorphous


    Yes we have up to two hundred pages in our VWX documents, and every time we add a new sheet we have to drag the new sheet to the new place. The entire process of making a new sheet and adding a title block (which is very very slow) can take up to three to five minutes. Not very efficient.
  3. Amorphous

    Best settings to export 3D (vwx) to 2D (dwg)

    Hi @Vasil Kitanov I have just sent the file to @Jim Wilson for other testing. Please ask to get it from him. The sheet related to this export is 1.511. We have tried all permutations for export options. So there's no point posting up a screen shot of one particular setting. Our consultants (yes there are many of them on this project) all complain that our DWG is so slow they can't use it. They can't even zoom in or out in the DWG. We tried taking out the hatches and that didn't help either. Hope you are able to find the issue with it.
  4. Amorphous

    Best settings to export 3D (vwx) to 2D (dwg)

    We are trying to export our 3D vwx to 2D dwg today. (wasting many hours) Our consultants (in China) say the files we export is so slow upon opening on their side. We are the only architects these consultants have ever met who cannot produce and provide usable CAD (DWG) files to them. I hate to say this. But we go in telling them about how great our BIM system is, but we walk out with tail between our legs looking like absolute fools. As Architects, we simply cannot fail to provide DWGs to other consultants. Happy to provide this DWG to anyone with AutoCAD for testing (we don't have it, so we can't verify what the consultants are telling us). Can this issue please get immediate attention?
  5. @Jim Wilson please give me your email and I'll shoot it over. @Matt Overton yes. This is a problem with surface hatches at the moment. You cannot choose 'tile' hatches in 'Textures' as the surface hatch. So in order to do a 'timber' or 'stone' hatch so we have the correct elevational hatch in hidden line drawings (Eg elevations and sections), we have to make tens of layers to achieve that. If 'tile' attaches were allowed to be attached to 'texture', the we would not have this problem. I'll play around simpler hatches and see.
  6. Amorphous

    Vectorworks is REALLY SLOW lately!

    Okay will give that a try. Thanks.
  7. Amorphous

    Vectorworks is REALLY SLOW lately!

    @Zeno are suggesting we should downgrade to VW2015 because it is a more stable version of VW?
  8. Amorphous

    Vectorworks is REALLY SLOW lately!

    Is it just me? Or is this speed quite frustrating for others too. We need a snappy program. SLOW.mov
  9. Amorphous

    Vectorworks is REALLY SLOW lately!

    Everything is slow! Simple things like: Editing a dimension is slow. Moving objects around is slow. Navigating between sheets is slow Save and commit is slow (yes it has improved, but lets face it, still slow) There's a 2-3 second delay in everything I do.... Is anyone at Vectorworks doing anything about this??? I don't want to be frustrated anymore.
  10. Amorphous

    Sudden Blue Background

    Lately, Vectorworks suddenly shows a blue background across multiples of our Mac terminals running both Mac OS 10.13 and Mac OS 10.14. We can't get rid of this problem and can't work this way. Does anyone have the same problem or a fix? We use RX580 (8GB) as our graphics card, and have tried to set Display Performance as both 'Best Performance' and 'Good Performance and Compatibility'
  11. Would be great if VW can also work out the innermost section line of a space, while retaining the section hatch of the objects you cut through. Currently you have to choose one or the other- merge the whole section and get one thick outline (but lose the class-based hatched for cut objects), or get the correct hatches (but not get this thick section line around the outmost merged object). As @Kevin McAllister says, this is currently a manual, 2D process we do in viewport annotation for our office.
  12. The Australian distributor actually has a far superior window and door modelling tool called Windoor. Nemetschek should buy it from them and put it into the standard VW version. We concur with this post, and personally would prefer the following simple things fixed over giving us any new features (my list is all about productivity and workflow): - Section Viewports rendering time (snappy renders please, even with 'surface hatches) - 2D DWG export from 3D models (Usable files, smaller size) - Titleblock Object (Let multiple users modify different title blocks in Project Share. Any operations on TB is sooooo slow!) - Stair tool (SO INCREDIBLY SLOW) - Visibility tool (wait five seconds us to load the tool) - Slab tool (try reshaping it, SO VERY SLOW) - Floor tool (in 2019 totally broken, corrupt objects, wrong class appearance, disappearing fills) - Grid Tool (appear in 3D, line thickness control!) - Space Tool (try reshaping it!) - Detail callout Tool (leader line goes crazy when line settings changed. Difficult to reshape geometry but maintain rounded corners) - Undo Operations (Really should be so slow it crashes a computer)
  13. @Jim Wilson thanks for your response. I did some experiment, and found that in some instances, the extreme slowless is caused by 'surface hatches'. Please see enclosed simple example, sided by side, where one takes 8 seconds (with no surface hatch), and the one with surface hatch takes many many times that amount of time (with surface hatch on). Should I post this 'surface hatch' issue as a separate troubleshooting case? You mentioned that sectioning speeds is slated for improvement. Can you indicate if is an improvement that can be expected in VW2019 SP3? Thanks again.
  14. Amorphous


    This tool has wasted so much of our office hours. - it doesn’t merge with other structural objects in section - class overrides in viewport do not work (eg we want dotted lines showing beams above in plan) - the solid fill in the beam object disappears out-of-nowhere, leaving our renders and elevations looking sh*t In the end a VW forum member offered a solution: that I should use ‘beam’ object in ‘framing member’ in lieu of the use of structural object. That worked. For one project, we went from (1) starting with ‘beam structural object’ then (2) abandoning this and remodelling them as ‘walls overhead’ (problematic) and then (3) in the end remodeling all those beams as ‘framing member- beam’. All in all, inclusive of the trial and error in generating 3D renders and incomplete elevations/section, multiple attempts at remodeling, discusssing this issue internally and with others, it was in total about 20+ hours office time down the drain. I say the following in the most sincere way: Please stop wasting my office time, the good people at Vectorworks. When you put out faulty tools like this, businesses (like mine) that rely on your products suffer a loss of billable hours from the abortive work incurred. That results in a loss of money. Kindly take note.
  15. I'm happy to report that since moving from VW2018 to VW2019, the 'Save and Commit' times have dramatically reduced. On our 1.2GB file (600MB as project file, 1.2GB as working file), the 'save and commit' time is now 60 seconds or less. However, a very important part of what this thread is about, namely 'Section Viewport render times', remain a big headache for our productivity with VW. For some simple viewports, we now get up to 10min rendering time for hidden line. For complex viewports, we get up to 30min. @Jim Wilson since this thread was started on 30 August last year, I would like to ask if you are able update us on what has been done, or what the plan is, to improve Hidden Line Render times? When can we expect a change? PS. There should be an easy way for users to 'Convert hidden line render to lines and polygons within Viewport', so we can continue to work, at 1-1 scale, with what has been rendered inside a viewport (I'll start a new feature request on this).


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.