Mirror losing original component reference after update.

[Anonymous]

Good morning everybody,

The June 11th update brought a bunch of goodies. I'm on the other hand experiencing a major bug that is affecting my workflow efficiency substantially. All the mirror operations lose the original components as a reference when said components are updated. This results in all the joints referencing the mirrored components to be broken. It happens in all the assembly files I have created, no matter the workflow followed. You can see the problem in the screenshots below.

[paul.clauss]

Hi @Anonymous

Thanks for posting! I tried to recreate this issue in a new file but was unable to - would you mind sharing the design you are working with? I'm happy to have a look and see what we can do!

[Anonymous]

Let me try to get that going for you. Thank you!

[Anonymous]

I generated two new files to reproduce the effect in a different project. I can create the same problem in an assembly file if needed. You can find the links below. Let me know if that works.

Original component

https://a360.co/2HPTbuM

Mirrored component in a second file:

https://a360.co/2HO8F2y

[paul.clauss]

Hi @Anonymous

Thanks for posting! I was able to reproduce this in your file as well as in a new file after seeing your setup - thank you for sharing.

I've logged an internal bug ticket for our development team to investigate a fix for this (internal reference FUS-40868). We appreciate you bringing this to our attention!

I did find that I saw no problems when I mirrored the component in the child file, as opposed to mirroring the x-referenced component in the assembly file. This won't be ideal in every design situation, but may allow you to avoid this issue while a long term fix is developed.

The problem appears to be that the mirror feature loses reference, but does not show an error. You may also be able to work around this by editing the mirror feature in the design timeline and reselecting the component to mirror.

I hope this helps! Please let me know if you have any questions.

[Anonymous]

Thank you Paul. I have never seen this happen before this update. I am currently working on other stuff in parallel since my assembly files contain many parts, and this specific problem is affecting a part that I have linked to many others through joints. The problem of reassigning the part in the mirror feature is that the mirrored part is generated as a new part in the assembly, so all the joints created against it get broken.

I use this feature a lot with parts that are very similar but mirrored, to avoid having to keep modifying two different parts whose design has only subtle differences. This simplifies the design when you several iteration steps to get to a final design, before splitting the two parts apart.

I appreciate you guys looking into this and I think I can survive with this bug for a while. Thank you very much for the efforts you all put into Fusion. You guys have walked a long way since the inception of this program and I can say is probably my favorite CAD software right now.

[paul.clauss]

Hi @Anonymous

Thanks for the response! We appreciate your kind words and are glad to hear you've been enjoying Fusion. Feel free to reach out on this thread whenever for an update on this issue.

[Anonymous]

Hi,

I am so frustrated with this problem.  After updating a component that was mirrored in an assembly, all the instances of components in that Mirror operation were missing.  I'm just new to Fusion 360 so I thought it might have been my fault, but I wasted enough time on it that I could have done individual instances of each component with joint relations.  Thanks for bringing this to the fore. Meanwhile, I'll stop using 'Mirror' (and this is hard, because I love the 'Mirror' feature).  This happens on even simpler assemblies like the one I'm working on. 

[jeff_strater]

@Anonymous, @Anonymous:  We have elevated the priority of this.  Once we find the bug, we will try to get it into a hot fix update as soon as possible.  Thanks for reporting this.

[Anonymous]

Good morning!

I was wondering if there had been any progress regarding this issue, or if you guys could provide an approximate ETA for this to be solved. I am trying to finish this project and would like to know if I have to rebuild the model avoiding the use of the mirror feature or if it is just a matter of waiting a couple more days. Thank you in advance, I appreciate the efforts.

[paul.clauss · Accepted solution]

Hi @Anonymous

Thanks for posting! While I cannot confirm an exact date when this issue will be resolved, it should be happening before too long. I'm happy to keep you posted here.

[Anonymous]

That was actually faster than I thought. The update that rolled out today seems to have taken the problem away with it. Thank you very much guys!

[paul.clauss]

Thank you @Anonymous for bringing this to us!

[dwrCons]

I am still having this problem, or perhaps it is another. When I mirror a component in one design, and import it into another, the mirrored component loses its link reference. The practical result is that the mirrored component loses its metadata for the appearance, showing "generic" as opposed to that selected from the source. Also, the mirrored components do not update when the source is modified. Is this still a work in process, or am I doing something wrong, or both? Thanks.

[TrippyLighting]

I'd urge you to create your own thread as this one is already marked as solved and particular AD employees may have changed to another areas.

This way you will get better responses. You can still reference/link  this thread.