macOS Mojave (10.14) Compatibility

[JohnAthayde]

2 hours ago, ptoner said:

Still getting this message in OSX.

 

This message is simply stating that the installed Vectorworks 2019 is not a pure 64-bit app. More detail when you click the "Learn More" button, which takes you to:

https://support.apple.com/en-us/HT208436

[ptoner]

Simply stating that after the initial move 10 years ago by Apple, Vectorworks still has not moved completely to 64bit. Add in the impending discontinuation of OpenGL, this is becoming a joke IMO.

Edited February 4, 2019 by ptoner

[PVA - Admin]

I've been getting this for a lot of apps on Mojave, it's them warning about future macOS versions. It does not affect Mojave compatibility at all and it's only detecting some remaining bits of installers and plugins for us.

 

[mjm]

3 hours ago, Jim Wilson said:

I've been getting this for a lot of apps on Mojave, it's them warning about future macOS versions. It does not affect Mojave compatibility at all and it's only detecting some remaining bits of installers and plugins for us.

 

When d'you expect VWX will be entirely 64 bit compliant Jim?

[Kingstone]

Wow!! Someone may have to fly to Germany and have some serious Nemetchek meetings.  Wait, I’ll be in Munich in March, maybe they’ll meet with me and Jim Wilson?  Right!!

[PVA - Admin]

8 minutes ago, mjm said:

When d'you expect VWX will be entirely 64 bit compliant Jim?

 

It is already that. There are just leftover elements that reference 32 bit components and the Apple alert is being overzealous. You could run Vectorworks 2019 on a mac that had no 32 bit capability at all (though currently they all still allow it). OpenGL will be replaced before Apple sunsets it, very likely by Metal or Vulkan.

Side note: When I say "OpenGL will be replaced" I mean it's technological guts, there will still be an OpenGL-like view in Vectorworks we aren't just removing it. We may call it Solid view or something more generic.

[mjm]

Thanks Jim

[Kingstone]

Yes, thanks also. 

[brentf]

i have only one issue, and have been using VW2019 since the day it came out and mojave since the day after it came out.  i know, bleeding edge and all.

 

if i have the object info palette open and [shape] button clicked, and select ANY object with any complex info, door, window, etc, i get a rainbow wheel for about 90sec.  if have the [data] or [render] button clicked, no issues whatsoever.  but if i need to adjust anything and click the [shape] option, it all comes to a halt.  clearly not as bad as some of you, but none the less annoying.  and NO FIX whatsoever with mojave.2, mojave.3, VW SP1, or SP2.  

 

to add insult to injury, my partner sitting next to me with a slightly newer MacBook pro has had ZERO issues since day1 with the same setup.  

 

any ideas welcomed.

[michaelk]

Have you tried running VW in a new user account or in safe mode?

 

 

[brentf]

no.  new mac user account?  what does that change/disable?

[dtheory]

I've had very good results by doing a full uninstall of my original installation of 2019 including ALL preferences and reinstalling from the 

downloadable sp2 installer... obviously if you are a person with heavy workspace customization, this would not be convenient.

I've been holding off on any serious customization until after everything seems to stabilize...

I still get an occasional spinning wheel, but just for a few seconds..  never perma-lock requiring force quit..  YMMV

[SVA Architects]

38 minutes ago, brentf said:

i have only one issue, and have been using VW2019 since the day it came out and mojave since the day after it came out.  i know, bleeding edge and all.

 

if i have the object info palette open and [shape] button clicked, and select ANY object with any complex info, door, window, etc, i get a rainbow wheel for about 90sec.  if have the [data] or [render] button clicked, no issues whatsoever.  but if i need to adjust anything and click the [shape] option, it all comes to a halt.  clearly not as bad as some of you, but none the less annoying.  and NO FIX whatsoever with mojave.2, mojave.3, VW SP1, or SP2.  

 

to add insult to injury, my partner sitting next to me with a slightly newer MacBook pro has had ZERO issues since day1 with the same setup.  

 

any ideas welcomed.

Have you tried turning off every other app - mail, preview, safari, photo, one drive, dropbox etc?  For me it reduced the spinning ball times. Mojave seems more CPU/ GPU/RAM hungry.  Yes it is a pain to reopen and close  other apps but at least you can some drawing done.  Is you partner’s Mac faster/more RAM/more graphics RAM?

Edited February 7, 2019 by SVA Architects

[brentf]

i restarted my computer, opened only VW and tried again.  drew 1 wall and added a door.  select door and rainbow wheel for 20+ sec.  my partner's MacBook is a few years newer but mine is a 2.5 i7 hers is a 2.6i7.  we both have 16GB ram and similar video cards.

[michaelk]

36 minutes ago, brentf said:

no.  new mac user account?  what does that change/disable?

 

It creates fresh new VW user preferences and doesn't load system extensions.  Or whatever system extensions are called now. :-).  

 

 

[SVA Architects]

12 minutes ago, brentf said:

