Provides access to members that identify a MultiPatch and permit controlled access to its parts. Note: the IMultiPatch interface has been superseded byIMultiPatch2. Please consider using the more recent version.

Product Availability

Description

A multipatch is a series of three-dimensional surfaces that are represented as groups of geometries.  These geometries may be Triangle Strips, Triangle Fans, or groups of Rings (ring-groups ). In a multipatch there is one triangle strip, or triangle fan per surface, whereas there can be one or more rings per surface. A single multipatch may comprise combinations of triangle strips, triangle fans, and ring groups.

         --------------------- Multipatch ---------------------

         |                                        |                                        |

Triangle Strip                     Triangle Fan                          Rings

 

Triangle strips are a sequence of connected triangles 0,1,2,3,4,...n that each build from their predecessor.

Triangle fans are a sequence of connected triangles that each use the first point in the sequence as an apex 0,1,0,2,0,3,0,4,...,0,n

Triangle strips and triangle fans specify surfaces by themselves.  A ring works contextually with other rings to specify a surface, but it may also be its own surface.

<->

The main difference between the ring and the triangles for a developer is when using

IPointCollection :: GetPoint(index)

 for the multipatch.

If the index points to a point in a (segment of a) ring, you get a reference to a copy of the point, otherwise you get a reference to the point directly.  This means that you can directly modify points in triangles but in order to modify points in a ring, you must use

IPointCollection :: UpdatePoint

Ring Groups

--------------

Rings all have the same structure, but they have a special role when defining a multipatch surface. The roles of rings are determined by the multipatch (they are not a property of the ring itself)

The roles are called:

• Ring (unknown)
• First Ring
• Inner Ring
• Outer Ring

One rule that is not enforced, but that should be followed when creating a ring group, is that all rings in a group are co-planar.  This is an OpenGL 3D graphics standard.

This means, for example, that a closed cube would comprise six ring groups.  Each group would have a single ring.  A hole in one of the sides of the cube would not alter the number of groups. Instead, an additional ring would be added to one of the groups to represent the hole.

<->

Another rule is that there is only one group per outer ring. If, for instance, there was another co-planar ring inside the hole mentioned above, this would be represented as another group.  This is because it is affectively another surface, even though it is coplanar with the side-ring and the hole-ring.

<->

Each group has a ring sequence, and in combination with the role of the rings in the sequence, a surface can be defined.  A multipatch can have a number of surfaces represented by ring groups, the different roles of the rings help to determine the one group from the next, and within each group, determine the structure of the surface.

Following are some examples of using the roles of rings in the ring sequence of a group to define a surface.

---------------------------------------------------------

Multipatch 1 - First Ring designates the start of a ring group. Any subsequent surface other than Ring breaks the sequence.

Triangle strip, triangle fan, ring, ring, ring, first ring, ring

The above sequence is interpreted as five surfaces as follows:

• Surface 1 - triangle strip
• Surface 2 - triangle fan
• Surface 3 - Ring
• Surface 4 - Ring
• Surface 5 - First Ring, Ring

---------------------------------------------------------

Multipatch 2 - Triangle strip, outer ring, inner ring, inner ring, ring, first ring, ring

This sequence is interpreted as four surfaces as follows:

• Surface 1 - triangle strip
• Surface 2 - outer ring, inner ring, inner ring
• Surface 3 - ring
• Surface 4 - first ring, ring

---------------------------------------------------------

Outer ring/Inner ring nomenclature is a more structured form for the surface than First Ring/Ring series. The former  explicitly defines that any subsequent inner is a hole in the ring.  In the sequence "Inner" must always follow "Outer" or "Inner".  It would otherwise be an error.  Anything other than "Inner" would stop the sequence for the Inner/Outer group.

Members

Inherited Interfaces

CoClasses that implement IMultiPatch

.NET Samples

3D multipatch examples (Code Files: CompositeExamples RingGroupExamples) |

.NET Related Topics

How to create a multipatch using a series of triangles |