Jump to content

Search the Community

Showing results for tags 'workgroup referencing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Calendars

  • In-Person Training - US
  • In-Person Training - UK
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups

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 3 results

  1. Following various advice on BIM best practice I've been setting up a project involving two buildings with a separate file for the site model and separate files for each of the two building models. All origins are synced across files (I'm using rotated view to work on the models) and I've managed to use Layer Import mode when referencing by having unique names for Design Layers + Story Names and Prefixes across the project. But workgroup referencing is bringing with it a whole host of trouble-shooting problems (and another [long] step in the file-save process). I find it very buggy. Which begs the question: why am I putting my building models (and sheets) in separate files? I would rather work in a single file for a host of reasons (including being easier for my colleagues to manage). Vectorworks can easily handle a project this size (two houses with 4 levels). And in terms of collaboration with other consultants, it doesn't matter that I have separate files or not does it? Convince me. @shorter?
  2. I'm using a current project to update our workflow to BIM best practice, specifically: Any projects with multiple buildings will have a separate file for each building Separate file for site model And all files will be set up with correct real-world coordinates and orientation, relying on rotated view to work with models. I'm going to assume it's still best these days to use Layer Import mode. In which case I need to ensure all design layers are uniquely named across all files in the project. But do I also need to do this for Story names? What about Level Types?
  3. Despite the advent of Project Sharing we still find ourselves (reluctantly) splitting files up in order to minimise memory usage when working in the main model file (and, to a lesser extent, save and commit time). If we weren't slowed down by large numbers of Sheet Layers and Viewports we'd almost certainly keep everything in one file. So in order to split files up we have to use Workgroup Referencing. But Workgroup Referencing is cumbersome, because the process of editing the model file, then doing a save and commit, then waiting for Dropbox to sync, then updating the workgroup reference is a long one. But the main culprit is the last step, updating the workgroup reference. Because it fetches the entire file every time you do it and locks up VW in the process. So until Vectorworks can handle a large number of Sheet Layers and Viewports without getting bogged down, it would be great if we had a new form of referencing that worked more like Project Sharing: It would support delta updates rather than having to fetch the entire file It would have a refresh button like Working Files do But it would behave differently to a Working File in the that you could create Sheet Layers that aren't pushed back to the Project File VE-101609
×
×
  • Create New...