IntersectTwoSets in Worksession - Bug

Use IntersectTwoSets with OutputLayer=FirstSet or OutputLayer=SecondSet in Worksession with the input from a reference file (not the active file). The result is put on a layer in the reference file and cannot be deleted without detaching the reference file or the active file is closed. If OutputLayer=Current then the result is put on the current layer in the active file.

This behavior is a problem if a mistake is made and the results wind up in the reference file where they are not wanted. Copy with Inplace option can be used to copy the result to the current layer in the active file, but the results remain in the reference file until it is detached or Worksession is closed.

In contrast if Rebuild is used with or without “Create new object on current layer” checked to rebuild an object on a reference layer, the result is put on the current layer in the active file. It is not possible for the results of Rebuild to wind up in a reference file.

Example files:
IssueWS.rws (560 Bytes)
Issue.3dm (1.9 MB)
InputAB.3dm (1.9 MB)

Hi David, thanks I’ll get this on the pile.
RH-78724 IntersectTwoSets and worksesisions


RH-78724 is fixed in Rhino 8 Service Release 2