-
Posts
12,808 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by PVA - Admin
-
-
20 minutes ago, Sky said:
I would like to upgrade to Mojave, but I still use VW2017 to import Revit kitchen equipment files because importing doesn’t work properly on VW 2018 or 2019. Does anyone know if 2017 works well enough on Mojave to just import a Revit object and save the file?
Same thing is happening in 2019 SP2? I have 6-8 various bugs related to Revit import on the changelist here between 2019 sp1 and 2019 sp2 -
- Popular Post
- Popular Post
I am thankful that I get to come into work every day, have nerdy debates and discussions with the people that design beautiful places and objects, and that I get paid to do it!
- 8
-
- Popular Post
- Popular Post
2 minutes ago, SVA Architects said:Well you are OK then. Keep smug and unhelpful.
A reply like that is not about being smug and unhelpful, it is about confirming whether something is a bug or whether an issue exists on your machine specifically.
I am also unable to replicate this here on 2019 SP2 on macOS 10.14. Do you get that same delay even in a new blank file or just certain ones?
- 5
-
If you restart the machine entirely, then open a new blank document and draw a simple line in it, then try to assign it a pen style from the attributes palette, does it reappear? or remain grey?
If it remains grey, reply back with this as well from your machine please:
-
What version of macOS and Vectorworks are you using? Does it appear the same when you expand the palette?
-
2 minutes ago, Wesley Burrows said:
Has the CPU core limit been lifted?
Checking now, though the engineer I need may already be indulging in some early Thanksgiving turkey. If I don't get an answer today I will recheck Monday. -
48 minutes ago, line-weight said:
given that it can be reproduced on a machine at VW HQ, why has it been allowed to persist into 2019 without any recommendation as how to mitigate it?
Simply because we have not yet found a way to solve the problem. However, this issue was already pulled and listed as a usability priority and engineering is very aware of it. Last I heard there were a few different methods that might possibly solve it, but the bug was not listed as fixed for SP2.
I am still able to replicate it here. The problem doesn't always appear right away, and gets more and more obvious the twitchier you are with the mouse (I am VERY twitchy with my mouse) as the face selection tries too hard to find all the small facets in BIMObjects (or in some cases, other mesh containers) before moving on to highlighting the faces the user wants. The original thought was that we could simply have push/pull ignore BimObjects since they dont really need to be push/pulled anyway, but it was not as easy as first expected to exclude that geometry from the tool's awareness. -
1 hour ago, sarahlizalee said:
Hi,
This is also an issue for me currently as I have re-downloaded vectorworks and input the new licence code however I still get the "Vectorworks cannot be activated because your software license has expired" notice. Is this an issue you someone can help me resolve please?
Thanks,
Sarah
You should now be approved and good to go. Let me know if it gives you any further trouble. -
4 hours ago, Boris said:
Your issue looks to be one that can be fixed by doing the following to set the dedicated GPU for use in Vectorworks, your machine is currently using the Intel GPU:
-
Could you post a screenshot of what you are seeing, please?
-
First make sure to go to Help > Check for updates and let it install 2019 sp2 which was just released recently. If it still crashes during conversion after that however, please send me the file directly and I can take a look.
- 1
-
They may have an older customized workspace that does not include those options. Have them check under Tools > Workspaces > Edit the Current Workspace, under the All Menus tab, and see if they see some of the Project Sharing options available.
-
8 minutes ago, Rob Glisson said:
I have 3 that are Late 2012 that I have been waiting to upgrade. So, I am accepting best options! Currently, we are thinking the new Mac minis.
The reason I mention the other ones is that seemed less expensive than the ones you mentioned ........ I must not have looked very hard!
We also have 2 Late 2014 iMacs and 3 Late 2015.
Well now make sure to check this: I do not think all of those machine will have Thunderbolt 3 connectors, which is the connection standard that I think most or all of these enclosures use. It's the one that uses the USB C port rather than the smaller Mini Displayport that they used to include. Thunderbolt 1 and 2 I THINK can be made to work with these via a series of adapters, but the performance benefits would likely be limited in these setups.Also, since iMacs have their own included display, the issue where eGPU performance improvements didn't appear other than on an external display, and even then in a reduced fashion may occur.
At the moment, I would only personally recommend an eGPU for the MAc Mini, where I saw immediate and very positive performance gains with little to no extra configuration. I'll keep testing with any other models I can get my hands on. I even have an iMac Pro here I'm going to test it with, not that it needs GPU improvement but just to see if I get the expected performance from the eGPU.- 1
-
3 minutes ago, Rob Glisson said:
Those should both work quite well, however they are quite pricey even though their price includes the GPU. The others supported by Apple officially are listed here along with the GPUs they're recommended for:
https://support.apple.com/en-us/HT208544
And if you have an IT guy handy that can install the GPU in the enclosure, you might save some solid cash. However, what Mac are you going to be using this with? I've seen eGPU at the moment working very well with the Mac Mini, but very poorly with a Macbook here in testing so far even though it should be just as good. -
2 minutes ago, cberg said:
VB-154300 Multiple space labels class fix doesn't seem to have made the cut in SP2.
It looks like the fix wasn't complete in time to make SP2, but it is marked as fixed in SP3. It may also appear as VB-156040, a duplicate filing of the same issue.- 1
-
1 minute ago, lvanda said:
Hi!
A week ago i received this message from your Acedemic Team:
"We have not received your proof of enrollment or academic employment to complete your Vectorworks® software request. Without it, your Vectorworks Educational License will expire on (date)."
So I provided this and it seems my account is active (my account status is "new"), but when I open Vectorworks a window pops up saying that "Vectorworks cannot be activated because your software license has expired". I am not sure what I am doing wrong. Any suggestions how to deal with this issue?
Moreover when i'm uploading the proof of enrollment and i'm trying update my profile first it saying "Your account could not be updated.", after that when I go for the second time to update my profile it saying "Notice: Profile updated.", but no picture is visible on my account.
Thank you for your help.
You should now be good to go, let me know if it gives you any further trouble after restarting and launching the application again.- 1
-
1 minute ago, Robin Mair said:
Doing a Check for Updates does not work for me, it just keeps telling me that I have the current version. I have SP1 installed, is there some other way of getting the SP?
It sometimes takes a bit to propagate to all locations. It should either pop up automatically on it's own or show up after running Check for Updates a few minutes after this post. -
Nearly 800 bugs were fixed in 2019 SP2 overall, the above is a summary of only issues that were corrected between 2019 SP1 and 2019 SP2. If you have any specific issues that you do not see here that you would like to know the status of, please let me know or link me to the bug and I will attempt to track it down for you.
-
- Popular Post
- Popular Post
Below is a summary of issues corrected and changes made between Vectorworks 2019 SP1 and Vectorworks 2019 SP2. A full list of all fixed issues listed with their bug IDs can be found HERE.
General:
- Sheet Layers - Extensive quality improvements to appearance when switching layers
- Multiple Drawing View - Significantly increased redraw speed in certain configurations
- Attribute Mapping - Increased stability
- Hybrid Objects - Improvements to stability and quality of Generate 2D from 3D results
- PDFs - Improvements to ungroup results, speed, importing PDFs from server locations, and migration from previous VWX formats
- PDFs - Image Effects should now properly export to PDF in all cases
- Sketch - Viewports should now properly display Sketch results in Foreground Render
- Resource Manager - Multiple fixes related to graphics and redraw after the palette is moved or resized
- Title Block Manager - Corrected a problem where the wrong Active File could be shown
- Viewports - Fixed an issue where Layer Opacity would not appear as expected
- Viewports - Fixed an issue where viewport scaling did not properly affect all contained text
- Viewports - Corrected a problem that could stop Black and White Only from affecting Annotations
- Undo - Extensive fixes related to application stability after performing various Undo-related operations
- Image Effects - Corrected an issue that caused Preview not to function on certain hardware
- Class Overrides - Corrected a problem where some wall component overrides did not always show properly in Best Performance graphics mode
- Data Tags - Extensive fixes to visibilities, linking, viewport interaction, and display of tag geometry
- Data Tags - Should now properly pick up pop-up data fields
- Data Tags - Should now see IFC Entity values as expected
- Offset Duplications should now work as expected in 3D views
- Title Block - When the stacking order of sheets is changed, the order should now update automatically
- Title Block - Conversions from 2018 should now include all text fields
- Title Block - Corrected a problem where editing a title block was unusually slow in some files
- Layer and Class Filtering - Filter button should no longer require multiple clicks to alter its state
- Fillet - Corrected a problem related to Best Performance graphics mode not displaying Fillets
- Xray Mode - Corrected a problem where the OIP would accept B key input erroneously
- Object Info - Fixed a problem that could cause the OIP to become unresponsive until closed and reopened
- Images - Cropped images should now display cropped as expected after being moved or copy/pasted from another locations
- Workspaces - Creating a new workspace from scratch should now include Object Context Menu
- Selection Highlighting - Should no longer flash during viewport renderings
- Import 3DS - Fixed a stability issue related to importing older 3DS files
- Stipple Tool - Increased responsiveness
Rendering:
- Renderworks Backgrounds - Corrected a problem where RW backgrounds would not appear in viewports
- OpenGL - Line thicknesses should now appear in OpenGL as they do in Wireframe
- OpenGL - Textures should now display as expected in OpenGL when viewing mesh objects migrated from 2018
- OpenGL - Should now display Hardscape objects as expected
- Clip Cube - Cube caps should now show as expected in render modes with Edges enabled
- Hidden Line - Extensive stability improvements
- Hidden Line - Fixed significant slowdown in render speed compared to past versions
- Viewports - Corrected a problem that could cause solid white backgrounds when the background should be transparent
Project Sharing:
- Project Sharing - Fixed an issue where rendering in a working file caused significant instability
- Project Sharing - Corrected a problem where unneeded checkouts were required
- Project Sharing - Corrected a problem related to changing referenced PDFs
Marionette:
- Marionette - Corrected a crash related to GetBBox
- Marionette - Corrected a crash related to Get Curve Point nodes
Architect:
- Horizontal Sections - Corrected a problem where objects within invisible containers would still show
- Horizontal Sections - Corrected cut graphics pen attribute graphics in many scenarios
- Slab - Fixed a crash related to Pick Walls Mode
- Slab - Corrected a problem where Textures did not display as expected without nudging or otherwise regenerating the slab object
- Stories - Corrected a problem where editing a Level Type would cause incorrect Z height appearance in Sections
- Section Marker - Fixed a number of cosmetic UI issues
- Section-Elevation Marker - corrected a problem with the first section line inserted did not use the expected defaults
Landmark:
- Site Model - Multiple corrections to sculpting interface and graphical appearance
- Plant Catalog - Corrected an problem related to deleting plants from a custom catalog
- Foliage - Fixed an issue that caused the tool to be unusable on certain hardware configurations
- Plants - Corrected a plant graphic issue tied to using Best Performance graphics
- Landscape Area - Stability improvements
- Site Model - Site Model from Boundary should now display it’s tooltip as expected
Spotlight:
- Spotlight Numbering - Sorting should now be saved across sessions
- Label Legend Manager - Changing the purpose to Right Reading should no longer display improperly
- Load Overview - Hierarchical View button now has correct graphic
- Lighting Device - Fixed a stability issue that occurred when swapping gobos
- Lightwright - Several Undo alerts being triggered erroneously should now be removed
- 6
-
Vectorworks, Inc. has released its second Service Pack (SP2) for the Vectorworks® 2019 product line. This Service Pack includes multiple fixes and improvements in the following areas:
- Heavy focus on correcting issues related to the Undo command
- Numerous stability enhancements in a number of areas such as: Multiple Views, Class Overrides, Attribute Mapping, Project Sharing
- Extensive improvements to VGM display of Annotations, Fills, Textures and more
- Large number of improvements to the behavior of the Data Tag object
- Improved the performance and quality of Generating 2D Graphics from 3D Components
This Service Pack is available for all licenses as a downloadable updater. To install the Service Pack, please select "Check for Updates" from the Vectorworks menu (Mac) or Help menu (Windows). For a full list of fixes and improvements in the 2019 SP2 updater, please visit THIS PAGE.
Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
Please note this Service Pack is currently available for all non-localized English versions.
- 4
-
Article updated today, Nov 20 2018:
- 1
-
16 minutes ago, jgmrussell said:
Hi all, I've been waiting to upgrade my mac os to Mojave until i was sure i could use 2018 and/or 2019. Is there any updates on this? TIA.
John
Expect one shortly.
-
4 minutes ago, Wesley Burrows said:
Reading it again it sounds like you've had the same lower performance under both configurations..... eGPU driving external display, and it just driving the internal display.
Correct, which is what is very odd. I would have expected perfectly fine performance with the Macbook > eGPU > Display configuration, though I'm going to try it lid shut today and see if thats enough to disable the internal display being the primary.
Supposedly when you move the menu bar to another menu in the Arrangement pane of the Display preferences it is supposed to do this, but the performance results I'm getting disagree. More poking. -
You may have Tools > Options > Vectorworks Preferences > Edit > Separate Sheet Views unchecked. I usually leave this on so when I switch back to a sheet layer, it remains in the zoom/pan orientation where I last left it.
- 1
macOS Mojave (10.14) Compatibility
in News You Need
Posted
Unfortunately a lot of people aren't able to fully control where their workload comes from or goes. No reason to argue these points though, all about getting a solution that works for @Sky however it comes.