Distorted Android

      + "float denomV = 1.0 / (aForce.y + Aw.x);                             \n"

      + "float denomH = 1.0 / (aForce.x + Aw.y);                             \n"

      + "float mvXvert = -B * ps.x * aForce.y * (1.0-quot.y) * denomV;       \n"  // impact the vertical   component of the force vector has on horizontal movement

      + "float mvYhorz = -B * ps.y * aForce.x * (1.0-quot.x) * denomH;       \n"  // impact the horizontal component of the force vector has on vertical   movement

 *

 * @y.exclude

 */

     {

     if( mJobNode[0]!=null )

       {

         sb.append(") ");

         }

       }

     }

       sb.append(mVertAttribs1[VERT1_ATTRIBS*i+POS_ATTRIB+1]);

       sb.append(',');

       sb.append(mVertAttribs1[VERT1_ATTRIBS*i+POS_ATTRIB+2]);

       }

     }

///////////////////////////////////////////////////////////////////////////////////////////////////

       sb.append(' ');

       }

     }

///////////////////////////////////////////////////////////////////////////////////////////////////

         }

       }

     }

///////////////////////////////////////////////////////////////////////////////////////////////////

 * <p>

 * This is a static, permanent modification of the vertices contained in this Mesh. If the effects

 * contain any Dynamics, the Dynamics will be evaluated at 0.

 * We would call this several times building up a list of Effects to do. This list of effects gets

 * lazily executed only when the Mesh is used for rendering for the first time.

 *

 * maps[1] = the map for the 2nd component

 * maps[2] = null

 * maps[3] = the map for the 4th component

 * A map's width and height have to be non-zero (but can be negative!)

 *

 * @param maps            List of texture maps to apply to the texture's components.

///////////////////////////////////////////////////////////////////////////////////////////////////

/**

 * Set Effect association.

 * This creates an association between a Component of this Mesh and a Vertex Effect.

 * One can set two types of associations - an 'logical and' and a 'equal' associations and the Effect

 * will only be active on vertices of Components such that

 * (effect andAssoc) & (component andAssoc) != 0 || (effect equAssoc) == (mesh equAssoc)

 * (see main_vertex_shader)

 * The point: this way we can configure the system so that each Vertex Effect acts only on a certain

 * subset of a Mesh, thus potentially significantly reducing the number of render calls.

 */

///////////////////////////////////////////////////////////////////////////////////////////////////

/**

 * Set center of a Component.

 * A 'center' of a (effect) component is a 3D point in space. The array of centers gets sent to

 * the vertex shader as a Uniform Buffer Object; in the vertex shader we can then use it to compute

 * the 'Inflation' of the whole Mesh per-component. 'Inflation' is needed by postprocess effects to

 * add the 'halo' around an object.

 * This is all 'per-component' so that a user has a chance to make the halo look right in case of

 * non-convex meshes: then we need to ensure that each component of such a mesh is a convex

 * sub-mesh with its center being more-or-less the center of gravity of the sub-mesh.

///////////////////////////////////////////////////////////////////////////////////////////////////

/**

 * Adds an empty (no vertices) texture component to the end of the text component list.

 * Sometimes we want to do this to have several Meshes with equal number of tex components each.

 */

   public void addEmptyTexComponent()