![]() When CRO is used with Layers Organizer, these prefixed layers are automatically grouped per Cross Reference for the same purpose.Īdditionally, these prefixes have the practical function for the programming logic to avoid re-importing and duplicating/triplicating/quadrupling etc. The prefixing therefore allows for Cross Referenced layers to be quarantined away from the working model’s layers, thus avoiding visual clutter with layers that are not ‘operational’, so to speak, in the working model. This aligns with the intention that Cross References are locked in the destination model and are not edited there - they are just for reference. (Just to say, in case it is helpful, the XRC and XR prefixing is only done for layers that have names unique to the source model being Cross Referenced, as it arrives in the destination / working model. It’s a significant development from the former Layers Panel plugin (I think that was the one), whose author had to abandon further development. So is Layers Organizer from the same source. Haven’t used it long enough myself to vouch for its stability, but it has been in production use in the developer’s own architectural practice for some time, without reported problems, and (he says) has saved his practice much money by avoiding having to migrate to much more expensive software for team development. Even though it was my problem, the authors were quick and helpful to respond to my tribulations. I was also having problems initially in a very large model, which completely went away after restarting SU. It doesn’t go on Tools, or Extensions, where I first looked for it, which is unusual but not unprecedented. I had a little difficulty getting started with it, as it puts its main menu entry on the Windows menu and I took some time to find it. It is cleverer than the existing Xref Manager plugin, which I have also used, in that it avoids duplicating definitions of subcomponents that may already appear in others’ sub models you have imported. ![]() And if, as recommended, you start with a completely empty main model, and Cross Reference in all the major sub-models, that problem also disappears if you use it from the start.īut I think it’s great, and intend to use it myself to keep track of sub components edited separately in sub model files, even when working solo. I think that is a small price to pay for the convenience it offers. It means that components and layers that come from Cross References appear out of sequence with native layers in the main model 认证网址✅Well, my collaborator has taken against a new plugin in the middle of building a large and complex model, and doesn’t like the way it prefixes cross referenced component names with XRC- and layers with XR. The impetus for commissioning it for our own use came from a desire in our mid-sized Architecture office to avoid the large up-front and productivity-ramp expense of moving to Revit or Archicad, further equipping SU /LO to be an end to end solution for teams.ĥ FREE licence keys available to the first five people to road test it and privately give me just one item of feedback.įind it here: 金沙js93252(中国)有限公司 It also addresses a problem we found using Trimble connect in our workflow - including the need to publish over a slow connection, and not having a visually orientating understanding of one’s cross references. It solves a key problem we found when using the File/Import/Reload process native to SU, namely the superimposition of multiple copies of content when many people in a team Import eachothers’ work. It has a clean and simple UI that allows you to visually understand what in your model is cross referenced and how up to date it is. The plugin facilitates team members breaking a project into parts and and cross referencing each others’ models in their own workspace. Cross Reference Organizer is designed to bring SU closer to being a design environment in which team members can collaborate simultaneously. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |