Jeremy Best

Hi Alex, you can use 'Batch Covert' in the File menu to automatically convert the entire Workgroup Folder from a previous version of Vectorworks (including all sub-folders and files). You'll need to select the applicable settings. See the definition/blurb box at the bottom of the dialogue which defines each option as you mouse over them.

Tech Support in the USA has advised this has been fixed by one of a few different things for different users. They have also confirmed that Vectorworks installers should be compatible with 'dynamic' volumes/partitions, so ignore my prior comment. Previously successful remedies have included: Trying the same installer again Re-downloading the installer. (The same one or a newer Service Pack if available) Extracting the installer using an alternative decompression program. (I've encountered trouble with WinRar in the past where it presented a [different type of] error while extracting a Vectorworks installer, but extracting the same zip with 7-Zip didn't present any issue). Alternatives include: Windows Explorer extraction (Windows default) 7-Zip Please update this thread with what remedy works for you. Thanks!

Hi @bcarrigg90 and @AJ Roslevich, I provide Tech Support for Vectorworks users in New Zealand. Currently I have a Windows 10 user experiencing this issue with Vectorworks 2018 which is highly unusual. We need to know what resolved this matter for you. Can you please tell us what worked for you? Here's what I've confirmed on my user's computer: The installation program doesn't load the default location automatically, but does permit it to be manually selected C drive permissions are the same as mine / should work Program Folder permissions are the same as mine / should work There is 50GB of space available on C drive Antivirus seemingly not interfering (although I won't rule it out. MalwareBytes) Latest, freshly-downloaded SP5 installer still affected Can you please advise what worked for you? @MMajor124 and @Jim Wilson, based on this discussion I suspect this the storage type of the disk/partition might be a factor. See basic vs dynamic storage types. To determine a disk type, open 'Disk Management' and look at the 'Type' column for the applicable volume. I expect the solution will be to format the volume/partition back to the 'basic' type.

Firstly, @Seth Thomas: That was some fantastic sleuthing. I take my hat off to you sir. Really, well done. I've just finished assisting two of our users with this issue. Changing the default compression worked for 'User 1' but 'User 2's experience was a bit different, - for whom: (I avoided running the updater at first (like I did for User 1) so as to determine if updating was a factor) her compression was already on PNG changing it to JPEG then back to PNG didn't work Resetting Vectorworks Preferences didn't work I was going to prescribe updating next but they did a complete uninstall/reinstall before I could and this did work - so it looks like using at least SP1.1 and using PNG as the default compression are both required for the Default Compression setting to have the desired effect.

I'm currently searching my historical Tech Support records for affected users and will attempt to verify if they are still afflicted today/ASAP.

While I've not yet seen any explicit 'green light' on the official discussion dedicated to this topic, the Vectorworks 2019 System Requirements now lists Mojave. One could consider that a 'blessing'… If I needed up upgrade to Mojave, I would first ensure I had a computer TimeMachine backup to restore from should any remaining issues affect my use of Vectorworks.

I would suspect that one of your Option keys is stuck down. Either that or your Vectorworks and/or your computer requires a restart. To test: Go into Finder and click-drag any document. If it gets a green '+' icon next to the cursor then your Option key is stuck down. If so, give each one a flick! I've had a few weird UI behaviours since setting up my new MacBook Pro 2018 and restarting was [all that was] necessary to remedy them.

If the issues you're experiencing are not addressed in the SP2 release notes then it won't make affect your situation. Perhaps they can be addressed regardless of the update. Could you please specify the nature of the issues you're experiencing?

It sounds like you're mixing up Workspaces with Workgroup Folders. Also, assuming you are trying to create a Workgroup folder and have it show up in your Resource Manager: You need to add the location of your Workgroup folder in the bottom section of the 'User Folders' tab in Vectorworks Preferences, not overwrite the path to the User Folder. Some content of your Workgroup folders must mimic the folder names and hierarchy found in your User Folder for Vectorworks to be able to locate applicable resources, e.g. Template files. (See the comment by Jonathan Pickup above for a quick way to create them). Of course you only need to include folders for the resources you intend to put there. Does that help?

I've had one user report the following relating to Undo, but this was on SP1. I couldn't reproduce it on Mac or Windows in SP1 so I'm expecting it was just a random hiccup that a computer restart would remedy. Still, I'm posting it here in case anyone else has experienced it. The user said, "moved a section viewport on a design layer, did a convert copy to polygons, and then tried to undo it – the viewport moved back to its previous position, but the polygon copy wasn’t un-created" Has anyone else experienced this? Please state version, Service Pack and operating system.

Any computer file or parts of the data it is made of - say one or more objects in a Vectorworks document - can become corrupt. In this situation corrupt means the computer code that defines an object has an error in it. One could liken it to the way a typo in a word makes it technically incorrect and dysfunctional. They're not usually caused by user actions, they're seemingly just random and probably caused by hardware hiccups or programming conflicts. Sometimes certain actions on a corrupt object cause it to be 'recreated' and/or 're-written.' In Vectorworks this can be just editing a [corrupt] symbol, or adjusting a [corrupt] wall's parameters, but often importing it into another document is a more likely solution, - if it can be fixed at all that is. This is partly why: Vectorworks recommends autosave is set to: Keep the 5 most recent backups - at minimum. - The more frequently your autosaves occur the higher this figure should be, so you have healthy versions of your objects you can retrieve if they subsequently become corrupt.

You're welcome @mjm! I've demonstrated this process through remote/online support many times before and only just thought of it recently myself! I think I was too busy putting out fires with buckets to think of getting the hose…

That sounds telling. Perhaps one or more corrupt objects. I think you missed this part of Method 2, Step 3: …check the 'Import Layer Objects' radio button

'Method 1' would. 'Method 2' would not.

I provide Tech Support for users in New Zealand. In my experience frequent crashing is not typical and I expect there is something particular to your circumstances affecting Vectorworks performance. When I encounter users experiencing frequent crashing it is usually due to one of the following - in rough order of cause: Cause: Far-Out-Objects Solution: If one or more objects (or your entire drawing/model) are too far from the Internal Origin (distinct from the User Origin) it can cause a wide variety of issues. Crashes can be more prone in some versions of Vectorworks evidently due to changes in how the software handles [hardware] resources which are pushed exponentially harder the further away objects are in any (X, Y or Z) direction. See the attached guided process I wrote to address this scenario. Cause: Graphics card drivers are out of date. (Windows users only). Solution: Update graphics card drivers Cause: Graphics card drivers are corrupt (Windows users only). Solution: Perform a 'clean' installation of graphics card drivers Cause: A Vectorworks system file has lost its mind Solution: Reset Vectorworks Preferences (The process, not the button in Vectorworks Preferences) Cause: Under-powered hardware / Too much demand on hardware Solution: This is very particular to the individual circumstances. Eg. Reduce number of monitors / total number of pixels being powered by your graphics card. Reduce the quantity or complexity of geometry in your file. Cause: Corrupt object Solution: A process of elimination to isolate and delete said object. Rule out Design Layers by deleting them 50% at a time, re-test for issue. Repeat. Submit your file to Tech Support if you need assistance. Cause: Corrupt file Solution: Export it to prior version then reopen in current version. OR Create 'New blank document.' Import all Design Layers including objects (Not copy/paste). Test. Failing this, resort to a backup file. Cause: Anti-virus software has interfered with an installation or update Solution: Uninstall. Download latest installer. Turn off antivirus 'real-time monitoring' or similarly named service. Reinstall Cause: Software conflict Solution: Close all other programs and restart Vectorworks. Test. No better? Then reboot in Safe Mode. Test. Better? Suspect extensions or seemingly 'small' or 'background' apps such as Seagate Dashboard which pretty conclusively caused heaps of crashing for one of my users. Problems GONE once removed. Tech Support Tutorial; Rectifying 'far out objects' - VW2021 & Prior.pdf Tech Support Tutorial; Rectifying 'far out objects' - VW2022+.pdf

We have a localised version of Vectorworks so all installers and updaters need to be generated separately and then tested before they can be released. Check again now. the Aus/NZ SP2 was made live around 2pm today.

Hi @RWSD, these symptoms sound particular to the file you're working on and seemingly not due to the quantity of geometry in it. You could try to search for this yourself or submit it to Tech Support for review/diagnosis and hopefully a fix. My experience suggests it could be one or more corrupt objects. To get this looked at ASAP please submit this issue through Tech Support channels: If you're in the USA: https://www.vectorworks.net/support/help If you're elsewhere: Contact your local distributor or if you're on Vectorworks Service Select submit there for priority attention. If you'd like to try troubleshooting this yourself, here's what I would try: Cleanse The File In-Transition Method 1: Export the file to a prior version Reopen it in the current version. If the problem persists; Open it in that prior version Method 2: Create a 'New blank document' Go: Tools > Organisation > Design Layers > New… > check 'Import Design Layers' and 'Choose…' your file Select all Design Layers > check the 'Import Layer Objects' radio button > click 'OK' See if the issue occurs in this document. This method (2) should only be used if method 1 doesn't work because it cannot import your Sheet Layer contents meaning you'll have to recreate most work produced in Sheet Layers. Check for what I call 'far-out-objects' Far-out-objects refers to the condition where either the main drawing or one-or-more stray objects are massive distances away from the Internal Origin. (Distinct from the User Origin). I'm discovering an every-widening range of symptoms brought on by this condition - which I've found to be one of the most common causes of Tech Support requests I receive. To rectify this condition without guidance requires either a decent aptitude with the Vectorworks interface or a fair bit of tenacity (relative to the severity of the condition). It's a hard process to write a one-size-fits-all set of instructions for but I'm currently trying to do this. I'll attach what I've done so-far for you to try if you wish. If you use it please let me know of any issues or suggestions you have. Tech Support Tutorial; Rectifying 'far out objects' - Written Guide.pdf

You're welcome Jim. Thanks for posting your results!

Hi @annatreg, I note that the build number you're on suggests you might be on SP0, or the first SP1. (They released an SP1.1 for some markets). In the release notes for VW2019 SP1 they mention the following: Section viewport rogue geometry issue should now be resolved. There's also at least one fix relating to Section Viewports in SP2 which has just been released for the main/USA market and will soon be out for other markets. Can you please try applying available updates / Service Packs and then update this thread with what Service Pack got applied and whether it fixed your issue.

Hi Jim, I don't expect 'Save As' to have the desired effect because this just saves the file as-it-is with a different name. You must choose 'Export,' as I did (in Apple's native Preview app) which recreates the content instead. I've since appreciated that Adobe's Acrobat Reader doesn't offer an Export-as-PDF facility so you'll need to find an application that does. Or for users on Windows that have a 'print to PDF' function in your Print dialogue that should work too. (Note: For Mac users reading this, you all have Preview and native 'print-to-PDF' included with your Mac). In the meantime, Jim I'll message you back your PDF that I exported. It works for me on Mac and Windows so please test it and report back here what result you get, - because if it doesn't work for you then something particular is going on that should be diagnosed. Cheers, Jeremy

