As per the original post.
Why is this the workflow instead of just copying the pattern itself? Seems very extra. I'm glad you've mentioned this simplification, however. If you follow PTC's intent in Article - CS297897 it instructs an extra pattern required if you use Publish Geometry instead of just grabbing the original feature like you have.
Solved! Go to Solution.
If you are asking why to use the method I detailed above versus the method from the article you note, then my answer is to use the one which best capture the design intent. In some cases, you could use both methods to get the same geometry. In general, I would use a reference pattern before a pattern of a pattern. This is due to model stability and regeneration time.
I have never patterned a copy geometry that I can recall. I do often use reference patterns in top down design schemes and the method I detailed above is the only way I am aware of to use the reference pattern functionality in a derivative model of a parent where the pattern is defined.
If you are asking why to use the method I detailed above versus the method from the article you note, then my answer is to use the one which best capture the design intent. In some cases, you could use both methods to get the same geometry. In general, I would use a reference pattern before a pattern of a pattern. This is due to model stability and regeneration time.
I have never patterned a copy geometry that I can recall. I do often use reference patterns in top down design schemes and the method I detailed above is the only way I am aware of to use the reference pattern functionality in a derivative model of a parent where the pattern is defined.