|
| enum | MultipleEdgesResolveMode : int { None = 0
, Simple = 1
, Strong = 2
} |
| | If Strong makes additional efforts to avoid creating multiple edges, in some rare cases it is not possible (cases with extremely bad topology), if you faced one try to use MR.duplicateMultiHoleVertices before MR.fillHole If Simple avoid creating edges that already exist in topology (default) If None do not avoid multiple edges.
|
| |
|
|
virtual unsafe void | Dispose (bool disposing) |
| |
◆ makeDegenerateBand
| unsafe bool MR.Const_FillHoleParams.makeDegenerateBand |
|
get |
If true creates degenerate faces band around hole to have sharp angle visualization
- Warning
- This flag bad for result topology, most likely you do not need it
◆ maxPolygonSubdivisions
| unsafe int MR.Const_FillHoleParams.maxPolygonSubdivisions |
|
get |
The maximum number of polygon subdivisions on a triangle and two smaller polygons, must be 2 or larger
◆ metric
◆ smoothBd
| unsafe bool MR.Const_FillHoleParams.smoothBd |
|
get |
If true, hole filling will minimize the sum of metrics including boundary edges, where one triangle was present before hole filling, and another is added during hole filling. This makes boundary edges same smooth as inner edges of the patch. If false, edge metric will not be applied to boundary edges, and the patch tends to make a sharper turn there.
◆ stopBeforeBadTriangulation
| unsafe MR.Misc.? Box<byte> MR.Const_FillHoleParams.stopBeforeBadTriangulation |
|
get |
Input/output value, if it is present: returns true if triangulation was bad and do not actually fill hole, if triangulation is ok returns false; if it is not present fill hole trivially in case of bad triangulation, (or leaves bad triangulation, depending on metric)
The documentation for this class was generated from the following file: