Reference Talk:UV Mapping

From POV-Wiki
Revision as of 17:15, 16 November 2016 by Jholsenback (talk | contribs) (discussion additions)
Jump to navigation Jump to search
  • Additional uv mapping supported objects.

Supported Objects

Surface mapping is currently defined for the following objects:

  • bicubic_patch : UV coordinates are based on the patch's parametric coordinates. They stretch with the control points. The default range is (0..1) and can be changed.
  • box : the image is wrapped around the box, as shown below.
  • lathe, sor : modified spherical mapping... the u coordinate (0..1) wraps around the y axis, while the v coordinate is linked to the object's control points (also ranging 0..1). Surface of Revolution also has special disc mapping on the end caps if the object is not 'open'.
  • mesh, mesh2 : UV coordinates are defined for each vertex and interpolated between.
  • lemon : cylindrical mapping wrapped around the axis from the base point to the cap point.
  • ovus : spherical mapping centered near the center of mass of the ovus (moving from one sphere to another as the ratio of radius progresses).
  • parametric : In this case the map is not taken from a fixed set of coordinates but the map is taken from the area defined by the boundaries of the uv-space, in which the parametric surface has to be calculated.
  • sphere : boring spherical mapping.
  • torus : The map is taken from the area <0,0><1,1> where the u-coordinate is wrapped around the major radius and the the v-coordinate is wrapped around the minor radius.

lemon's detail

the discs on each side get 0.25 each the spindle part gets 0.5 of the range.

[0 to 0.25 base disc, from center to border] [0.25 to 0.75 spindle from base to apex] [0.75 to 1.0 apex disc, from border (0.75) to center]

You might want to rephrase the above for native speaker.

--Le Forgeron 16:38, 26 September 2016 (UTC)

done supported objects

jholsenback 23:08, 28 September 2016 (UTC)

Supported Objects Updates

Unsure if we should call these bug fixes ... which is my guess since there was a previous implementation(s). Comment and/or note below and I'll update accordingly

jholsenback 17:15, 16 November 2016 (UTC)