Jump to content

Search the Community

Showing results for '“Project Sharing”' in articles.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Occupation


Homepage


Hobbies


Location


Skype

Found 64 results

  1. Vectorworks, Inc. has released Service Pack 4 (SP4) for the Vectorworks® 2020 product line. This service pack includes multiple fixes and improvements in the following areas: DWG import Freezing at reading model space entities Turning Unified View off DWG export Crashing at the end of writing entities and at exporting sheet layers to DWG ConnectCAD Applying text menu settings to equipment object Name text 2D Rack objects support for 54U high racks Terminator tool is no longer missing from ConnectCAD workspace Device Builder not accepting imperial units Object highlighting is improved for the Data Tag tool in section viewports Numerous stability enhancements in areas such as Project Sharing, Hardscape tool, Path Animation and more. This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2020. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2020 SP4 update, please visit this page. Please note this Service Pack is currently available for all non-localized English versions. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
  2. The following are real-world system requirements for running Vectorworks 2020. In some demanding cases, we would suggest a more capable machine than is described in these hardware profiles. Likewise, there are some less demanding situations where Vectorworks will perform well on older hardware. General Requirements: Operating Systems: macOS 10.15 (Catalina) macOS 10.14 (Mojave) macOS 10.13 (High Sierra) macOS 10.12 (Sierra) Mac OS X 10.11 (El Capitan) * * Not supported by Vision Windows 10 64-bit Windows 8.1 64-bit Windows 8 64-bit Windows 7 SP1 64-bit Minimum Hardware Profile: Entry-level Profile: For small projects, simple models/drawings with a low level of detail, simple renderings (such as small residential projects, small theaters, small landscaping design) Processor: 64-bit Intel Core i5 (or AMD equivalent) or better RAM: 4GB or more Graphics Card: OpenGL 2.1 compatible graphics card with 1GB of VRAM or more Some integrated graphics cards such as Intel Iris graphics are acceptable for simple models/drawings, but a dedicated graphics card is preferable. Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 2GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2060 series, AMD Radeon RX 500 series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM. Display Resolution: 1440 x 900 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Recommended Hardware Profiles: High-end Profile: For large projects, complex and very detailed models/drawings, complex renderings (such as large BIM projects, large entertainment venues, commercial sites, GIS, high-end landscaping design, photorealistic rendering) Processor: 64-bit Intel Core i7 (or AMD equivalent) clocked at 3GHz or better RAM: 16GB-32GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 8GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2080 TI series, AMD Radeon RX 5000 series). Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Mid-level Profile: For medium-size projects, complex models/drawings with a medium level of details (such as small commercial projects, mid-size entertainment venues, residential site modeling) Processor: 64-bit Intel Core i5 (or AMD equivalent) clocked at 2GHz or better RAM: 8GB-16GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 2GB-4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 4GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2070 series, AMD Radeon RX Vega series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM, with 3GB or more recommended for large files. Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Network Requirements for Project Sharing Project sharing requires high-speed network connections. As the network bandwidth increases, so does project sharing performance. Slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). LAN Sharing: Minimum: A Fast Ethernet (100Mbit/s) network connection Recommended: A Gigabit Ethernet (1Gbit/s) network connection is required for large projects. Cloud Sharing: Project sharing using cloud-based storage requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Hard Drive: Storing large project files on flash storage (SSD) is recommended. Additional Details Graphics Cards IMPORTANT – Several Vectorworks features have placed higher demands on graphic hardware. Additionally, the performance and quality of the graphics provided by the Vectorworks Graphics Module depend directly on the speed, memory, and supported extensions of the graphics card. These features have the potential to provide a very fast and fluid experience if used on capable hardware, or a noticeably slower experience if used on older or incompatible hardware. Graphics cards should support at a minimum OpenGL version 2.1; cards not meeting this recommendation will have limited functionality and poor performance. In general, the more powerful your graphics card is, the better your Vectorworks experience will be. The amount of Video RAM (VRAM) required to drive Vectorworks adequately depends largely on the size of the display being used and the complexity of the Vectorworks document. Medium-sized displays with a native resolution of 1920x1080 or less should be driven by a graphics card with at least 1GB of VRAM. Larger displays should use a modern graphics card with at least 2GB of VRAM, with 4GB or more recommended. OpenGL rendering of shadows and edges are VRAM-intensive and require at least 1GB, with 2GB of VRAM or more being preferable. If you want to take full advantage of OpenGL shadows and edges, especially in situations where you have any combination of the following: - many lights - point lights - image textures - anti-aliasing - high shadow quality - excessive geometry and if you have a graphics card with less than 1GB of VRAM, you should consider upgrading your graphics card. Using Multiple View Panes with different visibilities in all panes can be VRAM-intensive and require at least 2GB of VRAM, with 3GB or more recommended for large Vectorworks documents. We strongly recommend that all users check that their video drivers are current. The majority of display problems reported to our Technical Support department have been traced to older video drivers. In general, a recent graphics card running the latest drivers is preferable to an old high-end graphics card running outdated drivers. Vision requires a dedicated OpenGL 3.0 compatible graphics card supporting GL_ARB_draw_buffers extension, preferably released in the past three years. We do not recommend any integrated Intel video chipset. While Vision may run under these environments, we do not support them due to their lack of performance and speed. We recommend gaming cards over workstation cards for Vision due to the higher clock speed. For the latest information on our graphics card recommendations and other hardware recommendations, go to the Quality-Tested Hardware page. Vectorworks may be used in conjunction with real-time rendering engines which have their own demanding hardware requirements. For example see Lumion: https://support.lumion.com/hc/en-us/articles/360003476753-Which-graphics-card-do-you-need- Remote and Virtual Machines We do not consider remote login environments such as Remote Desktop, Terminal Services, and VNC or virtual machine environments such as Parallels and VMware to be appropriate for regular work, so Vectorworks performance in these situations is not of primary concern to us. They may be appropriate for administrative testing or utility purposes, and Vectorworks is fully functional in these environments. You should not expect high performance in these environments, however, especially with interactive screen feedback. We do support Vectorworks running under Boot Camp on Mac machines. As long as you have appropriate and current drivers for the hardware on your machine, you can expect fast and reliable Vectorworks behavior. Maintenance Releases Unless there is a known problem with a maintenance release of the operating system, we recommend the latest maintenance release at the time we ship a new release of Vectorworks as a minimum because that is what we test with. If you have problems with an earlier maintenance release, we will often ask you to update as an initial troubleshooting step. Optimizing Performance For users who work with large files and complex renderings, we recommend running with at least 8GB of RAM. When RAM runs out, Vectorworks usually continues to function but is slowed significantly by the need to access the hard drive to provide virtual memory. Extreme lack of RAM may cause operations to generate errors in cases where given sufficient RAM they would otherwise succeed. Faster hard drives can have a large impact on system performance, especially when virtual memory is actively being used. Faster or slower processor clock speeds have a predictable impact on Vectorworks performance. Hard drive size requirements are driven by the total size of Vectorworks, including all content files. You can reduce this size by opting not to install some of the larger Vectorworks content files. Project Sharing and Network Bandwidth The performance of Vectorworks when working on a shared project over the network will depend on the available network bandwidth. If the network bandwidth is insufficient, operations that transfer a large amount of data over the network will be slow. We recommend at minimum a Fast Ethernet (100Mbit/s) network connection. For large projects, a Gigabit Ethernet (1Gbit/s) network is required for a fast and fluid experience. Project sharing using cloud-based storages requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Although project sharing requires high-speed network connections in general, slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). Examples of data transfer times during commit and refresh operations for different bandwidths and project file sizes are shown in the chart below. Project File Size Network Bandwidth (download/upload) Commit/Refresh Data Transfer Time 100 MB 50Mbit/s ~20s 100Mbit/s ~10s 1Gbit/s ~1s 500 MB 50Mbit/s ~100s 100Mbit/s ~50s 1Gbit/s ~5s 1GB 50Mbit/s ~200s 100Mbit/s ~100s 1Gbit/s ~10s
  3. Introduced in Vectorworks 2020, Schematic Views were a welcome improvement over plot and model views. But because of some deficiencies, you couldn’t hit the ground running. Label legends in Schematic Views did not display consistently. Schematic Views were updating every time the model was edited, slowing down your workflow. More visual context was needed to easily edit model objects while working in Schematic Views, and more visual feedback was required to properly snap lighting devices to rigging objects. Reengineering in version 2020 Service Pack 3 (SP3) has addressed these issues, bringing significant improvements to the performance and stability of Vectorworks Spotlight. Faster Schematic Views: It’s a common part of your workflow to make a series of edits to a lighting device. You frequently update the device, whether it be changing the channel, adding an accessory, or even repositioning the device on the truss. Prior to SP3, each of these individual edits caused the Schematic View to regenerate, disrupting your workflow while you waited. Now, Schematic Views have an Update Geometry button, similar to the Update button for viewports. Each time the model is edited, its Schematic View is outlined in red. When the edits are complete, you can update the Schematic Views once and get the results of all prior changes. This quickens the pace of all Schematic View operations because the view is not updated with every change. Correct label legends: In the initial release of Schematic Views, the schematic label legends did not always look right. This was the result of a few bugs that were introduced when converting from the 3D model object to the 2D Schematic View. In SP3, schematic label legends support all options, containers, right-reading labels, and non-rotating layouts. Any update to the 2D label legend in the model is applied automatically to the Schematic View. More context when editing model objects from the Schematic View: With a Schematic View selected, you can click the Properties button on the Object Info palette to edit the properties of the corresponding model object. The feedback from many of you indicated that more visual context was needed; you could not immediately see the object you were editing. For SP3, clicking the Properties button automatically selects and fits to the model object, making it visible and graying all other previously-shown objects. If the object supports sub-classes, your user settings are preserved. Now you will have more context while making changes in the Properties dialog for the selected model object. Improved load attachment: With the initial release of Vectorworks 2020, issues with auto positioning sometimes made it difficult to attach lights to rigging objects. When inserting lights, there was no visual feedback to indicate the light’s position on the snapped truss (unlike when dragging lights). Sometimes, Auto Position picked the wrong truss in 2D or didn’t find a truss in 3D. Major improvements to auto positioning have fixed these problems. An improved search algorithm makes it faster and easier to attach lights at the correct position, and the AutoConnect highlighting from Braceworks now provides interactive feedback when inserting lights. When lights are attached to a truss with a hanging angle, they now assume the more precise Z height of the truss. Greater stability of Vectorworks: The improvements in SP3 have made Vectorworks faster and more reliable, especially when working with large files. Changes related to Project Sharing have also enhanced the stability of Vectorworks. Performance improvements: Performance of the lighting device object has notably improved. Depending on the file, Refresh Instruments is up to 50% faster than in 2020 SP2 and up to 100% faster than in Vectorworks 2018. Moving multiple lighting devices in Vectorworks 2020 SP3 finishes in half the time or less than in Vectorworks 2020, Vectorworks 2019, or Vectorworks 2018. Similar results occur when duplicating multiple lighting devices, except when using the Paste command. The Schematic Views workflow in Vectorworks 2020 made plot and model views obsolete. Removing the obsolete functionality has further increased performance, especially for design layer viewports. We are seeing performance improvements with all file sizes. Larger files show significant increases in performance. File open times for ~1,000 lighting devices: 2019 53 seconds 2020 SP2 26 seconds 2020 SP3 16 seconds Creating Schematic Views: 2020 SP2 40 seconds 2020 SP3 20 seconds Changing the view of a Schematic View: 2020 SP2 50 seconds 2020 SP3 25 seconds Moving ~1000+ lighting devices: 2020 SP2 5:00 2020 SP3 16 seconds Duplicating ~1000+ lighting devices: 2020 SP2 5:16 2020 SP3 18 seconds The Vectorworks 2020 Service Pack 3 is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2020, including Vectorworks Architect, Landmark, Spotlight, Designer, Fundamentals, Braceworks, ConnectCAD, and Vision. This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2020. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). To find out more about this release, read the Vectorworks 2020 SP3 tech bulletin. Contact tech@vectorworks.net with any technical questions.
  4. Working from home or remotely often requires resources that are typically stored on an office network or in another location. To limit disruptions, you will want to make sure that you have access to Vectorworks before working in a remote environment. The first thing you need to know is what type of license you own. If your Vectorworks serial number starts with “E” (Series E), you have an online activated license. This means the license must be activated while connected to the internet. There are also a limited number of activations for each Series E license. With Series E licenses, you may activate the software on two machines and only use Vectorworks on one at a time. If you plan on installing Vectorworks on a temporary computer, you will be granted a temporary activation to prevent any downtime. If you are permanently switching machines, you will want to make sure that you uninstall Vectorworks from the previous computer first. Once it is activated online, you can use Vectorworks for up to 90 days without an internet connection. After 90 days, Vectorworks will need to activate again. Keep in mind that any changes to your machine configuration (changing hardware, upgrading your operating system) may force Vectorworks to activate again, even if within the 90 days. *With the ongoing and ever-changing developments related to the coronavirus (COVID-19), we wanted to increase the ease of transitioning to a remote or work-from-home environment. In order to help, we are temporarily increasing the number of activations of Vectorworks Series E licenses by one. We intend to make this additional flexibility available for the next 90 days, while we monitor the situation globally. If your serial number starts with “G” (Series G), you have a network license of Vectorworks. Unlike Series E, this type of license can be installed on any number of machines. However, you will need to be connected to the network that runs the Site Protection Server application to use Vectorworks. If you are working remotely, this may be a challenge. There are a few different ways you can do this. First, you can connect to your office network (whichever network the Site Protection Server is running on) using a VPN. Once connected to the VPN, you can launch Vectorworks normally and find the server on the Login Dialog at the first launch. This will allow you to access Vectorworks for as long as you are connected to the VPN. *For IT professionals, SSH tunneling (port forwarding) is also an option* For professional licenses using Series G, you can also borrow the license if you are unable to remain connected to the network or plan on traveling while working with Vectorworks. The Borrow button can be found in the Login Dialog of Vectorworks. The license can be borrowed for up to 30 days unless otherwise limited by the License Manager. If your serial number starts with "B" (Series B), you will need the dongle connected to your machine in order to launch Vectorworks successfully. To switch computers, just move the dongle to that machine and use the same installer and serial number to install Vectorworks. Temporary License: If you are having trouble getting Vectorworks set up from home, please contact us directly and we will happy to provide a temporary license to get you up and running today. For customers in the United States, contact customerservice@vectorworks.net. For international customers, contact your local distributor at https://www.vectorworks.net/international. Once you have Vectorworks installed and activated, you may need to access files or drawings. These would need to be accessed through Cloud storage or manually transferred from one machine to another. When using Project Sharing, the best way to transition into a remote working environment would be to move the project to a supported cloud solution, like Dropbox. To move your Project File from a local server into a cloud storage solution like Dropbox, it is best to follow these steps: 1. Open your existing Project File(PF) in Vectorworks 2. Using the “Save A Copy As” menu command, save a copy as a PF to your Desktop 3. Create a folder within your local Dropbox folder 4. Move the new PF into that folder 5. Share the entire folder with the rest of the team. *Note- Make sure everyone working on the project has the Dropbox client installed* Working with Project Sharing and Dropbox requires a specific workflow. It is important to remember: 1. Don't duplicate, copy, or rename your Project File. You must use the "Save a Copy As" command to duplicate the file. 2. Turn off Backups (Dropbox provides sufficient history of all changes to the PF). 3. Do not store your Working File in Dropbox. Always save the Working File locally. For more information on using Project Sharing with Dropbox, please click the link below: http://app-help.vectorworks.net/2020/eng/index.htm#t=VW2020_Guide%2FProjectSharing%2FProject_sharing.htm&rhsearch=Dropbox&rhhlterm=Dropbox&rhsyns=
  5. The following are real-world system requirements for running Vectorworks 2020. In some demanding cases, we would suggest a more capable machine than is described in these hardware profiles. Likewise, there are some less demanding situations where Vectorworks will perform well on older hardware. General Requirements: Operating Systems: macOS 10.15 (Catalina) Currently in testing see LINK macOS 10.14 (Mojave) macOS 10.13 (High Sierra) macOS 10.12 (Sierra) Mac OS X 10.11 (El Capitan) * * Not supported by Vision Windows 10 64-bit Windows 8.1 64-bit Windows 8 64-bit Windows 7 SP1 64-bit Minimum Hardware Profile: Entry-level Profile: For small projects, simple models/drawings with a low level of detail, simple renderings (such as small residential projects, small theaters, small landscaping design) Processor: 64-bit Intel Core i5 (or AMD equivalent) or better RAM: 4GB or more Graphics Card: OpenGL 2.1 compatible graphics card with 1GB of VRAM or more Some integrated graphics cards such as Intel Iris graphics are acceptable for simple models/drawings, but a dedicated graphics card is preferable. Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 2GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2060 series, AMD Radeon RX 500 series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM. Display Resolution: 1440 x 900 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Recommended Hardware Profiles: High-end Profile: For large projects, complex and very detailed models/drawings, complex renderings (such as large BIM projects, large entertainment venues, commercial sites, GIS, high-end landscaping design, photorealistic rendering) Processor: 64-bit Intel Core i7 (or AMD equivalent) clocked at 3GHz or better RAM: 16GB-32GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 8GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2080 TI series, AMD Radeon RX 5000 series). Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Mid-level Profile: For medium-size projects, complex models/drawings with a medium level of details (such as small commercial projects, mid-size entertainment venues, residential site modeling) Processor: 64-bit Intel Core i5 (or AMD equivalent) clocked at 2GHz or better RAM: 8GB-16GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 2GB-4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card supporting GL_ARB_draw_buffers extension with 4GB of VRAM or more, preferably released in the past three years (e.g., NVIDIA GeForce RTX 2070 series, AMD Radeon RX Vega series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM, with 3GB or more recommended for large files. Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Network Requirements for Project Sharing Project sharing requires high-speed network connections. As the network bandwidth increases, so does project sharing performance. Slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). LAN Sharing: Minimum: A Fast Ethernet (100Mbit/s) network connection Recommended: A Gigabit Ethernet (1Gbit/s) network connection is required for large projects. Cloud Sharing: Project sharing using cloud-based storage requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Hard Drive: Storing large project files on flash storage (SSD) is recommended. Additional Details Graphics Cards IMPORTANT – Several Vectorworks features have placed higher demands on graphic hardware. Additionally, the performance and quality of the graphics provided by the Vectorworks Graphics Module depend directly on the speed, memory, and supported extensions of the graphics card. These features have the potential to provide a very fast and fluid experience if used on capable hardware, or a noticeably slower experience if used on older or incompatible hardware. Graphics cards should support at a minimum OpenGL version 2.1; cards not meeting this recommendation will have limited functionality and poor performance. In general, the more powerful your graphics card is, the better your Vectorworks experience will be. The amount of Video RAM (VRAM) required to drive Vectorworks adequately depends largely on the size of the display being used and the complexity of the Vectorworks document. Medium-sized displays with a native resolution of 1920x1080 or less should be driven by a graphics card with at least 1GB of VRAM. Larger displays should use a modern graphics card with at least 2GB of VRAM, with 4GB or more recommended. OpenGL rendering of shadows and edges are VRAM-intensive and require at least 1GB, with 2GB of VRAM or more being preferable. If you want to take full advantage of OpenGL shadows and edges, especially in situations where you have any combination of the following: - many lights - point lights - image textures - anti-aliasing - high shadow quality - excessive geometry and if you have a graphics card with less than 1GB of VRAM, you should consider upgrading your graphics card. Using Multiple View Panes with different visibilities in all panes can be VRAM-intensive and require at least 2GB of VRAM, with 3GB or more recommended for large Vectorworks documents. We strongly recommend that all users check that their video drivers are current. The majority of display problems reported to our Technical Support department have been traced to older video drivers. In general, a recent graphics card running the latest drivers is preferable to an old high-end graphics card running outdated drivers. Vision requires a dedicated OpenGL 3.0 compatible graphics card supporting GL_ARB_draw_buffers extension, preferably released in the past three years. We do not recommend any integrated Intel video chipset. While Vision may run under these environments, we do not support them due to their lack of performance and speed. We recommend gaming cards over workstation cards for Vision due to the higher clock speed. For the latest information on our graphics card recommendations and other hardware recommendations, go to the Quality-Tested Hardware page. Vectorworks may be used in conjunction with real-time rendering engines which have their own demanding hardware requirements. For example see Lumion: https://support.lumion.com/hc/en-us/articles/360003476753-Which-graphics-card-do-you-need- Remote and Virtual Machines We do not consider remote login environments such as Remote Desktop, Terminal Services, and VNC or virtual machine environments such as Parallels and VMware to be appropriate for regular work, so Vectorworks performance in these situations is not of primary concern to us. They may be appropriate for administrative testing or utility purposes, and Vectorworks is fully functional in these environments. You should not expect high performance in these environments, however, especially with interactive screen feedback. We do support Vectorworks running under Boot Camp on Mac machines. As long as you have appropriate and current drivers for the hardware on your machine, you can expect fast and reliable Vectorworks behavior. Maintenance Releases Unless there is a known problem with a maintenance release of the operating system, we recommend the latest maintenance release at the time we ship a new release of Vectorworks as a minimum because that is what we test with. If you have problems with an earlier maintenance release, we will often ask you to update as an initial troubleshooting step. Optimizing Performance For users who work with large files and complex renderings, we recommend running with at least 8GB of RAM. When RAM runs out, Vectorworks usually continues to function but is slowed significantly by the need to access the hard drive to provide virtual memory. Extreme lack of RAM may cause operations to generate errors in cases where given sufficient RAM they would otherwise succeed. Faster hard drives can have a large impact on system performance, especially when virtual memory is actively being used. Faster or slower processor clock speeds have a predictable impact on Vectorworks performance. Hard drive size requirements are driven by the total size of Vectorworks, including all content files. You can reduce this size by opting not to install some of the larger Vectorworks content files. Project Sharing and Network Bandwidth The performance of Vectorworks when working on a shared project over the network will depend on the available network bandwidth. If the network bandwidth is insufficient, operations that transfer a large amount of data over the network will be slow. We recommend at minimum a Fast Ethernet (100Mbit/s) network connection. For large projects, a Gigabit Ethernet (1Gbit/s) network is required for a fast and fluid experience. Project sharing using cloud-based storages requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Although project sharing requires high-speed network connections in general, slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). Examples of data transfer times during commit and refresh operations for different bandwidths and project file sizes are shown in the chart below. Project File Size Network Bandwidth (download/upload) Commit/Refresh Data Transfer Time 100 MB 50Mbit/s ~20s 100Mbit/s ~10s 1Gbit/s ~1s 500 MB 50Mbit/s ~100s 100Mbit/s ~50s 1Gbit/s ~5s 1GB 50Mbit/s ~200s 100Mbit/s ~100s 1Gbit/s ~10s
  6. sorry guys...i know you are doing your best, but all that information above about do's and don'ts does not exist for cloud based cad systems...there is no project sharing protocols, nor project sharing w/ dropbox protocols, no dongle protocols...nothing. You just sign in from any device and pow! everything is operational... to place it in perspective..for the time it takes someone to read the above information I can be up an running on a cloud cad system on any device...I just need to type in my email and password...
  7. SP3 is running quite well here. Have been doing al lot of training sessions on it and 1 actual real life project since the mayhem started. There is a thing here and there but I am happy with it now.
  8. How is SP3 running now? I haven't opened a file since my last gig in March. Some torturous version of SP2 was live then—and it was a giant bag of hurt. Just like SP1. And the original 2020 release. And the original 2019 release. And 2018. And 2017. And 2016. 2015… wait, is this a pattern? The video shows the pain of simply trying to dock my toolbars in late February. On one hand, I regularly had design assets move 50-100' without reason, become invisible or entirely disappear from my canvas. On the other, toolbars would sporadically transition from being neatly docked to a random scatter around my workspace. Thankfully, it was always difficult to get them re-docked and organized. I love paying a generous annual subscription for professional software that carries major bugs six months after release. Not that I need the primary design tool for my design business to be reliable. You know what they say… always trust your most important tasks to beta software. With Vectorworks, every release should be considered beta until at least SP4. Losing a day (or more) worth of work on every other project is a rite of passage, designed to create a sense of frustration-based camaraderie within the Vectorworks community. Does anyone else feel the love? Bug Video - Vectorworks 2020 SP2 - Toolbar Docking 20201226.m4v
  9. PVA - Jim

    Project Sharing - FAQ

    This article contains a number of frequently asked questions and answers in regards to Vectorworks 2016's new Project Sharing feature. If you do not find the information you are looking for below, please feel free to contact us directly HERE. -------------------------------------------------------------------------------------------------------------------------- Can I still use layer and resource referencing? When you share project files and use referencing, keep in mind the following rules: -Project files can be referenced into other project files and regular Vectorworks files; resources referenced from the file cannot be modified. -Regular Vectorworks files can be referenced into project files. For example, a symbol library can be referenced into a project file; resources referenced from the file can be modified. -Working files cannot be referenced into any other files; they are temporary files that can be deleted at any time. -Place the reference file in a location accessible by the project file and all users working on the project. -Relative reference paths are relative to the location of the project file, and the referenced file must be on the same volume as the project file. What if I need to leave the network that the project is on? Can I still work on the project? Yes, Project Sharing includes a Work Offline mode in case you need to take a laptop on a trip or you temporarily lose access to the network containing the project file. When in this mode, changes will ONLY be saved to the working file directly and any layers you have checked out will not be available to other users until you reconnect to the project and release them. If Vectorworks detects a loss of connection to the server, it will prompt you to begin working in offline mode. What if I want to see who made certain changes to a project? The History feature within the Project Sharing dialog will let you search not only for users, but by specific layers to either focus on ALL of a specific user’s changes, or to focus on which users made a change to a particular layer. Since you can add comments when checking out layers, editing layers or releasing layers, you can also search this comment history, so including useful keywords in the comment is advised. What should I do if my working file has become corrupted or I can no longer commit to the project file? 1. Do a Save A Copy As (Not just "Save As") of the working file and turn it into a regular VW file. 2. Have the administrator force release the layers that were checked out. 3. Delete your working file (you should have your changes in the "saved as" regular VW file). 4. Create a new working file from the project file. 5. Check out the necessary layers 6. Copy and paste the changed elements from the regular VW file to the new working file. Can I see changes made by other users live, in real-time? Not yet. Currently only after another user Commits changes to the project and you Refresh your working file will you see their new changes. Can a user with Fundamentals use Project Sharing? No, Project Sharing is only available in Architect, Landmark, Spotlight or Designer. Can I convert a Project file back to a regular Vectorworks file? Yes and no. You cannot “convert” a project back into a regular Vectorworks document, but you CAN use File > Save a Copy As (Not just "Save As") in order to create a non-project version of the working file, which from then on will function just like a regular Vectorworks file. The original project can then simply be archived or removed at your discretion. NOTE: Make sure that when using Save a Copy As, you then select the VWX file format to save as, not the default VWXW format: Can I store the project file on cloud storage? Google Drive, Dropbox or OneDrive? Yes, you can put project files (.vwxp) in Google Drive, Dropbox, OneDrive, or Box folders. NOTE: When using Google Drive, keep in mind that Project Sharing is only compatible with "Drive File Stream" if you are using Vectorworks 2020. It will still work with "Backup and Sync" on previous versions. Can I change the permissions for users that currently have layers checked out? Yes, but you should ALWAYS make sure that a user releases their layers and commits any changes before their permissions are altered to prevent a situation where a user is attempting to commit a change in an area they no longer have access to. Can I have more than one working file at once? Yes, but the Layers you checked out are restricted to the working file you checked them out in. A user cannot check out a layer in Working File 1 and then modify that layer in Working File 2. How is my user name determined? This is your computer's login name. If you attempt to access a Project file from more than one computer that you log into with two different login names, you will have to be added to the project file twice, once with each user name. What network permissions are required for users to access the location where a project file resides? Full access. Read, Write, Rename, Delete, Create, etc. Vectorworks uses a “safe save” technique for saving files, in which the previous version of the destination file is maintained until the last possible moment, to avoid potential file damage during save, such as by a hardware or network failure. To support this in a networked environment, permissions must be correctly set to handle the required file operations. In particular, the following two conditions must be fulfilled: 1) The user must have permission to delete files in the destination folder. This is usually the case when the user has write access to the folder. However, some network server configurations using fine-grained control (e.g. with Access Control Lists) may need to be specifically configured to allow this, by assigning “delete_child” permission to the folder. See (https://support.apple.com/en-us/HT201416) for more information. 2) Files created in the destination folder must inherit the permissions of the folder itself. Server installations that use Access Control Lists may need to ensure that “file_inherit” permission is set on the destination folder. (Note: On OSX Server, ACLs may need to be explicitly enabled. See https://support.apple.com/en-us/HT203574 ) What are the system requirements for using Project Sharing? In addition to the normal Vectorworks System Requirements We recommend 1Gbps network connection to the Project file, but 100Mbps will normally suffice. The performance of Vectorworks when working on a shared project over the network will depend on the available network bandwidth. If the network bandwidth is insufficient, operations that transfer large amount of data over the network will be slow. We recommend at minimum a Fast Ethernet (100Mbit/s) network connection. For large projects, Gigabit Ethernet (1Gbit/s) networks are highly recommended for a fast and fluid experience. Slower networks can still provide a satisfactory user experience if operations that transfer large amount of data over the network, such as committing changes to the project file or refreshing a local working file, are kept to a minimum. With OSX 10.9, Apple has made SMB the default protocol for connecting to network shares, moving away from the previous standard, AFP. We have observed some issues with SMB on OSX that cause permissions to be set incorrectly. If you experience problems with saving to a network share, attempt to connect via AFP to see if that solves the problem. From Finder, select Go->Connect To Server. Enter the prefix “afp:” prior to your share address. For example, “afp://myserver.address.net”. How should I start using cloud storage? Best practice: Move your VWX file into the cloud folder and then convert to a Project File. Second best is to move (*not* copy) your PF to the cloud folder. Once the project is there, leave it there, and never make any copies. Bad practice: Making copies, renaming, working on the file outside of Dropbox, or anything else you do in Finder/Explorer.
  10. Vectorworks, Inc. has released its second Service Pack (SP2) for the Vectorworks® 2020 product line. This Service Pack includes the release of ConnectCAD 2020 for Vectorworks Spotlight and Designer. From simple to complex, ConnectCAD allows AV system designers to lay out signal flows in an easy-to-read format. With ConnectCAD customers can: Create schematic drawings Effortlessly make changes throughout the iterative design process Diagram rack layouts Check for errors Create detailed reports Communicate effectively with onsite installation technicians Learn more about our ConnectCAD release at vectorworks.net/connectcad. Additionally, Vectorworks 2020 SP2 offers multiple fixes and improvements in the following areas: Text: Elevation Benchmark size changes Black text in Mac's dark mode Displaying text incorrectly in ConnectCAD Rack frame and Equipment items Align issue with Stage Deck Labels Text issues when zooming in/out text blocks Design Layers: After editing the source file, referenced Design Layer Viewports fail to show walls in OpenGL/Wireframe Design layer viewports not visible in edit Viewport visibilities menu or reverting back to old setup Unable to edit the text in symbols Structural Member Structural Member Settings Dialog with multiple structural members selected Length for Structural Members joined end to end Changing 3D attributes of multiple structural members Truss Previewing incorrectly Truss Cross object is not drawn when value above 1 inch Lighting devices not moving with rotated trusses via control points Video screen not moving with trusses attached Converting 3D Rotated Truss into a Hanging Position shows nothing in Top/Plan view Fixes a memory leak when zooming in/out, causing Vectorworks to stop or crash Auto-rotating image props in Renderworks modes not displaying correctly IES custom lights not working correctly in Renderworks render mode OpenGL viewports render black on Windows when using JPEG compression preference Numerous stability enhancements in several areas such as Property line, Schematic Views, Multi-View, Group selection, Section Viewports, Keynote and Label legends, and Worksheets Additional fixes and improvements included in SP 2.1 Hardscape Section Viewport alignment causing Vectorworks to freeze IFC export: Nested items exporting on internal origin Plants offset issues when changing the user origin offset Data Tags for doors and spaces are constantly changing and replacing upon reopening files Crash using the origin mode of the Flyover tool Additional fixes and improvements included in SP 2.2 - NEW Project Sharing Opening project files in a viewer application Project file and Working file becomes out of sync Checking out objects sync issues Rotation of hatches in Viewports Keynote Legend showing exceptionally large after making any adjustment Crashes after editing referenced IFC settings Working Plane fails to activate by double-click Vision 2020 SP2 This service pack includes multiple improvements and fixes in the following areas: Improvements in how materials (Textures) are transferred between Vectorworks and Vision via My Virtual Rig (MVR). Improved stability merging .MVR files into .v3s Palette positions are not saved Editing items from the scene graph jumps to the top upon completion This Service Pack is available for all licenses as a downloadable updater. To install the Service Pack, please select "Check for Updates" from the Vectorworks or Vision menu (Mac) or Help menu (Windows). For a full list of fixes and improvements in the 2020 SP2 updater, please visit THIS PAGE. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process. Please note this Service Pack is currently available for all non-localized English versions.
  11. The following are real-world system requirements for running Vectorworks 2019. In some demanding cases, we would suggest a more capable machine than is described in these hardware profiles. Likewise, there are some less demanding situations where Vectorworks will perform well on older hardware. General Requirements: Operating Systems: macOS 10.15 (Catalina) macOS 10.14 (Mojave) macOS 10.13 (High Sierra) macOS 10.12 (Sierra) Mac OS X 10.11 (El Capitan) Mac OS X 10.10 (Yosemite) Windows 10 64-bit Windows 8.1 64-bit Windows 8 64-bit Windows 7 SP1 64-bit Minimum Hardware Profile: Entry-level Profile: For small projects, simple models/drawings with a low level of detail, simple renderings (such as, small residential projects, small theaters, small landscaping design) Processor: 64-bit Intel Core i5 (or AMD equivalent) or better RAM: 4GB or more Graphics Card: OpenGL 2.1 compatible graphics card with 1GB of VRAM or more Some integrated graphics cards such as Intel Iris graphics are acceptable for simple models/drawings, but a dedicated graphics card is preferable. Vectorworks with Vision requires a dedicated graphics card with 2GB of VRAM or more, preferably released in the past three years (e.g. NVIDIA GeForce GTX 1050 series, AMD Radeon RX 400 series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM. Display Resolution: 1440 x 900 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Recommended Hardware Profiles: High-end Profile: For large projects, complex and very detailed models/drawings, complex renderings (such as large BIM projects, large entertainment venues, commercial sites, GIS, high end landscaping design, photorealistic rendering) Processor: 64-bit Intel Core i7 (or AMD equivalent) clocked at 3GHz or better RAM: 16GB-32GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card with 8GB of VRAM or more, preferably released in the past three years (e.g. NVIDIA GeForce GTX 1080 series, AMD Radeon Vega series). Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Mid-level Profile: For medium-size projects, complex models/drawings with medium level of details (such as small commercial projects, mid-size entertainment venues, residential site modeling) Processor: 64-bit Intel Core i5 (or AMD equivalent) clocked at 2GHz or better RAM: 8GB-16GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 2GB-4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card with 4GB or VRAM or more, preferably released in the past three years (e.g. NVIDIA GeForce GTX 1070 or 1060 series, AMD Radeon RX 500 series). Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM, with 3GB or more recommended for large files. Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. Network Requirements for Project Sharing Project sharing requires high-speed network connections. As the network bandwidth increases, so does project sharing performance. Slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). LAN Sharing: Minimum: A Fast Ethernet (100Mbit/s) network connection Recommended: A Gigabit Ethernet (1Gbit/s) network connection is required for large projects. Cloud Sharing: Project sharing using cloud-based storage requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Hard Drive: Storing large project files on flash storage (SSD) is recommended. Additional Details Graphics Cards IMPORTANT – Several Vectorworks features have placed higher demands on graphic hardware. Additionally, the performance and quality of the graphics provided by the Vectorworks Graphics Module depend directly on the speed, memory, and supported extensions of the graphics card. These features have the potential to provide a very fast and fluid experience if used on capable hardware, or a noticeably slower experience if used on older or incompatible hardware. Graphics cards should support at a minimum OpenGL version 2.1; cards not meeting this recommendation will have limited functionality and poor performance. In general, the more powerful your graphics card is, the better your Vectorworks experience will be. The amount of Video RAM (VRAM) required to drive Vectorworks adequately depends largely on the size of the display being used and the complexity of the Vectorworks document. Medium-sized displays with a native resolution of 1920x1080 or less should be driven by a graphics card with at least 1GB of VRAM. Larger displays should use a modern graphics card with at least 2GB of VRAM, with 4GB or more recommended. OpenGL rendering of shadows and edges are VRAM-intensive and require at least 1GB, with 2GB of VRAM or more being preferable. If you want to take full advantage of OpenGL shadows and edges, especially in situations where you have any combination of the following: - many lights - point lights - image textures - anti-aliasing - high shadow quality - excessive geometry and if you have a graphics card with less than 1GB of VRAM, you should consider upgrading your graphics card. Using Multiple View Panes with different visibilities in all panes can be VRAM-intensive and require at least 2GB of VRAM, with 3GB or more recommended for large Vectorworks documents. We strongly recommend that all users check that their video drivers are current. The majority of display problems reported to our Technical Support department have been traced to older video drivers. In general, a recent graphics card running the latest drivers is preferable to an old high-end graphics card running outdated drivers. Vision requires a dedicated OpenGL 3.0 compatible graphics card preferably released in the past three years. We do not recommend any integrated Intel video chipset. While Vision may run under these environments, we do not support them due to their lack of performance and speed. We recommend gaming cards over workstation cards for Vision due to the higher clock speed. For the latest information on our graphics card recommendations and for other hardware recommendations, go to the Quality-Tested Hardware page. Remote and Virtual Machines We do not consider remote login environments such as Remote Desktop, Terminal Services and VNC or virtual machine environments such as Parallels and VMware to be appropriate for regular work, so Vectorworks performance in these situations is not of primary concern to us. They may be appropriate for administrative testing or utility purposes, and Vectorworks is fully functional in these environments. You should not expect high performance in these environments, however, especially with interactive screen feedback. We do support Vectorworks running under Boot Camp on Mac machines. As long as you have appropriate and current drivers for the hardware on your machine, you can expect fast and reliable Vectorworks behavior. Maintenance Releases Unless there is a known problem with a maintenance release of the operating system, we recommend the latest maintenance release at the time we ship a new release of Vectorworks as a minimum because that is what we test with. If you have problems with an earlier maintenance release, we will often ask you to update as an initial troubleshooting step. Optimizing Performance For users who work with large files and complex renderings, we recommend running with at least 8GB of RAM. When RAM runs out, Vectorworks usually continues to function, but is slowed significantly by the need to access the hard drive to provide virtual memory. Extreme lack of RAM may cause operations to generate errors in cases where given sufficient RAM they would otherwise succeed. Faster hard drives can have a large impact on system performance especially when virtual memory is actively being used. Faster or slower processor clock speeds have a predictable impact on Vectorworks performance. Hard drive size requirements are driven by the total size of Vectorworks including all content files. You can reduce this size by opting to not install some of the larger Vectorworks content files. Project Sharing and Network Bandwidth The performance of Vectorworks when working on a shared project over the network will depend on the available network bandwidth. If the network bandwidth is insufficient, operations that transfer large amount of data over the network will be slow. We recommend at minimum a Fast Ethernet (100Mbit/s) network connection. For large projects, a Gigabit Ethernet (1Gbit/s) network is required for a fast and fluid experience. Project sharing using cloud-based storages requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. You can expect significant speed improvements when using Dropbox with LAN sync enabled. It is the preferred cloud-based sharing solution for project sharing and is highly recommended for project teams on the same Local Area Network. Although project sharing requires high-speed network connections in general, slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). Examples of data transfer times during commit and refresh operations for different bandwidths and project file sizes are shown in the chart below. Project File Size Network Bandwidth (download/upload) Commit/Refresh Data Transfer Time 100 MB 50Mbit/s ~20s 100Mbit/s ~10s 1Gbit/s ~1s 500 MB 50Mbit/s ~100s 100Mbit/s ~50s 1Gbit/s ~5s 1GB 50Mbit/s ~200s 100Mbit/s ~100s 1Gbit/s ~10s
  12. Project Sharing is a multiuser environment the streamlines project management and execution. It was developed to help Vectorworks users manage projects involving multiple users, fostering effective collaboration and communication within a project team. Project Sharing is a single-file structure providing a mechanism that allows multiple users to work within - and access parts of - a file, simultaneously. This type of multiuser environment offers all team members the opportunity to act together - sharing their knowledge and expertise to the overall design and documentation of the project. It allows for the entire team to think of a project holistically. More importantly, a multiuser environment means a single source of information that can be used for automation and quality checking in drawing production and data extraction - one of the greatest benefits of BIM. This workflow guide introduces the user to the basics of Project Sharing setup, configuration, and use:
  13. Vectorworks, Inc. has released its sixth Service Pack (SP6) for the Vectorworks® 2019 product line. This service pack includes multiple improvements in different areas. Project Sharing Project file being completely blank Editing outdated Title Blocks before refreshing Missing objects in the project file Async issues due to corrupted stairs Data Tags broken associations Fixes to Elevation Benchmark text sizes Fixes to Energos crash when including Roof objects in the calculations Adding IFC4 certification support to Vectorworks 2019 Overall stability improvements in different areas This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2019. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2019 SP6 update, please visit this page. Please note this Service Pack is currently available for all non-localized English versions. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
  14. The following are real-world system requirements for running Vectorworks 2018. In some demanding cases, we would suggest a more capable machine than is described by these recommendations. Likewise, there are some less demanding situations where Vectorworks will perform well on older hardware. General Requirements: Operating System: macOS 10.14 macOS 10.13 macOS 10.12 Mac OS X 10.11 Mac OS X 10.10 Windows 10 (64-bit) Windows 8 (64-bit) Windows 8.1 (64-bit) Windows 7 SP1 (64-bit) Minimum Hardware Profile Entry-level Profile: For small projects, simple models/drawings with a low level of detail, simple renderings (such as, small residential projects, small theaters, small landscaping design) Processor: 64-bit Intel Core i5 (or AMD equivalent) or better RAM: 4GB or more Graphics Card: OpenGL 2.1 compatible graphics card with 1GB of VRAM or more Some integrated graphics cards such as Intel Iris graphics are acceptable for simple models/drawings, but a dedicated graphics card is preferable. Vectorworks with Vision requires a dedicated graphics card, preferably released in the past three years. Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM. Display Resolution: 1440 x 900 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Recommended Hardware Profiles High-end Profile: For large projects, complex and very detailed models/drawings, complex renderings (such as large BIM projects, large entertainment venues, commercial sites, GIS, high end landscaping design, photorealistic rendering) Processor: 64-bit Intel Core i7 (or AMD equivalent) clocked at 3GHz or better RAM: 16GB-32GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card, preferably released in the past three years. Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Mid-level Profile: For medium-size projects, complex models/drawings with medium level of details (such as small commercial projects, mid-size entertainment venues, residential site modeling) Processor: 64-bit Intel Core i5 (or AMD equivalent) clocked at 2GHz or better RAM: 8GB-16GB or more Graphics Card: A dedicated OpenGL 2.1 compatible graphics card with 2GB-4GB of VRAM or more Vectorworks with Vision requires a dedicated graphics card, preferably released in the past three years. Using multiple view panes with different visibilities in all panes requires a graphics card with at least 2GB of VRAM, with 3GB or more recommended for large files. Display Resolution: 1920 x 1080 or higher Hard Disk: 10GB free disk space is required for the installation. 30GB or more is required for a full installation with all libraries. Installing Vectorworks on flash storage (SSD) is recommended. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Network Requirements for Project Sharing: Project sharing requires high-speed network connections. As the network bandwidth increases, so does project sharing performance. Slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). LAN Sharing: Minimum: A Fast Ethernet (100Mbit/s) network connection Recommended: A Gigabit Ethernet (1Gbit/s) network connection is required for large projects. Cloud Sharing: Project sharing using cloud-based storage requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. Hard Drive: Storing large project files on flash storage (SSD) is recommended. Additional Details Graphics Cards IMPORTANT – Several Vectorworks features have placed higher demands on graphic hardware. Additionally, the performance and quality of the graphics provided by the Vectorworks Graphics Module depend directly on the speed, memory, and supported extensions of the graphics card. These features have the potential to provide a very fast and fluid experience if used on capable hardware, or a noticeably slower experience if used on older or incompatible hardware. Graphics cards should support at a minimum OpenGL version 2.1; cards not meeting this recommendation will have limited functionality and poor performance. In general, the more powerful your graphics card is, the better your Vectorworks experience will be. The amount of Video RAM (VRAM) required to drive Vectorworks adequately depends largely on the size of the display being used and the complexity of the Vectorworks document. Medium-sized displays with a native resolution of 1920x1080 or less should be driven by a graphics card with at least1GB of VRAM. Larger displays should use a modern graphics card with at least 2GB of VRAM, with 4GB or more recommended. OpenGL rendering of shadows and edges are VRAM-intensive and require at least 1GB, with 2GB of VRAM or more being preferable. If you want to take full advantage of OpenGL shadows and edges, especially in situations where you have any combination of the following: many lights point lights image textures anti-aliasing high shadow quality excessive geometry and if you have a graphics card with less than 1GB of VRAM, you should consider upgrading your graphics card. Using Multiple View Panes with different visibilities in all panes can be VRAM-intensive and require at least 2GB of VRAM, with 3GB or more recommended for large Vectorworks documents. We strongly recommend that all users check that their video drivers are current. The majority of display problems reported to our Technical Support department have been traced to older video drivers. In general, a recent graphics card running the latest drivers is preferable to an old high-end graphics card running outdated drivers. Vision Pro requires a dedicated OpenGL 3.0 compatible graphics card preferably released in the past three years. We do not recommend any integrated Intel video chipset. While Vision may run under these environments, we do not support them due to their lack of performance and speed. For the latest information on our graphics card recommendations for Vectorworks 2018, go to the Vectorworks Knowledgebase. Remote and Virtual Machines We do not consider remote login environments such as Remote Desktop, Terminal Services and VNC or virtual machine environments such as Parallels and VMware to be appropriate for regular work, so Vectorworks performance in these situations is not of primary concern to us. They may be appropriate for administrative testing or utility purposes, and Vectorworks is fully functional in these environments. You should not expect high performance in these environments, however, especially with interactive screen feedback. We do support Vectorworks running under Boot Camp on Mac machines. As long as you have appropriate and current drivers for the hardware on your machine, you can expect fast and reliable Vectorworks behavior. Maintenance Releases Unless there is a known problem with a maintenance release of the operating system, we recommend the latest maintenance release at the time we ship a new release of Vectorworks as a minimum because that is what we test with. If you have problems with an earlier maintenance release, we will often ask you to update as an initial troubleshooting step. Optimizing Performance For users who work with large files and complex renderings, we recommend running with at least 8GB of RAM. When RAM runs out, Vectorworks usually continues to function, but is slowed significantly by the need to access the hard drive to provide virtual memory. Extreme lack of RAM may cause operations to generate errors in cases where given sufficient RAM they would otherwise succeed. Faster hard drives can have a large impact on system performance especially when virtual memory is actively being used. Faster or slower processor clock speeds have a predictable impact on Vectorworks performance. Hard drive size requirements are driven by the total size of Vectorworks including all content files. You can reduce this size by opting to not install some of the larger Vectorworks content files. Project Sharing and Network Bandwidth The performance of Vectorworks when working on a shared project over the network will depend on the available network bandwidth. If the network bandwidth is insufficient, operations that transfer large amount of data over the network will be slow. We recommend at minimum a Fast Ethernet (100Mbit/s) network connection. For large projects, a Gigabit Ethernet (1Gbit/s) network is required for a fast and fluid experience. Project sharing using cloud-based storages requires a high-speed internet connection (50Mbit/s or above). This method of sharing works best with small teams or small projects. It is not recommended for large teams or large projects. Although project sharing requires high-speed network connections in general, slower network speeds can still provide a satisfactory user experience if you minimize operations that transfer large amounts of data over the network (such as committing changes to the project file or refreshing a local working file). Examples of data transfer times during commit and refresh operations for different bandwidths and project file sizes are shown in the chart below:
  15. SMB on Mac OS has been a moving target, but it is getting better. It is more mature with Mac OS 10.10, 10.11 and beyond. NOTE: AFP is now deprecated as of 10.13. You should only use SMB. Some background information on SMB SMB is Microsoft’s proprietary network file sharing protocol. Most versions of OS X prior to 10.7 relied on an open-source implementation of SMB called Samba for accessing Windows file shares and sharing files with Windows clients. When the licensing terms for Samba changed, Apple had to develop their own SMB implementation. Apple has been struggling with it and it is still not as stable as it should be. Possible Issues with Project Sharing We have not seen any issues with SMB on Windows clients, but have seen issues saving from Windows SMB to Mac OS X 10.11, these issues are not present when saving to 10.10 or 10.12. On Mac OS X, we have seen ACL permissions problems with SMB2 and SMB3 with certain versions of OS X (early 10.9.x). We have not seen the same issues with AFP or SMB1 (“CIFS” protocol prefix). Many SMB issues are related to a mix of SMB protocols between clients. SMB3 (now the default for Mac OS 10.10) could have problems when interworking with machines that don’t have full support for SMB3. Much better results can be expected when all machines were on the same SMB protocol version. We have seen problems mixing AFP and SMB clients for the same share For Project Sharing, our recommendation is: Use SMB for both Mac and Windows. Use the latest version of macOS. Use the same SMB version that works well for all clients. Use the newest OS X version. SMB has version negotiation, so servers can be set to negotiate only up to SMB2 if there are machines that don’t fully support SMB3. Never mix AFP and SMB access to a share. Following these recommendations should provide a better experience. We are all hopeful that Apple will improve the stability of its SMB protocol at a faster pace now that they have made it the default protocol for Mac OS.
  16. Building Information Modeling, or BIM, authoring software, such as Vectorworks®, allows architects and other professionals within the AEC industry to create complex, data-rich 3D models for the purpose of exploring and documenting a design. This continually growing technology also allows for new ways of sharing information among all consultants on a project. As a result, it is essential to establish an agreed-upon method and file format for information exchange between the different disciplines on a team who are each utilizing different software. In some cases, a traditional 2D line drawing exchange, such as a PDF or DWG, is needed to support those who have not entered the 3D realm. Other times, exchange of only geometry in the form of a 3D DWG may be needed for clash detection and as a background for referencing. However, if the file exchange needs to support Building Information Models and the sharing of geometry and data, then the IFC file format should be considered. Download All Project Files
  17. In the attached PDF, we cover both some common questions about Project Sharing, as well as a number of suggested workflows and practices for its use. Introduction_to_Project_Sharing_2017.pdf
  18. The attached document below is an introduction to Project Sharing, along with this video series, provides an explanation of proper use and workflow suggestions.
  19. Vectorworks, Inc. has released its third Service Pack (SP3) for the Vectorworks® 2019 product line. This Service Pack includes not only larger than a normal number of performance improvements, but many new features have been made available to users. New Features: Cloud Presentations via Vectorworks Cloud Services: With the new Vectorworks Cloud presentation feature, you can generate presentations of designs with an intuitive drag-and-drop interface. This unique presentation capability helps to communicate and connect your design ideas with your clients’ expectations, including interactive 360 rendered panoramas that can be linked together to create a holistic, immersive experience, as well as a shareable web link. All that’s needed is an active Vectorworks Service Select membership and Vectorworks Cloud Services. Lumion LiveSync Plug-in: Perform real-time rendering while making design changes in Vectorworks. The LiveSync plug-in is developed by Lumion and is the first partner plug-in to use a new Vectorworks Graphics Sync (VGS) API, that provides live access to the Vectorworks 3D scene and enables third parties to connect the software to any 3D visualization engine imaginable. Lumion and the LiveSync plug-in are available on the PC (Windows) and for English language users on the Lumion website. MVR Workflow from Spotlight to Vision: Discover a better way to work with My Virtual Rig (MVR). The MVR file format creates a two-way connection between planning, previz and console systems that implement the support needed for a seamless workflow. Further, the MVR format contains the 3D model, texturing, position information and GDTF information from the design in Vectorworks Spotlight. Create a more efficient and connected workflow between design planning and previz, merging the iterative changes of the model between Spotlight and Vision without re-importing and redefining the performance cues each time. To learn more about this announcement, read our press release here. Many of the improvements are focused on the following areas: Section Viewports, macOS Mojave, Spaces and the Scaling of Symbols. The specifics on these topics are listed below: Section Viewport: ● Significant speed increase in switching between sheet layers that contain section viewports ● Corrected a large number of redraw problems related to section and edit views ● Section Lines, Elevation Benchmarks and other associated geometry will appear as expected ● Improved the effectiveness of Merge Cross Sections ● Reduced the high number of checkouts needed when using Data Tags in conjunction with Project Sharing and section viewports ● Significantly increased the reliability of section edit and update functions macOS Mojave: ● Users should no longer encounter freezes when selecting Extrude Along Path and other geometry types ● Quality of Pattern export to PDF improved on macOS 10.14 ● Corrected many dialog boxes and other UI graphical issues ● Increased response speed of keyboard arrow navigation in text fields ● Fonts for Wall Data Tags are controlled now as expected Space: ● Direct control over space and label component visibility has been restored ● Creating Space objects should now occur as fast or faster than in prior versions ● Volume calculations corrected ● Corrected a large number of stability issues related to Space objects ● Significantly increased the speed of many operations related to spaces General: ● Scaling of symbols including multiple types of geometry should now work as expected. This was not a single report but a number of related issues and requests. ● Dragging many resources from one location into the Resource Manager to another should now affect all selected resources as expected Rendering: ● Corrected issue that caused grouped objects under the Render tab to become locked ● Fixed many problems related to the display of Roof Face textures ● OpenGL scaling of Wall textures matches the expected appearance as Renderworks does ● A large number of causes for black viewports and missing geometry have been removed or corrected ● Publish should now update rendered viewports on command ● Corrected many issues that would prevent animation transitions between saved views from playing properly Project Sharing: ● Corrected issues that caused Project Sharing to take longer than it should ● Corrected an instability related to text style conflicts ● Speed improvements in certain slower use cases ● Corrected a problem that would prevent the placing of specific object types in Offline files ● Fixed an issue related to symbol replacement in VWP files Spotlight and Vision: ● Fixed an issue where the Instrument Summary could become inconsistent ● Flipped Symbol Edit Mode should now display instruments properly ● Corrected many instabilities related to Hanging Positions ● Load objects can now be attached as expected in 3D views ● Auto numbering should now increment as expected Landmark: ● Improved the responsiveness of site model sculpting highlighting ● Replacing a Hardscape offers the default Hardscape Content as well as content from within that file Architect: ● Stairs should no longer position loci erroneously ● Some stair dialogs are now showing an indicator for values that cannot be calculated ● Walls that did not convert properly from 2018 and prior versions into 2019 should now do so ● Data Tags no longer rotate along with the rotated plan ● Corrected many issues related to custom IFC presets This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2019. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2019 SP3 update, please visit this page. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
  20. Vectorworks, Inc. has released its third Service Pack (SP3) for the Vectorworks 2020 product line. This Service Pack includes: A large number of performance improvements Partner integrations with Enscape and NBS Chorus NBS Chorus is a benefit of Vectorworks Service Select membership Improved performance and quality fixes in Vectorworks Spotlight BCF improvements that offer greater BIM collaboration With an active membership in Vectorworks Service Select, you now have the ability to stylize images with machine learning in the Vectorworks Cloud Services portal Many of the improvements are focused on the following areas: Vectorworks Designer: This Service Pack includes partner integrations with Enscape and NBS Chorus, as well as improved performance and quality fixes in Vectorworks Spotlight, and BCF improvements that offer greater BIM collaboration. Vectorworks Spotlight: This Service Pack includes quality fixes from the reengineering of lighting devices and their Schematic Views, improving file open time and performance. Further, enhanced GDTF support streamlines the MVR workflow. For additional information about workflow and performance improvements in Vectorworks Spotlight 2020 SP3 click HERE. Vectorworks Landmark: This Service Pack includes fixes to the Site Model and Hardscapes. When you place plant objects in your design, it will now show plant tags automatically. Vectorworks Architect: This Service Pack includes partner integrations with Enscape and NBS Chorus, as well as BCF improvements that offer greater BIM collaboration. Vectorworks Fundamentals: This Service Pack includes a new pattern importer from the Mosa Pattern Generator online tool, performance updates, and speed improvements for opening files. Vectorworks Cloud Services: With an active membership in Vectorworks Service Select, you now have the ability to stylize images with machine learning in the Vectorworks Cloud Services portal. NEW Partner Integrations: Real-time Rendering Connection with Enscape for Vectorworks Free Beta: In keeping with Vectorworks’ dedication to integrating new technology that brings direct benefit to customers, we have teamed up with Enscape, providers of real-time rendering and Virtual Reality (VR) solutions. Enscape goes beyond other real-time rendering applications by developing plugins that work directly inside Vectorworks, so users can accurately gauge the impact of their design decisions as they are being made. Enscape is providing a free beta plugin to all Windows users in the Vectorworks 2020 Service Pack 3. The plugin provides a suite of Enscape rendering tools inside Vectorworks which can control the visualization in Enscape. As geometry, lighting, textures, or views are changed or added in Vectorworks, users will see these changes in real-time in Enscape. For easy virtual reality, the Enable/Disable VR Headset tool connects Vectorworks models directly to a VR headset like Oculus Rift S or HTC Vive with little to no setup. NBS Chorus Building specifications integration: The NBS Chorus integration enables users to access and dynamically link their models to the NBS online specification database, keeping the model as the central source of project information. Users will be able to open a web palette in Vectorworks, letting them work concurrently with their model and NBS Chorus. Any data modified in NBS Chorus via the web palette will update in the data record of the model, ensuring accurate and up-to-date specification information is accessible at all times from the model. The NBS Chorus integration is another step in creating a holistic BIM environment within Vectorworks. *NBS Chorus integration is available to users of Vectorworks Design Series products with an active membership in Vectorworks Service Select and an active NBS license. Additional fixes and improvements included in SP 3.1 Esri login dialog box not functional Stairs and plants not showing in NBS Chorus Additional stability improvements This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2020. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2020 SP3 update, please visit this page. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process. To learn more about this announcement, read our press release here.
  21. Vectorworks, Inc. has released Service Pack 4 (SP4) for the Vectorworks® 2019 product line. This service pack includes multiple fixes and improvements in the following areas: Fixed numerous issuesImplemented various corrections for with cropped bitmaps Numerous stability enhancements in areas such as Viewports, Section Viewports, Selecting Walls, Roofs, Extrude Along Path, Project Sharing and more Improved DWG import, IFC Export and export PDF performance This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2019. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2019 SP4 update, please visit this page. Please note this Service Pack is currently available for all non-localized English versions. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
  22. Vectorworks, Inc. has released a minor update in the form of Service Pack 3.1 (SP3.1) for the Vectorworks® 2019 product line. Below is a full list of issues corrected between Vectorworks 2019 SP3 and Vectorworks 2019 SP3.1: · No more repeated alerts during product shutdown · Design Layer Section Viewports and Section Viewport through a referenced Viewport will now show component fills · BIM workflow not working anymore because referenced viewports can’t be sectioned · Section Viewport through a Viewport will now show walls with components · Detail Level for Slabs in Section Viewport will be available · Section Viewports will show objects from Referenced Viewports · Cloud-based project sharing support for Dropbox Business and Box Drive is added · Distance in floating data bar will no longer be stuck on 0 when moving the object inside a Clip Cube This Service Pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2019. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of improvements in the 2019 SP3 update, please visit this page. Contact us at tech@vectorworks.net if you have any technical questions or problems during this process. Please note this Service Pack is currently available for all non-localized English versions. Respectfully, Juan Almansa Customer Success Director Vectorworks, Inc.
  23. When running the Vectorworks Updater, the Update may fail. This may be caused by incorrect permission settings, especially on Mac OS X/macOS. To fix this, try changing the permissions on the Vectorworks 2019 folder, in the Applications folder. Right-click on the Vectorworks 2019 folder and choose "Get Info". At the bottom of the window, you will see "Sharing & Permissions". You should see your current user name listed here, followed by (Me). If you do not see this, click on the + button on the bottom left of the window and add your user name to the list. Once it is added, change the permission to "Read & Write". Next, you will want to make sure those permissions are correctly applied to the items inside of this folder. To do this, click on the Gear icon at the bottom and choose "Apply to enclosed items". Once the permissions are applied, run the Vectorworks Updater again and it should complete successfully.
  24. Is it better for us to switch the sharing to SMB? If you are having issues with your current setup, yes. However its more important to ensure that ONLY ONE protocol is being used.  Why do you choose "full control" and not " Read/write" ? This reduces access problems in general and seems the most reliable.  We have problems with project sharing from time to time, would it be better to grant "Full control" and get less PS conflicts. Yes.

 

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.

×
×
  • Create New...