========
Textures
========

Texture mapping is the method of applying a 2D image to a 3D geometric surface in order to simulate detail that would not be feasible using geometry alone. Unlike other Visualize settings, textures can be set in two different ways - at the segment level or directly on the geometry. Segment-level texturing will apply the texture to all faces in the segment and subsegments. However, material palettes give you much more control over how the texture is applied, and are the recommended way to apply textures when a segment-level setting is too broad.

A material that is made from a texture makes use of at least one channel. Each channel contains information about the texture which affect the way the texture appears. A normal, unadorned texture uses the diffuse channel.

.. csv-table::
	:header: "Channel name", "Description"
	
	"Diffuse", "The diffuse channel represents the primary color of a surface. For an untextured surface, the diffuse channel might be a solid color. When texturing a surface, the texture image replaces the colors of the diffuse channel. This is the default setting when applying textures in Visualize."
	"Specular", "Texture is applied to the surface of the object as if the texture was a specular highlight"
	"Emission", "Texture is rendered with colors that appear to glow"
	"Transmission", "Using the transmission channel, the texture is converted to grayscale, and its values are used to determine opacity. White values are fully transparent, blacks are fully opaque."
	"Mirror", "A texture channel to be used as the mirror color. The average intensity of the three chanels determines the relative contribution of the environment over the underlying texture."
	"Bump", "The bump channel is used by Visualize to create a surface that appears rough or ridged in order to simulate a higher degree of realism. Bump mapping is described :ref:`here <bump_mapping>`."
	"EnvironmentTexture", "This channel describes a single texture applied to a surface, which appears as a reflection of the surrounding environment."
	"EnvironmentCubeMap", "This channel describes six textures applied to a surface, which appears to be a reflection of the environment. Not as susceptible to distortion as ``EnvironmentTexture``."

**NOTE:** Most GPUs require texture dimensions to be a power of two. If your texture dimensions are not a power of two, HOOPS Visualize will automatically downscale the texture to the nearest power of two. One exception is with very small textures. The smallest texture size is 16x16, therefore, if your texture is smaller than this, it will be upscaled to 16x16.

Texturing a polygon or surface is accomplished in a number of steps:


.. _step1:

Step 1: Acquire the Image
-------------------------

The most convenient way to import images into Visualize is to using the ``HPS::Image::File::Import`` function, although it is possible to use a programmatically-defined or a generated image as texture data. Any byte array will work. Images files are loaded synchronously by Visualize, so if you expect image loading to take a long time, you should use a separate worker thread. The only requirements to specify when loading images are the filename and the image format. Supported 2D image formats are noted :doc:`here </general/supported_file_formats>`. Any problems associated with loading an image will be reported using an ``HPS::Image::IOException``. In this example, an image of a tree is used to texture a quad.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step1]
		   :end-before: //! [texture_step1]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step1]
		   :end-before: //! [texture_step1]

``HPS::Image::File::Import`` returns an ``HPS::ImageKit``. When defining an image in this way, only the image format and filename must be provided. However, when defining images that are loaded without the use of ``HPS::Image::File::Import``, the dimensions, the image format, and the image data itself must be supplied so that the kit can be composed. That operation is described below:

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step1b]
		   :end-before: //! [texture_step1b]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step1b]
		   :end-before: //! [texture_step1b]
		   
		   
Step 2: Define the Image in a Portfolio
---------------------------------------

A portfolio is a collection of data that is accessible to your application. Portfolios are discussed in the :doc:`Portfolios section </prog_guide/0401_portfolios_introduction>`. The topic explained here is no exception - the image imported in the previous step must be defined in a portfolio. Data in a portfolio is accessible to any segment that uses the portfolio (this includes segments that inherit the portfolio from an ancestor). Best practices suggest the image itself should be given a name.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step2]
		   :end-before: //! [texture_step2]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step2]
		   :end-before: //! [texture_step2]
		   
		   
Step 3: Define a Texture From the Image
---------------------------------------

