Once the installation is complete, fill out the registration form with your current information:. Edited November 29, by JimW. Posted September 26, I have copied all the dvd to the root of the ssd drive, but on trying to install the software all I get is the log file below.
Traceback most recent call last : File "InstallVectorworks. But tech support may be able to help. If you do get it to install, pay attention to the version of Quicktime. Posted September 27, You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible. Restore formatting. Medium-sized displays with a native resolution of x or less should be driven by a graphics card with at least 2GB of VRAM.
If you want to take full advantage of shadows and edges, especially in situations where you have any combination of the following:. 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. Vectorworks may be used in conjunction with real-time rendering engines which have their own demanding hardware requirements. 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.
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.
For users who work with large files and complex renderings, we recommend running with at least 16GB 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. Several tasks in Vectorworks leverage multiple CPU cores. Faster or slower processor clock speeds also have a predictable impact on Vectorwork's 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. 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. 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. 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 - especially with interactive screen feedback. We do support Vectorworks running under Bootcamp on Intel Macs. 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.
On Windows, we recommend against updating QuickTime primarily because most Windows users are not aware that Vectorworks depends on QuickTime and can possibly change behavior when QuickTime is updated. We have never had problems, however, which were traced back to bugs in newer releases of QuickTime, so updating QuickTime on Windows is not a risky choice.
Vectorworks runs well and is fully supported in either environment, and we have no known problems in Vectorworks caused by running under a 64 bit operating system. Having said that, the following are also true: -Vectorworks does not use 64 bit addressing and does not benefit from running in a 64 bit environment. Should you choose to run 64 bit Windows you should make sure you carefully choose your hardware and driver versions to avoid problems.
Optimizing Performance: Newer processor architectures often bring substantial improvements in performance.
0コメント