Copy Sketch to Component gives error / not possible?
Create component from body doesn't work well for this, to get it to work create an empty component then drag the sketch into the empty component it should bring the body along with it.
Mark
Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Hi @GeorgScharioth, a couple of comments:
1. You can do this with a slightly different workflow:
- Create a sketch
- Create an Extrude, choose "New Component". This really combines the "Create Component From Body" command into the Extrude
- Now, you can drag the sketch into the new component
here is a screencast:
Fusion could be made to handle your scenario. I will file a request to make that change. However, there will always be cases where this will not work. For instance, if you start modifying the body after it is created, you will never be able to do this restructure.
2. There are reasons why you might not want the sketch inside of the component. The primary reason you would want to do this is to support "top/down" design. In this workflow, you create one sketch at the root of the design, and create several components from the one driving sketch.
3. Personally, I would just recommend that you follow @TrippyLighting's "rule #1": If you are planning to work with components, start with an empty component and activate it (which now happens by default when you create a new component).
Jeff Strater
Engineering Director
Also, relative to your suggestion: "i also don´t understand why bodys are not a new component by default".
At one point in Fusion's history (before it was released), we actually implemented it this way. It sounded like a really good idea at the time, for exactly the reasons you suggest. However, what we found was that it was really clumsy in practice. A very common workflow involves temporarily creating bodies that are later joined together (think of modeling a dumbell - you make the wieghts first, then the bar that joins them together). This was causing a lot of components to appear and disappear from the browser that were not necessarily. Also, a component is a fairly heavy object - it has origin geometry, bodies folder, etc, which was all way more than was needed for simple body. So, we pulled it back out, and internally consider that one of our bigger design failures. In fact, every time we discuss an idea that is a big change that seems like it should be simple, we always apply the "is this going to cause problems like single-body parts" criteria to it.
Personally, I think the best approach is to just learn the difference between bodies and components, and when to use each, then be deliberate about thinking about which construct you need for a given workflow. Here is a help article on the topic: Bodies and Components
Jeff
Jeff Strater
Engineering Director
