Rhino 9 WIP BUG: Clipping Drawings with Worksessioned Files

Rhino Rhino for Windows
,
1

We have been testing the Rhino 9 WIP clipping drawings. It is awesome to have the ability to UseSourceLayer (new in Rhino9 WIP) to have the output stay on the same layer as the source (this is a gamechanger for us).

However, when clipping a file that has a worksessioned file attached, the linework resulting from the worksessioned file is not editable. It seems to act as worksessioned geometry (eg it is visible and selectable, but not editable, even if you try to explode it). This means it can’t be exported (only the clipping geometry from the active file can be selected, edited and exported). Is there a way to make the worksessioned geometry “live” within the active file? (model attached)

It’s unclear where the linework / geometry resulting from the clipped worksessioned file exists - it is not in the active file, neither is it actually part of the worksessioned file. This also means the linework resulting from the worksessioned file can’t be deleted from the active model, even if the worksessioned file is refreshed or detached.

Models and worksession attached.

Test 01_blue.3dm (149.9 KB)

Worksession_Test.rws (1.6 KB)

Test 03_grey.3dm (96.6 KB)

Test 02_red green yellow.3dm (56.6 KB)

For reference: architecture models - we have an “active” file for proposed building, and worksessioned files for the surrounding buildings. We would like to export a clipping drawing that captures both.

2

sp3,

I recently had this same discussion, and I think it will apply equally to this.
Bug/ Feature Request? Section through Worksessions - Rhino / Rhino for Windows - McNeel Forum

One trick I did not mention in that thread but have found can occasionally help when working with worksessions is exploding a worksessioned item to pull a copy of its layers into the active model. This is completely a work around and not very practical if there are many worksessioned items being sectioned, but from time to time it is just what one needs. When one tries to copy from a worksessioned model it places all new objects on the current layer in the active model, but when one explodes a worksessioned item the program creates an exploded duplicate complete with layers and properties in the active model.

I hope this is of some use at some point until we see a real fix.