Jump to content

ptoner

Member
  • Posts

    108
  • Joined

  • Last visited

Everything posted by ptoner

  1. Noticing this in Vectorworks 2023 and 2024, don't even need a second screen for this to be an issue WindowServer maxxing out when using Vectorworks is very common in our office of over 40 staff. It is becoming a big issue.
  2. This not an old issue. It is common through all versions of VW. Currently 2021 SP5 on brand new iMac using OSX Monterey 12.2.1. Processor: 3.8GHz 8-core 10th-generation Intel Core i7 processor, Turbo Boost up to 5.0GHz * MEMORY: 64GB 2666 MHz DDR4 * Storage: 512GB SSD storage * Graphics: Radeon Pro 5500 XT with 8GB of GDDR6 memory We have 30+ licences and experience this issue regularly enough. One of the reasons why we moved on ARCHICAD for BIM projects. It continues to happen and is never resolved. If you are wondering why revenue is decreasing, then this is one of the reasons.
  3. Upgrade to the latest version of Mojave, OSX 10.14.6 as there is a specific SMB protocol bug fix. Most of our issues went away after we upgraded the OS and to VW 2019 SP5.3 Try this! https://support.apple.com/en-gb/HT209149 Improves file-sharing reliability over SMB. PS important to note that the server where the files are stored should also be updated to OSX 10.14.6
  4. This issue has been raising its head in our network, now it is a constant issue. Using VW 2019 5.1 and users continually get the .bak and .vtmp files and other associated network issues. They have had this for months through all the 2019 versions. To be honest it is a massive pain everyday for me and the user. Tech Support really need to do more to solve this. I will need to log a call first thing tomorrow when I am back in the office.
  5. Yep, we will be leaving this upgrade until at least service pack 4, going by previous experiences.
  6. So from April to now, Vectorworks have not done anything about or even acknowledged that it is an issue it seems. Excellent support.
  7. This very issue is happening constantly on our network. We have SMB & AFP both enabled as there are massive issues that only MS Office has over the SMB network. So we have to have both on. This only really effects about 20% of our users but is a constant issue. On VW 2019 SP3 &SP4
  8. This is still happening to machines in our office. Where these ever finally addressed?
  9. If you get the spinning again, just disconnect form your network, you problem will instantly vanish. Vectorworks has issues with SMB access over a network. Major issue in our environment of over 30+ staff using VW.
  10. Only way to stop this is to work locally and disconnect from the network you are on.
  11. Didn't solve my issues at all. No difference. The only thing that stops beachballs is copying files to work on locally and then disconnecting for the network /server. Seems like VW is having issues with working over macintosh networks.
  12. Yep, only started playing up this week. Same happens when I select text boxes..
  13. Multiple instances from of Vectorworks 2019 SP 3.1, undocking the Object Info has no effect.
  14. Same issue on a users computer on High Sierra, also happening on Mojave for me.
  15. And also Network issues with your server. SMB or AFP and the naming of shared folders on the networked drive can also cause you beachballs.
  16. It is not a philosophy, it is a coping mechanism. We already have made the change to another CAD/BIM Package.
  17. It will come back, worked for a little while in my iMac also then started up again.
  18. Complete uninstall and reinstall with VW 2019 SP2. On OSX 10.14.3. This is still happening at least 3 times a day when either selecting text or click on a symbol or view. VW2019 is getting beyond a joke now, glad that the rest of the office isn't sitting with this issue. Last Vectorwork that adequately worked, was version is 2018SP6 on High Sierra. When will these issues be addressed without blaming Apple all the time?
  19. 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.
  20. Installed and running OSX 10.14.3 now. Sadly Apples fix list is embarrassingly non existent. https://support.apple.com/kb/HT209149
  21. Through my research, and using a iMac with a boosted graphics card, I am leading towards the GPU being the issue in most cases.
  22. Sound advice it's my first port of call to see what is eating up what resource. Activity Monitor helps narrow down issues very well.
×
×
  • Create New...