The surface topology to create for the output grid. See the descriptions and image below.

The type of primitive to output if Surface Type is not Points. When this is Automatic, polygons, NURBS surfaces, or Bezier surfaces are output, depending on whether the cross sections are polygons, NURBS curves, or Bezier curves.

If Surface Type is Rows, Columns, or Rows and Columns, and Close Implicit Backbone Curve is enabled or cross sections are all closed, this option will add an extra vertex as needed to each curve to ensure that there are separate vertices for parametric curve u or v coordinate values 0 and 1. If any output primitives are polygon soups, NURBS surfaces, Bezier surfaces, or bilinear mesh primitives, this option similarly also adds any extra vertices that would be needed to ensure that all uv seams can be generated correctly. See the image below.

When enabled, the order of the points and primitives in the grids will be adjusted to be column-major, having all points/primitives of one column before those of the next column, instead of the default row-major, having all point/primitives of one row before those of the next row. Toggling this also reverses normals, so Reverse Cross Sections may be useful to separately reverse normals.

When this toggle is enabled, the implicit curve between the cross sections is considered to be closed, treating the cross sections as forming a loop, instead of a line. See the image below for an example.

When enabled, a vertex uv attribute will be generated for the output surface, based on the parameters below. U corresponds with the cross section parametric coordinate, and V corresponds with the parametric coordinate between the cross sections. When Surface Type is Points, this will be a point uv attribute.

When enabled, a vertex uv attribute will be generated from scratch for the output surface, based on the parameters below, even if one is already on the input, instead of copying U from the input.

When enabled, the individual U and V coordinate distances will be scaled, relative to other edges, by the corresponding edge lengths. When Normalize Computed Us and Normalize Computed Vs are on, U and V coordinates will still be scaled to be within the 0 to 1 range, but the relative lengths in UV space will be proportional to their lengths in physical space. See the image below.

When enabled, the U coordinate will be scaled to go from 0 to 1, (before UV Scale is applied). Otherwise, U will correspond with the average distance around the cross sections on the mesh, ignoring any stretch applied by Stretch Around Turns. Either way, U can be scaled by the first component of UV Scale. When this is enabled and Normalize Computed Vs is disabled, V will be scaled such that U and V appear scaled similarly in space, though depending on the Use Max Cross Section Length for Proportional Scale option. This is especially useful for things like applying repeating rope textures, where the texture should be applied isotropically. See the image below.

When enabled, the V coordinate will be scaled to go from 0 to 1, (before UV Scale is applied). Otherwise, V will correspond with the average distance along the mesh in the V direction. When this is enabled and Normalize Computed Us is disabled, U will be scaled such that U and V appear scaled similarly in space. See the image below.

When Normalize Computed Us is disabled and this is enabled, the range of U is rounded to the nearest positive integer, in order for textures to wrap correctly in the U direction. This rounding is applied after the corresponding component of UV Scale is applied, so that UV Scale can still be approximately a scale per length unit for small geometry when both Normalize Computed Us and Normalize Computed Vs are both disabled. See the image below.

When Normalize Computed Vs is disabled and this is enabled, the range of V is rounded to the nearest positive integer, in order for textures to wrap correctly in the V direction. This rounding is applied after the corresponding component of UV Scale is applied, so that UV Scale can still be approximately a scale per length unit for small geometry when both Normalize Computed Us and Normalize Computed Vs are both disabled. See the image below.

When Normalize Computed Us is enabled and Normalize Computed Vs is disabled, this controls whether the maximum cross section length will be used for computing the V scale, instead of the average of the previous and next cross section lengths for each V edge. If the cross section length varies significantly, this can result in the texture appearing stretched in some places, but can also avoid instability and inconsistency in the V scale. See the image below.

When this is enabled, any computed U values will be replaced with maxu-u, (e.g. 1-u if Normalize U is enabled and UV Scale has 1 for the first component), to avoid textures appearing backward. This should be on for textures to appear correct on surfaces viewed from the front, (i.e. normals pointing toward the camera), and should be off for textures to appear correct on surfaces viewed from the back, (i.e. normals pointing away from the camera). See the image below.

An additional scale on the generated UV coordinates. When Normalize U or Normalize V is on, the corresponding scale is applied after normalization. Otherwise, this scale is a scale per length unit, e.g. 0.5 would correspond with a period of 2 length units. If Make Computed Us Wrap Seamlessly or Make Computed Vs Wrap Seamlessly is enabled, the corresponding scale is applied before rounding to a positive integer number of repetitions of the U or V space, so that textures will still wrap correctly.

Attributes to copy from cross sections to the output grids. Any attributes that have an applicable transform type, (position, vector, normal, quaternion, or transform matrix), will be transformed appropriately by the transform of each vertex.

When enabled, an integer point attribute with the specified name will be added to the output, containing the number of the point row within each grid.

When enabled, an integer point attribute with the specified name will be added to the output, containing the number of the point column within each grid.

When enabled, an integer primitive attribute with the specified name will be added to the output, containing the number of the quad row within each grid.

When enabled, an integer primitive attribute with the specified name will be added to the output, containing the number of the quad column within each grid.

When enabled, an integer point attribute with the specified name will be added to the output, containing the primitive number of the input cross section corresponding with each point.