Bug with instance numbering in patterned assemblies

Bug with instance numbering in patterned assemblies

TrippyLighting
Consultant Consultant
582 Views
4 Replies
Message 1 of 5

Bug with instance numbering in patterned assemblies

TrippyLighting
Consultant
Consultant

Found anbother little glitch.

 

When an assembly is patterned such as the circulatr pattern of the Carrier assy:1 in the screenshot below as expectd the instance of it is called Carrier assy:2. One would expect for the instances within Carrier assy:2 also to receive an increased instance count, fo example Bottom PCB assy:1 to increase to Bottom PCB assy:2 but that's not the case.

One of the effects is that when Carrier assy:1-Bottom PCB assy:1 and Carrier assy:1-Bottom PCB assy:1 are added to a selection set and then one chooses to hide the selected components/assemblies, only one of them is hidden.

 

Assembly instance bug.png


EESignature

0 Likes
Accepted solutions (1)
583 Views
4 Replies
Replies (4)
Message 2 of 5

zhanganchun
Alumni
Alumni
Fusion Assembly pattern is a kind of Instance pattern. Only top level selected instances will be patterned, so we can see Carrier assy:1 and Carrier assy:2. Those two instances reference to the same component/assembly internally. So all datas under them are the same actually, like Sketches, Constructions, or component instances like Carrier board:1. But Fusion do add some functionalities to support kinematic structures. Carrier board:1 under different parent can have different relative positions, ground property and even visibility control. It makes them behaves like different instances.
Terry

Software Engineer - Fusion 360
0 Likes
Message 3 of 5

TrippyLighting
Consultant
Consultant
I am fully aware of what an instance is as opposed to an independent copy. This is not differnt from any other 3D software I've worked with. In Solid Works , or Geomagic Design that terminology does not even come up. In Blender they are called linked copies and you can choose which of the features you want linked to the original. Very nifty by the way !

I understand that the original top level instance and the patterns instance refer to the same data, but so is every other instance. That's the concept of an instance. However, if I instance a single component , the new instance gets a differnt number.
I am assuming that Fusion does not do that for the component and subassembly instances in a patterned top level assembly so as to maintain the relations e.g. Joint constraints between these parts and subassemblies within that top level assembly. That makes sense!

If that is so by design, then there is a bug with creating a selection set. You did not answer that part of my message.
iIn the design you can see in the screenshot I've created three selection sets. The two I want to talk about are "Roll Eyes" and "Apples"
These indicate two variants of a design for this lighting system.
The selection set "Apples" refers to components that are all either differnt components or are top level such as "Apple - leaf:1" and "Apple - leaf:2"
All of th components in that selection set have differnt instance names. When I hide that selection set as expected all components in that selection set are hidden.

The second selection set is created from two components. "Gator board -disk:1" in "Carrier assy:1" and "Gator board -disk:1" in "Carrier assy:2". When I hide that selection set, only one instance of the gator board is hidden. It is certainly not expected behavior when an operation on a set is not applied to all componets in that set.

It may have been an incorrect conclusion on my part to attribute this issue to the instance naming topic described above.

EESignature

0 Likes
Message 4 of 5

TrippyLighting
Consultant
Consultant

I've created a little screencast with quick view to show the problem with the "Apple" selection set:

LINK to dropbox


EESignature

0 Likes
Message 5 of 5

zhanganchun
Alumni
Alumni
Accepted solution

Thank you for reporting the visibility command issue. The selection set has successfully selected the instance in two paths, but the visibility command fails to hide them. Will create an internal bug to track that.

Thanks!

Terry

Software Engineer - Fusion 360
0 Likes