Upstream Selection Sets are not visible in downstream components

[S-R]

I am currently working on a project that is based on 8020 extrusions and hardware. I have separated logical components into individual assemblies, e.g. an assembly for a hinge includes the hinge itself and required fasteners. That logical assembly is then inserted into a downstream assembly, e.g. attached to an extrusion. Due to a large number of components (~2000), Fusion slows to a crawl. I thought to hide non-essential components like support fasteners, end caps, etc. until the final render would speed things up because fewer components would need to be rendered on screen. I used Selection Sets in upstream components to achieve this task. In my hinge example, I have used a selection set to hide all components except for the hinge itself and the single fastener at the revolute joint. However, in downstream components (the extrusion and hinge assembly), the Selection Sets for upstream components (the hinge) are not visible. 

What is the reasoning behind hiding Selection Sets in downstream components? Is this an incorrect use of Selection Sets? Is there a better workflow I am missing?

Thank you

[TrippyLighting]

I cannot speak to the up-stream/down stream topic as I am not sure exaclty what you mean. A screencast would certainly help commnicating the issue.

However, another "setting" that also helps is to not only hide components but to also conisder to set some of the components to unslectable (it's in the same manu as show/hide/.

This is helpful for components that you may want to keep visible for reference and navigation but don't need to actually select.

Fusion 360 searches for selectable objects in the viewport in a cone shaped vlome (IIRC) protruding from the mouse cursor and the fewer objects it needs to search the better the vielwport performance will be.

[S-R]

I have created a screencast to better illustrate my question.

http://autode.sk/2cKMSfX

[TrippyLighting]

I cannot watch the screencast as you set it to "private"

[S-R]

Sorry about that. Please try again.

[S-R]

I have been creating Selection Sets in the top-level model as a workaround, but it is repetitive. I hope the screencast better illustrates my issue.

[TrippyLighting]

I am not sure I am intepreting your screencast corectly, but it looks like that you are trying to hide components that belong to a linked assembly.

Selection sets are specific do a single design file.

As such it would help if you wuld reduce the amount of linked components that you use excessively and unnecessarily.

[Phil.E · Accepted solution]

That is a great use for selection sets. But there are limitations to how they behave.

A selection set is only kept at the top level of the browser. This is not carried along with the xref because the xref is a child of the assembly it goes into and only the parent can have a selection set. I believe the design is intended to make them always available right at the top, and not buried in layers of sub-assemblies. But that was before xrefs and you are showing the other side of that coin: what happens when you import sub-assemblies with deep nested structures and want to use existing selection sets. It gets just as complicated going the other direction, so thanks for pointing that out.

So this is only a current limitation. I have no idea what it would take to implement it, but you could post this to the Idea Station: make selection sets for child components. 

Thanks,

[TrippyLighting]

Instaed of hiding these parts it might already be helpful if you set these parts to "unselectable".
Fuision 360 looks for selectable objects is a cone volume protruding from the mouse cursor. The more objects are slectable the more that algorithm has ot work.

Setting these parts to un-selectable will help and may be enough.