The Resource Manager and Resource Selector allow you to browse the content online, and they will automatically download the required files on demand. From the Resource Manager, you can also drag a library resource directly onto your drawing. For example, you can browse line type resources from the Attributes palette, and browse plant styles (Vectorworks Landmark required) from the Plant tool’s Tool bar.įrom both the Resource Manager and Resource Selector, you can drag a library resource to a file in the file browser pane to easily import it. The Resource Selector has a similar browser pane, to provide access to resource libraries at the point of use. In the Resource Manager palette, the file browser pane (on the left) provides easy access to the resource libraries for even faster access, designate frequently used libraries as “favorites.” Keeping all origins at the internal origin also has some advantages with referenced design layer viewports as it can prevent some unwanted shifts of viewports/viewport content.Hundreds of resource libraries are available for use with the Vectorworks application, and you can add custom libraries, as well. Of course there are limits to what Vectorworks can handle, but distance from the internal origin is no longer the problematic issue at it used to be in the past. Since Vectorworks became 64-bit I have not noticed any serious performance issues with large drawings (including 3D) being at hundreds of kilometers away from the internal origin. In that case keep all origins at the internal origin and work at actual coordinates. if you are working with georeferenced data/objects where you need to work with coordinates as you already mentioned in your reply. This performance issue needs a bit of nuance, e.g. If the above isn't applicable or doesn't resolve performance to your satisfaction, please contact your local Vectorworks agent to get the Tech Support needed to get your Vectorworks running normally. Identifying culprits can take a bit of work, but fixing them is relatively easy. Just 'Edit' them to get their guts (images/2D/3D parts) and reassemble them as a new resource. While targeted testing demonstrates that Vectorworks is reliably backwards-compatible, the longer resources are around the more opportunity they have to become defunct and this it seems is the most likely explanation for corrupt resources. Nothing lasts forever, this includes the compatibility/suitability/usability of resources created years ago in older versions of Vectorworks. Legacy stuff: Symbols, Plug-in objects or other resources. Centre your drawing over the Internal Origin and pull in your User Origin unless it has to be where it is for georeferencing. If objects or the 'User Origin' are ~8 km / ~5 miles or more away from the " Internal Origin" this will weigh heavily on computation and can cause a broad range of seemingly unrelated symptoms.
Make sure you Mac meets the Vectorworks 2017 System Requirements. One aspect in particular is the Navigation Graphics: Go > Vectorworks preferences > Display > Navigation Graphics - and set this to 'Good Performance and Compatibility' or 'Best Compatibility.' This will improve responsiveness and stability.Ĭheck for stray objects in your Design Layers. Vectorworks 2017 requires more hardware performance than 2016 because it has enhanced capabilities. The non-specific symptoms you've described leave many possible causes, but here are some common ones: (Following best-practice always helps too). If you're experiencing performance issues with Vectorworks 2017 please know that it is not typical and that if you're running it on hardware appropriate to the increased demands of 2017 and the complexity of your documents, then you can expect to achieve normal performance as well. Hi my experience, when set up correctly and running on adequate hardware Vectorworks 2017 performs well.