Defining the image as a texture makes it available as a texture map. The texture must be given a name so that it can be referenced later when it gets applied. 

.. admonition:: note

	Note that the image needs to be defined in the same portfolio as the texture.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step3]
		   :end-before: //! [texture_step3]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step3]
		   :end-before: //! [texture_step3]

As a 2D array of pixels, textures can be mapped to a 3D object in many potential ways. The parameterization source defines this mapping. Visualize offers nine types of parameterization that can be used for geometry:

.. csv-table::
	:header: "Parameterization source", "Description"

	"``Cylinder``", "Automatically creates the texture map based on a cylindrical mapping. The Visualize Cylinder primitive cannot be textured, although a cylinder or cylinder-like object formed from a shell would benefit from this mapping."
	"``NaturalUV``", "Stretches the texture along meshes and NURBS surfaces according to their natural internal parameterization. For meshes this is range [0..1]. For NURBS surfaces this is range [0..(control point count - degree)]. Shells do not have a natural parameterization, so the [u,v] coordinates are generated according to the following formula: [u=x+z, v=x+y], where x, y, and z are object space coordinates."
	"``Object``", "The XYZ coordinates of the local geometry. Identical to world space (see below) except that this coordinate system is before modelling matrices are applied."
	"``PhysicalReflection``", "An alternative setting for environment mapping. When set, this calculates the environment coordinates as a reflection between the normal (to the item being textured) and the view vector. The result is that the environment map is not held at a fixed position."
	"``ReflectionVector``", "This is the recommended setting for an environment map. It matches the behavior of OpenGL environment mapping, in that the environment is held at a fixed position along the view vector."
	"``SurfaceNormal``", "The surface normal computed for the local screen pixel."
	"``Sphere``", "Automatically creates the texture map based on a spherical mapping. The Visualize Sphere primitive cannot be textured, although a sphere or sphere-like object formed from a shell would benefit from this mapping."
	"``UV``", "Used for traditional image based texture maps. The parameterization source comes from a user supplied (u,v) coordinate set with the ``SetVertexParameters`` routine. This is the default value."
	"``World``", "A three-valued parameter (XYZ) corresponding to the surface pixel's 3D world coordinate position (the coordinate system of geometry after modelling matrices have been applied, but before projecting through a camera into a window). The Z value is ignored unless there is a texture matrix that has set."


Step 4: Assign the Portfolio to the Segment
-------------------------------------------

The segment must be told to use the portfolio that defines the texture. Note that a segment can only use one portfolio at a time. Portfolios inherit to subsegments just like other attributes.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step4]
		   :end-before: //! [texture_step4]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step4]
		   :end-before: //! [texture_step4]
		   
		   
.. _0404_step5:

Step 5: Set the Vertex Parameters
---------------------------------

This step is important because it determines how the image is applied to the geometry. A mapping must be created between a pixel in the image and the vertices of the geometry that will be textured. ``SetVertexParameters`` assigns a pixel of the image to a vertex and interpolates the image between them. To this end, any texture using UV parameterization is understood to have [u, v] coordinates that correspond to the corners of the image, as shown below:

.. image:: images/texture_coordinates.png

*The vertex coordinates*

Normally, you would assign each corner of the image to a vertex on the geometry, although that does not necessarily have to be the case. It is possible to use a floating point value between 0 and 1 as a vertex coordinate and Visualize will choose the appropriate texel for each pixel.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step5]
		   :end-before: //! [texture_step5]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step5]
		   :end-before: //! [texture_step5]
		   
In the example above, ``vertices_map`` is the mapping between the vertices of the shell and the texture coordinates. After calling ``SetVertexParameters``, Visualize will understand, for example, that the shell vertex 2 will correspond to ``vertices_map[2]`` and thus ultimately corresponds to ``params[4]`` and ``params[5]``. The result is the shell vertex 2 gets a UV coordinate of [1, 1].


Step 6: Apply the Texture to the Geometry
-----------------------------------------

