Jump to content

Jeremy Best

  • Content Count

  • Joined

  • Last visited

Community Reputation

89 Excellent


About Jeremy Best

  • Rank

Personal Information

  • Occupation
    Customer Support
  • Homepage
  • Hobbies
    Mountain biking. Designing - both processes, tools and products.
  • Location
    New Zealand

Contact Info

  • Skype

Recent Profile Visitors

1,280 profile views
  1. Vectorworks Inc endorsed Catalina for Vectorworks 2020 back in October 2019, so it's fine to expect the software to deliver its advantages. Assuming you have ideal conditions, my answer is, absolutely. I say 'ideal conditions' because there are a myriad of variables that determine how well software performs and the setup and historical maintenance are factors, even if the previous version worked fine. If you want to get a fair sense of software stability and performance, you need to provide ideal conditions and rule out variables that can compromise performance. Of those variables, here's what comes to mind on-the-fly: To get software to run as best as possible; Instead of just upgrading your operating system, erase then install it fresh. - You should expect to do this at least every few upgrades anyway. Account for inevitable data corruption. 1 in 1500 files are corrupt, so: Expect to recreate your resource files at some point. Vectorworks resources and others. Set up perpetual backups so you can recover lost data or turn back time should you identify/experience a corruption. Don't expect a migrated macOS user account to function as well as a virgin one. There's just too many files handled in this process to expect flawless execution. Ensure your system is capable of the task you are executing. Just because the previous version of software did something the current one has trouble with, it doesn't mean the newer software is cause. Which brings me to: Keep in mind that newer software employs newer conventions that older hardware or drivers won't/can't handle. Ensure ALL your OS, hardware, drivers and software are current.
  2. @Eric Chase & @Wesley Burrows, Thanks for sharing your experience. I'm keen to hear what results you get from either completing the Resetting Vectorworks Preferences process, or a clean installation - excluding your Vectorworks User Data and Preferences Folder (at least initially).
  3. The issues mentioned above sound like they might relate to a memory leak reported in this topic:
  4. There are many potential causes of slowdowns, in both software and hardware (as illustrated by the account of Aspect_Design above) so you're best to contact your local Vectorworks Tech Support provider. Just shooting from the hip here, you could also: Test in a new blank document with no other files open and without using any resources you've already created Check for 'Far Out Objects' in the document concerned (see my attached guided process) Try closing all other programs to rule out conflicts Tech Support Tutorial; Rectifying 'far out objects' - Written Guide.pdf
  5. Hi @Jiyoon Kim, Here's one probable and easy explanation… if you're working in OpenGL render mode: Go: View > Rendering > OpenGL Settings… Check the 'Detail' setting. The higher this is the slower your computer will perform, especially as you add more objects/geometry. Medium should provide enough detail without necessarily taxing your computer. But like @Art V indicates, there are many variables that could be at play so the more details you can provide about your file/model and the conditions will help others help you.
  6. Hi @Innes, this level of performance is not typical, therefore a cause or causes should be able to be determined and rectified. Please contact your local distributor for support. Here's a quick (incomplete) list of variables that could be cause or contribute to your symptoms: Hardware resources are being pushed to their limit. (2D objects only or not). In order of likelihood: Insufficient Memory available or the rate of 'swap' is higher than your computer can keep up with. 'Memory pressure,' too high. (Common). Hard drive getting full. (Fairly common). This can compound the above problem. Hard drive getting old/slow. (Rare, so unlikely cause). This can compound the aforementioned memory problems. Given the nature and pattern of your symptoms, I think hardware burdens (above) are the most likely cause for you. I suggest: Open Activity Monitor and keep it visible while you work. Use the Help menu to learn how to appreciate the readouts, but in the Memory tab, Memory Pressure will probably be the most important readout. Other potential causes: Far Out Objects could be present in your drawing/s. (Highly common and affects all CAD programs). - See this post which includes a guide on correcting this condition. One or more corrupt objects. Vectorworks not up-to-date. - If you're not already on Service Pack 6, then that should be your first objective. One or more corrupt resources. Graphics card drivers (macOS) needs to be reinstalled. (I've never had need to prescribe this to-date).
  7. Hi @Andrew Pollock, This page from the Vectorworks Help website explains how to do this. https://app-help.vectorworks.net/2020/eng/index.htm#t=VW2020_Guide%2FSetup%2FSetting_default_object_attributes.htm You can also customise what options are available within the Attributes palette. This is achieved by putting a modified copy of the pertinent Vectorworks resource file into the correlating folder within your Vectorworks User Data and Preferences Folder. The following Vectorworks Help page provides more details: https://app-help.vectorworks.net/2020/eng/index.htm#t=VW2020_Guide%2FResourceManager%2FCreating_custom_resource_libraries.htm
  8. All the considerations, variables and possibilities involved with UX and UI design makes it easy to appreciate why there are designers who specialise in this field!
  9. I don't think so because I know that when I have a collection of objects selected, I want to be able to tell what I'm about to de-select. Especially important when they're overlapping and have similar profiles. I can also see how having no-preselection highlighting would create uncertainty about the selectability of objects that are visible but aren't selectable when Layer or Class Options are set to any option other than Show/Snap/Modify.
  10. @RonMan and @RafaelPernia, Seeing as this PDF hatch-colour issue has occurred before Catalina it's probably not particular to Catalina and the discussion should be moved to it's own thread in the Troubleshooting forum. Given that this issue isn't affecting everyone it's less likely to be a VW bug and more likely to be caused by: Corrupt resources (hatches etc) or Classes brought forward over the years. Something particular to your Vectorworks installations, or [Operating] system setup. The following post might hold the key for your issue, but if not it at least highlights how this kind of result could be caused by something other than Vectorworks: If this matter warrants further collaboration please restart it in the Troubleshooting Forum or submit it to the Vectorworks Tech Support provider for your region or submit a bug report. (See 'BUG SUBMIT' at the bottom of this page).
  11. In our market at least, waiting for SP2 has been the preferred choice of users for whom fewer bugs in the latest versions of Vectorworks is more important than the immediate benefits offered by new features. - 2018 was the first year in many years that the operating system became the primary reason to wait for subsequent updates, due to the lateness and significance of changes introduced in Mojave. I agree it would be great if the release dates could be at polar opposites in the calendar, but as @Pat Stanford pointed out, if Vectorworks, Inc changed their release cycle, they'd be in a difficult situation should Apple change their own release date again. It seems pretty certain that their long, close and interdependent relationship with Apple affords them the early-insight needed to adjust to changes earlier than others. Or maybe it's their massive coffers! 😉 While the proximity of the VW and macOS release dates is a factor in how quickly compatibility can be achieved, the biggest factor for Mojave was the lateness and significance of the changes that developers had to respond to. - Trends indicate this is not something that will occur every year and even if they do, I think Vectorworks, Inc have proven their ability to adjust accordingly to such circumstances, evidenced by the comparatively quick and smooth compatibility achieved with Catalina.
  12. By reducing the opacity of the respective colours, enabling them to combine [when overlapping]. - The Pre-Selection Highlighting one primarily - because it's on top - but making both Selection Highlighting and Pre-Selection Highlighting translucent enables a wider variety of display possibilities, including if you have multiple objects with overlapping edges. Notice the deepening shades of the selection colour of overlapping edges of selected objects in the video.
  13. But what about the following scenario. While I agree with the need for a better implementation I see a problem that would need to be handled at the same time: When you have multiple objects selected (highlighted orange) and you want to deselect one of the two objects… If your proposal is implemented, when passing your cursor over the object you're about to Shift-click to deselect, there would be no preselection highlighting because the object will be showing the 'selected' highlighting colour. There would need to be a third mode of display to differentiate this scenario and I think it might be possible using current settings. I've started experimenting with contrasting colours and opacities and figure contrasting widths, which - alone or combined - might be an appropriate solution. When the two differing-but-translucent colours of 'pre-selection' and 'selected' overlay, they produce a mixed colour indicating an object is already selected. What I haven't found is a set of colours I like. Testing Colour Contrasts & Opacity.mov
  14. I think this is a great idea however I believe it will need to be limited to affecting text only in certain areas to avoid some complications. Because palettes and control windows rely on a somewhat fixed layout in order to make visual sense and maintain relationships between associated controls, increasing the size of text in certain places would shunt all GUI features to the right and/or down, making for some rather troublesome results for some windows. Some places would definitely benefit from this at no risk though, such as the Callout text editor window. You can already adjust the text size for the Smart Cursor text in the Interactive Appearance Settings in Vectorworks Preferences, so perhaps more controls could be added there to enable this capacity for elements that can accommodate these adjustments. You can still get some of the benefits offered by high-resolution screens without ever-diminishing text sizes by either: Altering the (projected) resolution of the display in your operating system preferences/settings. - I recommend this method so long as you don't set the screen resolution lower than that prescribed by the System Requirements for Vectorworks. Or Adjusting 'Ease Of Access' 'Scale and Layout' percent in Display settings on Windows. I have tested and recommend this method. The second of the above options (in particular) might adequately serve the functionality requested here. What do you think @Martin Forsby?
  15. @zorkonius, @B Cox, May I offer you an alternative perspective of the situation with regard to support for prior versions of Vectorworks. This is my personal view based on my 35 year history with Macs and being in the world of Vectorworks in varying degrees since 1997. Vectorworks have not changed how long they deliver support for versions of Vectorworks. Certainly not at least since 2014. Good fortune is the only reason prior versions of Vectorworks and other applications have continued to work on subsequent releases of Mac OS X and macOS, as prior versions didn't receive updates to ensure compatibility beyond ~1 year (same as now). You can see evidence of compatibility issues: In VW2016 (2015 - 2016) on macOS High Sierra (2017): If the 'File > Open' dialogue window is resized it displays solid grey in the new/expanded area). This trend of good-fortune stopped when Apple released macOS Mojave which included major caveats for software developers. Further significant changes have been introduced with Catalina. This situation is similar to other big changes Apple has made in the past all of which warranted adjustments by developers: Moving to move to 32-bit in 'System 7' in 1991. When they changed from PowerPC processors to Intel CPUs in 1994. Replacing their Classic 'System' operating systems with the Unix-based Mac OS X in 2001. Updating the legacy versions of Vectorworks to accommodate these big changes would be costly. Investing resources to enable compatibility would drive up the price of subsequent versions of Vectorworks. For 7 of the last 8 versions Apple has provided updates to their operating system for no more than 1 year after release. You can always remain on prior versions of macOS at no cost - except the cost of missing out on helpful new features and contemporary bug fixes. 'Backwards compatibility' is a seperate matter. It refers to the capability to open files made by prior versions of the software concerned. This capability persists in the current version. Vectorworks 2020 (2019) can open files from the first version carrying this name, Vectorworks 8 (1999).


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...