Parasolid file too large when exported

Rhino
1

Hello! When I try to export a polysurface into a .x_t file, I get a very large file which I am unable to use because of its size. Any way that I can reduce the file size?

I have attached here the Rhino file with a mesh that I want to subtract from the beam to get a solid. I had used the MeshtoNURB function to convert the mesh to a polysurface and then used Nonmanifoldmerge/CreateRegions to obtain the difference between the two polysurfaces but the file obtained is too large.

2_session.3dm (3.3 MB)

Thank you in advance!

1 Like
2

Hi Loveni,

Converting the mesh directly to nurbs resulted in each mesh triangle converted to a nurbs patch. This is rarely useful with meshes with a lot of faces. Your mesh has about 80,000 faces

Using the Rhino7 workflow quadremesh > subd > nurbs will result in significantly fewer surfaces in generating the nurbs object. However there will be some unavoidable variation from the mesh.

I’m doing the quadrememesh > subd step now, but its very slow with this mesh. In my experience it typically does not take this long. The mesh is good, so that’s not the issue, perhaps is the complex topology.

1 Like
3

This reminds me, how is it Rhino can deal with parasolid format, but not actually implement parasolid tools … :thinking:

This mesh might be one of those 45min long calculations, more or less, depending on computer power:

image
image1920Ă—1080 220 KB

I gave it about 10 min and had to abort. I might try again later and do a longer cycle.

1 Like
4

Hello- is a mesh not usabler output for your purposes?

-Pascal

1 Like
6

It finished converting but unfortunately I think it’s not going to help you.

There is a larger deviation from your mesh to the nurbs than I anticipated, and the X_T file is about 100Mb. Even with zipping it it is too large to post here.

I used the “Interpolate Subd” option which should have eliminated some volume shrinking.

I saved an STL mesh from the subd nurbs that will show you how the surface changed.
2_session mesh from subd nurbs STL.zip (9.2 MB)

1 Like
7

Thanks for your help. When I tried doing quadmesh > subd > nurbs, I obtain an open polysurface; do you know why this is the case?

What would you suggest trying in this case to obtain a smaller file size?

Thanks!

1 Like
8

I don’t think its possible to get a smaller nurbs object with this topology without altering the volume and faithfulness to your original mesh surface to a greater degree.

If you PM me your email address I can send you a DropBox link to the X_T file and Rhino file that I saved. It is a closed polysurface.

2 Likes
9

I have done the NonManifoldMerge operation before CreateRegions to get the difference between the beam and polysurface. However, when I try to share the nodes (shared topology) in ANSYS, it fails; any idea why that might be? Can I send you the Rhino file with the two .x_t files created if that can help?