PVA - Admin

But anecdotally, when I first started here I thought "Well no one cares what it LOOKS like, as long as it works." and with seasoning and experience and interaction with professional designers, I have learned that this is absolutely not the case. Form and Function should ideally work together, not be subservient to one another.

I think that the concern is we would focus on one to the exclusion of the other, which we will not. Theres also the ever present "X shouldnt be worked on until Y is complete" but again, that doesn't apply since these systems that seem to all be part of a single unit are worked on by very different teams and one is rarely waiting on the other. A lot of the time it can appear as if we had, say 200 engineers, and users will think "Well all 200 should be working on the UI until its great" when in reality, only a dozen or so have the skillset to work on our UI, and then a subset of that group[ are all who can work on it at a given time. Don't let yourselves fall into that mental trap (I do on occasion), we can do quite a few things concurrently and we do not let any engineers sit idle. We are definitely focusing on UI in general at the moment and will continue to for 2020, but the Quality initiative isn't ended as of 2019, it will be carried through.

This happens to you in 2018 SP1.1 and 2019 SP2 still on Mojave, currently?

You should now be good to go, try activating again and let me know if it gives you any more trouble.

Used licenses are normally sold at a discount compared to the brand new ones. It's perfectly fine to buy one from another user here, the only extra step is contacting sales@vectorworks.net just before the purchase so that they can confirm the previous owner and transfer ownership of the license to you.

You should now be good to go, try activating again and let me know if it gives you any trouble.

No that is not normal, email GlobalSupport@vectorworks.net directly, include the email address you registered with and they should be able to get things sorted out for you.

Reply back with the following from that machine please: Also, do you not see any of the render works options, as in theyre not in the menu at all, or are they in the menu and grayed out? Do you see Renderworks listed next to licensed products on the Help > About Vectorworks dialog?

What I am asking is that for any users who experienced this issue (however frequently) prior to 2019 SP1, have you seen it since SP1.1 or since SP2 at all? If it was frequent, did the frequency change after either of these patches?

Pertinent to this thread, a sample of the Summit keynote, time index 38:20 - 43:08: @Ian Lane discussing things we are taking into consideration for UI redesign, not just as far as something like dark mode would be concerned, but more in depth as well.

If you had not seen them already, the keynotes from this years design summit are available for viewing here: Keynote: Antoine Predock Keynote:

The limit is still in place, however some good news: We have not detected any threading-related problems in tessellation, so the engineers in charge of the VGM are discussing removing the limit completely. I will keep an ear on this as it affects a lot of my work as well, and if there ends up being a way to enable more cores prior to an update, (this is possible but only something id push for if we don't plan to simply unlock it in the near future) I will post.

Double checking with them now.

Since it's an older version that wont get any patches, and since that sounds familiar as a bug that's likely been fixed since then: Your best bet may just to be to disable the class of the bitmaps in the section viewport then simply place the bitmaps behind/in front (whichever is appropriate) of the section viewport on the sheet layer directly.

Log in here and make sure you have requested either an extension of your current license or the most recent version if you like: https://student.myvectorworks.net I see no student accounts under the email you used to sign up here on the forum, is it possible you used a different one?

I have no way to confirm this until I can test them together, unfortunately.

So far I haven't found a good eGPU solution for the Macbooks, for some reason even in Mojave, I havent seen the expected speed increases like I saw on the Mac Mini. Mojave claims to be able to boost graphics performance even on the native internal display, but so far in all my tests I see slower performance both in Vectorworks and other benchmark apps, will post more once I find out whats going on.

They will usually send you a link to an upload service so they can properly track it through the regular support channel.

Glad the visibility issue is sorted. No, I would not expect that much of a slowdown between the two versions, but in 2019 there are more settings than existed in 2017 that could be slowing it down unnecessarily. Get that file to tech@vectorworks.net and have them take a look, normally they can find the cause.

Who has seen this issue occur again AFTER 2019 SP1.1 and/or SP2?

If it does not have a dedicated card, that would the precise reason why. We can not guarantee compatibility just because of the cost of user hardware, only it's actual capability. We have much more stringent requirements than other software packages, yes.

What operating system are you on? Which service pack of Vectorworks 2019 are you using?

It's the legacy tech holdover as we transition things to the VGM. Eventually it will be gone and Vectorworks will always use Best Performance. The main two reasons it is still here are 1) for users who insist on using hardware below our recommendations, and 2) to allow workarounds while the VGM is upgraded and polished. We won't get rid of it until there is no longer a need to mess with it at all during troubleshooting and it no longer "resolves" any visibility issues by letting you revert to the old engine.

I see this and a number of semi related roof and roof component attribute issues marked as fixed in SP3, but they were not marked as fixed in time for SP2.

Yes, sorry for the confusion. I sorted them by area of interest, I didn't mean to imply the fixed listed below each category were only for a namesake module.