-
Posts
12,808 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by PVA - Admin
-
-
I am unable to replicate this on 10.14.2 in this file or in a new test document. Did you already speak with support about this directly? Did you uninstall and then restore your workspace or was the crashing happening even in the default ones?
-
If you switch to a different workspace, one of the default ones provided, does the tool crash there as well? Does the same crash happen after updating to the latest macOS 10.14.2?
-
Correct, no two things in Vectorworks can be named the same string of text. This will change in the future, but for now there is no avoiding it.
- 1
-
1 minute ago, gentlegiant67 said:
Since my post I updated to osx 10.14.2, it seems, that solved the problem. Is that possible?
Yes, a large portion of the OS compatibility issues encountered with Vectorworks and Mojave were Apple bugs. -
The 6th and final service pack for Vectorworks 2018 has been released:
This patch brings Vectorworks 2018 in line with Vectorworks 2019 SP2's compatibility with Mojave.
- 1
-
Just now, chrispolo said:
@Jim Wilson Please help 😥
If it is still slow on your hardware, you will likely need to reduce how much of the model you are working with, or use superior hardware. Unfortunately the model was filled with so many complex imported polys and meshes that nothing else can be done to speed it up significantly other than by redrafting the heavier objects. -
Reply back with the following from one of the newer machines youre using and I can take a look:
-
Replied in a private message.
-
3 minutes ago, MikeB said:
I guess my original thread got hijacked by the view-ports turning black issue.
This is indeed what happened, the geometry discussion can continue here now and other issues will be kept separate.
-
We closed it because the problem was indeed solved, but too many similar issues were splitting off and then recombining in that thread.
You are now getting this problem in 2019 SP2 on your machine with files you imported from older versions? -
I asked this way as a means of politely confirming that the issue had indeed been solved. This issue should no longer be present as of 2019 SP2. The issue did in fact end up being a combination of problems coalescing to cause similar symptoms and was not a straightforward fix at all. It even required fixes from MAXONs end in the Cinerender engine, which ended up being why older versions of Vectorworks could not be patched as well.
36 minutes ago, MHBrown said:The digital world does not contain "frequencies." It will do the same thing every time when the same conditions are met.
If this had indeed been the case, it would have been corrected sooner. As much as I would like this line of logic to be true (it would certainly make my job easier) it is not.
-
4 minutes ago, John Whyte said:
How many computers can i install my license on ?
I have three computers, i sync all my files between them using dropbox.
I would like to be able to install VWX on all my 3 machines, obviously i would only be able to run it on one machine at at time.
Is that possible ?
The EULA allows an E series license to be installed on 2 machines and use it on either one or the other at a given time. -
Ah, your version may be heavily customized, I know Computerworks adds different modules and tools compared to the stock version we use here. I would check with them directly.
- 1
-
Just now, Irina said:
Are we allowed to share this in our Spanish Forum? @Jim Wilson
Absolutely.
- 1
-
3 minutes ago, D-VECT said:
Hi Jim,
I am a new Vectorworks user, and I saw your posting and would like to know more about this tool.
Current operating system: Windows, Vectorworks version: 2017, Landscape and in German. I tried enabling this tool but I could not find it where to even look for it.
Do you think you can make a few screenshots to help me out? Thanks!!
Best place to start is likely here:
-
2 minutes ago, line-weight said:
I'm curious whether anything came out of your chat @Jim Wilson?
At the moment, it is limited to finding either Wall objects, or Features in Walls that use the exact same component as the exposed face of the wall is using, but no further. It's in as a wish to expand this ability but there was nothing quick that could be done to improve it. -
8 hours ago, Stephan Moenninghoff said:
@Jim Wilson I think it's gone. I haven't seen it since SP2. Thanks!
I havent seen it so far either and I spent nearly all day yesterday rendering. I am extremely hopeful.- 2
-
There may not be much that can be done here. This is definitely a file that will require powerful hardware, but it looks like these objects were imported. Do you know where they came from originally?
I had thought this was very slow for only having around 8000 objects, but they aren't all extrudes, the stadium for instance is an imported mesh that has 8000 polys on it's own. For the actual number of polys in this file, this is the speed I would expect from it. Rendering in Final Shaded polys, or Shaded Polys, will definitely be slow, those render modes are some of the oldest in Vectorworks and have not been optimized for some time. You can often get a similar look in OpenGL or Renderworks that will complete faster, what style are you looking to get? Image examples would be welcome. -
Light will not be getting any greener. All the issues we could patch have been fixed, but the issues users are having with Mojave and Macs with Nvidia GPUs (Apple hasn't released drivers for them that work well) and the issues theyre having with printers being made compatible with the OS remain, so we didn't want to cheerfully push users to update unless they NEED to for some reason. My production mac here is remaining on 10.13 for the time being.
- 3
-
Are there any additional monitors plugged into that machine or just the internal one? How many Undo operations do you have set under Tools > Options > Vectorworks Preferences > Session?
-
The file size will increase after you render a viewport if File > Document Settings > Document Preferences > Display > Save Viewport Cache is enabled. This setting means you don't have to rerender the viewport every time you open the file, but the cached high dpi image can increase filesize significantly.
Taking a closer look now.- 1
-
22 hours ago, Kevin McAllister said:
I'm sure its related to selection highlighting still being single core.....
You got it. This limitation will indeed be removed and things will become much snappier.
Disabling selection highlighting entirely helps, but I can't personally tolerate just the selection handles unless I'm doing a demo and not modeling things. My first version was Vectorworks 12.5 so I got used to the highlighting in 2008 right away and have relied on it ever since.- 1
-
This looks to be a huge file with a massive number of polys, I would expect it to require serious horsepower to run. Would you be able to send me that file directly? I can test it here and see what may be slowing it down unduly.
- 1
-
Walls on Walls generally works as expected, its when things that aren't walls or things that have the same class/material/fill have a coplanar (coliniar?) edges that it rapidly breaks down. Going to push this a bit more with the engineer tomorrow, we've set aside some time to chat about it.
- 2
Selecting walls crashing
in Troubleshooting
Posted
Absolutely. Since i wasn't able to replicate it here, its very likely this is something that can be corrected for your setup.