jblock

This article is for Windows users with AMD graphics cards only. If you are using a different operating system or graphics card, click HERE. This article is intended for Windows users that currently have a graphics card from AMD. Normally these cards are of the Radeon or Firepro lines. The primary purpose is to troubleshoot desktops and laptops that have both an AMD card as well as an integrated Intel graphics chip that are not properly using the more powerful AMD graphics when Vectorworks is open and a document is viewed in wireframe or OpenGL. These settings will have no effect on the Renderworks modes. As of this article's writing, the AMD Pro Settings can be configured as described below to attempt to force the machine to use the more advanced AMD hardware instead of the integrated (and weaker) Intel graphics: 1) To configure Switchable Graphics settings, right-click an empty area of the Desktop and select AMD Radeon Settings from the menu. 2) Select System. 3) Select Switchable Graphics. 4) In the Switchable Graphics menu, the Running Applications view will be displayed by default. This view lists recent and current running applications and their assigned Switchable Graphics mode. 5) If Vectorworks is not available in this view, click on the Running Applications option and select Installed Profile Applications to view all applications detected by the graphics driver, as shown in the picture below. 6) If Vectorworks is not listed, use the Browse option to locate and add the application to the list. 7) Select the High-Performance mode for Vectorworks and the change will take effect the next time Vectorworks is loaded. High Performance - Selects the discrete GPU, which consumes more power but provides better performance 8 ) Reboot your machine, then launch Vectorworks and check the performance in OpenGL.

Firefox: Beginning with Firefox 68 (released July 2019), Mozilla has protection mechanisms to prevent accessing local files from the browser. Therefore, viewing local Web Views on Firefox 68 and above will not work immediately. Follow these steps to allow local file viewing to work in Firefox. 1. Open Mozilla Firefox and type about:config into the URL bar at the top of the page, and press enter. 2. After going to this URL, you’ll be directed to this screen. Please click the “I accept the risk” button. 3. Type "security.fileuri.strict_origin_policy" in the search bar provided at the top and you’ll find the value we need to change. It should be true by default. Double-click this to change this value to false. Viewing Web Views locally in Firefox should now work. Safari: In Safari 11 (prior versions are fine), Apple has updated its default protection mechanism. For browser protection purposes, the browser can no longer access local files or resources located on a local drive (i.e. any file located within your /Users directory). Therefore, viewing local Web Views on Safari 11 will not work immediately. Luckily, there is a way to allow this to work again. However, you will need to perform the following steps to allow this feature to work in Safari 11. 1. Within the menu bar within Safari, click on the Safari tab, and click “Preferences.” 2. The Preferences menu will now appear. Go to the “Advanced” and check “Show Develop menu in menu bar.” 3. The new “Develop” menu should now appear in the menu bar. Select “Develop,” and then select “Disable Local File Restrictions.” Viewing Web Views locally in Safari should now work. NOTE: This does not apply to viewing Web Views on a server using Safari 11; this still works as expected even with the updates. Chrome/Internet Explorer/Opera: Local viewing is not accessible to users in these browsers. Please use the “Preview” functionality within the Export Web View dialog or use a browser that’s compatible with local file viewing.

When entering your activation key in the Site Protection Server app, you may receive the following alert: “Activation failed, because of unknown error (error code: -148)” This is likely due to permission problems in one of the necessary directories. Check the following folder and make sure the active account has administrative or Read/Write privileges: /var/tmp/vektorworks