i just noticed that on some models it is nearly impossible to achieve a smooth result without introducing extra ridges, by coincidence i noticed that it seems to be using the display mesh as a basis which is often pretty low res.
why does it not just create a new mesh from the nurbs for this process?
@Trav any idea?
This is the way many commands work that depend on mesh input and are given nurbs. If the goal is very exact meshing I would mesh the model and then provide it to the command, or, increase the display mesh settings.
in that case it would make sense to implement the mesh settings into the command, like we have in emap or zebra.
i am pretty sure people are not aware of that, i am a long term user (maybe not the best) and i also had no clue and had to find out accidentally. in this topic nobody new how to fix that issue, when i tried there with a better input rendermesh it worked much better.
