Thanks @Anders,
I was forgetting about this way with NodeInCode. I’ll still work on exposing the remeshing methods directly too, as I think there are some options in there that didn’t make sense to have on the component, but might be useful in a script, such as separating the different topology update steps from the vertex smoothing and projection steps.
@mdesign
For your point 1. - yes curves set as features should always be preserved. Just set Sharp=True.
About point 2. - Combining this remeshing with isosurfacing is something I am looking at for future versions. You can currently use some other isosurfacing tool such as Dendro and pass the result to TriRemesh, but I think combining these steps into one script could potentially make it faster, as the remeshing could pull to the distance field directly.
@eghbalpourf - There’s no need to include the naked vertices as feature inputs - boundaries of open meshes are always treated as features.
To make curves on a flat surface features, the input mesh needs edges on these curves
triremesh_internalcurve.gh (7.3 KB)
This and the issue of inserting internal vertices is also covered in this other reply further up this thread.