Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I voted for this. One very important reason why this would be an important tool to have is that if the pattern uses a parameter for the number of bodies, you can't simply use a boolean operation on the resulting bodies and expect it to work, because the number of bodies can change. (Depending on your model, you may be able to do an extrude or revolve that joins the bodies by passing through them, but that's an ugly hack, if you ask me.) I usually try to work around this by patterning features, but there are cases where this doesn't work either or it's far more elegant to pattern bodies that are then instantly all joined together.
For bonus points, also support intersecting patterned bodies. Less useful, but you can make some cool objects by making a circular pattern or patterning objects over a path and then intersecting them.
This is huge for parameter driven models. The workaround right now (as @jmunkki5ZDPV said above) is to create redundant geometry that "captures" the child bodies of a pattern or array. Even this is flaky, as the feature will often throw a warning or fail to unite all the bodies in large complex models.
Please make this a priority for the next feature sprint team Fusion!
This would be really great. I'm working with a model right now that uses parateres for the number of elements, but I have to go back though the history and re-select the pattern elements manually, and it takes a long time to recompute. I expect that an option in the pattern dialog to automatically join would allow for significant optimization internally to drastically speed up this kind of computation.
