hexagon logo
Register Sign in
  • State Not Answered
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 46 views
  • Users 0 members are here
Options
Related

Uniform mesh from different parts

giordano.bruno
Good morning,
 
is it possible to create a uniform mesh (without discontinuities) from different parts? I would like to preserve the parts in order to assign easily their properties, once for example I export the bdf to Marc.
 
Thank you
Parents
  • 0
    Due to the way Parts work, meshes in different Parts will always be separate. Are you using surface meshes, or solids? For surface meshes there are a couple of ways you can make them match at Part boundaries:
     
    1. Using mesh seeds. Nodes will be duplicated in the exported bdf and you will need to merge the duplicates in Mentat.
    2. Using Edge Ties. This forces a matching mesh and joins pairs of coincident nodes using a rigid connection. If you have lots of Parts then this is probably the easiest way to create a matching mesh. When exporting the bdf, you have the option of retaining the rigid links, or leaving the meshes unconnected. If you use the second option you will again have to merge the duplicate nodes in Mentat.
    snip15
    Alternatively, if you define properties in Apex then the property regions should be preserved when you move to Mentat and you could modify them as necessary - might that be a simpler approach?
Reply
  • 0
    Due to the way Parts work, meshes in different Parts will always be separate. Are you using surface meshes, or solids? For surface meshes there are a couple of ways you can make them match at Part boundaries:
     
    1. Using mesh seeds. Nodes will be duplicated in the exported bdf and you will need to merge the duplicates in Mentat.
    2. Using Edge Ties. This forces a matching mesh and joins pairs of coincident nodes using a rigid connection. If you have lots of Parts then this is probably the easiest way to create a matching mesh. When exporting the bdf, you have the option of retaining the rigid links, or leaving the meshes unconnected. If you use the second option you will again have to merge the duplicate nodes in Mentat.
    snip15
    Alternatively, if you define properties in Apex then the property regions should be preserved when you move to Mentat and you could modify them as necessary - might that be a simpler approach?
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement