GC reports nonmanifold mesh when mesh is just not oriented consistently
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- cpp
- Área
- computer-graphics
Línea de trabajo
Start by locating the GC validation that reports a mesh as nonmanifold and reproduce the case where the mesh is manifold but faces are inconsistently oriented. Decide whether the intended scope is revised error text, explicit orientation detection, or an orientFaces() method; done means the selected behavior distinguishes or resolves this case without misreporting it.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
GC will report that a mesh is nonmanifold even in cases where it is manifold, but the faces are not consistently aligned.
Level 1 fix
A quick improvement would just be to change error reporting to something like:
Mesh is either nonmanifold, or faces are not oriented consistently.
Level 2 fix
A bigger fix would be to detect that faces are inconsistently oriented, and report this explicitly:
Mesh is manifold, but faces are not consistently oriented.
Level 3 fix
The ultimate fix would be to actually fix the normal orientation, if the mesh is manifold and orientable. There are some design decisions here (e.g., which of the two orientations should we pick?) but generally this should be pretty straightforward.
We could also implement this as a general-purpose method like orientFaces(), which is probably useful in its own right. Then the user can be asked to call this method explicitly:
Mesh is manifold, but faces are not consistently oriented. Please call orientFaces() before trying to build a ManifoldSurfaceMesh.
This may be better than automatically orienting someone's faces, which might violate the principle of least surprise.
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 183
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nmwsharp/geometry-central
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
nmwsharp/geometry-central#256 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
nmwsharp/geometry-central#255 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
nmwsharp/geometry-central#253 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
nmwsharp/geometry-central#247 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
nmwsharp/geometry-central#246 ·
Todos los issues de nmwsharp/geometry-central
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
ros2/message_filters#338 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
subsurface/subsurface#4984 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
litertlm-android AAR ships no consumer ProGuard rules → "mid == null" SIGABRT in minified apps Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
google-ai-edge/LiteRT-LM#3739 ·