topic Re: Paste New Fails? in Fusion Support Forum

Paste New Fails?

avi.sato — Tue, 16 Nov 2021 11:35:40 GMT

I am running Fusion 360 on a Macbook Pro and have created a model (a chess-board with pieces). Trying to create a duplicate set of pieces using copy/paste-new fails. I see no error but it simply doesn't create a new copy. I can individually copy some of the pieces but not others. I have no idea why. It's quite a simple model so it shouldn't have much geometry to deal with, I don't think, that could be confusing it. The pawns in particular won't create new instances, though they copy using duplication or mirroring without an issue -- that doesn't help me, though, as F360 doesn't allow me to disconnect multiple instances and apple different appearances to them that way. Any help would be greatly appreciated.

https://a360.co/30vJD76

I've been using F360 since it first released and this is the first time I've encountered this, though I have rarely had to use the paste-new function as creating multiple versions of a single thing are usually easier to do in other ways. In this case, though, creating an entire set then duplicating it makes sense. Thanks so much!

Re: Paste New Fails?

TheCADWhisperer — Tue, 16 Nov 2021 13:14:20 GMT

I did not do enough experimenting to describe the root cause, but my initial impression is that I would avoid all unnecessary links to prior geometry.

Re: Paste New Fails

avi.sato — Tue, 16 Nov 2021 13:16:08 GMT

I don’t understand what you mean. Doesn’t the paste-new command sever links
to existing geometry?--

佐藤娃火 | avi sato | avisato.com | avi.sato@icloud.com

Re: Paste New Fails?

jeff_strater — Tue, 16 Nov 2021 13:49:30 GMT

thanks for sharing the model. We will look into this. I've seen a few cases like this, but there is no pattern that I've found yet - each case is specific. We'll see if we can find what is causing the problem in this case and log a bug for it, and also see if we can identify a workaround in this case.

Re: Paste New Fails?

jeff_strater — Tue, 16 Nov 2021 17:18:31 GMT

quick update - the problem is the "copy/paste bodies" features. Here are the problem features for the pawn component.

What is happening in your design here is that there are cases where the top-level component was active when an extrude was created, which creates the body in the top component, and then is restructured into the component. I believe that these features are a problem for Paste New (also for Save Copy As for a component). Unfortunately, there is no easy fix here. There is no way today to go back and change the active component so that an Extrude goes into the right component (that is on our list to address).

I'll try to share more later, and maybe a simple example to illustrate, but at the moment, I think this is probably the difference between components that succeed and those that fail.

Re: Paste New Fails?

jeff_strater — Wed, 17 Nov 2021 00:44:18 GMT

following up. Here is a quick example showing how restructuring bodies is a problem for Paste New. Two simplified versions of your pawn model. In the first, the central body is created in the root component, then copied to the child component. In the second, the central body is created in the child component. The first fails in copy/paste new, while the second succeeds.

If you are interested in the "why" here: Paste New (and Save Copy As) try to identify the features that are related to the component in question. The extrude in the the first component is not identified as belonging to the "paste new fail" component, because it is, in fact, not owned by that component. You can tell this if you have "component color swatches" turned on. You can see here that the sketch and first extrude are owned by the green component ("paste new fail"), while the second extrude is owned by the blue component (the root component). In the second case ("paste new ok"), all the sketches and features are owned by that component. This is what makes the difference in Paste New.

You can probably fix up your model, though it will require some feature deletion and re-creation. I don't think you will have tons of downstream failures as a result, but I have not tried it yet.