Border problems

[matfrem]

I use this to fox some ground meshes and I need to keep borders clean. So I changed this:

// Border check
//if (v0.border != v1.border) continue; <= old version, destroys borders
if (v0.border || v1.border) continue; <== my version, keeps border vertices

Hope this helps.

[Zylann]

Are you using this to keep terrain chunk border vertices intact? I'm considering this library for that purpose, but I'd like to be able to configure it so that specific vertices (on the borders) don't get touched.

[matfrem]

yes, it works. with the modification i've told.

…

On Sat, Apr 27, 2019 at 1:42 AM Marc ***@***.***> wrote: Are you using this to keep terrain chunk border vertices intact? I'm considering this library for that purpose, but I'd like to be able to configure it so that specific vertices (on the borders) don't get touched. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACEZ6E2NMKLNFEM5M7FAAX3PSOHP5ANCNFSM4HGBQDNQ> .

[Error1000]

This also resolves an issue where it would leave gaps in meshes that have duplicate triangles that have the same position data but different texture coordinate data or other data.

[neurolabusc]

I believe this issue actually the same as issue 24. I believe this is resolved with a recent pull request which initializes borders before the first error metric calculations. Therefore, I am closing this issue. If you feel this does not address this issue, can you re-open the issue and provide an example mesh that demonstrates the problem.