Jump to content

koto-in

Member
  • Posts

    8
  • Joined

Posts posted by koto-in

  1. On 11/11/2022 at 4:50 PM, Pat Stanford said:

    Unlikely.  Many of the distributors make tools that are specific to their markets.

     

    But it is possible it will make some future version. The Stair tool was originally created by Computerworks.

    Well, in this case, it's not about a market specific tool, but is rather a question of usability.  The new window tools shine while the existing ones are lackluster at best.  On the other hand, Vectorworks has been owned by Nemetschek for 22 years so perhaps it is understandable that the German version would see new features first.  I just hope we don't have to wait too long.

  2. We have had dozens of users with the issue, I could not say what percentage exactly, but its large. I'd guess upwards of 30% of our Mac population.

    do you agree with this from the zdnet link above:

    "Apple unleashed OS X 10.11 El Capitan just under two weeks ago, and if you've not already pulled the trigger on the upgrade then I suggest you put your upgrade plans on hold until the first update is out unless you like dealing with bugs."

    Yes, very much so. 10.11 doesn't really have any "I MUST HAVE IT!" features for me, so I would completely agree on holding off until 10.11.1 or 10.11.2. Personally I'm sticking with 10.10.5 for now.

    Which means you believe the issue will eventually be resolved on Apple's end?

  3. As of this service pack, Vectorworks 2016 has been made compatible with OS X 10.11 El Capitan.

    Still crashing on launch.

    10/14/15 5:05:38.398 PM Vectorworks[835]: ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to /var/folders/yh/rplw4hh08xl220008k8wx88r0000gp/T/net.nemetschek.vectorworks.savedState

    10/14/15 5:05:45.395 PM Vectorworks[835]: Attempt to load executable of a type that cannot be dynamically loaded for CFBundle 0x7fd5a61743d0 /Vectorworks 2016/Plug-Ins/SketchUpWorker.vwlibrary> (executable, not loaded)

    10/14/15 5:06:00.514 PM diagnosticd[137]: error evaluating process info - pid: 835, puniqueid: 835

    10/14/15 5:06:00.517 PM com.apple.xpc.launchd[1]: (net.nemetschek.vectorworks.135712[835]) Service exited due to signal: Segmentation fault: 11

    10/14/15 5:06:00.559 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[839]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash

  4. So maybe the problem lies in doing a clean install and migrating VW data. Subsequent reinstallation of VW doesn't seem to solve the problem.

    Anyone else having similar experiences with a clean install or updated installation?

  5. No, thats the issue. The problem you're seeing doesn't lie in Vectorworks or its user data, the issue is with the migration of the account breaking your user account.

    You are only seeing the symptoms of the issue in Vectorworks it sounds like, but likely other applications would be affected as well. The account migration in El Cap has caused widespread issues for many users of many applications, its been a pretty messy upgrade this year for Apple, on par with the mess we saw between 10.4 and 10.5.

    In this Os, Apple removed the ability to verify and repair disk permissions, instead replacing this with a live always-on permission correction which actually locks a lot of permissions down that would otherwise have been modifiable in 10.10 and prior. New user accounts start with their permissions all at default settings, so new apps install and function fine on the new account, but cant function on the accounts broken during the OS migration process.

    I'm afraid that all of my other applications are running splendidly and the computer is faster than ever before. It's only Vectorworks that is displaying symptoms and you seem to be saying that the problem lies in the OS. If my user account is broken, how to explain why all my other applications are working fine?

    You seem to be suggesting that because Vectorworks crashes at startup, all applications should be reinstalled in a new user account. The only alternative would be to switch users every time one wants to use Vectorworks. Neither of these scenarios is really acceptable. As I said before, I can only hope that an update will sort this out.

  6. But an uninstall and reinstall of Vectorworks 2016 would/should have wiped out all relevant user data. I also installed VW 2016 on a clean installation of El Capitan so it shouldn't be any different than a new Vectorworks 2016 user starting on a new OS installation.

    Or do you think that it is necessary to uninstall Vectorworks 2016 from Yosemite before migrating all other non-VW 2016 user data to a clean installation of El Capitan?

    I also have older VW versions still on the computer. Could they be playing a role in the crashing? I didn't have any problems with Vectorworks 2016 on Yosemite.

  7. Vectorworks 2016 crashes on opening for me. Reinstalling and deleting preferences did not have any effect. I was only able to work around it by creating a new user as described above. Hoping that SP1 will solve this problem.

×
×
  • Create New...