Component Axes Change When Imported

copy
axis
import
components
help

#1

Hi everyone. I have this low-poly tree, which I turned into a component and as you can see in the first screenshot the axes are set in the center of the trunk for more precise planting in projects.

Now when I import this SKP into a new file via File > Import, the axes of the component change to the axes of the document.

I either have to have both files open and copy-paste from one to another to keep the axes location, or set them manually after importng. Is there a way to keep the component information when using the Import option?


How Is Ungrouped Model Turned into Face Me Component on Import?
#2

I’ll bet you made the tree a component and then saved the SketchUp file to some location for easy access. Look at the Outliner in your second example with the axis off at the corner. I expect your tree component is nested in another component. Is that right?

When you use File>Import to import a SketchUp file, it treats the file as a component. Any components in the file are nested within. And the parent component’s axes are automatically placed in the lower front left corner as they would be when you create a component without manually placing the axes.

Instead of saving components that way, use the Components window and drag the component from In Model to the library you’ll keep it in. when you want it again later, drag it back in from the Components window.


#3

Yes, to both. You’re right Dave. This is what the Outliner shows in the imported file.

And this is how it appears in the pre-saved file:


Thanks a lot. Now it’s clear.

Will I achieve the same result if I Explode the imported geometry 1 time, to get rid of the auto-component group?


#4

Yes. If you explode the top-most component, you would be back to what you were expecting. This will be fine for now but going forward, I think you’d find it better to import components using the Components window. when you drag them into the model space, you’ll have hold of them by their origins so they’ll be easier to place with precision.


#5

@DaveR, I’m sorry to revive this topic again but apparently I’m having trouble. I hope you can look through again, if it’s not much time consuming.

Ok, so as you can see, this is the separate file of the tree component. I’ve made a collection under the Components library, like you said, for easy drag-and-drop, which is on the left of the screenshot.

Now, this is what happens when I drag-drop this component into a new file:

You said, that File > Import would put whatever is imported under a component definition. But this drag-drop process also puts it into a new component. There is something I struggle to understand.

There is a mysterious “Expand” button which, after activating, shows that there is a second component.

Now drag-dropping this second component works correctly and the anchor is in the middle of the trunk ground. My question is:

• What is the ‘Expand’ button for in the first place? Why doesn’t the Component window show the second component by default?
• Since drag-dropping from a component collection library puts the object into a new component same way as Importing, I have to manually delete the auto-component and keep the other one.

Perhaps I’m doing something wrong? I thought drag-dropping wouldn’t create an auto-component. Just trying to avoid the additional step of deleting it, for more precise planting. Thanks a bunch in advance.