Hi everyone, ( @Samuel Derenboim, @assemblyarchitecture, @gmm18 and @JCArchitects) I have an interim solution. Not all PDFs are affected by this issue, so I suspect the way they are formatted by the software that generated them is the outside-Vectorworks factor. I have confirmed this issue does not correlate with a PDF's file version. As all PDFs should be compatible with Vectorworks and as it occurs in VW2019 but didn't in VW2018 I'll be submitting a bug report today. On the bright side, here is an interim solution: PDFs exhibiting this issue should all work with VW2019 if you: Open the PDF in a PDF viewer or editor (say Preview on Mac or Adobe Acrobat Reader DC on either Mac or Windows), then Export the PDF as it is / with no changes. (You may want to keep a multi-page PDF entire to maintain context in your records). Then import into VW2019. If the above does not resolve it for you, try a different PDF viewer/editor and please let me know what you encounter. Cheers, Jeremy

Thanks @JCArchitects! I'll PM you my Tech Support INBOX link to obtain your PDF files.

( @twaikin ) I should probably clarify, that as I understand it, they haven't reduced how readily Landscape Area objects update. (That's still an active request, although if they all update fast enough it's probably a moot request). What they did is fix an issue that made the update process of these objects [with particular qualities/size] so slow.

Hi all, I'd like to hear from anyone who has or is currently experiencing this issue in any version of Vectorworks. I've had two users report this, one on Mac, one on Windows, both in Vectorworks 2019 SP1: The first user said Sheet Layer Viewports weren't being affected by alterations to their Class visibility settings, but changing Class visibilities in Design Layers turned off those Classes in all Sheet Layer Viewports instead. The second user only described that: In Design Layer > change visibilities of Classes = Those same Classes get turned off in [all] Sheet Layer Viewports. Restarting the computer was confirmed as a remedy by the first user. Is there anyone else experiencing this? And if so can you please reply including: Vectorworks version and Service Pack Platform and operating system. Cheers! Jeremy

UPDATE: The cause of Landscape Area objects being really slow to update was found by engineers and the issue fixed. It is now 10x faster. The fix is implemented in Vectorworks 2019. @twaikin