Now that the texture is loaded, and the segment is using the portfolio, all that is left is to tell Visualize to use the texture to color faces. The ``SetFaceTexture`` function sets the texture on all faces in its segment.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [texture_step6]
		   :end-before: //! [texture_step6]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [texture_step6]
		   :end-before: //! [texture_step6]
		   
.. image:: images/textured_quad.png

*The textured quad*

Now that the texture is defined, it can be put into a :ref:`material palette <prog_guide/0501_materials_introduction:Defining material palettes>`, which would give you more options for applying textures. For example, to apply one or more textures to only certain faces of a shell, the texture must be in a material palette.


.. _bump_mapping:

Bump Mapping
============

Bump mapping is a technique that is used to simulate 3D bumps or ridges upon a textured surface in order to make the surface appear more realistic. The actual object is not changed geometrically. A special image called a bump map or height map is used to define the height and location of the bumps. In the bump image, larger color values indicate higher bumps in the composite image. During lighting calculations, Visualize uses the bump map to slightly disturb the surface normals of the object in order to achieve this effect. Since the effect depends on surface normals, lighting must be enabled in order to make bump mapping work.

To use bump mapping, load and define the diffuse texture :ref:`as shown above <step1>`. Then, load and define the bump map as a second texture. When the textures are applied using ``SetFaceTexture``, specify the channel that corresponds to each texture.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_bump_mapping.cpp
		   :start-after: //! [direct_bump]
		   :end-before: //! [direct_bump]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_bump_mapping.cs
		   :start-after: //! [direct_bump]
		   :end-before: //! [direct_bump]
		   
.. image:: images/bump.png

*A diffuse texture (left) combined with a height map (right) creates a bumped texture (center)*

The same effect can be achieved using a :ref:`material palette <prog_guide/0501_materials_introduction:Defining material palettes>`. Likewise, a bump map can also be set in a material kit, as shown below:

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_bump_mapping.cpp
		   :start-after: //! [mka_bump]
		   :end-before: //! [mka_bump]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_bump_mapping.cs
		   :start-after: //! [mka_bump]
		   :end-before: //! [mka_bump]
		   

.. _environment:

Environment Mapping
===================

Environment mapping is a technique that uses a texture to simulate a reflection on a surface. Although some realism is sacrificed, this reflective mapping is much more efficient than traditional ray-tracing in which color is computed using a projected ray. As described in the table at the top of the page, environment mapping uses the ``HPS::Material::Texture::Channel::EnvironmentTexture`` channel.

The following example demonstrates how to setup an environment map:

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_environment_mapping.cpp
		   :start-after: //! [environment]
		   :end-before: //! [environment]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_environment_mapping.cs
		   :start-after: //! [environment]
		   :end-before: //! [environment]
		   
.. image:: images/environment_map.png

*An environment map used on a model of a car*

**NOTE:** Environment mapping uses face normals to generate the appropriate color to apply on each area of the geometry. For this reason, using environment mapping on a surface with few faces does not give a good result because the surface will have only a few normal values.


Decals
======

Visualize supports texture decals. When this setting is used, any transparent portions of the texture show the underlying diffuse color, rather than making the entire material transparent. Visualize expects that the decal image will be mapped to vertex coordinates the same way that a normal texture is.

.. tabs::

	.. group-tab:: C++
	
		.. literalinclude:: ../../../internals/tests/docs/source/cpp/00700_load_texture.cpp
		   :start-after: //! [decal]
		   :end-before: //! [decal]
		   
	.. group-tab:: C#

		.. literalinclude:: ../../../internals/tests/docs/source/cs/00700_load_texture.cs
		   :start-after: //! [decal]
		   :end-before: //! [decal]
		   
.. image:: images/decal.png

*Textures on some quads demonstrating decaled surfaces*

In this image, the first quad is untextured (to show the diffuse color). The middle quad is textured, however, the diffuse color is not visible because ``SetDecal`` has not been called. This causes the face of the polygon to be transparent because Visualize draws the face with a normal, non-decaled texture. The third quad shows a properly decaled surface.