i restarted my computer, opened only VW and tried again.  drew 1 wall and added a door.  select door and rainbow wheel for 20+ sec.  my partner's MacBook is a few years newer but mine is a 2.5 i7 hers is a 2.6i7.  we both have 16GB ram and similar video cards.

Reduced from 90 to 20 secs?  Similar to my experience.  I am still reviewing my options with hardware and CAD software for serious work as my ‘solution’ is only a way to get some work done temporarily. The long term solution rests with the software/hardware providers.  So far I have heard no real admission that there is a serious issue or timeframe to deal with Apple’s new direction with Metal over OpenGL.  There will be more technical rebuttals here but my view of Operating systems and productivity software is that they should quietly serve the brain in the background with few if any glitches not occupy the brain.  I am an architect not a programmer. That is why I chose Mac and Vectorworks years ago over windows and Autocad etc.  

Edited February 7, 2019 by SVA Architects

[brentf]

good points indeed.  i hate the notion of closing photoshop, sketchup, mail, safari, etc just to expedite delays!  i've been using VW since miniCAD6 and honestly this is the most frustrating.i'm in the process of a total uninstall and reinstall of 2019.  along the way i found and trashed remnants from VW 2015, 2016, 2017, & 2018, so hoping fingers crossed something in there helps until the engineers figure it out.  i always (used to?) brag that i use the mac and VW because "they just work"  

[brentf]

well @dtheory i owe you a beverage of your choice.  clean install and voila!  there might be a 1/4 second delay after selecting a door or window now, but no beachball and no interruption of workflow.  THANK YOU ALL SO MUCH.

[JohnAthayde]

6 hours ago, michaelk said:

 

It creates fresh new VW user preferences and doesn't load system extensions.  Or whatever system extensions are called now. :-).  

 

 

 

In application, it helps VW ensure that the bug is in their software and not a conflict between multiple softwares, old versions, malformed preferences files, etc.

 

Your user folder has a hidden folder called "Library" where most of this is stored in either Application Support or in the newer construct of a "container". Over years these can build up and cause slow downs. A new user account doesn't load this stuff, so it's a quick way to narrow down potential causes. 

[brentf]

as part of my complete purge before i reinstalled, i went through the library folder and everywhere else and deleted everything called vectorworks or nemetschek.  clearly something worked.

[Jeremy Best]

Hi @brentf and for the attention of anyone else who is experiencing beach-balling with Vectorworks 2019 on macOS Mojave. I provide Tech Support for customers of the New Zealand distributor, Megabits and have encountered one user with very similar symptoms. (Click something or place something on the drawing area causing beach balling for a long time). 

 

The solution in that case was the widely prescribed process Resetting Vectorworks Preferences. 

 

In an earlier attempt to help this user I experimented somewhat by only retiring their Vectorworks User Folder only and not the complete process above. I tried this because it had been migrated from the previous version which sometimes goes awry in some way that can result in one or more symptoms of differing variety, but as it turned out the full process is what's proven to be necessary. (Creating an additional Mac login/user account effectively creates this same result). 

 

There are a few different items within the Vectorworks User Folder (and hidden Vectorworks system files) that can become corrupt/problematic at random and are responsible for a variety of symptoms. The Resetting Vectorworks Preferences process is commonly prescribed because it quickly deals with all components at once that could be the cause. 

 

While there seems to be an apparent correlation with the adoption of macOS Mojave and Vectorworks 2019 take note that I have encountered these symptoms on prior operating systems and they have often been remedied using the Resetting Vectorworks Preferences process. I'm just pointing out correlation does not equal causation, so Mojave may not be the cause in this instance. But it might... 😜

Edited February 7, 2019 by Jeremy Best
Grammatical Corrections

[rjtiedeman]

I updated to Mojave 10.14.3 and also got a Vectorworks 2019  Library update right after. Now when I open a project from 2 weeks ago the lighting is set very dark. When I need these display 3Ds in the future all the lights will need adjusting up and tested. I estimate it will be at least 1 (non-billable) hour each. Thank you Apple.

 

Also my 3Dconnection still doesn't work unless unplugged. But it does work with 10.14.3 after replug. Note the receiver only works when plugged into the iMac. I will not work plugged into my TSB 3 Docking Station where it's easy to get to.

 

Good news Mac OS 10.15 coming  Sept 19. They are looking for a name.

 

Running Vectorworks 2019 SP-2 (build 463397) iMac Pro (2017) 10 core, 64GB. OS 10.14.3 (18D109)

Edited February 9, 2019 by rjtiedeman
added system information

[Ross Harris]

8 hours ago, rjtiedeman said:

Good news Mac OS 10.15 coming  Sept 19. They are looking for a name.

 

This is perfect I think.....

[RGyori]

On 2/8/2019 at 11:55 PM, Aspect_Design said:

 

This is perfect I think.....

Over the years Death Valley has been one of my favorite places to visit; however, given Mojave's on-going saga, I think any name with "death" in it may be ill advised.😱 

[Jim Smith]

For the longest time Mac OS was using 1960's TV references for the names of their OS. Mojave was the cleanest break with that, & in MHO has been fraught with issues. I would respectfully submit this 1960's TV reference as a name :