PVA - Admin

Looks like it has been approved, let me know if it gives you any trouble.

Approved, let me know if it gives you any more trouble.

The issue is that there is NO variable that can be changed at the present time to prevent Vectorworks from freezing in these scenarios. I will test CPU clock speed to see if that can help mitigate it, but it cannot be avoided entirely until we replace more of it's older systems.

Looks like it was approved just recently, retry launching Vectorworks and activating now and let me know if it still gives you an error.

Uh, looks like this wasn't before the migration, the file was just removed. This thread in the archive forum only consists of Zoomers original post, apologies.

Video added to original post as well, just uploaded so may take a second to process:

Oh it's hardware is impressive indeed: https://9to5mac.com/2017/06/14/ipad-pro-versus-macbook-pro-speed-tests/ On the (admittedly few) benchmarks you can run on both ios and macos, the Ipad Pros have been holding their own well. I havent seen results for the latest one, this article is from last year. Honestly it's rapidly approaching or already viable that the ipad hardware could support Vectorworks now, but we of course can't just port it over from macos to ios, the UI would have to be dramatically different on such a device.

Thank you very much! If I can help anyone create awesome products, buildings, landscapes or entire worlds from scratch, I'm more than happy to do so. (While Neil is indeed an employee here now, I assure you he is not paid to tolerate me 😉 )

I didnt get to do ANY of this at the Summit, even though I did do a lot of research and testing for these topics. I thought I was getting a longer chunk of time but I only had time to cover some other things related to lit fog and controlling lighting that I thought would be more pressing. Since these items got cut, I plan to create a few video tech tips on them instead soon.

I had a truly fantastic time at this summit. I spoke and shared a few rounds with @Wesley Burrows, @willofmaine, @michaelk, @Pat Stanford, @Jan-Burger TROOST, @Diego-Resuelvectorworks and at least a half dozen other regulars here on the forum and they were treated to the dubious honor of having me pour words out at them in person. Which I am told is similar to being near a running jet engine. The main complaint I heard from most of the folks I talked to was a sore brain from trying to store all the things they learned, and that they wanted it to last even longer than it did. Which in my opinion, are two very healthy "problems" for an event to have. Once I hear tell of where we might be hosting the next one; I'll try to spill the beans on it at soon as possible 😉 Next time... MORE messy selfies after Old Fashioneds.

I am fairly certain we will be putting the keynote up first and somewhat soon, but I do not know the release schedule for the recordings of the sessions, they may not be public for some time.

JPEG is a smaller more compressed file format, often it can lack colors or definition the other export formats include. However, depending on what you are exporting, the more "lossy" compression formats like jpeg works just fine, because the geometry you are exporting isnt affected by what they cut corners on. I Believe PDFs use PNG images internally by default, but I am not sure. All these files being below 9mb at 300DPI though is fairly normal, unless I am misunderstanding what you're asking about.

You can have it installed on TWO machines and use either machine as long as you don't use both concurrently. There is no PC3 permitted by the license agreement. If you installed and activated on a machine, and then did not open or use Vectorworks on that machine for 90 days, or didn't have internet access for 90 days, that machine would no longer have it's license. It doesn't release it actively, it just expires. However, if you just reinstall windows from an OEM disk (and not install another copy or version of windows from elsewhere), it most likely will not require using up another activation. Normally the activation server can see that the machine is the same one and it will simply refresh the activation and not use up a new one. However, this is a totally normal use case and if you DO hit the activation limit when this happens, you can call in to tech support, we can check the license history and then clean up your activations for you to get you going. In the future we'd rather have a portal so that you can see all your activations and administer them yourself.

This happens when you have two "coplanar" faces, or two faces that occupy exactly the same plane (or in this case, planes AND volume) in your model. This can be solved by lowering the wall heights and using peaks to match the bottom of that roof geometry, or by slicing the bottom of that roof geometry off such that it no longer occupies the same space as the wall. OpenGL effectively doesn't know which face it should be showing, so it attempts to show both which results in this hatched look. The lines are simply because you are in OpenGL with Draw Edges turned on, OpenGL is unable to combine surfaces like Hidden Line and some of the other render modes.

