Jump to content

Search the Community

Showing results for tags 'surface'.

The search index is currently processing. Current results may not be complete.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


    • General Modeling
    • Software Connections
    • Variation & Optimization
    • Post-Processing
    • Feature Programming
    • Installation
    • Miscellaneous
    • Ideas and Suggestions
    • FAQ


  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media


  • Mr. Arne Bergmann's Blog
  • Mr. Arne Bergmann's Blog
  • Rel 3.1
  • Joerg Palluch's Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 10 results

  1. Dear all, I'm having some issues trimming the Brep or Surface either with curves, surfaces or Breps. My intention is to parametrize the end of the Brep or Surface in order to end at the transom (x=0) of the hull, while at the same it follows the step. I manage only to trim the surface (04_UpperSectionSurface) first on the principal plane (X=0) first and then trim the Brep (06_Step|Upper_Section_Brep) on the step geometry, however this ends with some discrepancies on the final Brep, due to the initial trimming of the 04_UpperSectionSurface. I'm attaching a few screenshots of the area, while also the model. Could you please advise upon the matter? Thanks a lot. Best regards, George TestSWAN_v2.cdbc
  2. Hi, In my project, I create curves, then revolve the curves to create surface geometry. Next, I use surface groups to group all surfaces together. My question is: how do I create solid geometry from surface geometry to simulate in Star CCM++? curve_body_AUV.cdbc
  3. Hi together, The software CAESES is a CAD and optimization platform. For students and PhD students there are free non-commercial licenses available. In addition, there are low-price offers for start-ups and smaller companies. CAESES can be used for 2D and 3D parametric modeling, see this link for some information about its CAD capabilities. Here are some screenshots: Compared to traditional CAD systems, CAESES is a bit different. It comes with a strict object-oriented approach, i.e. the user sets up dependencies between objects and these dependencies are then kept. This makes it easy to automate the geometry generation process. Here are some features of CAESES: Full 2D and 3D modeling capabilities (NURBS-based)Roughly 20 curve types and 15 surface typesStandard transformations (translation, rotation, scaling)Writing of custom features and functionsBoolean operationsTrimmingFillets between surfacesMorphing functionality for deformation of existing geometrySurface tessellation control through e.g. trimesh objects to create and fine-tune custom STL dataCommon import and export formats e.g. IGES, STEP, PARASOLID, STLIndustry-specific modules for blade and ship designBatch mode for non-GUI (hidden) geometry generation in the background Cheers Joerg LAST UPDATE: NOV 2017
  4. 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
  5. Hey, If you have been to our Users Meeting 2013 in Berlin in the mid of October you have seen my presentation: Intersecting surface in parametric models: Subsurface modeling. The presentation will be available on our website within the next days. http://www.friendship-systems.com/downloads/presentations This is the live demo project file. It is sorted with multiple numbered scopes. This sorting is helping you to understand the order of creation and makes it easier to reuse it in your own projects. Subsurface: It is the trimming/cutting functionality in CAESES-FFW.Creates a new surface on the basis of an existing parent surface.CAESES-FFW provides some Feature Definitions which will help you creating subsurfaces. Here you can find them: Menu -> Features -> Surfaces -> subsurface or in the CAD Menu next to the object Sub Surface If you have any questions to subsurface modeling please don't hesitate to post them here or contact me. Best regards Karsten UM2013_SubsurfaceModeling.fdb
  6. The easiest way to flip the normal of a given surface is by reversing one of the surface directions u or v. In a NURBS/B-Spline surface this can be done with the command .reverse(1,0) or .reverse(0,1). In a Metasurface you can reverse start and end position or you create an image surface and in the u or v domain you enter [1,0] instead of [0,1].
  7. 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
  8. Just a little but helpful thing: In order to get the type documentation of an object in your project (such as points, curves, surfaces), click on the icon in the object editor: This opens up the documentation browser and shows information about the type. Quick and easy... Cheers Joerg
  9. 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
  10. Hi All, Please try out this parametric CAESES model of a volute for a blower. The basic shape is controlled by a function (red) to control the offset of the outer shape from the inner circle. If you switch off the visibility of the trimesh (named volute, click on its icon in the object tree) you can see the surface topology behind it. If you are a bit experienced, such a model is set up in 15 min from scratch. Have fun!volute1.fdb
  • Create New...