Is the ʼWorksessionʼ tool used for collaborating on large files in Rhino?
Short Answer
Yes — in Rhino 3D, the Worksession tool is a standard professional method for collaborating on large files by attaching multiple model files into one working session without fully merging them. It helps teams split geometry by discipline or scope. Limitation: it is not true simultaneous live co-authoring in one file.
What You Need to Know Before
Warning: Worksession references can break if attached files are moved, renamed, or saved to inconsistent network paths. A very common failure is users trying to edit geometry in an attached reference file directly, which Rhino does not allow unless that file is set as editable.
How to Use Worksession in Rhino
Command: Worksession
Shortcut: No default keyboard shortcut
Quick Steps:
- Run
Worksessionfrom the command line, then open the Worksession panel/dialog and choose Attach to add external Rhino files. - In the attachment options, set one file as Editable if needed, and keep other files attached as references.
- Use the combined model for coordination, layer control, and checking context, then save the session host file without merging all geometry into one heavy file.
- Run
Variables & Settings
Key Setting: Editable file option in the Worksession attachment list
Expert Setting: Only one attached file can typically be made editable in the active session workflow, while the others remain reference-only. This controls whether you can modify linked geometry versus using it only as context for coordination.
Why it Fails
- Cause 1 (Geometry): Extremely heavy linked models with dense meshes, blocks, or detailed display modes can still make the session slow, even when files are split.
- Cause 2 (layers/Locks): Required objects may be on off, locked, or hidden layers inside attached files, making users think the reference did not load correctly.
- Cause 3 (Command/Logic): Users often expect Worksession to behave like full file merge or cloud co-authoring, but it is a reference-based workflow with limited direct editing of attached files.
Quick Fix & Best Practice
- Quick Fix: Reopen
Worksession, then use Attach or reattach the missing file from the correct network or project folder, and verify the intended file is marked Editable if changes are required. - Manager’s Verdict: Use Worksession for large Rhino projects when teams need shared context without constantly merging files. Avoid it when you need true simultaneous editing of the same objects or strict revision control across many remote users.
FAQ
Can multiple users work on related Rhino files with Worksession?
Yes, as long as each user manages separate referenced files and coordinates file ownership.
Does Worksession reduce Rhino file size permanently?
No, it mainly improves workflow by referencing external files instead of merging all content.
Can I edit every attached file inside Worksession?
No, referenced files are generally not all editable at the same time in the session.
.
