I watched the video capture and also looked at your file, thanks for providing these. I think I’m still confused about the question though. If I make a smooth shaded version of your model and then ExtractRenderMesh, I get the mesh with 10686 polys. Is this not what you wanted? Can you explain more about whether this is a problem for you in the render or analysis mesh or if you expected the 9996 poly count? Sorry I’m missing the question. If you want to ask this question in Korean, I can bring in one of our support people from Seoul too.
Yes, the settings for smooth and slower render mesh changed from Rhino 4 to Rhino 5 which now produces about half as many polys in this case. I don’t know if the change causing this is due to a value difference in the render mesh settings or a larger change deeper in Rhino’s render mesh calculation. Is there a problem you are trying to solve or avoid? I can try and dig deeper to find out the mesh parameters used in this default if that’s all you wanted to know. You may find QuadrangulateMesh and ReduceMesh useful as well.
Hi Knead, Just so you know, I am not trying to be rude to you, I am just having fun since it all became so abstract. With animated icons that doesn’t make sense in my culture, and with Korean too.
I ran your Korean through Google translate, and it made no sense at all to me. Google isn’t good enough yet.
I absolutely agree that this Newsgroup is better than the previous web newsgroup. (I still miss the NNTP version though) I was just making a joke because the old NG could not show strange animated gifs.
ahh… yes… slippery mind is one of my strong sides…
And I have to say that I really miss the efficiency of using a propper newsreader. This NG works ok, but I spend far less time on it. (Which I am sure McNeel is happy about ;))