ShapeDiver: Optimization doubt - Mesh or Brep? (20.0 KB)

In this definition I’ve got a message that suggests me to convert breps and surfaces in mesh, but converting surfaces with mesh surface, after join and weld everything after subdivide is adding a lot of components. Which is better under the computational time point of view: surfaces/breps with less components or meshes with more components?

And in the case I would like to have some breps as a final result because I would like the user will download them so I cannot create meshes from scratch. Is still a good choice to convert breps in surfaces for the visualization in ShapeDiver?


We suggest converting all surfaces and b-reps into meshes as the viewer will anyways convert them internally if they are not meshes. The reason why they get converted into meshes is because it is the format we need to be able to display them in the browser. If you convert them to mesh in GH, then you have control over the quality of your mesh. If you don’t, then our system will convert them into mesh and try to optimize them as much as possible, but you won’t have total control over the quality of your mesh and this process of conversion also adds to the computational time. If possible, try to always build meshes from scratch instead of using b-reps or surfaces and then converting to mesh. Even though building meshes from scratch needs more GH components, maybe some scripting and mathematical calculations, these components are normally more simple and take way less computational time. The more components doesn’t mean always more computational time, it is what each component itself does what matters the most. If you want to know more about the difference between b-reps and meshes, I suggest to read I also suggest reading:

Regarding exporting/downloading of b-reps or surfaces, just plug those geometries in the ShapeDiverExportDownload component but whatever is going to be displayed, convert to mesh. These processes are done separately.

Thanks cool! :slight_smile: