Search the Community
Showing results for tags 'match'.
The search index is currently processing. Current results may not be complete.
Found 2 results
Hi together, With version 3.1, you have the additional skinning option for meta surfaces. This allows you to have a low number of generating cross sections (curves in surface direction) while matching given boundary curves, also called rails. See the attachment for a simple example. In former versions, one solution to approximately match such boundaries has been to increase the number of cross sections - which is expensive and increases the data of the resulting NURBS surface. Here, this new skinning method is a good alternative to the existing auto-cubic point interpolation. Finally, when it comes to the new BRep type that also comes with version 3.1, it is even recommended to exactly match boundaries for further processing such as Boolean Operations and fillet modeling. Cheers Joerg metasurface_skinning.fdb
Hi together, For general sweep surfaces, we provide the type FSweepSurface but also the transformation FSweepTransformation, which is more powerful: With this transformation, you can control the shape of the swept surface (=>meta surface) along the path with your own functions for each profile parameter. If you want to use this transformation and you need to match a start and end profile, then please find attached an example where two sweep transformations are merged in a single meta surface. We simply fade from one definition into the other one by using two curve engines in a single meta surface. The attached project still contains the intial setup, from which a feature definition was created (from selection) - in order to encapsulate the two sweeping profiles. Just set the scope "01_..." to visible if you like to have a look at it. Cheers Joerg SweepTransformation.fdb