willofmaine

Hmm... I don't get that message. Try going to Vectorworks Preferences > Session > Check for Updates (near the bottom) and make sure that "Never" is selected.

Glad I could help calm the Irritation-O-Meter!

You should be able to prevent this without uninstalling. In the Finder, right-click on one of your 2018 files, select "Get Info," and then adjust "Open With" so that VW 2018 is the default for all of your .vwx files.

I don't know... I think they've succeeded admirably in enlisting the widest group possible with the best real-world files for Beta testing... their entire customer base. All of us users. After at least 20, maybe 30 hours with VW 2019, only about 10 of which were billable, I'm back to VW 2018. Excessive crashing was the final straw (and this with a brand new, fresh project; luckily I didn't convert any projects over from 2018).

As it turns out, ultimately, the ability to search may be preferable to having the sub-classes automatically expand, though, absolutely, both abilities would be best!! Unfortunately I say this based on brief use, 'cause I've run, screaming, back to VW 2018. The ability to search in this case is especially effective because as soon as the "Class:" menu is clicked on, the cursor is in the search field, ready for typing without yet another click. It's these little things that make a huge difference in a world where time used to be money, but now clicks are money. Too often, VW requires way too much clicking...

Thanks, Matt! Thanks for confirming & for submitting a bug.

In Vectorworks 2019, the ability to hover over classes in the OIP and see them automatically expand to reveal sub-classes has been dropped(!?!). This is SORELY missed!! Please bring this ability back!!! Soon. With Service Pack 0.5. Thank you. VWIS147

I've had a couple of problems with section viewports. One is that I wasn't getting a single, continuous fill for the cut plane. Turns out there's a new setting in the OIP, "Detail Level," that needs to be set to "Low." Otherwise, in the "Medium" and "High" settings, wall and slab components are shown. Another issue, which I think is a bug, is that if the viewport's section line has a jog, the cut plane fill may partially or entirely disappear... Maybe you're encountering one or both of those issues...

In VW 2019, Viewport Sections with Section Lines that have jogs seem to lose their fill at the section plane. This doesn't seem to always happen; it seems as though it may depend on how the section line relates to geometry in the model. But in complex (i.e., real world...) project files, it does seem to always happen (I'm assuming this is because there's so much more geometry that the section line passes through...). This isn't an issue in VW 2018, where fills are as expected, in all cases. See screenshots; related VW files also attached. VWIS144 03-Fill as Expected in VW 2018.vwx 02-No Fill in VW 2019.vwx

"Refresh Libraries." Who woulda guessed? Anyway, that did the trick, Thank You!

Oh no, are you falling behind? Won't they let you upgrade from 2018 SP3 to 2019?!?

Holy mackerel. Yep. I get the spinning beachball, and it's game over. Oops, actually, didn't have to Force Quit. After a minute or two, the "Replace" dialogue box closes and Vectorworks is back, but with no replacement realized and, further, selected objects don't show in the OIP. Closing and reopening the file resolves objects not showing in the OIP. But it gets weirder - after reopening the file and trying "Replace" again, it still took a couple of minutes, but then I was able to successfully select a replacement symbol and carry on with no (apparent) further issues... Sporadic, inconsistent bugs are my favorite... *sigh*.

Odd, mine says "Story" in that empty column header. I'm guessing Spotlight doesn't use stories? In which case, maybe it's having a bit of an identity crisis; maybe it thinks it's Architect and is looking for stories that aren't there?...

Thanks Alan, this is great. Guess I shoulda searched for "Flip" as well as "Mirror"... I guess the only difference between this and mirror is that you can't define the flip access. And, oddly, unlike the Vectorworks Flip command, this flips about the origin, rather than the object's own center (which, for Marionette objects, may actually be a good thing since, at least so far, I've always wanted to mirror about the origin). Any particular reason that in your "Mirror object (2) v2018.vwx" file you use the "Duplicate Object" node? It seems to work just as well without it (it seems the Flip node always creates a duplicate...). Thanks!

Seems like it's the English language that's the culprit here! Thanks!