JimW

Forum Administrator
  • Content count

    10,184
  • Joined

  • Last visited

Everything posted by JimW

  1. The 2017 Design Summit is on the calendar! September 18th through the 20th, 2017 at the Baltimore Marriott Waterfront Hotel, 700 Aliceanna Street, Baltimore, MD. You can sign up HERE to be kept informed of the details as they become public. I would also very much appreciate you visit THIS PAGE and click the "I Have an Idea" button, and choose which of our proposed topics that you would want to attend a session for. If you don't see what you want on the list, please add it. The breakout sessions are not yet set in stone, so now is the time to speak up! This year we elected to double down on the time spent preparing training materials and content for you to enjoy that include new features we plan to add in Vectorworks 2018. Also, this time we picked a venue much closer to our offices in Columbia MD, so it'll be even easier for us to bring more of our people to meet you all, share a few drinks, enjoy delicious food, and answer your questions.
  2. In what may very well be a record in bug report response speed, this issue is slated to be fixed. Most likely in SP2 but i'll see about getting it moved to SP. (In all honestly however, I think engineering may decide to focus on a number of issues related to the Title Block first which I would completely understand.)
  3. That menu is set to edit the Design Layer (Direct Section editing is new in 2018) not to edit the crop, the same options do appear above. That however seems separate from the issue itself.
  4. This looks like a customized workspace, as those items are normally in View > Standard Views. I recommend removing the items or item set via the workspace editor and then re-adding them.
  5. I was able to confirm this during the Summit on 2018 SP0 running on Windows 10, along with some other Floating Data Bar issues. Someone (possibly Patrick) beat me to filing them.
  6. For Design Layer Viewports, it works, showing the rest of the model in grayed wireframe when editing the crop object, with darker wireframe within the crop. However, on a sheet layer, the "Other Objects" being shown when i toggle the setting seem to be the other viewports on the sheet layer but not the rest of the model contained in the viewport im actively editing. I just tried the same test in 2017 and got the same result. This seems unfamiliar but I'll confer with the techs and see what's going on or if I simply never noticed the change before.
  7. Just tested here on a fleshed out file and no, it is not working as expected. It isn't completely nonfunctional but it's behaving differently than I remember. Checking now.
  8. Should be controlled under Tools > Options > Vectorworks Preferences > Display > Show Other Objects while in editing modes.
  9. I'm PRETTY confident in calling this a bug, I was able to replicate immediately. Same behavior with a 3D poly, the other other 3D objects I know of that an both be affected by the Offset tool as well as have a texture. 2D objects always keep their fill and pen attributes when being offset, so I would expect 3D offsets to do the same with textures. Submitting as a bug now. VB-145794
  10. Just had the chance to formally file this. VE-98254 Going to catch up on many others in the coming weeks as well.
  11. Would you mind sending me that file? The Site Model on it's own in a test file would be perfectly fine. Feel free to direct message it to me if you do not want to post it publicly.
  12. E series licensing (The standard pro type) is the same for both Mac and Windows. I am fairly confident this is now globally how it is handled, but if you are located in the UK then yes the license should work for either, you'd just need different installers. I would say from personal experience, Windows tends to have more, but smaller and easily fixed problems, whereas some Mac problems are fewer but can be unfixable because of OS updates. However, this trend seems to be changing and genuine bugs (ie not a problem that turned out to be operator error) tend to more and more often be cross platform. (I do want to take a look at the analytics to see if my personal impressions match the concrete data, but I have a few items to tend to from the last week that I need to clear up first.)
  13. If you're using more than one 1080p display or a single 4K or other high res display, I suspect you will see a significant improvement. The 600 series was powerful at the time but its lower VRAM allotment really hinders it today. If you like, send me the file and I can show you how it will perform on more recent hardware in a video before you make your decision.
  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.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. Instantaneous replication of the issue in the file, submitting this as a bug now. There are a few already submitted semi-related to this but not with such clear cut examples, thank you! VB-145786
  16. File > Print > Print PDF is doing this? Does the regular File > Export PDF do this as well? When you're doing the actual physical print, what application are you opening the PDF in? Acrobat, Adobe Reader, Preview?
  17. If you save the files from either of the Macs onto the mac desktop, transfer the files to the windows machines desktop and attempt to open it, what occurs?
  18. Article updated as of September 13th, 2016. A graphics card or "GPU" is an essential component of any computer that intends to run something as visually intensive as Vectorworks. This dependency will only increase with future versions of Vectorworks relying more heavily on GPUs. One of the most common causes of odd behavior or instability in Vectorworks encountered by Technical Support are due to users working with insufficient or outdated hardware. To help remedy this, below you will find a list of graphics cards recommended by Technical Support representatives: Graphics cards are currently produced mostly by two companies; Nivida and AMD. The two product lines that you should consider most closely are the GeForce and R7/R9 series from each respectively. These cards are normally marketed as being for gamers, but they work excellently with Vectorworks. These companies also offer a Quadro and FirePro line of cards marketed towards CAD professionals, but these cards are very often overpriced and have poorer driver support than their gaming counterparts. Nvidia: GeForce GTX 1080 GeForce GTX 1070 GeForce GTX 1060 GeForce GTX 1050 Ti GeForce GTX Titan X GeForce GTX 980 Ti GeForce GTX 980 GeForce GTX 970 GeForce GTX Titan Black GeForce GTX Titan Z GeForce GTX Titan GeForce GTX 780 Ti GeForce GTX 780 GeForce GTX 770 GeForce GTX 760 Ti GeForce GTX 760 GeForce GTX 750 Ti GeForce GTX 690 GeForce GTX 680 (Note: the "M" or mobile versions of these cards are significantly less powerful than their full desktop counterparts.) AMD: RX 480 RX 470 RX 460 R9 Fury X R9 Fury R9 Nano R9 390 R9 380X R9 380 R9 370 R9 295X2 R9 295X R9 290X R9 290 R9 285 R9 280X R9 280 R9 270X R9 270 R7 265 R7 260X R7 260 R7 250X R7 250 R7 240
  19. It is my great pleasure to share with you what we've been working on: Vectorworks 2018. This release was a bit unusual in that it turned out to be a number of large features and scores of small features intermixed, with very few in between. Many of you reading this may have already had a look at what was coming in the Teaser Tuesday section, but for any just joining us: https://forum.vectorworks.net/index.php?/forum/71-teaser-tuesdays/ There we cover the features in a good bit of detail and branch out a bit in a number of discussions, definitely worth a look if you haven’t read through them already. Below, the official launch commercials for Vectorworks 2018: Then we have the more focused feature videos about some of the more important or otherwise impactful features included in this release: Finally, in the below post, a comprehensive listing of user-facing changes that didn’t make it into the marketing material, but that you may find important and useful nonetheless. I am now free and clear to discuss any and all parts of Vectorworks 2018, ask away!
  20. I can check after the Summit is over. Apologies, no access to the tracking system from here.
  21. For the Facebook wary, there should also be a stream on our page: http://www.vectorworks.net/design-summit
  22. Email Tech@Vectorworks.net and reference this thread, they should be able to take a look and see what machines were activated and get you sorted out.
  23. Whereas Web View let you send an OpenGL representation of your drawing to clients and coworkers, it is now possible to render out a complete 360 degree view from within Vectorworks, using Renderworks modes. To create a rendered panorama, first set up your view the way you want the panorama to appear. This can be from a saved view with class and layer visibilities included, or you can set these up manually right before export. The rendering mode you are currently in and the resolution of your drawing area won't affect the export, these are controlled in the export settings. Under File > Export, select Export Panorama. You will be able to export the file locally or to cloud storage, and if you choose to store it on the cloud, you can get a direct link that will let viewers view your panoramic render natively in a browser. Since you get the link immediately a placeholder OpenGL version of your rendered panorama will appear first if users access the link before the Renderworks rendering is complete: OpenGL Preview: http://bit.ly/2ulQI9z Rendered view: http://bit.ly/2ulGjH2 If you choose to open the resulting panorama JPG directly from local storage, you will see the distorted perspective image, similar to those used in Renderworks Backgrounds. To view it as a 360 panorama, you will need to open it in a compatible viewing application on your desktop or mobile device, or upload it to a service that provides one on the web, like Facebook. Anyone who has created a Vectorworks Cloud Services account will be able to store their 360 pano on the cloud and share their links with anyone, but you will only be able to process files on the cloud if you are currently subscribed to Service Select.