search

cutdigital / mcut

A library for detecting and resolving intersections between two surface meshes.
https://cutdigital.github.io/mcut.site
Other
395 stars 69 forks source link

TextureCoordinates instance running abnormally in MCUT V1.2.0. #37

Closed xueyuanhong closed 7 months ago

xueyuanhong commented 9 months ago

TextureCoordinates instance running abnormally in MCUT V1.2.0. TextureCoordinates instance can run normally in MCUT V1.1.0.

chitalu commented 9 months ago

Hi @xueyuanhong,

Do you have an example image?

xueyuanhong commented 9 months ago

Screenshot of running results(TextureCoordinates instance running abnormally in MCUT V1.2.0)： TextureCoordinates

xueyuanhong commented 9 months ago

Screenshot of running results(TextureCoordinates instance can run normally in MCUT V1.1.0)：

TextureCoordinatesV1 1_1 TextureCoordinatesV1 1_2 TextureCoordinatesV1 1_3

chitalu commented 9 months ago

Hi @xueyuanhong

Is your problem simply that 1) the output being shown in the terminal/console is different between V1.2.0 and V1.1.0, or 2) that the texture coordinates that are propagated from the input meshes and onto the output connected components (computed by MCUT) are incorrect?

xueyuanhong commented 9 months ago

My problem is simply that1) the output being shown in the terminal/console is different between V1.2.0 and V1.1.0 . What causes TextureCoordinates of MCUT V1.2.0 to not run properly ?

chitalu commented 7 months ago

This issue is now resolved on latest version (1.3.0).