Derive Bug, including deselected components.

[HughesTooling]

Just created a derived design and noticed one subcomponent I deselected while exporting is in the derived design.

You can see in the edit dialog the MovingParts component is deselected but the component and all its subcomponents are in the derived design. Can't share the design here but can email a link to support. Edit was able to fix by toggling selection. Also just noticed the picture below is the source design not the derived so you'll need to take my word that the deselected components where in the derived design.

Mark

[helfenj]

Hi Mark,

Can you send me the link to the file directly: john.helfen@autodesk.com.

I can get the files to my team and see if they can repro.

Does this happen often or is this the first time you have seen this?

If I understand correctly when you edited the derive and toggled the MovingParts component the issue was resolved, meaning the component no longer appeared in the target file, correct?

Just trying to understand the steps to repro and severity of this.

Thanks,

John

[HughesTooling]

I'm not sure I can let you have the version with the error. I needed to keep working on the design so the current version seems OK now after toggling select\deselect.

My workflow this time is a bit different to what I've used in the past. In the past I just selected the components I wanted from the main assembly but that puts all components\subassemblies at the top level in the derived design's browser. What I did this time was select the top component in the browser, in effect selecting the whole design then unselect the subcomponents I didn't need. Done this way the whole derived design in one subassembly in the derived design.

You can see below the derived design is now under one component and easier to manage.

What I'm doing is designing a mould tool in one design then exporting the parts I need to manufacture. I found in the past having the CAM and all design work in one file hit performance badly after a certain point.

Mark

[helfenj]

Hi Mark,

Completely understand. This new information is helpful and maybe enough to repro.

In the future, if you get to a point where you can repro and have a file you can share you can post it here. In the meantime, we will see if we can repro and corner it.

Thanks,

John

[HughesTooling]

I just opened V1 of the design and it doesn't have the problem! This was the version that should have the problem.

Where I had the problem, I'd created the derived design and saved once but not closed the design. It looks like opening the version maybe fixes the problem. I've had problems before with Fusion where saving, closing the design then open fixes the problem. Even made screencasts of problem files, exported and made a bug report on the forum only to find the file I shared had no problem. Seems like it might be one of those transient bugs that are near impossible to reproduce or fix. If you are going to be able to recreate the bug it seems it will be when the derive is first created. By the way I used derive from the Create menu in the source assembly.

Thanks Mark