Block instances bake in the wrong place - bug?

[Sukey_Thomas]

Im trying to place block instances using Grasshopper. The block instances need to have a very specific point as their base point.

I can get them into the correct place in GH, but when I bake them out, either using the right-click option or content cache, the resulting Rhino Blocks are not in the correct position - it seems like the baking operation uses a different origin point?

But sometimes the baking works fine and the gems end up placed correctly

Am I misunderstanding something fundamental about blocks? Or is this a bug?

BLOCK BAKE ISSUE.gh (14.0 KB)

[Japhy]

Hi Sukey_Thomas,

We’ll need the block as well.

@Jeana769Hadley

You’re not misunderstanding—this is a known quirk of how Grasshopper and Rhino handle block definitions and their insertion points. The issue usually comes from a mismatch between the block definition’s base point (set when the block is created in Rhino) and the insertion point

This would be a stop ship bug if true.

Here is your definition with a quick block i setup.
Block.3dm (107.9 KB)

[Sukey_Thomas]

I suspect the issue was because of conflicting blocks in the Rhino file, because I cannot recreate the behaviour in a fresh .3dm

When block instances are baked out, is the block definition also baked out if it doesnt yet exist in the Rhino file?

I see there are now two blocks in the file, but one has zero top level and zero nested instances

block bake issue.3dm (4.2 MB)