Starting in December, we will archive content from the community that is 10 years and older. This FAQ provides more information.
When I insert a component using "Insert Derive", Fusion usually adds the component to the Window and the Browser. When inserting more than one component from different files, only the first gets added to the Window and Browser. All consecutive derives are "ghost" components. You can select them via the History, but only the blue shadow of the component appears. "Find in Browser" and "Find in Window" in the History menu do not work. If I close and re-open the file before inserting a second component it works as expected.
I can recreate the bug in new designs when inserting screws from my library, but I could not recreate it using arbitrary shapes.
My screw library uses threads (not modeled) and a few user parameter describing the geometry.
The screenshot show a "ghost" screw in the Window. The joints are not necessary to recreate the bug.
The file is available here: https://a360.co/2FzUtOQ
The second screw does not show up in the online preview, but after downloading the Fusion Archive and importing it it is visible again in the history, but nowhere else.
Solved! Go to Solution.
Solved by kgrunawalt. Go to Solution.
Solved by tyler_henderson. Go to Solution.
This certainly doesn't look right. I downloaded your design and I see the same thing. Can you tell me if the designs you are inserting are in the same Hub and Project as the target design?
Tyler Henderson
Principal User Experience Designer
Also, if you run "Compute All" (on the Modify panel), does that fix the issue?
Tyler Henderson
Principal User Experience Designer
Compute All does strange things... It changes which derived component is displayed in the Window and Browser. But all other derives become "ghosts". Recomputing everything multiple times just switches between the derived components.
No particular reason other than playing around with the new feature. But I agree these components don't need to be edited and Insert would do the job just fine.... But this should be possible with both methods.
Ok, this is certainly not expected. I'll get a bugged logged for this. Another thing to try is push Derive (on the Create panel) and see if you get the same weird behavior.
Tyler Henderson
Principal User Experience Designer
I think we discovered the issue. Was one of these designs created by copying (Save As) another design? I tried this theory and was able to reproduce exactly what you're seeing.
Tyler Henderson
Principal User Experience Designer
@tyler_henderson wrote:
I think we discovered the issue. Was one of these designs created by copying (Save As) another design? I tried this theory and was able to reproduce exactly what you're seeing.
Should I take from that "save as" imposes some... condition? Could you elaborate on why this occurred to y'all as a possibility in the first place?
Yes! I used Save As and User Parameters to create all different kinds of lengths and sizes.
So is that behaviour still just a bug or is my workflow not recommended? Maybe Fusion needs a Duplicate Design option that properly takes care of „separating“ files?
Save copy as does not impose a condition. The problem is an identity issue between the original and saved-as model that should not happen. This is a bug that causes the second derive to fail.
For the moment, there is no workaround other than avoiding deriving a save-copy-as source and target into the same design. We are working on a fix. We're sorry for the trouble.
Having the same problems as the OP.
I have the same workflow, saved a 'template' file with minor differences on the copies.
Managed to get the insert to work using the create in the derived part
Getting a lots of crashes when updating the derived part though
Hopefully you can fix soon.
I've created a copy of one component design and made hours of changes. Later on, I inserted a derive of another component, that would eventually not sync changes and, if removed, become a ghost link. Now I can't remove this ghost component and can't insert updated derives...
There is a way to overcome this bug?
Can you delete the Derive feature from the timeline? Or maybe promote the version just prior to inserting the Derive?
Tyler Henderson
Principal User Experience Designer
Why is this marked as the solution? Is the solution just that its a bug?
I'm having this issue now. And its bad timing, as I was just on the phone today with Autodesk about purchasing the license to lock in the price for the future. This a deterrent. Does anyone know if a solution has been figured out at this point?
Apologies, this shouldn't be marked as solved, but anyone can accept a post as a solution. This issue is being actively worked on. The internal issue number we are tracking is FUS-44617.
Tyler Henderson
Principal User Experience Designer
Can't find what you're looking for? Ask the community or share your knowledge.