Jump to content

Search the Community

Showing results for tags 'project sharing'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 31 results

  1. Hi everyone. I wonder if the following is a bug. When working on a shared project, despite of diligent save and commit / close and release / refresh usage, we find the following: If someone duplicates a sheet layer, or changes the name of a sheet layer, the project management somehow cannot keep track of this - the sheet layer numbers and names don't match anymore. Please see the screenshot below. The highlighted area indicates where the numbers and names are wrong. It's not in English but one can see the difference. Trying to update, reopen etc. will not solve the issue. This particular project is not using automated title blocks/drawing coordination, but simple hand-written sheet numbers and names. The only thing that puts the project sharing sheet list back on track is temporarily saving the project as .vwx file and the re-sharing it.
  2. We are a UK based small sized office of 12 architects. Our computers are all Apple Macs, most of them are 2-year old with OSX Yosemite. I attach a screen grab of a system report which roughly covers our hardware background. Vast majority of our projects are run under Project Sharing. After a few service packs we found VW 2016 quite smooth and stable to use but since we have upgraded to VW 2017 with SP2 we have been experiencing many crashes and general instability. Just in January at least five of our projects suffered from numerous crashes. My colleagues have been constantly reporting problems ever since. Some of this projects had started in VW 2016 and were updated later to 2017, some of them were started from scratch in VW 2017. This does not seem to matter. We also have further projects to be upgraded to 2017 but at this stage we decided to pull up the handbrake instead. We also got in contact with the local Vectorworks Support Service as usually. They helped us out a lot in previous cases but currently it seems like they have become too busy and are not able to respond on time. I afraid we cannot afford a week - or even more - delay in response, if we get any at all… Our last two requests have not been answered by the time of this post, although they were issued on the 25th and 30th January. Having look at the request ID numbers, they must have received about 60 (!) requests from others within three working days. The increasing number of these requests also concerns us although I must admit that I do not know how many of these they receive usually on a daily basis. As things stand we are not sure whether we are having local issues with the software or there are general problems. Besides, any problem with project sharing seems utterly complex to identify. I do not think that we are able to send over our files to the Support Service every time and wait until they come up with any working solution. Sometimes they just send us back a fixed file by their engineers without any explanation what went wrong. I am not sure in that how we could prevent further issues then. I’d had 10 years of work with ArchiCad before I started using Vectorworks about three and a half year ago. The methodology of project sharing is almost identical which at least made it easy to understand how it works. However the stability of this function since it has been introduced in VW is rather divisive. Every time a new service pack is being introduced we are quite tentative whether we should upgrade or not. Sometimes previous issues simply re-incarnates and the software becomes unstable again. You never know. I thought I would share our experience which might draw the attention of other users who might have similar issues or alternatively it can be confirmed that this must be a separate and local problem only within our office if no one else finds VW 2017 unstable. All comments are appreciated. (Is there a new service pack in the pipeline maybe?)
  3. I finally installed 2017 on my laptop because I have some clients that have fully committed to 2017, and the main reason is the project sharing over a cloud drive. This is only the 2nd file I've worked on. I had already clicked on "Save and Committ" so hopefully everything actually saved. When I clicked on Close and release VW crashed. When I reopened the file I got this error message. So WTF? Did my changes actually get saved to the master project file? Has anyone else had this issue or am I special?
  4. I use VW Architect in a small design office where we are often project sharing with large files. Using iMacs and a Mac mini server, VW2017. 600MB connection to both server and internet. We've had a lot of problems with crashes when we keep the project file on our server when committing changes. We solved this by using dropbox instead. Although there is an added lag time going through the off-site dropbox server, we aren't getting the crashes as the committed changes happen on our local machine before being uploaded. We're thinking of implementing this throughout the office, but before we signup for dropbox business, etc. I wanted to ask if anyone else has reached a similar conclusion, or if anyone has experience of dropbox project sharing and could offer some pros and cons. Would appreciate any advice, thanks.
  5. @JimWWe work in a remote location with unreliable internet, Dropbox and Google drive are not optimal because they have to sync to the cloud before the file is transferred over the LAN. Resilio sync is our preferred solution because it can operate wholly peer to peer, it is more flexible than google/dropbox as it allows any folder to be synced not just the one approved by google/dropbox and it is more cost effective. Could you support Resilio Sync please?
  6. I seem to remember that working files automatically refreshed when opened in 2016, but in 2017 it seems like we have to manually refresh after opening to retrieve the latest changes from the working file. Does anyone know if there's a setting somewhere that addresses this? Otherwise, the 2017 Project Sharing improvements are pretty good.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×