Pattern on Path Suppress Breaks Model

[cheneymax]

When I suppress a component in a pattern on path operation, it causes components in a different assembly (also created with pattern on path) to spread way out. Any ideas where I've gone awry?

Edit: Forgot to link screencast 🙂

[jhackney1972]

In your Screencast I see a big error come up which I cannot read real well.  Plus, you are say it affects another assembly, don't you mean another sub-assembly within the same assembly.  Please attach your model so the forum users can troubleshoot it for you.  If you do not know how to attach your model, open it in Fusion360, select the File menu and then choose Export and save the .F3D file to your hard drive. Then use the Attachments section of a reply forum post to attach it.

[cheneymax]

Yes, you are correct! It's a different sub-assembly within the same assembly. It's entirely possible my lack of knowledge in "best practices" is causing the problem here. I have so many different subassemblies nested in other subassemblies at this point. The errors were referring to 2 rigid joints and 2 rigid groups being unable to compute, both of which are in that separate subassembly. 

Model is attached. Thank you for your help!

[jhackney1972 · Accepted solution]

You had the same components crossed between two different sub-assemblies.  You probably are saying, it was the same design why not?  Indeed you should use the same component over again but not the same instance.  Copy and Paste the component to get an identical one and use it in the other assembly.  I did this for the two shaft assemblies, this is why the color went out the window.  Next, why use Pattern on a Path when a much simpler Rectangular Pattern, in one direction will do the trick.  I sort of did this quick and dirty but I hope you get the idea.  You do know you can activate a sub-assembly and copy and paste from another and it will join the active sub-assembly, it really is helpful.  Your model by a different name is attached.

[cheneymax]

First off, thank you so much for taking the time to not only troubleshoot my mistakes but also make an informative screencast as well! 

I am having a bit of difficulty understanding what you mean by "crossing components" or rather what I might have done in order to go that route. Does that mean that I had a copy of a component stacked on the original, but in a different subassembly? 

I am also realizing from the file that you sent back that there are quite a few ways I can go about simplifying my workflow (not making everything into a separate subassembly for instance). I honestly don't know why I used Pattern on Path 🙄!

Again, I truly appreciate you taking the time to help me out! Have a great weekend!

[jhackney1972 · Accepted solution]

---

@cheneymax wrote:

I am having a bit of difficulty understanding what you mean by "crossing components" or rather what I might have done in order to go that route. Does that mean that I had a copy of a component stacked on the original, but in a different subassembly? 

I agree, I did not word my statement very well about crossing components between sub-assemblies.  I hope my new Screencast will clear up what I really wanted to portray.

[cheneymax]

That makes a lot of sense! Thank you again for all of your help!