opacity of referenced components

[Cotral.RD2]

Hello

Why cant I change the opacity of imported/referenced parts without breaking the link? 

I was trying to import a model as reference and I just cant change its opacity!!

Pavan

[jeff_strater]

this operation is considered a model change, and you cannot make a model change in a referenced component from the top level - you have to open the design in a separate tab to change the opacity.

[HughesTooling · Accepted solution]

If you create a component to contain your imported linked components you can change opacity of the linked components from the container component.

Mark

[Cotral.RD2]

this works for me! thanks!!

[P.IM]

Dude. THANK YOU.

[tawoodYHL59]

I can't believe that we still need this work-around for such an obvious feature.  If I can turn on/off the visibility in the higher level assembly, I should be able to change the opacity.  But putting every inserted component into a separate container seems like a workaround that I can use.

[raven.zino]

It is year 2024, and this is still not addressed... And in my opinion, this shouldn't be marked as "Solved" with only a workaround. Opacity control for referenced components is very much needed. And the workaround of using an envelope component isn't the solution as it doesn't provide detailed level of control for a complicated assembly that involves linked items, and therefore one can't choose to opaque subcomponents A and B to capture one view and then C and D for another screen capture or render. If your work happens to involve switching back and forth, it could easily be quite frustrating. And this is just one of many practical limitations due to the lack of such direct opacity control.

[eSonOfAnder]

Just submitted a feature request ticket about this here, and strongly urge everybody else to do the same thing. This is basic operations right here.

[camundsonAH42P]

Here we in 2025 with the still with the same issue with only a work around!

[camundsonAH42P]

Where is this to be found?

[tawoodYHL59]

Are you asking what the workaround is?  Read above the reply marked as "Accepted solution".  Before importing a component into a design, create a new "dummy" component as a container for the imported component.  You can then change the opacity of the dummy.

[ScottWatrous]

Still hoping for the basic functionality of changing opacity of any body, component, or whatever, when linked. It feels like I am far more likely to want to make a component mostly transparent and 'unselectable' when it is linked and I'm pulling it in purely as reference while working on something else. For example linking some machine vise or a common component that I use multiple places. I want to see it there, as a ghost, while I work on the stuff native to this design. The fact that Fusion has the ability to change opacity at all is fantastic. But that it's so limited to being tied to how that model exists in its base state means the best aspects of this adjustment have been cut off at the knee. The proposed workarounds (making a component for the linked component to live in, or, having to adjust the base model every time I just want to quickly see through the part without hiding it) are things to be endured with much cursing and gnashing of teeth and incredible disruption to workflow, having to do things that feel illegal. All until a proper solution is provided that just, like, works.