Worksession bug : TweenSurfaces creates object in attached file

Rhino Rhino for Windows
1

Normally, all objects created in the context of a worksession reside in the currently active file.
It does not seem to be the case when creating a surface with TweenSurfaces.
And although the surface seems to exist, if one opens the said attached file, he will not find the surface in question.
It seems to lie in some parallel universe…

File 01.3dm (60.0 KB) File 02.3dm (46.2 KB)

2

I repeated the problem.

Download osuire’s files. Open File 02. Start a worksession and attach File 01.

TweenSurfaces on the two surfaces.

Result is a surface which is not on any existing (or at least visible) layer.

From What on the created surface.

surface

ID: 3207025b-fda5-4970-ad38-de2afc812291 (192)
Object name: (not named)
Layer name: File 01.3dm::Default

A slightly similar bug: Worksession Error - Copy InPlace

3

Hi,

Also related to this:

4

Hello - as far as I can see this is fixed in the V7/WIP. The specific bug track item is a little ambiguous at the moment, I’ll check withe developer to see if we can give it a more accurate status…

https://mcneel.myjetbrains.com/youtrack/issue/RH-56613

-Pascal

5

I use V6

6

Generally, fixes that are considered too major and risky for V6 are made in V7. This is typical of development when we are nearing the end of a product development cycle and moving towards the next release.
Sometimes it is possible to “surgically” get a fix in. This risk assessment is made by the developers and not made lightly.

1 Like