Search the Community
Showing results for tags 'lofted'.
The search index is currently processing. Current results may not be complete.
Found 2 results
Hi, This is a post in the context of project performance: If you use loops with feature definitions, take care where you declare ("create") your participating objects: Most of the times, objects can be declared outside of the loop since the dependency is kept within the loop by means of the expression mechanism! In the attached example, I create N curves in between of two given rail curves and store them in a list for surface creation. The two points on the corresponding rails are declared right before the loop starts. You could also declare them within the loop but - and here comes the message - they would be created again and again, i.e. at each iteration (N-times). In the end, this might slow down your feature execution when it comes to a higher number of objects that get declared within a loop. Hope this helps ... Cheers Joerg loop.fdb
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