It is not uncommon to hear that people who are able to work on projects alone choose to ignore using worksets. Choosing to avoid adding any unnecessary complexity to the experience is one reason I hear. Another is, "Worksets are only required (and therefore useful) when people have to work on the same model together at the same time." It's true, I have written as much.
If this person is you, there are a couple of subtle benefits you might want to consider.
One way around this is to open more than one session of Revit. Each Revit session uses a separate Windows Clipboard, in memory set aside for each session of Revit. That makes it harder to use Copy/Paste to pass things back and forth if necessary.
If we use Worksets instead we are working in a Local File. We link files based on the central file though. The consequence of this is that we can open any number of other linked files in the same session of Revit now because we'll be opening a Local File, not the Central File. Revit doesn't object to that condition. NICE! It's enough reason for me to enable Worksets on every project, at least every one that will be involved in linking with other RVT files.
Regarding #2 - Choosing which worksets to open when we open a project is quite helpful because we can be creative with worksets and linked files and find ourselves able to choose which linked files should be opened too. Otherwise we have to wait until the file opens and then use Manage Links to Unload them or frequently use Visibility/Graphics to turn them on/off as required.
The trick is to create a unique Workset for each linked file we'll be using. Then we can choose which one to open when we open the project itself, demand loading of linked files via Worksets...since we can't manage links until the file is fully opened and all links are loaded. It starts here when you open a project (see image below).
When Revit begins to open the project the first thing it will load is the Worksets dialog which will give us a chance to decide which of them should be opened or closed. Anyone who has worked on projects with several (or many) large linked files knows how each file increases the initial opening time required for a project. Why put up with that at all?
Have I convinced you to give it a try? I hope so!
If this person is you, there are a couple of subtle benefits you might want to consider.
- Opening inter-linked files in the same session
- Selectively loading worksets while opening the file
One way around this is to open more than one session of Revit. Each Revit session uses a separate Windows Clipboard, in memory set aside for each session of Revit. That makes it harder to use Copy/Paste to pass things back and forth if necessary.
If we use Worksets instead we are working in a Local File. We link files based on the central file though. The consequence of this is that we can open any number of other linked files in the same session of Revit now because we'll be opening a Local File, not the Central File. Revit doesn't object to that condition. NICE! It's enough reason for me to enable Worksets on every project, at least every one that will be involved in linking with other RVT files.
Regarding #2 - Choosing which worksets to open when we open a project is quite helpful because we can be creative with worksets and linked files and find ourselves able to choose which linked files should be opened too. Otherwise we have to wait until the file opens and then use Manage Links to Unload them or frequently use Visibility/Graphics to turn them on/off as required.
The trick is to create a unique Workset for each linked file we'll be using. Then we can choose which one to open when we open the project itself, demand loading of linked files via Worksets...since we can't manage links until the file is fully opened and all links are loaded. It starts here when you open a project (see image below).
When Revit begins to open the project the first thing it will load is the Worksets dialog which will give us a chance to decide which of them should be opened or closed. Anyone who has worked on projects with several (or many) large linked files knows how each file increases the initial opening time required for a project. Why put up with that at all?
Have I convinced you to give it a try? I hope so!
