Inserting linked file on the same location?

I have two files, when I copy/paste back and forth, the location of the objects is where I want them, they share a common origin.

When I insert one file in the other, the location and angle change.

How can I prevent this?

I already tried to set the ModelBasePoint to 0

Hi Simon -
Can you post those two files (or simplified versions)?
-wim

Hi Wim,

See attached.

Weirdly enough, when I tried to simplify at first, I tried to do this by copying and pasting some elements to 2 new Rhino files. But then the issue went away.

So these files attached are the original files I’m working with, I deleted as much as possible, to avoid NDA etc … Even now the problem only exists when trying to insert the LCD file into the Decorative file. With the original files the issue is there both ways.

The LCD file is from our client, I didn’t change much in it.
The Decorative file, contains elements from our client, but it is a new file I started from my computer.

The client works also with Rhino, they use a lot of block instances which are nested into eachother and have a lot of different layers, which I try to leave intact.

The client themselves also import files from another company in this drawing, which were probably drawn in autoCAD.

I couldnt reduce the meshes until the file size was under 20MB, so I had to use weshare:

the steel structure should line up with the meshes.

When trying to insert LCD.3dm into Decorative.3dm

Dag Simon -

When you insert the “LCD” file, it asks for the insertion point. Note that this point relates to the CPlane of the active viewport. Your “Right” viewport in the “Decorative” file has the custom “LS TOP” CPlane as the active CPlane. When inserting the “LCD” file, the geometry is mapped from the world origin and orientation in that file to this custom CPlane.
-wim

Hey Wim,

Bedankt :slight_smile:

That fixes it, I expected something with the CPlanes. Is this intended behavior? Once you know it, it kinda makes sense, but there isn’t really any way to know this beforehand? Or was this a really obvious?

I’m still struggling a lot with CPlanes from time to time. Sometimes I just orientate the entire drawing in frustration, instead of using CPlanes…

… wait a minute … as I am typing this … I realise that might be the reason for that behaviour in the first place?

You can draw the inserted file in the regular world axis. And in the receiving file you set a CPlane in the desired orientation? The inserted file’s origin snaps to the receiving’s file active C-plane origin?