NGonulate crash

Hi,

NGonulate crashes on a large imported mesh.
No McNeel error report comes up.
I could upload the mesh here, but zipped it is 8MB.

What to do, where to send to?

-C-H-A-R-L-E-S-

Hi Charles - please upload large files here: http://www.rhino3d.com/upload , include ‘Att’n: Pascal’ in the comment, and I’ll get it.

thanks,

-Pascal

Hi Charles - thanks, I got the file - NGonulation worked here - instantly in fact, no crash. I’m not sure what to suggest except, possibly, try again with the (delayed, I know) next WIP. I sent you back a link to the Rhino file.
Do you get the crash on every attempt?

-Pascal

Hi Pascal,

the crash comes up on every attempt and immediately.
I’ll just wait for the next WIP and come back to this then.

Thanks,
-C-H-A-R-L-E-S-

Hello Pascal,

your file is more than the double size than mine.

In the original, it is a very dense mesh, ngonulated it is leightweight.
What is the reason the file becomes so large?

Thanks,
-C-H-A-R-L-E-S-

Hi Charles - good question - NGons do not remove any vertices from the mesh, as far as I know, they only pretend to in order to simplify the display. So, I guess some extra data might be expected from nGons, but it does seem that double is a lot. I’ll see what I can find out.

-Pascal

Hi Pascal,

Interesting.
When the ngonulated mesh gets exploded, then the vertices are all there again.

-C-H-A-R-L-E-S-

Hi Charles - I’ll check with Dale, but my guess of the moment is that NGonulating on this mesh creates a large number of small NGons, not just the obvious ones at the back and the obvious planar parts, and each of these needs to be kept track of - what vertices are in each nGon and so on , adding data to the file - some are just a few vertices, so there are really a lot.

-Pascal

Hi Pascal,

with the new WIP there is no crash anymore.

-C-H-A-R-L-E-S-