Copy constraints in pattern
I am thinking your wanted to use the term Joints in your title instead of Constraints but that is not important. If you want to maintain your components joints, in a pattern, one easy way to to create your joined assembly and pattern the assembly. If you Insert a complete assembly, into your model, as a sub-assembly, then pattern it, all joints are maintained. You can update the inserted or local sub-assembly as needed, just be sure you edit the original.
John Hackney, Retired
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
If you can share a design we can elaborate on how this works (or doesn't) better. I often answer forum posts during breaks at work, but I don't usually have the time to also create a model from scratch.
we are currently working on a "Copy with Joints" project that will help with this. It is not specifically "pattern with joints", though that may come later. But, it will give you the ability to bring joints along with new instances of a component.
Jeff Strater
Engineering Director
@jeff_strater good to know!
What would it take to convince the Fusion 360 team to provide a detailed modeling roadmap?
Hi Mr Maciej Stawowski,
I am unsure about the nature of the problem ... if there is some...?
Please consider looking into the attached file demonstrating the creation of patterned bolt/nuts assemblies.
It is worth noticing that pattern object (in F360 as in many other software) is a synonym for arranged references (*pointers, wzorów) to the respective object(s). In this way, a patterned meta-object (meta is overlaying function on the object like in f(g(x)) ) becomes efficient in terms of memory, rendering speed, etc…. However, it is hard not to notice the fundamental requirement here. The pattern’s object (or g(x)) must be self-contained; it can’t refer to external/dependent/interfering object. One abstract example here is … set (1,2,3.0) is patternable in ℝ, but (1,2,3.0, y) might not be (fully) if y doesn’t belong to the set’s domain, e.g. y∈ℂ.
By stepping down on F360 ground, the pattern feature can act on faces, bodies and components. The first two, by their nature, are self-contained. However, a component object might not be. It can, for example, contain a joint, referring to external to-it-self objects. What would the F360 engine do with such ‘non-compliance? There are many options here. The extremes are: show a mouse-clicker a blue screen (send him to gulags), or just ignore what is ‘outside permissible domain’ and continue with the task ( show the middle finger, and keep walking). For good or bad,… the TF360 implemented the algorithm adopting the second option … sort off. Although meta-feelings about the final solution might vary … it is what it is.
Please look at the attached file … and analyze what happens with a bolt’s grease, which has been purposefully excluded (for this example only, always use the lubricant!) from BoltNutWasher assembly.
Attached files:
Bolt_Pattern.f3d Fusion *.f3d ( 0.2MB) https://a360.co/3fh9ZRK
Flange_Param.png 4K_mono ( 6MB) https://a360.co/3r1uHb2
Flange_Param_arcd.png 4K_stereo ( 5MB) https://a360.co/3S9CTlx
Z Poważaniem
MichaelT
Hi TF360 … why does the material/appearance library not contain greases, lubricants and other sleazy stuff? Shame on you! 🙄
