Bug? / weird behaviour in pattern along path

Bug? / weird behaviour in pattern along path

DDD9999
Enthusiast Enthusiast
344 Views
2 Replies
Message 1 of 3

Bug? / weird behaviour in pattern along path

DDD9999
Enthusiast
Enthusiast

Hi,

Please excuse the lack of screencast, this is simple enough if not easier via text.

 

For reference I am Win10, i5-5500K, latest version of Fusion (with the updated UI), top of the line SSD.

 

My model is a 10x16mm with 7 bodies, appearances etc. I am trying to use this as a component.

 

The bug is that when using pattern on path to copy a number of components, everything works reasonably well. I can pattern copy 180 components, so a total of 1260 bodies in a few seconds. However, if I convert this to a single body (either in original form, i.e. 10x16mm, or the group of 1260 bodies) it becomes so slow it crashes. Every time.

 

I don't know enough about the low-level to assume it might be this single body would contain god knows how many pieces of information to define all the vertices? Whilst components are referenced.

 

I'm not sure, so I have posted it here in case it is in fact a bug. If nothing else, perhaps learn why this behaviour occurs to improve my knowledge of Fusion.

 

Kind regards

0 Likes
Accepted solutions (1)
345 Views
2 Replies
Replies (2)
Message 2 of 3

karina.harper
Autodesk Support
Autodesk Support
Accepted solution

Hi @DDD9999 

 

This is somewhat expected. Components are a package for bodies - this data is computed differently. Patterning a body creates many individual copies of that body, whereas patterning a component can create instances of an identical component - this is easier and quicker for Fusion to compute.

This is a great video on the subject

And Jake Fowlers AU Class handout is full of great related information.

 

Let me know if that makes sense or if I can elaborate further!

 

Cheers,

 

Karina

 

0 Likes
Message 3 of 3

karina.harper
Autodesk Support
Autodesk Support

Hi @DDD9999 

 

Do you have any other questions on this?


Cheers,

 

Karina

 

0 Likes