topic Re: opacity of referenced components in Fusion Design, Validate & Document Forum

opacity of referenced components

Cotral.RD2 — Tue, 04 Dec 2018 07:31:37 GMT

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

Re: opacity of referenced components

jeff_strater — Tue, 04 Dec 2018 08:00:16 GMT

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.

Re: opacity of referenced components

HughesTooling — Tue, 04 Dec 2018 09:09:45 GMT

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

Mark

Re: opacity of referenced components

Cotral.RD2 — Tue, 04 Dec 2018 10:30:31 GMT

this works for me! thanks!!

Re: opacity of referenced components

P.IM — Tue, 14 Jun 2022 22:36:59 GMT

Dude. THANK YOU.

Re: opacity of referenced components

tawoodYHL59 — Tue, 26 Sep 2023 02:08:37 GMT

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.

Re: opacity of referenced components

raven.zino — Mon, 06 May 2024 03:04:00 GMT

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.

Re: opacity of referenced components

eSonOfAnder — Fri, 06 Sep 2024 18:15:45 GMT

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.

Re: opacity of referenced components

camundsonAH42P — Mon, 05 May 2025 22:07:47 GMT

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

Re: opacity of referenced components

camundsonAH42P — Mon, 05 May 2025 22:08:17 GMT

Where is this to be found?

Re: opacity of referenced components

tawoodYHL59 — Mon, 05 May 2025 22:53:43 GMT

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.

Re: opacity of referenced components

ScottWatrous — Sat, 10 May 2025 23:35:05 GMT

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.

Re: opacity of referenced components

danielWNW3M — Mon, 09 Feb 2026 19:55:23 GMT

Just checking, is this workaround still the only way in 2026? I have some designs for which adding an extra component to contain the linked component is really inconvenient.