Honestly I would have expected they take the same time, or as you suggest, that the polygons would take more time. That is weird... But yes, from what I understand modifying object parameters (anything from moving a simple pile of things all the way to bulk altering values of a collection of complex plugin objects like Doors) is all controlled by "Core" which is the single thread engine that does all our math and geometry calculations as well.

This is after installing 2019 SP1.1? You can confirm which version youre on under About Vectorworks, latest build for 2019 is 460795. Vectorworks isn't completely compatible with Mojave yet, but I have heard the latest sp resolves most text delay issues.

The fact that it is still two years away and not longer, is precisely because it was given top priority. No matter how high on the list we push it, this was always going to be a multi year project. There is only one team with the know how to work on it at any given time, and then only a few chunks it can be broken up into for individual engineers to work on. We can't go the route a lot of game development companies can go and hire a huge warehouse of contract engineers to plug away at it for 6 months and then be done. I proposed this very thing, and it is simply not possible because of the age, size, complexity and organization of our code base. It didn't come down to a cost of investment or we would have spent the cash happily.

It is indeed confusing. Some of the older portions of Vectorworks are capable to completely utilizing a core... and doing hardly anything with that usage. However you're right, ill do a more modern test (I havent done a practical one since the Intel Core 2 Duo days now that I think about it) and confirm how much of a factor clock speed really is both inside and outside of geometry.

Got it, you should now be good to go. Let me know if it gives you further problems.

Gotcha, thanks for clarifying. This, this is very hard, as Vectorworks is now changing dramatically in which hardware affects what from version to version. So for instance, my answers to the above in 2017 would be completely different in 2019. One machine may stack up more favorably in 2019 but not so obviously in 2017 or vice versa, but this is just because im one guy testing things in my little mad scientist lab of an office. As Vectorworks' guts are more modernized and as we get our hands on more hardware, we will have better and clearer answers for you for the critical day to day performance of certain hardware configs.

If Apple would freaking finally resume selling one, id push users to buy it. My main motivation with this eGPU testing is that it really, really, really seems like Apple wants to make everyone use eGPUs so that they can still make slim/tiny/aesthetically pleasing devices at the cost of performance. Theyre happy forcing users to carry half a dozen dongles everywhere with their laptop, so it would really not surprise me at this point if the new Mac Pro was just a glossy black sphere with 4 usbC ports that they expect you to plug eGPUs, displays, and dongles of all sorts into. I dont WANT them to do that, but it's looking more and more like they might, so im preparing information to support users if that eventually happens. I would LOVE to be completely wrong and for them to release a new modifiable, professional chassis that could last users another full decade, and if that happens i will gladly toss all this prep work in the trash.

Typo on my part, they are 194 and 198 not 104 and 108 for both. Apologies, fixed in the database as well.

If there was hardware you could lay hands on that would cut even 20% off the time of sectioning and other geometry-heavy things like site modeling, I would be text-shouting it from the virtual hilltops. If I DO find that to ever be the case (before we get the geometry calc modernized,) you can be sure that I will make it very difficult to avoid hearing me talk about it 😉

Yes, thats the geometry phase choking and not letting your computer flex it's full muscle, thats normally the fault of Vectorworks older code we havent yet replaced. The 4 core limit for more rapidly offloading things from older single threads to multiple threads is set for now and wont change until stability catches up to the new tech. However this just means a 4 core or higher CPU will be faster for Vectorworks general drafting than a 2 core or lower CPU, with clockspeed being much less of a factor than core count.

If you mean SECTION viewports on sheet layers, i suspect theyd be the same or in near-as-makes-no-difference territory, ill set up a clearer test later on but it can be hard to get 2 CPUs from the same generation where the only difference is the clock speed, ill see what i can get my hands on.