Modernised Workgroup Referencing in Wishlist - Feature and Content Requests Posted October 13 39 minutes ago, Christiaan said: Sure, but consider the problems I've identified. These are not in that category: Data Tags don't work in WGR files, so we can't tag windows in elevation views of the model. Adjustments can be made to gridlines in the Annotations layer of viewports in WGR files, but those adjustments are wiped out when updating the WGR. Bugs that have no workarounds, e.g. the foliage tool showing denser foliage in a WGR file compared to the original model file. And it's now my understanding that because of the way WGR works (i.e. deleting and replacing data) we can't expect these issues to be fixed with the current technology (at least not to 1 and 2). So perhaps Matt is right, the solution to my problem is to deal with the speed problems with large files. That may happen quicker than overhauling WGRing. A project I'm working on at the moment weighs in at 2GB if we keep everything in one file (I was working on one last year that would probably be 4GB). But file size is not the problem (in fact it's more space efficient to keep everything in one file); the problem is navigation through layers slows and working with the nav palette and organisation window slows down significantly. Of course, all tools should work whether referenced or not, and yes, referencing does need an overhaul. Referencing in VW is different from Mstn, and I am not sure why, but I am pretty sure there are associative objects in Mstn that when you update a reference you don't lose the connection. Walls and Spaces, for example, would be great in separate files but linked so that when the wall references updated the spaces did automatically. The biggest issue we see with referencing is resource conflict, and in particular now with styles, invisible resource conflict, like the title block record format. The fact that we even get resource conflict when referencing a wall from an IFC model, isn't ideal. Data Tags in Elevation views is an interesting one. Where are you placing the tag? Sheet Layer Viewport or Section Viewport in a Design Layer? Have found that simply identifying the window using it's own tag, is better than a data tag, given all you really need in an elevation is the window number, or do you do something more elaborate? I would be very worried working in a file that big. And you use project sharing? How many people on the team are having to download/upload to that and how often do they do so, and how long does it take to save and commit and then refresh? I suppose there are two schools of thought. You either keep it lean, with more, smaller files, or all in one big file. We prefer the former. What would you do if you had to rebuild that file? Our 400,000 sqft BIM is spread over 10 models, weighing in at a total of 600Mb, with no file bigger than 200Mb. When combined into one model they are 200Mb.